[bazzite/nvidia] Plymouth "nvidia kernel module not loaded. Falling back to nouveau"
I switched from kinoite to bazzite with nvidia about a month ago.
With recent updates, I'm getting the message in the title during boot.
My kargs:
rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 nowatchdog gpu_sched.sched_policy=0 nvidia_drm.modeset=1
4 Replies
And finally, to check if I am using the correct image.
It appears I am using the nvidia module? I'm a little confused.
On an unrelated note, I was tinkering with my BIOS earlier (Z170A Sli Plus) and flipped
Windows 8.1/10 WHQL Support
on, which subsequently made grub not show. I'll fix that later.
I forgot to mention that I am not using secure boot.
Woke up and my monitor was blank. No output.
Several attempted reboots and no change to that.
I couldn't even access my BIOS, even after plugging monitor into the motherboard graphics output.
So I reset my BIOS. Could access it after this but another reboot saw the vga debug led become a steady red.
More reseats of the gpu in the same slot and the problem still persisted.
Moving the card up one slot fixed thie issue and I'm back into bazzite.
Hopefully I haven't broken that slot ;_;
Going to do more research
Because it seems to be just a cosmetic thing, I'll just ignore the message from now on.
At least until the nvidia module actually doesn't load.For what it is worth to you:
- Some hardware need to load some drivers, from the UEFI-BIOS, that are signed by the vendor, which might need SecureBoot Enabled.
- To boot
Bazzite
in SecureBoot enabled, you need to enroll the MOK-Key.
This is especially needed after you reset/update your UEFI-BIOS.
To do that you need to first boot with SecureBoot disabled, then use the below command and reboot after you enable SecureBoot again in the UEFI-BIOS:
Bazzite
uses it's own akmods
MOK-Key these days with respect to older versions...
(I'm running Bazzite-nVidia
with encryption and SecureBoot enabled,)Same problem here with the cinnamon-nvidia image. The secure boot thing above does nothing to change it. I should note, mine isn't cosmetic, the driver actually fails to load when I see that message. If I reset the kargs again, then reboot, it magically works again...but only for that first boot. It will go back to not working on the second boot, even though the kargs have not changed.
Yea i have the same as what you describe, see: https://discord.com/channels/1072614816579063828/1212374800908030032