Hi! I’m new to Linux. I try to be moderately tech savvy, but it’s been hard to gain a solid understanding so far due to being literally unable to use my system. Apologies if I’m a little slow to understand any help provided, but thanks in advance!
I can’t get Nvidia drivers to work. I’ve been troubleshooting this issue for several days. I’ve come across many similar forum posts, but none of the advice provided seems to be of use for my circumstances.
My GPU is an RTX 3060 ti, so I have been installing the most up to date versions of everything as per rpm fusion’s recommendations.
Things I’ve tried -
Reinstall Fedora on top of itself
Wipe partition and reinstall Fedora completely
Download and flash Fedora again in case of corrupted files
Manually making sure every necessary rpm repo is available and being used
Making sure secure boot is 1000% disabled (confirmed in both BIOS and Konsole)
Waiting an entire hour after completing the driver install, to be sure five minutes has passed
Using the Discover GUI to install instead of Konsole
Things I’ve experienced -
Booting to black screen, able to access console with CTRL+ALT+F3
Booting to black screen, completely unresponsive
Booting to console (unprompted), sometimes able to input commands, sometimes unable to type
Booting, but only one of my monitors functions and is low resolution
Booting seemingly normally, but after login black screen with only cursor available (my most recent fail state)
I’m at a total loss at this point. I’ve been doing my best to fix it myself and have learned a fair bit in doing so, but I’m now out of ideas and don’t know what to try next, please help me
Copy and paste is the easiest method as pre-formatted text (</> button in this dialog box when you’re writing as post… you can surround it with three back ticks on blank line, top and bottom, too
like this
If you don’t use pre-formatted text, it buggers up the formatting when anyone quotes it.
However if there’s too much to do that comfortably run those commands piped into fpaste and paste the URL(s) it provides here.
Of course you can always direct the output to a file and then use an editor to trim it up before copy and pasting the entire thing into here. There’s a post limit of 32 KB.
See man fpaste for a quick way to transfer output from terminal commands and the post the URL here. For maximum visibility you can then use a system with working GUI to post the output (as pre-formatted web-discoverable text using the </> button) here. If you don’t have easy access to a system with a web browser you can use a Live USB installer to view the journals (using journalctl with the —directory option) and paste directly into a forum post.
In file included from /usr/src/kernels/7.0.14-201.fc44.x86_64/include/linux/hrtimer.h:21,
from /usr/src/kernels/7.0.14-201.fc44.x86_64/include/linux/interrupt.h:13,
from ././common/inc/nv-time.h:30,
from nvidia-uvm/uvm_linux.h:37,
from nvidia-uvm/uvm_common.h:43,
from nvidia-uvm/uvm_api.h:28,
from nvidia-uvm/uvm_va_space.c:24:
/usr/src/kernels/7.0.14-201.fc44.x86_64/include/linux/timer.h:192:50: internal compiler error: in c_addr_space_name, at c-family/c-common.cc:657
The other puzzle (in common with various other recent bug reports) is why falling back to nouveau doesn’t work properly. KDE Plasma clearly does in principle work with nouveau, because that’s how all our live USBs work.
I’ll have to admit, I blacklisted nouveau about 3 years ago and haven’t used it at all to my knowledge, so when it buggers up I’m lost.
I’d start from first principles here, given that the OP has had to fiddle quite a bit so perhaps removing akmods and reinstalling the lot from the RPM Fusion guide might be apposite.
Clean slate and all that,
I’ve not heard of any gcc 16 internal errors from anyone else building this stuff, but then again I’ve not been particularly watching gcc bug reports either!
@rinux the results of the attempt by akmods to build and create the drives and insert them into your system will be documented in /var/cache/akmods/nvidia/.last.log
It should start like this:
2026/06/05 21:58:50 akmods: Building RPM using the command '/usr/sbin/akmodsbuild --kernels 7.0.10-201.fc44.x86_64 /usr/src/akmods/nvidia-kmod.latest'
/tmp/akmods.jPnPQzjk/results/kmod-nvidia-7.0.10-201.fc44.x86_64-595.80-1.fc44.x86_64.rpm
2026/06/05 21:59:19 akmodsbuild: * Rebuilding /usr/src/akmods/nvidia-kmod.latest for kernel(s) 7.0.10-201.fc44.x86_64: Building target platforms: x86_64
2026/06/05 21:59:19 akmodsbuild: Building for target x86_64
2026/06/05 21:59:19 akmodsbuild: Installing /usr/src/akmods/nvidia-kmod.latest
2026/06/05 21:59:19 akmodsbuild: setting SOURCE_DATE_EPOCH=1780012800
2026/06/05 21:59:19 akmodsbuild: Executing(%mkbuilddir): /bin/sh -e /var/tmp/rpm-tmp.PXKMKN
2026/06/05 21:59:19 akmodsbuild: Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.MEAaim
2026/06/05 21:59:19 akmodsbuild: + umask 022
and it absolutely must end looking like this:
2026/06/05 21:59:19 akmods: Installing newly built rpms
2026/06/05 21:59:19 akmods: DNF detected
Updating and loading repositories:
Repositories loaded.
Package Arch Version Repository Size
Upgrading:
kmod-nvidia-7.0.10-201.fc44.x86_64 x86_64 3:595.80-1.fc44 @commandline 10.5 MiB
replacing kmod-nvidia-7.0.10-201.fc44.x86_64 x86_64 3:595.71.05-1.fc44 @commandline 10.5 MiB
Transaction Summary:
Upgrading: 1 package
Replacing: 1 package
Total size of inbound packages is 9 MiB. Need to download 0 B.
After this operation, 7 KiB will be freed (install 10 MiB, remove 10 MiB).
Running transaction
[1/4] Verify package files 100% | 38.0 B/s | 1.0 B | 00m00s
[2/4] Prepare transaction 100% | 4.0 B/s | 2.0 B | 00m00s
[3/4] Upgrading kmod-nvidia-7.0.10-201. 100% | 1.3 MiB/s | 10.5 MiB | 00m08s
[4/4] Removing kmod-nvidia-7.0.10-201.f 100% | 0.0 B/s | 7.0 B | 00m08s
Warning: skipped OpenPGP checks for 1 package from repository: @commandline
Complete!
2026/06/05 21:59:36 akmods: Successful.
If you don’t get output which finishes with “Successful” and a few lines about rpm’s being installed, it won’t be working when you reboot.
Quite why nouveau is also unhappy is something I’ll leave to those who have used it. I can barely spell it…
Ooh it might be? I haven’t done any overclocking in a long time but I do remember messing with stuff when I first bought the thing years ago. I’ll check the BIOS in a sec
