nvidia-smi shows "No devices were found"

Tani · 2026-08-13 10:19:22

i have lenovo ideapad gaming 3 with integrated Iris Xe graphics and dedicated GeForce GTX 1650 Mobile

> nvidia-smi
No devices were found

> lspci -k | grep -A 2 -E "(VGA|3D)"
0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
	Subsystem: Lenovo Device 3a5b
	Kernel driver in use: i915
--
0000:01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1)
	Subsystem: Lenovo Device 3a5b
	Kernel driver in use: nvidia

glxgears also produce an error

> glxgears             
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  33
  Current serial number in output stream:  34

> sudo dmesg -H | grep -iE 'nvrm|gsp|xid'
[  +0.007844] r8169 0000:02:00.0 eth0: RTL8168h/8111h, e4:a8:df:ec:5a:d9, XID 541, IRQ 173
[  +0.044292] NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  610.57.04  Release Build  (root@)  
[  +4.760710] NVRM: GPU0 s_executeBooterUcode_TU102: Booter failed with non-zero error code: 0xb
[  +0.000021] NVRM: GPU0 kgspExecuteBooterLoad_TU102: failed to execute Booter Load: 0xffff
[  +0.000001] NVRM: GPU0 kgspBootstrap_TU102: failed to execute Booter Load (ucode for initial boot): 0xffff
[  +0.000131] NVRM: GPU0 _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP
[  +0.000001] NVRM: GPU0 _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)
[  +0.000015] NVRM: GPU0 RmInitAdapter: Cannot initialize GSP firmware RM
[  +0.000739] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2119)
[  +0.000650] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
[Aug13 14:54] NVRM: GPU0 _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP
[  +0.000005] NVRM: GPU0 _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)
[  +0.000020] NVRM: GPU0 RmInitAdapter: Cannot initialize GSP firmware RM
[  +0.000716] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2119)
[  +0.000753] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
[  +0.000417] NVRM: nvAssertFailedNoLog: Assertion failed: rmapiLockIsOwner() && rmGpuLockIsOwner() @ conf_compute_api.c:81
[Aug13 15:01] NVRM: GPU0 _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP
[  +0.000006] NVRM: GPU0 _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)
[  +0.000022] NVRM: GPU0 RmInitAdapter: Cannot initialize GSP firmware RM
[  +0.000681] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2119)
[  +0.000457] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
[Aug13 15:25] NVRM: GPU0 _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP
[  +0.000006] NVRM: GPU0 _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)
[  +0.000021] NVRM: GPU0 RmInitAdapter: Cannot initialize GSP firmware RM
[  +0.000719] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2119)
[  +0.000495] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
[  +0.161286] NVRM: GPU0 _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP
[  +0.000005] NVRM: GPU0 _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)
[  +0.000020] NVRM: GPU0 RmInitAdapter: Cannot initialize GSP firmware RM
[  +0.000677] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2119)
[  +0.000600] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
[  +0.160458] NVRM: GPU0 _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP
[  +0.000012] NVRM: GPU0 _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)
[  +0.000025] NVRM: GPU0 RmInitAdapter: Cannot initialize GSP firmware RM
[  +0.000646] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2119)
[  +0.002203] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
[Aug13 15:35] NVRM: GPU0 _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP
[  +0.000006] NVRM: GPU0 _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)
[  +0.000020] NVRM: GPU0 RmInitAdapter: Cannot initialize GSP firmware RM
[  +0.000895] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2119)
[  +0.000588] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
[Aug13 15:43] NVRM: GPU0 _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP
[  +0.000006] NVRM: GPU0 _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)
[  +0.000021] NVRM: GPU0 RmInitAdapter: Cannot initialize GSP firmware RM
[  +0.000614] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2119)
[  +0.000576] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
[  +0.155426] NVRM: GPU0 _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP
[  +0.000005] NVRM: GPU0 _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)
[  +0.000020] NVRM: GPU0 RmInitAdapter: Cannot initialize GSP firmware RM
[  +0.000602] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2119)
[  +0.000487] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
[  +0.155679] NVRM: GPU0 _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP
[  +0.000006] NVRM: GPU0 _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)
[  +0.000020] NVRM: GPU0 RmInitAdapter: Cannot initialize GSP firmware RM
[  +0.000564] NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2119)
[  +0.000467] NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

seth · 2026-08-13 11:22:02

Please don't grep - post your complete system journal for the boot:

sudo journalctl -b | nc termbin.com 9999

(might be something like bumblebee/bbswitch or acpi_call powering the GPU down)
Do you dual-boot the system?

Since this is a Turing chip you could also try https://aur.archlinux.org/packages?O=0&K=580xx

Tani · 2026-08-13 12:03:23

Thanks for the reply,

https://termbin.com/q39b1

No, i do not dual-boot

seth · 2026-08-13 12:50:45

"nvidia-drm.modeset=1 nvidia_drm.fbdev=1"
Those are default anyway.

Aug 13 14:53:25 tanipartner kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5d699725-2d97-4c15-9cfb-acacfe322632 rw loglevel=3 quiet nvidia-drm.modeset=1 nvidia_drm.fbdev=1
Aug 13 14:53:25 tanipartner systemd[1]: Queued start job for default target Graphical Interface.
Aug 13 14:53:25 tanipartner systemd[1]: Starting Remount Root and Kernel File Systems...
Aug 13 14:53:25 tanipartner systemd[1]: Finished Remount Root and Kernel File Systems.
Aug 13 14:53:25 tanipartner systemd-modules-load[301]: Module 'nvidia_uvm' is deny-listed (by kmod)
Aug 13 14:53:29 tanipartner systemd[1]: Reached target Graphical Interface.
Aug 13 14:53:30 tanipartner dbus-broker-launch[593]: Service file '/usr/share/dbus-1/services/org.erikreider.swaync.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Aug 13 14:53:37 tanipartner dbus-broker-launch[649]: Service file '/usr/share/dbus-1/services/org.erikreider.swaync.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Aug 13 14:53:38 tanipartner kernel: nvidia: loading out-of-tree module taints kernel.
Aug 13 14:53:38 tanipartner kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Aug 13 14:53:38 tanipartner kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 509
Aug 13 14:53:38 tanipartner kernel: nvidia 0000:01:00.0: enabling device (0006 -> 0007)
Aug 13 14:53:38 tanipartner kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  610.57.04  Release Build  (root@)  
Aug 13 14:53:40 tanipartner systemd[636]: Starting Swaync notification daemon...
Aug 13 14:53:40 tanipartner swaync[1036]: Starting SwayNotificationCenter version swaync 0.12.6
Aug 13 14:53:40 tanipartner swaync[1036]: configModel.vala:513: Loading Config: "/home/tani/.config/swaync/config.json"

System boots, nvidia modules load (late) after the root switch and AFTER the graphical target is reached, sway is starting somewhen around that.

Aug 13 14:53:42 tanipartner systemd[636]: swaync.service: Main process exited, code=exited, status=1/FAILURE
Aug 13 14:53:42 tanipartner systemd[636]: swaync.service: Failed with result 'exit-code'.
Aug 13 14:53:42 tanipartner systemd[636]: Failed to start Swaync notification daemon.
Aug 13 14:53:42 tanipartner systemd[636]: swaync.service: Scheduled restart job, restart counter is at 5.
Aug 13 14:53:42 tanipartner systemd[636]: swaync.service: Start request repeated too quickly.
Aug 13 14:53:42 tanipartner systemd[636]: swaync.service: Failed with result 'start-limit-hit'.
Aug 13 14:53:42 tanipartner systemd[636]: Failed to start Swaync notification daemon.
Aug 13 14:53:43 tanipartner kernel: NVRM: GPU0 s_executeBooterUcode_TU102: Booter failed with non-zero error code: 0xb
Aug 13 14:53:43 tanipartner kernel: NVRM: GPU0 kgspExecuteBooterLoad_TU102: failed to execute Booter Load: 0xffff
Aug 13 14:53:43 tanipartner kernel: NVRM: GPU0 kgspBootstrap_TU102: failed to execute Booter Load (ucode for initial boot): 0xffff
Aug 13 14:53:43 tanipartner kernel: NVRM: GPU0 _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP
Aug 13 14:53:43 tanipartner kernel: NVRM: GPU0 _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)
Aug 13 14:53:43 tanipartner kernel: NVRM: GPU0 RmInitAdapter: Cannot initialize GSP firmware RM
Aug 13 14:53:43 tanipartner kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2119)
Aug 13 14:53:43 tanipartner kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

swayenc produces a lot of errors, ultimately bails and THEN the nvidia errors pop up.

Step #1, only boot the multi-user.target (2nd link below) and check nvidia-smi from there.
If it responds, manually progress to the graphical target (starting sway) and see whether that changes anything about the GPU.

Might just be a race condition.

Tani · 2026-08-13 13:05:52

Thanks for the reply

Still gives "No devices were found" after booting the multi-user.target

seth · 2026-08-13 13:14:02

https://forums.developer.nvidia.com/t/n … 14s/350097
You might want to check whether firmware (UEFI) updates are available for your device

https://github.com/ublue-os/bazzite/issues/4494

I was able to resolve this issue by delete all nvidia*.conf in /etc/modprobe.d/ directory.

Don't just do that, but why are you blacklisting nvidia_uvm?

modprobe -c | grep -v alias | grep nvidia

W/ the closed source 580xx driver you may try to disable the https://wiki.archlinux.org/title/NVIDIA … P_firmware to possibly side-step this (this will not work w/ nvidia-open, it critically depends on the GSP)

Tani · 2026-08-13 13:41:52

Yes , firmware is up to date last update for my firmware was in 2024

Deleted my nvidia.conf, still the error

i am not blacklisting nvidia_uvm , i believe its in my mkinitcpio so it builts into the intramfs and systemd shows the error as its already loaded

> modprobe -c | grep -v alias | grep nvidia
options nvidia NVreg_UseKernelSuspendNotifiers=1
options nvidia NVreg_TemporaryFilePath=/var/tmp
options nvidia_drm modeset=1
options nvidia_drm fbdev=1
softdep nvidia pre: ecdh_generic,ecdsa_generic

I will try the 580xx version and report again if it solves it.

seth · 2026-08-13 13:50:31

Deleted my nvidia.conf, still the error

seth wrote:

Don't just do that

What "your" nvidia.conf, which file specifically - and what were the contents?

Tani · 2026-08-13 13:59:59

/etc/modprobe.d/nvidia.conf

it just had nvidia-drm.modeset=1 nvidia_drm.fbdev=1 which as you said are the defaults anyway

Tani · 2026-08-13 14:19:22

switching to 580xx and disabling gsp also did not fix the error

new system journal: https://termbin.com/292r

seth · 2026-08-13 14:50:14

Aug 13 19:40:21 tanipartner kernel: pci 0000:01:00.0: 31.504 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x4 link at 0000:00:1c.0 (capable of 252.048 Gb/s with 16.0 GT/s PCIe x16 link)
Aug 13 19:40:21 tanipartner kernel: pci 0000:01:00.0: ROM [mem 0xfff80000-0xffffffff pref]: can't claim; no compatible bridge window
Aug 13 19:40:21 tanipartner kernel: pci 0000:01:00.0: ROM [mem size 0x00080000 pref]: can't assign; no space
Aug 13 19:40:21 tanipartner kernel: pci 0000:01:00.0: ROM [mem size 0x00080000 pref]: failed to assign
Aug 13 19:40:21 tanipartner kernel: nvidia 0000:01:00.0: enabling device (0006 -> 0007)
Aug 13 19:40:21 tanipartner kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x24:0x72:1603)
Aug 13 19:40:21 tanipartner kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Aug 13 19:40:21 tanipartner kernel: DMI: LENOVO 82K1/LNVNB161216, BIOS H4CN25WW(V1.10) 06/14/2022

The firmware is from 2022… does it allow you to toggle rebar or other devices (wifi, camera, …)?

Does it help to add "pci=nocrs" to the https://wiki.archlinux.org/title/Kernel_parameters ?
Do you run into this w/ the LTS kernel or eg. https://grml.org ("can't assign; no space" is unrelated to the nvidia driver)

Tani · 2026-08-13 17:20:25

No, it does not allow toggling rebar or any other device

pci=nocrs did not help

i had a ubuntu live usb so i tried this there

ubuntu@ubuntu:~$ sudo dmesg | grep -iE 'nvrm|nouveau|rminitadapter'
[    3.036508] nouveau 0000:01:00.0: enabling device (0006 -> 0007)
[    3.036594] nouveau 0000:01:00.0: unknown chipset (167000a1)
[    3.036628] nouveau 0000:01:00.0: probe of 0000:01:00.0 failed with error -12

seth · 2026-08-13 18:23:35

12 is ENOMEM, same condition.

Aug 13 19:40:21 tanipartner kernel: pci 0000:00:1f.5: BAR 0 [mem 0xfe010000-0xfe010fff]: can't claim; no compatible bridge window
Aug 13 19:40:21 tanipartner kernel: pci 0000:01:00.0: ROM [mem 0xfff80000-0xffffffff pref]: can't claim; no compatible bridge window
Aug 13 19:40:21 tanipartner kernel: pci 0000:01:00.0: ROM [mem size 0x00080000 pref]: can't assign; no space
Aug 13 19:40:21 tanipartner kernel: pci 10000:e0:06.0: bridge window [io  size 0x1000]: can't assign; no space
Aug 13 19:40:21 tanipartner kernel: pci 10000:e0:17.0: BAR 4 [io  size 0x0020]: can't assign; no space
Aug 13 19:40:21 tanipartner kernel: pci 10000:e0:17.0: BAR 2 [io  size 0x0008]: can't assign; no space
Aug 13 19:40:21 tanipartner kernel: pci 10000:e0:17.0: BAR 3 [io  size 0x0004]: can't assign; no space
Aug 13 19:40:21 tanipartner kernel: pci 10000:e0:06.0: bridge window [io  size 0x1000]: can't assign; no space
Aug 13 19:40:21 tanipartner kernel: pci 10000:e0:17.0: BAR 4 [io  size 0x0020]: can't assign; no space
Aug 13 19:40:21 tanipartner kernel: pci 10000:e0:17.0: BAR 2 [io  size 0x0008]: can't assign; no space
Aug 13 19:40:21 tanipartner kernel: pci 10000:e0:17.0: BAR 3 [io  size 0x0004]: can't assign; no space
Aug 13 19:40:21 tanipartner kernel: pcieport 10000:e0:06.0: can't derive routing for PCI INT D
Aug 13 19:40:21 tanipartner kernel: ahci 10000:e0:17.0: can't derive routing for PCI INT A
Aug 13 19:40:21 tanipartner kernel: pcieport 10000:e0:06.0: can't derive routing for PCI INT A

Did you change anything about the HW?
(Replaced drive, wifi, …)?

Do you have other related BIOS options (above 4G decoding, SR-IOV support)?

lassiness · 2026-08-14 05:39:33

Hey there! I also used to have similar problems like this. If you're using the nouveau drivers, ditch them and get the "nvidia" drivers with the addition of "nvidia-utils" and "lib32-nvidia-utils". AND if you're using a different kernel make sure to get the respective "linux-XXXX-headers" along with the "nvidia-dkms" package instead of the normal one. make sure to enable the multilib and extra repo in your pacman.conf before doing so. after installation, edit your grub to have
GRUB_CMDLINE_LINUX_DEFAULT="nvidia-drm.modeset=1"
then regenerate the grub config with "sudo grub-mkconfig -o /boot/grub/grub.cfg"
then reboot and report here if it works

seth · 2026-08-14 07:29:11

The OP wrote:

0000:01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1)
Subsystem: Lenovo Device 3a5b
Kernel driver in use: nvidia

Whatever your problem was/is, that's not the OPs one - their device doesn't work because the bus cannot be addressed.

Tani · 2026-08-14 11:30:26

No change in HW

No options for 4g decoding or sr-iov support either

Is there a chance that its just broken/faulty gpu?

seth · 2026-08-14 15:05:23

There's always a chance, but a bogus bus layout is rather not caused by a fused GPU core…
On a desktop I'd say you put the GPU into the wrong PCI slot, but that's not an option here

Does a later bus rescan allow the GPU to be addressed?
https://stackoverflow.com/questions/323 … f-pcie-bus

You're sure that you cannot disable *any* devices in the BIOS? Not even the IGP or GPU?

Tani · 2026-08-14 16:08:44

Just checked bios menu again, i can disable wifi and GPU (not igpu)

did try disabling wifi but still got the same error

seth · 2026-08-14 17:51:34

Have to tried to … turn it off and back on again?
(Ie. the gpu: disable it, boot, re-enable it, boot again… any changes?)

Tani · 2026-08-14 18:03:21

sorry for using vague language,

yes i did exactly that, disabled it, re enabled it , no changes

Lone_Wolf · 2026-08-15 13:32:19

Wifi and bluetooth are often provided by the same chip which stays active if only one of them is disabled .
Please try disabling both for testing purposes .

seth · 2026-08-15 15:49:23

And for clarification, because #18 does not say that at all: you did try to toggle the GPU (not only the wifi)?

Tani · 2026-08-15 17:17:10

yes i did toggle the gpu too

i have
i)disabled only the wifi
ii)disabled only the gpu
ii) disabled both

still the same erros after renabling each time

Tani · 2026-08-15 17:18:44

is there any software that can give more information on what could be the problem?

seth · 2026-08-15 19:37:47

The problem is that the device is not addressable - usually that's a bad hardware config or bogus BIOS.
For a notebook "bad hardware config" should™ not be a thing.

Does adding "pci=realloc" to the kernel parameters help (should have asked that before instead/along nocrs)

Otherwise you could try to lie to the BIOS and see whether that changes anything

acpi_osi=! acpi_osi="Windows 2015"

https://learn.microsoft.com/en-us/windo … inacpi-osi

Arch Linux

#1 2026-08-13 10:19:22

nvidia-smi shows "No devices were found"

#2 2026-08-13 11:22:02

Re: nvidia-smi shows "No devices were found"

#3 2026-08-13 12:03:23

Re: nvidia-smi shows "No devices were found"

#4 2026-08-13 12:50:45

Re: nvidia-smi shows "No devices were found"

#5 2026-08-13 13:05:52

Re: nvidia-smi shows "No devices were found"

#6 2026-08-13 13:14:02

Re: nvidia-smi shows "No devices were found"

#7 2026-08-13 13:41:52

Re: nvidia-smi shows "No devices were found"

#8 2026-08-13 13:50:31

Re: nvidia-smi shows "No devices were found"

#9 2026-08-13 13:59:59

Re: nvidia-smi shows "No devices were found"

#10 2026-08-13 14:19:22

Re: nvidia-smi shows "No devices were found"

#11 2026-08-13 14:50:14

Re: nvidia-smi shows "No devices were found"

#12 2026-08-13 17:20:25

Re: nvidia-smi shows "No devices were found"

#13 2026-08-13 18:23:35

Re: nvidia-smi shows "No devices were found"

#14 2026-08-14 05:39:33

Re: nvidia-smi shows "No devices were found"

#15 2026-08-14 07:29:11

Re: nvidia-smi shows "No devices were found"

#16 2026-08-14 11:30:26

Re: nvidia-smi shows "No devices were found"

#17 2026-08-14 15:05:23

Re: nvidia-smi shows "No devices were found"

#18 2026-08-14 16:08:44

Re: nvidia-smi shows "No devices were found"

#19 2026-08-14 17:51:34

Re: nvidia-smi shows "No devices were found"

#20 2026-08-14 18:03:21

Re: nvidia-smi shows "No devices were found"

#21 2026-08-15 13:32:19

Re: nvidia-smi shows "No devices were found"

#22 2026-08-15 15:49:23

Re: nvidia-smi shows "No devices were found"

#23 2026-08-15 17:17:10

Re: nvidia-smi shows "No devices were found"

#24 2026-08-15 17:18:44

Re: nvidia-smi shows "No devices were found"

#25 2026-08-15 19:37:47

Re: nvidia-smi shows "No devices were found"

Board footer