I have a Dell G15 with an Intel i9-13900HX and an NVIDIA GeForce RTX 4060. I’ve enabled Optimus in the BIOS. When I boot into Fedora 43 with KDE, the system freezes right after I select Fedora as the boot option. Interestingly, Fedora 43 with GNOME works fine, but with KDE, the system becomes unresponsive, and I’m unable to access a TTY or CLI environment to troubleshoot the issue.
Same issue. I have an Acer Predator PH16-71 with an NVIDIA GeForce RTX 4080, and switchable graphics is also enabled. Fedora 43 KDE shows the spinning loading animation on the boot logo screen for a few seconds, and then freezes indefinitely. I have reinstalled Fedora 43 KDE about 5 times with and without disk encryption, but the issue persists. May have to revert to Fedora 42 for now.
Same issue here. I’m on a IdeaPad Flex 5, I’m only able to go back to 42 KDE for now. Hopefully there is a fix soon. One thing I would like to know is how to apply the fix once it’s out. Am I able to update from the 42 KDE environment or is it more involved?
Same one. Acer Nitro 5 an515-55 Fedora 43 refuses to boot with NVIDIA GTK 1650m
I haven’t tried installing FC43 KDE on my Lenovo Legion 5 Pro (16ACH6H - Ryzen 7 5800H + Nvidia GeFroce RTX 3070)
It was set to discrete when Kernel 6.17.4-200.fc42 installed, I was given a black screen on boot, but num/cap lock indicators worked. But Ctrl+Alt+F3 didn’t work.
I was able to switch to the integrated GPU of the 5800H to get back into the system. Not ideal but I might be able to upgrade the Nvidia open-kernel driver to get things working again?
Could it be this bug?
You could test by removing the rhgb argument from the command line when booting like so:
- In GRUB, when the Fedora kernel you are booting is highlighted, hit the e key to edit the command.
- Delete the
rhgbfrom the command (using the arrow keys and Backspace or Del). - Boot into the edited command line using CtrlX or F10.
If that works, it’s been suggested that reinstalling the Nvidia drivers fixes the problem: Fedora 42->43 kde/gnome upgrade issue - #4 by rewirefiner282
You could alternatively make the command line fix permanent by executing:
sudo grubby --update-kernel=ALL --remove-args="rhgb"
…but this disables the “graphical boot” with the manufacturer logo, which many users like to retain.
2 Likes
I’ll try this and report back. My laptop has an AMD gpu but still facing the same issue. I’ll let you know soon if that fixes it.
Yep that worked! Thanks a bunch! I’ll apply that permanent fix. Thanks again!!!
1 Like
Thank you, this got me through on my Dell Inspiron 2-in-1 7405, yep AMD chipset, after a successful, no-issue desktop upgrade.
1 Like
I have an Nvidia Optimus system fresh install and it seems to get stuck at nouveau not being able to find any screens. Can’t get to any prompts or anything.
Kinda inexcusable I can’t even get though the first boot and all the bugs we are having with this release. I’ve been using it for years and promoted it heavily but I think I’m gonna try to find something else.
Yep the fix doesn’t worked for me either with NVIDIA 1650m graphics card.
I am using HP Omen laptop with Intel 12th gen with Nvidia 3060, for me I do not think its the NVIDIA driver that is culprit, because removing it still causing problem, its most probably some configuration problem from both Fedora and KDE end.
I got an workaround by bypassing the SDDM screen. For that:
Step 1: Pressing ‘e’ during boot and then choosing run level 3
Step 2: Log-in into TTY
Step 3: After logging in to user account I simply use this command: startplasma-wayland.
This fixes the problem, but you have to do it in every boot. Fedora team really need to look into this and fix the problem. Fedora and KDE needs to fix this issue.
Do you see “undefined symbol” errors from SDDM processes, like this user does?
You should check out Bazzite. They are very Nvidia friendly.
I have been unable to find a solution myself, but it may be helpful for others to check out this post: