Attention Nvidia GPU / Driver users! update to latest kernel and drivers could cause issue on plasma wayland [resolved]

[joekamprad]

Read here:

Only Black Screen after login (after kernel/nvidia update)

Just added the parameter, upgraded my system and rebooted. It’s working for me with the nvidia_drm.fbdev=1 kernel parameter too. But as this option is still considered experimental, I’m not completely sure how to feel about that. On the other hand, iirc the 560.x branch is still beta. So that would be the normal kind of trade-off you need to accept when running software in this state.

And here:

Kernel 6.11 causes SDDM Wayland to just display a black screen if `fbdev=1`...

Fix for systemd-boot bootloader:

You would need to fire up a terminal (e.g. Konsole) and edit the file /etc/kernel/cmdline with your favourite text editor like this:

sudo nano /etc/kernel/cmdline

There you should see a single line where you append the parameter

nvidia_drm.fbdev=1

Also make sure that the parameter

nvidia_drm.modeset=1

is present somewhere in this line. Otherwise append it too.

If using nano as your text editor, just hit CTRL+X after editing the line and confirm with y and Enter that you would like to save the file.

After that, you can upgrade your system like normal and after a reboot everything should be up and running.

Only Black Screen after login (after kernel/nvidia update)

Here is the soultion for systems that run systemd-boot as boot manager: You would need to fire up a terminal (e.g. Konsole) and edit the file /etc/kernel/cmdline with your favourite text editor like this: sudo nano /etc/kernel/cmdline There you should see a single line where you append the parameter nvidia_drm.fbdev=1 Also make sure that the parameter nvidia_drm.modeset=1 is present somewhere in this line. Otherwise append it too. If using nano as your text editor, just hit CTRL+X after …

Fix for grub-bootloader:

Edit the file /etc/default/grub with your favourite text editor like this:

sudo nano /etc/default/grub

In the line starting with:
GRUB_CMDLINE_LINUX_DEFAULT=
add the boot option nvidia_drm.fbdev=1 (not removing others!)
So your line will look similar to this with the option added:

GRUB_CMDLINE_LINUX_DEFAULT='nowatchdog nvme_load=YES nvidia_drm.modeset=1 nvidia_drm.fbdev=1 loglevel=3'

Also make sure that the parameter

nvidia_drm.modeset=1

Is present somewhere in this line. Otherwise, append it too!

If using nano as your text editor, just hit CTRL+X after editing the line and confirm with y and Enter that you would like to save the file.

On Grub you will need to generate a new config now:
sudo grub-mkconfig -o /boot/grub/grub.cfg

And you are ready to reboot to see if all work again.

---

//News:
[3 Okt 24 // 21:11 CET] From what i see discussed on Arch packaging and nvidia upstream it is still not 100% clear what is the reason for the issue. Could be it is resolved already and the nvidia_drm.fbdev=1 option will not be needed in a future update of the packages related.

https://gitlab.archlinux.org/archlinux/packaging/packages/nvidia-utils/-/blob/main/make-modeset-fbdev-default.patch?ref_type=heads seems new …

Will be in 560.35.03-5 of nvidia-utils and should fix the issues finally.

With the current nvidia-utils package we see drm modesetting and the fbdev option are now enabled by default without any extra intervention needed!

You will still have the option added under /etc/kernel/cmdline or in /etc/default/grub they can be removed now. Also, it will not harm if they are there.

[winnyace]

On Nvidia 560.35.03, as reported by nvidia-smi, using Wayland and Plasma, using the LTS kernel, things seem fine so far.

[joekamprad]

yes LTS kernel will be fine from what i see users reporting.

[z580c]

I’m not at my laptop to check if I have the kernel parameter set right now, but I know for a fact I updated to 6.11 last night and had no issues with my machine on the standard kernel with the latest nvidia drivers running plasma on wayland.

Does EOS ship with fb.dev=1 pre-set on an nvidia install? It’s definitely not something I have toggled myself knowingly (and I feel like I would know given how these settings are required to be implemented )

[joekamprad]

no we do not, as of it was not needed till now.
Could be we will add it, if it is consent to do so.

[ricklinux]

I just added nvidia_drm.fbdev=1 to my grub command line and updated grub. Then i installed the 6.11 kernel and headers. It boots and loads now on my GTX 1060 on Plasma Wayland.

[d-air1]

I’m using nvidia-open-dkms and didn’t notice a problem on upgrade.

[Heidelberg]

Yep. Have this issue as well.

[ultrablazed]

It broke for me aswell

[Euphuzade]

I know it doesn’t help at all but same thing occurred on my end. Went overboard and just did a fresh install of the OS and then I found this thread. Currently using X11.

[joekamprad]

x11 should work in all cases, only Wayland session is causing issues from what users posting

[mehmetcankamar]

I’m also having some problems with x11. It’s not a black screen but I’m having glitches in the taskbar and a white overlay problem when I try to open the menu.

No chance to work with Wayland, only black screen.

Adding nvidia_drm.fbdev=1 seems to have solved my problem for now.

[tulambin]

Same issue hear, glad I chose LTS at install on a recent new build because my other PC’s I had to chroot to install the LTS.

I’m not going to do anything and just wait since their are no instructions of how to add

nvidia_drm.fbdev=1

To the kernel perimeters and with a new Nvidia driver upgrade it may get fixed without adding fbdev=1.

I’m using all default EOS KDE plasma settings.

Wayland, systemd-boot etc.

[DarklinkFighter]

I also have this issue…
I am not that deep into system / driver / window manager stuff…

How to exactly fix it?

[EDIT:]
Ok I installed the linux lts kernel and updated Grub like this: (So this is only for Grub users I guess…)

1. During the black Screen Press CTRL + ALT + F1 (or F2 or F3) until a console terminal screen apears
2. Login with your username and password
3. Make sure everything is up to date sudo pacman -Syu
4. Install the linux-lts kernel with sudo pacman -S linux-lts linux-lts-headers
5. Update the Grub Menu with sudo grub-mkconfig -o /boot/grub/grub.cfg
6. Reboot with sudo reboot

After that I could select the lts kernel in the advanced entry in my grub boot menu.
With that I get to my kde plasma screen again
If the latest kernel works again after nvidia or kernel updates I will switch back to that one i guess.
But for now this should hopefully work

// moderation edit:
In case you arte using nvidia package and not nvidia-dkms you will need to add the correspondending nvidia-lts package to the install line:
sudo pacman -S linux-lts nvidia-lts
In this case, headers are not needed for the nvidia packages.

[stibbons]

Only Black Screen after login (after kernel/nvidia update)

You would need to fire up a terminal (e.g. Konsole) and edit the file /etc/kernel/cmdline with your favourite text editor like this: sudo nano /etc/kernel/cmdline There you should see a single line where you append the parameter nvidia_drm.fbdev=1 Also make sure that the parameter nvidia_drm.modeset=1 is present somewhere in this line. Otherwise append it too. If using nano as your text editor, just hit CTRL+X after editing the line and confirm with y and Enter that you would like to save…

[joekamprad]

Added the missing info to my initial post.

[joekamprad]

Thanks added your tutorial too!

[Salarak]

wow I just joined this forum and Im glad I did that haha.Im just a linux newbie and have been having this issue today now it fixed. Thanks!

[winnyace]

Welcome to the forum and to Linux as a whole. I hope things will be great for you.