I haven’t noticed any issues running the Nvidia drivers with the latest kernels fortunately. 3080 and 5600x system with two 1440p monitors.
It sticks on the loading Kernel and ram disk for about 5 seconds then goes right into it. I do have my system configured to automatically mount two 5400RPM HDDs though, not sure if that makes an impact or not.
Someone suggested nvidia-drm.modeset=1.
Tried it, I never get the desktop when its added, so that didn’t help ;-(.
I did just try an update and I still get the same issues, almost, if not a month later.
I do not seem to have any issues with Garuda Hyprland and Nvidia. Just lost, as its my first few days in Hyprland. “Total Hyprland Newbie”
Seems to be related maybe to just the Garuda KDE Dr460nized build? Thats just a guess nothing more than a guess.
Anyone here up for a “Used Nvidia Gear Sale?”
If it’s free sure. 
I don’t even want this shit for free^^
Never again…
Works fine here, and no we are not a sales platform.
“sadly”… NVidia seems to be the primary reason people have issues running linux. not “my software isn’t available on linux” people who won’t try linux… the people who actually try to use linux, then hit issues caused by weird hardware(mostly NVidia hardware, but that is only a numbers thing)
that’s why this clip exist .
No but I got 3 AMD cards laying around, thats guarenteed to give you days of driver patching fun and windows blue screening if you want to do any Microsoft Flight Simulator our Starfield. It will make your VR headset display a nice black screen when you want to use it as well.
Personally I am not a fan of either, glad to hear AMD works in Linux. I sure did not have that experience with Winblowz and AMD. Every time I turned around I had a bios update or patch to apply to get something working.
They each definately have thier quarks. They both make me miss a dumb terminal and HP/UX at times.
Break for PC History 101:
Back in the '80s, '90s, there were no “industry standard” PC hardware architecture. Every PC manufacturer had their own architecture bus, but they tried very hard to make it (the hardware) “IBM Compatible.”
What that meant:
They had one defining test for their own “IBM compatible” hardware: Microsoft Flight Simulator. If it failed, they failed.
Thus endeth the lesson.
EDIT: The “lesson” forgot that all the PC manufacturers had their own version of DOS. The only official DOS was IBM’s PC-DOS (by MS).
But I loved DR Dos!! Well and I did like OS/2 alot!
Digital Research (Gary Kildall) wasn’t quite on the scene as an alternative but followed shortly, as far as a PC OS. He was actually very prominent in other OS circles.
You can’t blame Gary all that much. History has it he was out flying his plane when Bill Gates came calling for a DOS. Instead, he paid some penniless programmer $60,000 for what became the DOS.
Personally, I loved DR-DOS. It went above and beyond. For anyone wanting to squeeze out just a few more KB from config.sys or autoexec.bat (gaming, for me), especially on lower-end PCs like mine, it was darn near critical. It was also one of the first DOS to try incorporating virtualization.
Kildall was too cool. 
P.S. I ran OS/2 (on an IBM PS/2) from P.M. 2.1 through 4.0 Warp. I did 5 on a better machine.
Somewhere in there Linux ruined it all. 
I was able to fix this slow boot issue by adding the following to my grub line. I am now back to almost instant boot times and able to apply all updates finally: nvidia-drm.fbdev=0
My grub line as an example:
rd.driver.pre=vfio-pci intel_iommu=on rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 vfio-pci.ids=10de:1c82,10de:0fb9 pcie_acs_override=downstream,multifunction video=efifb:off iommu=pt nvidia-drm.fbdev=0
In reference to this actual issue posted. It appears we need to get off Nvidia 545.29.X driver. The nvidia forums have acknowledge slow boot, drm issues and something else I forget now.
Not sure how to do that without a manual install of the driver.
Here is the post:
You can also grab the 545 driver and apply the patch file posted in the url above and it fixes the issue as well.
What we need is an update with the 535.146.02 driver being installed / built, the fix has been applied in this new feature branch. Also fixes a hyprland and wayland issue with the driver.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.