Hello, everyone!
I recently built a gaming PC and decided to go with fedora as it worked very well on my thinkpad.
I followed the RPM fusion guide and before following any steps made sure my system was up-to date and I had met any prerequisites.
I first followed the secure boot steps and then the how to/nvidia steps.
Everything went according to the guide and I thought it would work but after a reboot, I get a black screen after choosing fedora from the boot menu. I tried the guide multiple times with the same steps but nothing seems to work.
Does anyone have a solution? Is anyone facing the same issue?
Iāll try this first thing tomorrow. I am incredibly tired from this. I also dread the kernel updates nowā¦ I was thinking of getting an amd GPU and I just might in the near future.
Yeah, I was gonna say, but didnāt want to talk down your newly purchased hardware: if youāre building or buying a PC with intentions to put Linux on it, it still makes more sense to get an AMD GPU.
The āNVIDIA situationā is improving, but very slowly. Though, even AMD GPUs arenāt entirely issues-free either: VRR/Freesync/GSYNC is still not working well for many users under Wayland on both AMD and NVIDIA.
So, Iām on the fence, sell my GPUs or wait and see what develops in a year or so. But yeah, I feel burnt out and tired too. My NVIDIA drivers died three times since December or so, and Iām not even using Linux full time yet
First I changed from Windows to Linux and the second step was to get rid of Nvidia. Since then my live with Linux is a pleasure. Then there was the issue with Realtek network adapters and its drivers. Till I realized my second network-adapter is Intel, since then I avoid the RTL one
While planing to buy new hardware it makes sens to have a look at https://linux-hardware.org/ to get an idea if there are troubles with it.
Woah, I didnāt know something like this existed! Thanks for sharing.
Yeah, I really am thinking about getting an amd gpu and just be done with it. Iāll try nobara and maybe cachy once but if they donāt work, Iāll use windows till I get an amd gpu.
Lots of Windows switchers are in this situation as NVIDIA is far more popular than AMD on the Windows side, though that may be changing because of the way NVIDIA has been behaving recently.
So most of us have NVIDIA GPUs and weāre trying to make it work with what we have. And Iām not too fond of the idea of selling my RTX4080 that is not even two years old, it works great on Windows. On top of this, it is really a bad time now to buy a GPU, even AMD GPUs are badly overpriced right now.
And I second the Realtek issues: I have problems with both Realtek on-board NIC and Realtek onboard audio on my main (newer) PC that are as bad as my NVIDIA issues.
So, Iād need a new network card, a new audio interface and a new GPU. So Linux may be free but there may be significant monetary costs associated with a Windows->Linux switch.
Besides, many AMD GPU owners still have VRR/Freesync issues under Wayland, so getting an AMD GPU may not even solve all of my Linux issues.
I donāt even know if I want to do it any more. Iām running into too many issues and I donāt hate Windows that much and I have it under control (I build custom ISO installers). I may need to wait couple of years when I build a new PC then I might consider Linux again and do a more targeted build for Linux.
I understand your struggles, I really do. I too have suffered because of realtek.
I still have linux but on this system, I just want to play games, watch movies and shows in peace. I canāt do that unless I get over this nvidia issue and it doesnāt look like thats going to be happening anytime soon. At least definitely not with fedora, might try nobara and if that doesnāt work, Iāll try cachy.
If that fails, I can only conclude that linux isnāt ready for a full on switch.
I used the rpm fusion guide to install it on my RTX3090, and it has been working fine for ages ā several years and many upgrades of both OS, kernel, and drivers. It even works with secure boot.
Itās much better under X11. Wayland is the problem. It needs like another 20 years to mature and get the basics right.
OK, soā¦ I do, and it does not work properly under Wayland. There is heavy flickering and screen turns often black when alt-tabbing out of a game. BTW, AMD owners have this problem too.
I have been told at least twice on this forum alone that NVIDIA drivers must be reinstalled/rebuilt with every major kernel update and yeah, it broke three times since December, on two different PCs, one with 3080 (twice) and one with 4080 (once, but I only used it for few days).
All I did was run a system update in Discovery and reboot and the driver reverted to Nouveau and had to reinstall. There were frequent posts from people who had this problem too. Do you sacrifice a goat or spit over your right shoulder before running system updates? Because I have no clue what Iām doing wrong and Iām close to giving up because itās way too frustrating.
There are occasional problems with a new kernel but rare and mostly due to timing of release from rpmfusion and the kernel team. As Leigh notes, always wait after an update from rpmfusion is installed before a reboot. I typically open the system monitor (gnome) and check the CPU trace.
I use Wayland exclusively, and no issues here. VRR is a different matter though. But this is mostly an issue with the EDID table reported by the monitor. I had to create and install a custom EDID table for my monitor on Windows as well to prevent this.
Each kernel version requires a rebuilt of the nvidia kernel modules, and akmods does take care of this. You ONLY need to wait a few minutes before reboot. dnf info last will show a new transaction with the status OK.
You will also find a new kmod-nvidia package installed with rpm -qa kmod-nvidia\*
See, this is what Iām talking about: how the heck is an average user supposed to know this? How much time is āenoughā? Five minutes? Ten minutes? Why isnāt Discovery doing this properly? Is there a warning anywhere? Stuff like is frustrating and discouraging for new users.
I reboot when Discovery (KDE software manager/store) tells me to reboot. If this is the wrong way of doing updates then itās a major UI/UX design flaw. And I have no idea what āCPU traceā is and I shouldnāt need to know.
The entire Linux graphics subsystem is just too fragile. Iām not a software engineer but this entire ādrivers are built into the kernelā Linux thing just seems bizzare and the biggest reason for Linux driver issues and failures. On Windows I can just install a driver without ever worrying about the kernel or ārebuildingā the drivers and there isnāt even a need to reboot.
It works fine in Windows without any tinkering. The only times it flickers slightly is during some static content inside the game, like loading screens or menus and even that is rare. Under Wayland the flickering is nauseating, unusable.
it does not matter, if you reboot to early, then the next boot will take much longer, because akmods will compile and install the needed kernel modules.
But itās best to wait for a few minutes and give the system time to finish the job. Check with rpm / dnf or look at /var/log/akmods/akmods.log
We probably mean different types of āflickeringā.
Monitor would go dark for 1-2 seconds, like a mode switch.
I had to increase the lower VRR limit frequency from 24Hz to 48Hz.
If you mean some textures are corrupted / flickering then this is something else. I leave VRR disabled. because importing a custom EDID table deactivates VRR on current stable 570.* drivers anyway. This was implemented in the new BETA 575* driver, but I had no time yet to test.
