I use Fedora in my Gaming PC wich is in exclusive configuration :
Virtual diplay with custom Edid in grub.cfg (GRUB_CMDLINE_LINUX video drm.edid_firmware)
Sushine for moonlight
module Xone (for xbox gamepad) signed for secure boot
Since yesterday, i cannot boot on Fedora.
Can you help me with any step i have to repaire my installation.
The PC steel working great with the last Kernel 8.17.10.300 ! (but is anoying because i have to connect à display to use grub and chose the none default kernel)
In journalctl i found this error “Could not load the Qt platform plugin “xcb” in “” even though it was found.” and it repeat and repeat and never boot.
My mistakes :
I used a custom Edid in /usr/lib/firmware/edid/ but i forgot to add it to initramfs with dracut ! But it was not probleme with the last kernel, and until i saw this error i add configuration in /etc/dractu/custom/custom.cfg and apply dracut --regenerate-all --force
is steel working with last kernel
List all installed kernels
--------------------------
To get the index number of all the installed kernels:
sudo grubby --info=ALL | grep -E "^kernel|^index"
The output should be something like this:
index=0
kernel="/boot/vmlinuz-6.11.11-200.fc40.x86_64"
index=1
kernel="/boot/vmlinuz-6.11.10-200.fc40.x86_64"
index=2
kernel="/boot/vmlinuz-6.11.8-200.fc40.x86_64"
index=3
kernel="/boot/vmlinuz-0-rescue-6a0d0e8a953c43e682bd4f1a6e0143be"
Change the default kernel using index
-------------------------------------
Now we can change the default kernel by using the index number:
sudo grubby --set-default-index=1
Verify the default kernel
-------------------------
Verify that the right kernel has been set as default:
sudo grubby --default-title
The output will be the default kernel title:
Fedora Linux (6.11.10-200.fc40.x86_64) 40 (Workstation Edition)
Do not forget, if you install a newer kernel the index get set to 0 again and you would habe to repeat the steps above, if your system still is not boot able as you like.
Thank you, for now, i will use the 6.17.10.xxx kernel to boot.
But i continue my search to understand what is happening. It seems to be related to AMDGPU drivers.