Nvidia Drivers Fedora 37

select · April 11, 2023, 3:54pm

Nvidia driver is installed but isn’t being used.

Neofetch

OS: Fedora Linux 37 (Workstation Edition) x86_64 
Host: GP66 Leopard 11UH REV:1.0 
Kernel: 6.2.9-200.fc37.x86_64 
Uptime: 9 mins 
Packages: 1922 (rpm) 
Shell: bash 5.2.15 
Resolution: 1920x1080 
DE: GNOME 43.4 
WM: Mutter 
WM Theme: Adwaita 
Theme: Adwaita [GTK2/3] 
Icons: Adwaita [GTK2/3] 
Terminal: gnome-terminal 
CPU: 11th Gen Intel i7-11800H (16) @ 4.600GHz 
GPU: NVIDIA GeForce RTX 3080 Mobile / Max-Q 8GB/16GB 
GPU: Intel TigerLake-H GT1 [UHD Graphics] 
Memory: 2522MiB / 63991MiB

When I run nvidia-smi I get the error

NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

lspci -k | grep -A 2 -E "(VGA|3D)"

00:02.0 VGA compatible controller: Intel Corporation TigerLake-H GT1 [UHD Graphics] (rev 01)
	DeviceName: Onboard - Video
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 12fb
--
01:00.0 VGA compatible controller: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] (rev a1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 12fb
	Kernel driver in use: nouveau

To install the drivers I ran the commands in Howto/NVIDIA - RPM Fusion, which were:

sudo dnf update -y
sudo dnf install akmod-nvidia
sudo dnf install xorg-x11-drv-nvidia-cuda

and by running the command modinfo -F version nvidia I get:

530.41.03

dnf list installed *nvidia*

akmod-nvidia.x86_64                                        3:530.41.03-1.fc37                    @rpmfusion-nonfree-nvidia-driver
kmod-nvidia-6.2.9-200.fc37.x86_64.x86_64                   3:530.41.03-1.fc37                    @@commandline                   
nvidia-gpu-firmware.noarch                                 20230310-148.fc37                     @updates                        
nvidia-persistenced.x86_64                                 3:530.41.03-1.fc37                    @rpmfusion-nonfree-nvidia-driver
nvidia-settings.x86_64                                     3:530.41.03-1.fc37                    @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia.x86_64                                 3:530.41.03-1.fc37                    @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda.x86_64                            3:530.41.03-1.fc37                    @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.x86_64                       3:530.41.03-1.fc37                    @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-kmodsrc.x86_64                         3:530.41.03-1.fc37                    @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.x86_64                            3:530.41.03-1.fc37                    @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-power.x86_64                           3:530.41.03-1.fc37                    @rpmfusion-nonfree-nvidia-driver

sudo lsmod | grep nouveau

nouveau              3403776  0
drm_ttm_helper         16384  1 nouveau
mxm_wmi                16384  1 nouveau
drm_display_helper    200704  2 i915,nouveau
ttm                   102400  3 drm_ttm_helper,i915,nouveau
video                  73728  3 msi_wmi,i915,nouveau
wmi                    45056  5 video,wmi_bmof,msi_wmi,mxm_wmi,nouveau

sudo lsmod | grep nvidia does not output nothing.
dmesg | grep -iE 'secure|nvidia' → as visible secure boot is disabled

[    0.000000] secureboot: Secure boot disabled
[    0.017616] secureboot: Secure boot disabled
[    2.867381] nouveau 0000:01:00.0: NVIDIA GA104 (b74000a1)
[    5.117471] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input31
[    5.117516] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input32
[    5.117567] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input33
[    5.117622] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input34
[    6.133367] nvidia: loading out-of-tree module taints kernel.
[    6.133374] nvidia: module license 'NVIDIA' taints kernel.
[    6.139730] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    6.190362] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[    6.190366] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[    6.190892] NVRM: No NVIDIA devices probed.
[    6.190975] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[    6.908974] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[    6.908978] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[    6.909588] NVRM: No NVIDIA devices probed.
[    6.909710] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[    7.369768] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[    7.369774] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[    7.370407] NVRM: No NVIDIA devices probed.
[    7.370511] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[    7.990266] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[    7.990271] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[    7.990690] NVRM: No NVIDIA devices probed.
[    7.990771] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   14.250854] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   14.250859] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   14.251313] NVRM: No NVIDIA devices probed.
[   14.251395] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   16.146526] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   16.146531] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   16.146989] NVRM: No NVIDIA devices probed.
[   16.147078] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   22.997352] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   22.997357] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   22.997905] NVRM: No NVIDIA devices probed.
[   22.997989] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   25.528654] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   25.528659] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   25.529153] NVRM: No NVIDIA devices probed.
[   25.529255] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   26.710462] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   26.710467] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   26.710929] NVRM: No NVIDIA devices probed.
[   26.711056] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   35.717063] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   35.717068] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   35.717618] NVRM: No NVIDIA devices probed.
[   35.717709] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   36.794487] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   36.794492] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   36.794929] NVRM: No NVIDIA devices probed.
[   36.795017] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   42.778017] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   42.778022] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   42.778635] NVRM: No NVIDIA devices probed.
[   42.778742] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   43.850019] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   43.850024] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   43.850622] NVRM: No NVIDIA devices probed.
[   43.850720] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   56.842296] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   56.842300] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   56.842761] NVRM: No NVIDIA devices probed.
[   56.842857] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   58.359975] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   58.359980] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   58.360582] NVRM: No NVIDIA devices probed.
[   58.360673] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   59.459466] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   59.459471] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   59.459930] NVRM: No NVIDIA devices probed.
[   59.460027] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   60.561646] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   60.561652] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   60.562085] NVRM: No NVIDIA devices probed.
[   60.562203] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[   61.659089] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[   61.659099] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[   61.659540] NVRM: No NVIDIA devices probed.
[   61.659625] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[  826.739312] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[  826.739317] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[  826.739742] NVRM: No NVIDIA devices probed.
[  826.739826] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[  827.815288] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[  827.815292] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[  827.815730] NVRM: No NVIDIA devices probed.
[  827.815815] nvidia-nvlink: Unregistered Nvlink Core, major device number 510
[ 1016.390876] nvidia-nvlink: Nvlink Core is being initialized, major device number 510
[ 1016.390880] NVRM: The NVIDIA probe routine was not called for 1 device(s).
               NVRM: nouveau, rivafb, nvidiafb or rivatv 
               NVRM: was loaded and obtained ownership of the NVIDIA device(s).
               NVRM: driver(s)), then try loading the NVIDIA kernel module
[ 1016.391482] NVRM: No NVIDIA devices probed.
[ 1016.391576] nvidia-nvlink: Unregistered Nvlink Core, major device number 510

Am I doing something wrong? (Before installing this drivers I did install the wrong ones, but then I removed them, they are not showing in the list, but can that be causing this error?)

Thank you for your help

computersavvy · April 11, 2023, 7:23pm

You noted that you installed the wrong drivers. Where did you obtain them from and how did you install them? Also, how did you remove the wrong one?

Note that nvidia-smi cannot function unless the nvidia drivers are loaded and functioning.

The command modinfo nvidia would be helpful with just the first few lines that should look something like this

]# modinfo nvidia
filename:       /lib/modules/6.2.9-200.fc37.x86_64/extra/nvidia/nvidia.ko.xz
firmware:       nvidia/530.41.03/gsp_tu10x.bin
firmware:       nvidia/530.41.03/gsp_ga10x.bin
alias:          char-major-195-*
version:        530.41.03
supported:      external
license:        NVIDIA

I note that your GPU is the RTX 3080 which is one of the newest from nvidia. That driver should support it, but more info is needed to find out why the nouveau driver is being loaded instead.

Have you tried rebooting or a power off and cold boot to see if the error is repeated?

We should be able to see the full kernel messages from the boot if you first do a clean boot then run dmesg | grep -iE 'secure|nvidia|nouveau'. The portion you posted ends before it fails on loading nvidia and falls back to nouveau.
The output from cat /proc/cmdline would also be helpful.

nimsi · April 11, 2023, 8:56pm

Similar problem. I install a clean fedora workstation, update it from the gnome store, install the nvidia driver and get exactly the same problem as the author of the thread. You can not update and immediately install the nvidia driver and the result will be the same - does not work.
Nvidia 2080

computersavvy · April 11, 2023, 10:29pm

You first need to update everything.
Then reboot so the new kernel is in use. (make sure secure boot has been disabled before the next step)
Then install the nvidia drivers.
Then reboot so the kernel modules are loaded and active.

Please provide details about where in that process you encountered the problems.

sergiomartin · April 12, 2023, 6:12pm

Same here (but with the v390 driver).

Ploblem start few days ago in a upgrade.

Later I do a:

Clean install
Upgrade system
Reboot
Install rpm fussion nvidia drivers
Wait 20 minutes
Reboot
System working with Nouveau

After install nvidia drivers systemctl list-jobs no showing any module recompiling.

Sorry about my bad english.

computersavvy · April 12, 2023, 7:10pm

Do you have secure boot enabled or disabled.?

If it is enabled the nvidia drivers will not load unless you also have the kernel modules signed and the key enrolled using mokutil.

The 390 driver may have problems with the 6.2.X kernels. It is really old, and the GPUs it supports are old as well.

You can also only use xorg as the DE with that version.

To find out if the driver is properly built and installed try dnf list installed '*nvidia*' and look for a package such as kmod-nvidia..... with your kernel version as part of the name.

select · April 12, 2023, 9:22pm

Hello everyone, sorry for the late response. @computersavvy Firtly I installed the drivers from this URL Howto/NVIDIA - RPM Fusion, and the ones that I should have isntalled are right above (and that’s what caused the confusion) provided in the link Howto/NVIDIA - RPM Fusion.

After this, I got tired of trying different solutions, so I just did a clean install, ran the correct commands and it worked. I will leave here a print of the commands that most people should be using for their drivers, since the documentation might confuse some people, as it confused me (and it is not my first time using fedora).

So, to explain it well. First do the command sudo dnf update -y (-y is optional it just makes so that you don’t have to press y and enter during the installation) and if a new Kernel is downloaded (check the output and search for it) you must update Grub (in case you are running a dual boot) so that the entry shows, if you are using UEFI: sudo grub2-mkconfig -o /etc/grub2-efi.cfg, to copy the command I always come to this link Update grub in Fedora · GitHub and look for the lfom comment. Then reboot your system and select the new kernel entry in the grub menu (again, only in dual boot, if you do not have dual boot it will automatically boot to the newest driver (I believe)). Check the kernel version by doing uname -r and make sure that it is the same as the one installed during the sudo dnf update -ycommand. After that to the command sudo dnf install akmod-nvidia and wait a couple of minutes, if you are on a laptop your fans will fire up, so usually when they calm down (fedora docs say that some systems can take up to 5 minutes in this step) you can move to the next step which is to run the command sudo dnf install xorg-x11-drv-nvidia-cuda to install cuda. This is optional, but I believe that most people will want that. Upon running this last command, run the command modinfo -F version nvidia and it should output the version of the driver such as 440.64 and not modinfo: ERROR: Module nvidia not found.. If you get the second option, I am sorry I don’t know how to fix it, but there must be a fix in some other place. If you see the driver version, then reboot the system. When it starts, run the command nvidia-smi and it should not output any error, and your nvidia driver is working. However, in case of a laptop, that usually has an intel graphics card and a Nvidia graphics card, and if you have an external monitor connected to your PC the graphics card that will load the monitor is the Intel one. To change it you must put your NVidia as the primary option, the documention is good and its here: Howto/Optimus - RPM Fusion . If you are in gnome basically you just have to run the copy command and change the file, it should look like my second image. However, one importante step is that this only works on XORG, so you must log out, click in the gear in the bottom right corner and select the Xorg option (in my case it is the last option). Reboot the system and it should be good to go.

TO the ones that aren’t able to install the drivers, this might help. If not sorry. The nvidia-smi output should be similar to my third image.

sergiomartin · April 13, 2023, 5:54am

Hello, my secure boot is disabled:

$ dmesg | grep -iE secure
[    0.000000] secureboot: Secure boot disabled
[    0.011894] secureboot: Secure boot disabled

$ dnf list installed '*nvidia*'
Paquetes instalados
akmod-nvidia-390xx.x86_64                  3:390.157-1.fc37   @rpmfusion-nonfree-updates
nvidia-gpu-firmware.noarch                 20230310-148.fc37  @updates          
nvidia-persistenced.x86_64                 3:530.41.03-1.fc37 @rpmfusion-nonfree-nvidia-driver
nvidia-settings-390xx.x86_64               390.157-1.fc37     @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-390xx.x86_64           3:390.157-2.fc37   @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-390xx-cuda.x86_64      3:390.157-2.fc37   @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-390xx-cuda-libs.x86_64 3:390.157-2.fc37   @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-390xx-kmodsrc.x86_64   3:390.157-2.fc37   @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-390xx-libs.x86_64      3:390.157-2.fc37   @rpmfusion-nonfree-updates

No kmod-nvidia... with the kernel version, only a akmod-nvidia-390xx.x86_64.

sergiomartin · April 13, 2023, 7:40am

Only for desacarting the kernel 6.2 issue, I installed openSUSE Tumbleweed with kernel 6.2.9, Nvidia drivers working perfectly.

seth-storm · April 13, 2023, 9:06am

If you have multiply video cards like intel/Nvidia, try:

sudo prime-select nvidia

Reboot.

Worked for my laptop.

select · April 13, 2023, 10:58am

Hi @sergiomartin, what is your graphics card? If it is a recent one (at least 950 and above (I believe)) I think you have the wrong drivers installed. You ran the commands from the print below which are for Nvidia GeForce 400/500.

You probably don’t want these commands since their are for old graphics cards. Probably the ones you want are the ones in the print below. For a complete guide you can follow my comment which is somewhere above this message, it is a huge comment so it should be easy to find. Initially in my installation I also installed the wrong driver version. When I noticed it I uninstalled the drivers and installed the new ones, however it did not work, I tried different solutions and nothing worked. SO I got tired, made a clean install again, ran the right commands (the ones below (it has some tricks, follow my comment somewhere above)) and it worked.

I hope you cna get it to work!

select · April 13, 2023, 11:00am

HI @seth-storm, I will check it out. I made my Nvidia as the Primary GPU, do you know that, in order to use that tool I should that for the default settings? Thanks!

sergiomartin · April 13, 2023, 11:41am

Hello @select , thanks for your help. I have an old graphics card:

NVIDIA Corporation GF116 [GeForce GTX 550 Ti] (rev a1)

It corresponds with the 390 driver, I use that driver since I have this computer years ago on diverses distributions, fedora for years, ever works, since now.

Since the error I do a clean install (yesterday) no solves the problem.

computersavvy · April 13, 2023, 6:13pm

Not at all required. The system automatically updates grub when a new kernel is installed.

I suspect the issue with the older GPU and drivers may be that the nvidia 390 driver might not be able to support the 6.2 kernel.
The fact that the 390 driver is so old and the GPUs it supports are so old means few still have computers with those old devices. It thus seems less critical to support them, especially with the rapid development pace of the kernel.

You likely could do a downgrade of your kernel to either a 6.0 or 6.1 version and the driver would then work.

The 6.1.18 kernel is available at kernel-6.1.18-200.fc37 | Build Info | koji

seth-storm · April 13, 2023, 6:33pm

I don’t know. I know that command fixed my problem with dual video card in my laptop.