After last update: Cannot open iommu_group: No such file or directory

After doing this 'proxmox-boot-tool kernel pin 6.8.12-2-pve`. Is there anything to do when a new version comes out?
Do I need to remove or modify this line when the new kernel is fixed or upgraded? If so I am not sure where( What file) or how to remove this to get back to the newer kernel.
Appreciate any step by step instructions.
Thanks
 
  • Like
Reactions: Stoiko Ivanov
Also present on Intel i7-6770HQ.

Code:
cat /etc/default/grub

[...]
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on"
GRUB_CMDLINE_LINUX=""
[...]

Code:
pvesh get /nodes/prox1/hardware/pci --pci-class-blacklist ""

[...]
0x030000 │ 0x193b │ 0000:00:02.0 │          0 │ 0x8086 │ Iris Pro Graphics 580
[...]

`proxmox-boot-tool kernel pin 6.8.12-3-pve` works to re-enable.
Is it safe to update the rest of the packages after rolling back and pinning the older kernel?
yes seems like it
 
Changelog of 6.8.12-5:
Code:
proxmox-kernel-6.8 (6.8.12-5) bookworm; urgency=medium

  * revert Ubuntu patch disabling IOMMU functionality for Skylake iGPU

  * update sources to Ubuntu-6.8.0-51.52
Can anyone confirm the kernel as updated restores IOMMU for all these Intel graphics sets impacted here, not just "Skylake"? Mine is the Haswell processor variant, but maybe these are all treated as the same here?
 
See the patch for the full details:
https://lore.proxmox.com/pve-devel/20241126163636.825951-3-s.ivanov@proxmox.com/

`lspci -nnk` should provide the PCI-id of your GPU

I hope this helps!
So I see this when running that command, and find the "1912" variant in your patch details, so should work?

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06)
Subsystem: Dell HD Graphics 530 [1028:06ba]
Kernel driver in use: vfio-pci
Kernel modules: i915
 
So I see this when running that command, and find the "1912" variant in your patch details, so should work?

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06)
I would assume so - yes - but I'd also suggest that you just try it out - if it worked before and was now broken, then chances are this patch might help.
If it never worked then the reason might be something else entirely (in which case looking through your journal after a boot and potentially opening a new thread, if you don't find the reason might help)
 
I am fairly new to this - did not patch the newer kernel but am for now having previous version pinned at boot - can you confirm this patch will be included in upcoming larger system update? Thanks!
 
Hi,
I am fairly new to this - did not patch the newer kernel but am for now having previous version pinned at boot - can you confirm this patch will be included in upcoming larger system update? Thanks!
you do not need to patch the newer kernel yourself. The patch is already included in 6.8.12-5 as was already mentioned in this thread.