Correct GRUB flags for PVE Install and code 43 related? #277
Comments
|
This line: is actually backwards - it forces using I was having issues getting i915 to load, even when explicitly told with |
|
Thanks for the clarification. My setup works and I got the MOK key enrolled for the module. So that message means nothing for me, right? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My system is based on an Intel 12900HK and an Intel Iris Xe 96EU.
I managed to install the DKMS module somewhat successfully on the system but I'm getting this message:
[0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.12-7-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on iommu=pt i915.enable_guc=3 i915.max_vfs=7[0.083357] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.8.12-7-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on iommu=pt i915.enable_guc=3 i915.max_vfs=7 use xe.force_probe='46a6' and i915.force_probe='!46a6'I've also noticed in the guide that it says to blacklist the xe module.
Now I'm confused on what I should do: should I blacklist the xe module or, as far as I understood, use
i915.force_probe='!46a6'to force the use of the i915 module?Could it be that me not using the correct GRUB flags is giving me issues in a Windows VM? I have a display dummy in the HDMI port and this way I can RDP in the system without a display configured. But trying to use Sunshine gets me a code 43 error and trying to connect to the machine through Parsec before using RDP gives me the same code 43 error.
Having no dummy or display connected to the HDMI doesn't allow me to RDP to the machine without a virtual display set up in Proxmox.
The text was updated successfully, but these errors were encountered: