Fedora 37/36/35 NVIDIA Drivers Install Guide [530.30.02 / 525.89.02 / 520.56.06 / 515.86.01 / 510.108.03 / 470.161.03 / 390.157 / 340.108] - Comment Page: 14
This is guide, howto install NVIDIA proprietary drivers (manually using .run installer) on Fedora 37/36/35/34/33/32 and disable Nouveau driver. This guide works with GeForce 8/9/200/300/400/500/600/700/800/900/10/20/30/40 series cards.
GeForce RTX 40 series cards works with 530.xx, 525.xx, 520.xx NVIDIA drivers, (RTX 4090)
GeForce RTX 30 series cards works with 530.xx, 525.xx, 520.xx, 515.xx, 510.xx and 470.xx NVIDIA drivers, (RTX 3090, RTX 3080 and RTX 3070, RTX 3060, RTX 3060 Ti)
GeForce RTX 20 series cards works with 530.xx, 525.xx, 520.xx, 515.xx, 510.xx and 470.xx NVIDIA drivers (RTX 2080 Ti, RTX 2080, RTX 2070 Ti, RTX 2070, RTX 2060)
GeForce GT/GTX 600/700/800/900/10 series...
Works like a charm! thanks a lot!
Fedora 23 kernel 4.3.3
GeForce GT 640 video card
NVIDIA driver x86_64-361.18.run
“Fedora 23/22/21 nVidia Drivers Install Guide”
After switching from nouveau to a nvidia driver,
how do I a switch back to nouveau?
Thanks,
-Darin
Hi Darin,
Check 5. Fedora 23/22/21 Uninstall nVidia drivers and Enable Nouveau
Worked perfectly for me and settled issues with a secondary screen. Thank you soooooo much !!! I would never have figured that out on my own in a million years…
nvidia-installer: version 352.79 ([email protected]) Wed Jan 13 17:02:35 PST 2016
Linux localhost.localdomain 4.3.3-301.fc23.x86_64 #1 SMP Fri Jan 15 14:03:17 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1000M] (rev a1)
How will the update process look like? e.g. when v361 becomes stable, how do I update?
Hi Roman,
Just boot to runlevel 3 and run new installer, then boot back to runlevel 5.
Thanks! I guess it’s worth mentioning in the tutorial
so far looks like driver installed properly. proceeding to fixing the boot splash screen )
—————–
nvidia-installer -v |grep version
nvidia-installer: version 352.79 ([email protected]) Wed Jan 13 17:02:35 PST
—————–
uname -a
Linux localhost.localdomain 4.3.3-303.fc23.x86_64 #1 SMP Tue Jan 19 18:31:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
—————–
lspci |grep -i VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GF106 [GeForce GTS 450] (rev a1)
Goes well, then does not go any further during the “Starting Switch Boot…”
Any Ideas?
Hi Ahmad,
Could you first post output of following commands:
Worked perfectly for me!
[[email protected] ~]# nvidia-installer -v |grep version
nvidia-installer: version 361.18 ([email protected]) Sat Jan 9 21:52:21 PST 2016
[[email protected] ~]# uname -a
Linux fedora 4.3.3-303.fc23.x86_64 #1 SMP Tue Jan 19 18:31:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[[email protected] ~]# lspci |grep -i VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)
[[email protected] ~]#
Works like a charm.
nvidia-installer -v |grep version
nvidia-installer: version 352.63 ([email protected])
uname -a
Linux dzik 4.3.3-303.fc23.x86_64 #1 SMP Tue Jan 19 18:31:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
lspci |grep -i VGA
02:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1)
perfect
nvidia-installer: version 352.79 ([email protected]) Wed Jan 13 17:02:35 PST 2016
4.3.4-300.fc23.x86_64 #1 SMP Mon Jan 25 13:39:23 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 425M] (rev a1)
Worked!
[[email protected] ~]# nvidia-installer -v |grep version
nvidia-installer: version 352.79 ([email protected])
[[email protected] ~]# uname -a
Linux cody-linpc.bncdiagnostics.com 4.3.4-300.fc23.x86_64 #1 SMP Mon Jan 25 13:39:23 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[[email protected] ~]# lspci |grep -i VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)
Every time I execute this tutorial, it goes to drakut emergency shell, what is happening?
Hi Alex,
Could you post output of following command:
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
04:00.0 3D controller: NVIDIA Corporation GK208M [GeForce 920M] (rev a1)
Thanks!
This is (unfortunately) nVidia Optimus device. Could you disable Intell graphics/Optimus from BIOS?
# nvidia-installer -v | grep version
nvidia-installer: version 358.16 ([email protected]) Mon Nov 16 19:59:22 PST 2015
# uname -a
Linux athos 4.3.4-300.fc23.x86_64 #1 SMP Mon Jan 25 13:39:23 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
# lspci |grep -i VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] (rev a2)
The driver is running but it creates a problem with the systemd service abrt-xorg (enabled by default). The result is a “degraded” state for systemd due to that service not operating properly. abrt-xorg reads the journal files and watches for problems via the command `abrt-dump-journal-xorg -fxtD` (run `systemctl show abrt-xorg`). The Xorg.0.log is now piped into the journal file via gdm so the abrt subsystem abrt-xorg can watch it for crashes. I note that `journalctl -e _COMM=gdm-x-session` works fine, so I suspect there may be an upstream problem here.
xorg.conf below refers to /etc/abrt/plugins/xorg.conf
abrt-dump-journal-xorg -fxtDv
abrt-dump-journal-xorg: Loading settings from ‘xorg.conf’
abrt-dump-journal-xorg: Failed to read ‘MESSAGE’ field: Bad message
abrt-dump-journal-xorg: Cannot read journal data.
The above command is run when the service starts:
systemctl status abrt-xorg
● abrt-xorg.service – ABRT Xorg log watcher
Loaded: loaded (/usr/lib/systemd/system/abrt-xorg.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2016-02-07 12:10:57 EST; 5s ago
Process: 3487 ExecStart=/usr/bin/abrt-dump-journal-xorg -fxtD (code=exited, status=1/FAILURE)
Main PID: 3487 (code=exited, status=1/FAILURE)
Feb 07 12:10:55 athos systemd[1]: Started ABRT Xorg log watcher.
Feb 07 12:10:55 athos systemd[1]: Starting ABRT Xorg log watcher…
Feb 07 12:10:57 athos abrt-dump-journal-xorg[3487]: abrt-dump-journal-xorg: Cannot read journal data.
Feb 07 12:10:57 athos systemd[1]: abrt-xorg.service: Main process exited, code=exited, status=1/FAILURE
Feb 07 12:10:57 athos systemd[1]: abrt-xorg.service: Unit entered failed state.
Feb 07 12:10:57 athos systemd[1]: abrt-xorg.service: Failed with result ‘exit-code’.
Workaround is to disable abrt-xorg (`systemctl disable abrt-xorg`)
Setup appears to be working. I got an error during the nVidia installer when it was setting up the 32 bit environment. It was missing libEGL.so.1 Screenshot here http://imgur.com/wfoQAzP
=> nvidia-installer -v |grep version
nvidia-installer: version 361.18 ([email protected]) Sat Jan 9 21:52:21 PST 2016
=> uname -a
Linux Legion 4.3.4-300.fc23.x86_64 #1 SMP Mon Jan 25 13:39:23 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
=> lspci |grep -i VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)
# nvidia-installer -v |grep version
nvidia-installer: version 340.96 ([email protected]) Sun Nov
# uname -a
Linux dhcppc4 4.3.4-300.fc23.x86_64 #1 SMP Mon Jan 25 13:39:23 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
# lspci |grep -i VGA
02:00.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce GT 220] (rev a2)
I think my post will be related to comment above of “Phil K on February 7, 2016 at 7:02 pm”
There are problems with SElinux while some system devices and modules try to contact “/dev/nvidiactl”
I have mentioned this exactly after system bot with “journalctl -b”
First of all I forgot to disable SElinux: So from enforcing mode I set it to permissive (not completely disabled for test purposes)
nvidia-installer -v |grep version
nvidia-installer: version 340.96 ([email protected]) Sun Nov 8 22:50:33 PST 2015
uname -a
Linux hostname.u.dont.care 4.3.5-300.fc23.x86_64 #1 SMP Mon Feb 1 03:18:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
lspci |grep -i VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)
ls -Z /dev/nvidiactl
system_u:object_r:device_t:s0 /dev/nvidiactl
SELinux messages:
SELinux is preventing gnome-shell from ioctl access on the chr_file /dev/nvidiactl.
***** Plugin restorecon (90.5 confidence) suggests ************************
If you want to fix the label.
/dev/nvidiactl default label should be xserver_misc_device_t.
Then you can run restorecon.
Do
# /sbin/restorecon -v /dev/nvidiactl
***** Plugin device (9.50 confidence) suggests ****************************
If you want to allow gnome-shell to have ioctl access on the nvidiactl chr_file
Then you need to change the label on /dev/nvidiactl to a type of a similar device.
Do
# semanage fcontext -a -t SIMILAR_TYPE ‘/dev/nvidiactl’
# restorecon -v ‘/dev/nvidiactl’
***** Plugin catchall (1.40 confidence) suggests **************************
If you believe that gnome-shell should be allowed ioctl access on the nvidiactl chr_file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep gnome-shell /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
########## Next message titles with almost same “help context as above”
SELinux is preventing gnome-shell from ‘read, write’ accesses on the chr_file /dev/nvidiactl.
SELinux is preventing gnome-shell from getattr access on the chr_file /dev/nvidiactl.
SELinux is preventing gnome-shell from open access on the chr_file /dev/nvidiactl.
SELinux is preventing abrt-hook-ccpp from getattr access on the file file.
SELinux is preventing plugin-containe from ioctl access on the chr_file /dev/nvidiactl.
SELinux is preventing plugin-containe from open access on the chr_file /dev/nvidiactl.
SELinux is preventing plugin-containe from ‘read, write’ accesses on the chr_file nvidiactl.
I’m not SElinux expert )
But following help tips in Selinux messages not fixing this.
Same messages still appear.