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.
Okay, so if I get this right, Nvidia accepted this as a bug and is working on a fix. I will keep an eye on the thread in the Nvidia discourse then.
As a Linux beginner, where can I find this “fbdev=1”?
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 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.
3 Likes
I just added it to my grub command line, updated grub and then installed the latest kernel & headers. It now boots and loads on my Gtx 1060 using Plasma Wayland just fyi.
Allright so 2 ways, witch one is best to use?
I wonder when it will be fixed in EndeavourOS to work with Grub and systemd-boot without modifications? There is no problem in CachyOS.
Those two ways relate to different bootloaders, systemd-boot or grub.
So the one of them you use now will determine the way to add the kernel parameter.
1 Like
Maybe it already has those kernel parameters.
Oh yeah I see now, we’ll I’m tired from work so that’s my excuse 
2 Likes
Same.
Worked for me
Unfortunately, it’s not a solution for me. Clean EOS install - nvidia install using nvidia-inst and black screen! If I add nvidia_drm.fbdev=1 to /etc/kernel/cmdline (nvidia_drm.modeset=1 is already written) After reboot nothing changes and only a black screen…
1 Like
Hi,
I had the same behaviour after nvidia-dkms update, adding new kernel parameter and rebooting. I the switched to tty3 and reinstalled the nvidia-dkms package which solved the problem. Then I remembered that a kernel parameter only takes effect after the initrd ist rewritten, which seems to be a hook in the nvidia-dkms package. So it should be enough to “sudo reinstall-kernels” after adding nvidia_drm.fbdev=1 to /etc/kernel/cmdline
The clean install already has the latest kernel. If you added the kernel parameter after the install and didn’t update the kernel it hasn’t rebuilt the initrds.
Try now sudo reinstall-kernels
Out of curiosity what would you do if you only have one Kernel installed? I remember i ran into that issue before and i was at least lucky that i didn’t have auto-login active so i could switch to X11. But what could you do if that doesn’t work. Will ctrl+alt+F3 at least bring up a terminal?
Well i have a number of choices. I could have gone into a tty and downgraded but i have btrs with snapshots on grub so i just booted into a working snapshot and then rolled back to a working snapshot prior to the update.
1 Like