Nvidia gpu seems to not be found or recognized

So i was checking my driver with nvidia-smi and it shows NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. lsmod doesn’t show nvidia or nouveau, and i have the latest driver (515 dot something), dmesg shows NVRM: No NVIDIA GPU found. multiple times (cl1p.net - The internet clipboard). I have registered nvidia driver to secure boot in the past, disabling it doesn’t help, booting to older kernels either.

And my laptop have intel gpu, if that helps.

1 Like

Please check these command:

glxinfo | egrep "OpenGL vendor|OpenGL renderer"

How to knows your GPU?

lspci | grep -e VGA

The message is the following:

NVRM: No NVIDIA GPU found.
[   51.576741] nvidia-nvlink: Unregistered Nvlink Core, major device number 509

Your GPU is not supported by this drivers: 515

Suggestions

Please visit this NVIDIA page and check what is the last NVIDIA drivers support your GPU

More Information

dmesg | grep -iE 'secure|nvidia'
journalctl -b | grep nvidia

also this command the know the NVIDIA version installed in your system:

dnf list installed \*nvidia\*

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.

This ERROR means your NVIDIA module is not load… by the error mentioned before, you can check with this command:

lsmod | grep nvidia

More Information

https://rpmfusion.org/Howto/NVIDIA

Regards.,

2 Likes

We need to know what nvidia GPU you have.
Please post the output of dmesg | grep -iE 'secure|nvidia' and inxi -Fzx in </> Preformatted text tags so we can see what the system is seeing about that adapter.

Thanks for replying,
glxinfo shows

OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics (TGL GT1)

lspci shows

0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-H GT1 [UHD Graphics] (rev 01)

My gpu is supported, it’s RTX 3050 Laptop GPU

dmesg:

[    0.000000] Command line: BOOT_IMAGE=(hd0,gpt7)/vmlinuz-5.19.11-200.fc36.x86_64 root=UUID=cd058225-55b0-4869-80bb-155734bd5a5d ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init
[    0.000000] secureboot: Secure boot enabled
[    0.000000] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
[    0.016648] secureboot: Secure boot enabled
[    0.078931] Kernel command line: BOOT_IMAGE=(hd0,gpt7)/vmlinuz-5.19.11-200.fc36.x86_64 root=UUID=cd058225-55b0-4869-80bb-155734bd5a5d ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init
[    1.205387] integrity: Loaded X.509 cert 'Fedora Secure Boot CA: fde32599c2d61db1bf5807335d7b20e4cd963b42'
[    8.440315] nvidia: loading out-of-tree module taints kernel.
[    8.440327] nvidia: module license 'NVIDIA' taints kernel.
[    8.510554] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[    8.510560] NVRM: No NVIDIA GPU found.
[    8.511061] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[    9.583032] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[    9.583036] NVRM: No NVIDIA GPU found.
[    9.583707] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   15.762271] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   15.762277] NVRM: No NVIDIA GPU found.
[   15.762857] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   17.562789] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   17.562810] NVRM: No NVIDIA GPU found.
[   17.563751] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   61.073604] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   61.073611] NVRM: No NVIDIA GPU found.
[   61.074643] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   64.819103] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   64.819113] NVRM: No NVIDIA GPU found.
[   64.820789] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   66.291002] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   66.291009] NVRM: No NVIDIA GPU found.
[   66.292003] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   99.260191] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   99.260197] NVRM: No NVIDIA GPU found.
[   99.260697] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[  100.128911] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[  100.128917] NVRM: No NVIDIA GPU found.
[  100.129438] nvidia-nvlink: Unregistered Nvlink Core, major device number 509

journalctl:

Oct 13 11:15:13 super-power kernel: Command line: BOOT_IMAGE=(hd0,gpt7)/vmlinuz-5.19.11-200.fc36.x86_64 root=UUID=cd058225-55b0-4869-80bb-155734bd5a5d ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init
Oct 13 11:15:13 super-power kernel: Kernel command line: BOOT_IMAGE=(hd0,gpt7)/vmlinuz-5.19.11-200.fc36.x86_64 root=UUID=cd058225-55b0-4869-80bb-155734bd5a5d ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init
Oct 13 11:15:13 super-power dracut-cmdline[323]: Using kernel command line parameters:  rd.driver.pre=btrfs   BOOT_IMAGE=(hd0,gpt7)/vmlinuz-5.19.11-200.fc36.x86_64 root=UUID=cd058225-55b0-4869-80bb-155734bd5a5d ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init
Oct 13 04:15:18 super-power systemd[1]: Starting nvidia-powerd.service - nvidia-powerd service...
Oct 13 04:15:18 super-power /usr/bin/nvidia-powerd[873]: nvidia-powerd version:1.0(build 1)
Oct 13 04:15:19 super-power kernel: nvidia: loading out-of-tree module taints kernel.
Oct 13 04:15:19 super-power kernel: nvidia: module license 'NVIDIA' taints kernel.
Oct 13 04:15:19 super-power kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509
Oct 13 04:15:19 super-power kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 509
Oct 13 04:15:20 super-power kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509
Oct 13 04:15:20 super-power kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 509
Oct 13 04:15:20 super-power /usr/bin/nvidia-powerd[873]: Allocate client failed 38
Oct 13 04:15:20 super-power systemd[1]: nvidia-powerd.service: Main process exited, code=exited, status=1/FAILURE
Oct 13 04:15:20 super-power /usr/bin/nvidia-powerd[873]: Failed to initialize RM Client
Oct 13 04:15:20 super-power systemd[1]: nvidia-powerd.service: Failed with result 'exit-code'.
Oct 13 04:15:20 super-power systemd[1]: Failed to start nvidia-powerd.service - nvidia-powerd service.
Oct 13 04:15:20 super-power audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-powerd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Oct 13 04:15:20 super-power systemd[1]: nvidia-powerd.service: Consumed 1.465s CPU time.
Oct 13 04:15:27 super-power kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509
Oct 13 04:15:27 super-power kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 509
Oct 13 04:15:28 super-power kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509
Oct 13 04:15:28 super-power kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 509
Oct 13 04:16:12 super-power /usr/libexec/gdm-x-session[1906]: Kernel command line: BOOT_IMAGE=(hd0,gpt7)/vmlinuz-5.19.11-200.fc36.x86_64 root=UUID=cd058225-55b0-4869-80bb-155734bd5a5d ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init
Oct 13 04:16:13 super-power kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509
Oct 13 04:16:13 super-power kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 509
Oct 13 04:16:15 super-power systemd[1866]: Started app-glib-nvidia\x2dsettings\x2duser-2482.scope - Application launched by gnome-session-binary.
Oct 13 04:16:15 super-power systemd[1866]: Started app-gnome-nvidia\x2dsettings\x2duser-2482.scope - Application launched by gnome-session-binary.
Oct 13 04:16:16 super-power kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509
Oct 13 04:16:16 super-power kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 509
Oct 13 04:16:18 super-power kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509
Oct 13 04:16:18 super-power kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 509
Oct 13 04:16:18 super-power nvidia-settings-user.desktop[2482]: ERROR: NVIDIA driver is not loaded
Oct 13 04:16:22 super-power packagekitd[1446]: Failed to get cache filename for nvidia-gpu-firmware
Oct 13 04:16:51 super-power kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509
Oct 13 04:16:51 super-power kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 509
Oct 13 04:16:52 super-power kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509
Oct 13 04:16:52 super-power kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 509

It looks like i have 515.65 driver and 20220815-139.fc36 nvidia-gpu-firmware.noarch

And lsmod | grep nvidia outputs nothing.

It’s RTX 3050 Mobile GPU

inxi output:

System:
  Kernel: 5.19.11-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-36.fc36 Desktop: GNOME v: 42.5 Distro: Fedora release 36 (Thirty
    Six)
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming F15 FX506HC_FX506HC
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: FX506HC v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: FX506HC.310 date: 11/25/2021
Battery:
  ID-1: BAT1 charge: 38.5 Wh (87.5%) condition: 44.0/48.1 Wh (91.5%)
    volts: 11.5 min: 11.7 model: ASUS A32-K55 status: discharging
CPU:
  Info: 6-core model: 11th Gen Intel Core i5-11400H bits: 64 type: MT MCP
    arch: Tiger Lake rev: 1 cache: L1: 480 KiB L2: 7.5 MiB L3: 12 MiB
  Speed (MHz): avg: 2441 high: 2700 min/max: 800/4500 cores: 1: 2700
    2: 2700 3: 2700 4: 2700 5: 2700 6: 2700 7: 2700 8: 2700 9: 2700 10: 2700
    11: 995 12: 1306 bogomips: 64512
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel TigerLake-H GT1 [UHD Graphics] vendor: ASUSTeK driver: i915
    v: kernel arch: Gen-12.1 bus-ID: 0000:00:02.0
  Device-2: Sonix USB2.0 HD UVC WebCam type: USB driver: uvcvideo
    bus-ID: 3-7:3
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3 driver: X:
    loaded: modesetting unloaded: fbdev,vesa gpu: i915
    resolution: 1920x1080~144Hz
  OpenGL: renderer: Mesa Intel UHD Graphics (TGL GT1) v: 4.6 Mesa 22.1.7
    direct render: Yes
Audio:
  Device-1: Intel Tiger Lake-H HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 0000:00:1f.3
  Sound Server-1: ALSA v: k5.19.11-200.fc36.x86_64 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.58 running: yes
Network:
  Device-1: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
    vendor: AzureWave driver: mt7921e v: kernel bus-ID: 0000:2d:00.0
  IF: wlp45s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: 3000 bus-ID: 0000:2e:00.0
  IF: enp46s0 state: down mac: <filter>
Bluetooth:
  Device-1: IMC Networks Wireless_Device type: USB driver: btusb v: 0.8
    bus-ID: 3-14:4
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 bus-ID: 0000:00:0e.0
Drives:
  Local Storage: total: 476.94 GiB used: 28.49 GiB (6.0%)
  ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNU512GZ size: 476.94 GiB
    temp: 32.9 C
Partition:
  ID-1: / size: 117.95 GiB used: 28.18 GiB (23.9%) fs: btrfs
    dev: /dev/nvme0n1p8
  ID-2: /boot size: 973.4 MiB used: 274.9 MiB (28.2%) fs: ext4
    dev: /dev/nvme0n1p7
  ID-3: /boot/efi size: 256 MiB used: 41.6 MiB (16.3%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 117.95 GiB used: 28.18 GiB (23.9%) fs: btrfs
    dev: /dev/nvme0n1p8
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 44.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 320 Uptime: 15m Memory: 15.37 GiB used: 2.46 GiB (16.0%)
  Init: systemd target: graphical (5) Compilers: gcc: 12.2.1 Packages: 17
  note: see --rpm Shell: Zsh v: 5.8.1 inxi: 3.3.21

You claim it is an nvidia 3050 but inxi does not see it, and the kernel is unable to load the driver at boot time.

Secure boot is enabled.
Have you followed the steps to either disable secure boot (which will then allow an unsigned module to load)?
or to sign the kernel module so it loads with secure boot enabled.?
https://rpmfusion.org/Howto/Secure%20Boot?highlight=(\bCategoryHowto\b)

I have tried to disable the secure boot from EFI and it still doesn’t work, and i have registered the modules in the past. Maybe it’s possible to re-register the modules just to make sure?

Faulty modules will act similarly.
I am assuming you installed the nvidia driver from rpmfusion.
Please post the output of dnf list installed '*nvidia*' so we can see exactly what is installed for you.

@northnsouth

Graphics:
  Device-1: Intel TigerLake-H GT1 [UHD Graphics] vendor: ASUSTeK driver: i915
    v: kernel arch: Gen-12.1 bus-ID: 0000:00:02.0
  Device-2: Sonix USB2.0 HD UVC WebCam type: USB driver: uvcvideo
    bus-ID: 3-7:3
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3 driver: X:
    loaded: modesetting unloaded: fbdev,vesa gpu: i915
    resolution: 1920x1080~144Hz

the conclusion for this output is:

your GPU is Intel TigerLake-H GT1 [UHD Graphics]
you KERNEL driver for this GPU is gpu: i915 intel

you could please run sudo nvidia-bug-report.sh and add nvidia-bug-report.log here, WARNING it’s quite large so use preformat utils here…

Regards.,

Yes i installed it from rpmfusion.

Here’s the output you asked:

akmod-nvidia.x86_64                        3:515.65.01-1.fc36 @rpmfusion-nonfree-nvidia-driver
kmod-nvidia-5.18.18-200.fc36.x86_64.x86_64 3:515.65.01-1.fc36 @@commandline     
kmod-nvidia-5.19.11-200.fc36.x86_64.x86_64 3:515.65.01-1.fc36 @@commandline     
nvidia-gpu-firmware.noarch                 20220815-139.fc36  @updates          
nvidia-persistenced.x86_64                 3:515.65.01-1.fc36 @rpmfusion-nonfree-nvidia-driver
nvidia-settings.x86_64                     3:515.65.01-1.fc36 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia.x86_64                 3:515.65.01-1.fc36 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda.x86_64            3:515.65.01-1.fc36 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-cuda-libs.x86_64       3:515.65.01-1.fc36 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-kmodsrc.x86_64         3:515.65.01-1.fc36 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-libs.x86_64            3:515.65.01-1.fc36 @rpmfusion-nonfree-nvidia-driver
xorg-x11-drv-nvidia-power.x86_64           3:515.65.01-1.fc36 @rpmfusion-nonfree-nvidia-driver

The log exceeds char limit, so please visit cl1p .net/log

You have an intel GPU, as shown by the inxi output you posted.
If you also have an nvidia GPU with the fairly common dual GPU config found in many laptops then the system is not seeing that at all.

Also, with the posted output of the installed nvidia packages you seem to not have updated frequently or recently since the kmod-nvidia packages were only built for the 5.18.18 & 5.19.11 kernels. Your version of the nvidia driver is 515.65.01 while the latest nvidia driver is 515.76.

All this leads me to question whether you actually have an nvidia GPU installed. If you do then this may be an issue at the hardware level since it seems that system is not actually seeing the device at all. I see that the specs for that laptop show that a GTX 1660 Ti should be installed.

As a first step I would recommend the following

  1. Remove all the nvidia drivers.
    sudo dnf remove '*nvidia*'
  2. Update the system fully
    sudo dnf upgrade --refresh
  3. Wait at least 5 minutes after the upgrade completes then reboot.
  4. reinstall the nvidia drivers.
    sudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda
  5. Wait at least 5 minutes after the install completes then reboot.
  6. Now check the status of the nvidia drivers
    lsmod | grep -iE 'nouveau|nvidia'
    lspci | grep VGA
    If the nvidia card still has no drivers activated then it seems certain to be a hardware issue. If the output of lspci does not show the nvidia GPU then it certainly is a hardware issue.
    I have an asus laptop and mine shows
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630]
01:00.0 VGA compatible controller: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] (rev a1)

system update installs a new kernel 5.19.14-200 previously 5.19.11-200, but now i can’t use wifi on both kernel! @computersavvy

With ethernet connection, i did what you wrote but it still doesn’t work. How is it a hardware issue if nvidia works perfectly fine in windows?

Did you follow the steps I listed?
Were there any changes?

In step 6 I said
If the nvidia card still has no drivers activated then it seems certain to be a hardware issue. If the output of lspci does not show the nvidia GPU then it certainly is a hardware issue.

How does that read It is a hardware issue? To me and almost everyone else it would read If all the above (steps 1-5) fail then it seems it may be hardware. All the steps above are about making sure that the software is up to date, and step 6 is certainly about verifying both the drivers and the hardware are seen.

The key fallacy in your interpretation is that you seem to be assuming that because it works in windows it has to work in linux, which is like comparing apples and rocks. Totally different.

Maybe if you were to post the results of some of those steps, including the output of the commands in step 6 we could have more info to potentially assist further.
Please also post the output of dmesg | grep -iE 'secure|nvidia'

I did follow the steps you listed, and i see no changes.

Alright here are the outputs

Step 6
lsmod outputs nothing.
0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-H GT1 [UHD Graphics] (rev 01)

And here’s the dmesg

[    0.000000] Command line: BOOT_IMAGE=(hd0,gpt7)/vmlinuz-5.19.15-201.fc36.x86_64 root=UUID=cd058225-55b0-4869-80bb-155734bd5a5d ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init
[    0.000000] secureboot: Secure boot enabled
[    0.000000] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
[    0.016301] secureboot: Secure boot enabled
[    0.078633] Kernel command line: BOOT_IMAGE=(hd0,gpt7)/vmlinuz-5.19.15-201.fc36.x86_64 root=UUID=cd058225-55b0-4869-80bb-155734bd5a5d ro rootflags=subvol=root rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init
[    1.213301] integrity: Loaded X.509 cert 'Fedora Secure Boot CA: fde32599c2d61db1bf5807335d7b20e4cd963b42'
[    8.370099] nvidia: loading out-of-tree module taints kernel.
[    8.370110] nvidia: module license 'NVIDIA' taints kernel.
[    8.439964] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[    8.439970] NVRM: No NVIDIA GPU found.
[    8.440472] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[    9.464793] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[    9.464798] NVRM: No NVIDIA GPU found.
[    9.465351] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   15.633769] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   15.633775] NVRM: No NVIDIA GPU found.
[   15.634804] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   17.580381] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   17.580388] NVRM: No NVIDIA GPU found.
[   17.581327] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   25.587174] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   25.587180] NVRM: No NVIDIA GPU found.
[   25.588121] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   28.949964] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   28.949970] NVRM: No NVIDIA GPU found.
[   28.951200] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   30.285136] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   30.285143] NVRM: No NVIDIA GPU found.
[   30.285848] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   35.522018] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   35.522025] NVRM: No NVIDIA GPU found.
[   35.522786] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   48.486083] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   48.486093] NVRM: No NVIDIA GPU found.
[   48.486910] nvidia-nvlink: Unregistered Nvlink Core, major device number 509
[   49.496611] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[   49.496618] NVRM: No NVIDIA GPU found.
[   49.497294] nvidia-nvlink: Unregistered Nvlink Core, major device number 509

Hello @northnsouth ,
Have you checked your BIOS settings to make sure they are not affecting the distro seeing your GPU? I would think the laptop GPU is also subtly different than actually having the corresponding RTX card, just saying embedded usually changes things on the driver front. If the hardware is new enough, a wait for a kernel update may be in order.

You also did not post the output of lspci | grep VGA.
That should show both GPUs
You may also try lspci | grep -i nvidia

At least one of those should show the nvidia GPU. If both fail to display the nvidia gpu then it seems hardware failure, or as noted above possibly bios related.

You do seem to have secure boot enabled which can prevent loading the nvidia driver even if the driver is properly installed, though it would not prevent seeing it with the lspci command.

You also should have the nvidia firmware installed.

# dnf list installed nvidia*firmware*
Installed Packages
nvidia-gpu-firmware.noarch                                                  20220913-140.fc36                                                   @updates

I have good news, the card works now magically

lspci | grep VGA

0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-H GT1 [UHD Graphics] (rev 01)
0000:01:00.0 VGA compatible controller: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] (rev a1)

nvidia-smi

+-----------------------------------------------------------------------------+
| NVIDIA-SMI 515.65.01    Driver Version: 515.65.01    CUDA Version: 11.7     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0 Off |                  N/A |
| N/A   51C    P0    N/A /  N/A |      3MiB /  4096MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      2060      G   /usr/bin/gnome-shell                1MiB |
+-----------------------------------------------------------------------------+

I’m not sure about what happened, but this issue resolved after a few hours since i installed linux-firmware package that comes with nvidia-gpu-firmware package.

I did that install to resolve the wireless adapter issue.

1 Like

Good deal! :thinking:

It almost sounds like the firmware was not properly loading so the driver could not be properly loaded. Glad you were able to find a solution.

:smiley:

1 Like