No, except Lenovo never said that this hardware will support Linux. This is where I was being an idiot. So, if I were to start over how do I purge NVIDIA driver and redo everything? or do I just gave up? sigh.
This is the crux of it:
[drm:nv_drm_dev_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate NvKmsKapiDevice
The NVIDIA driver loads partially but DRM/KMS fails (Failed to allocate NvKmsKapiDevice).
@malcolmlewis Is removing the existing nvidia packages and installing the drivers the āhard wayā a viable path forward?
https://en.opensuse.org/SDB:NVIDIA_the_hard_way
Unless something changed for the current boot, the OP is not using the nvidia-drm.modeset=1 boot option.
Maybe adding nvidia-drm.modeset=1 and possibly removing sysfb.modeset=0is worth a shot given the ādual VGAā nature of the laptop?
[EDIT]: the modeset option might already have been tested before, maybe in combination with other options, not sure about the outcome.
Also, there is a recent thread that might or might not apply (Ampere arch vs. Turing here) with somewhat similar symptoms rtx-a3000-disappearing; @malcolmlewis should know better (as usual 
)
@BLP Can you check the output from cat /usr/lib/modprobe.d/50-nvidia.conf the drm option should be in there. Also lsinitrd | grep -Ei "nouveau|nvidia" and cat /proc/driver/nvidia/params
I suspect a hardware issue as indicated by @OrsoBruno.
Also check for BIOS updatesā¦
@malcolmlewis so for cat /usr/lib/modprobe.d/50-nvidia.conf is:
# Nouveau must be disabled to load the nvidia kernel module:
blacklist nouveau
# Make a soft dependency for nvidia-uvm as adding the module loading to
# /usr/lib/modules-load.d/nvidia-uvm.conf for systemd consumption, makes the
# configuration file to be added to the initrd but not the module, throwing an
# error on plymouth about not being able to find the module.
# Ref: /usr/lib/dracut/modules.d/00systemd/module-setup.sh
# Even adding the module is not the correct thing, as we don't want it to be
# included in the initrd, so use this configuration file to specify the
# dependency.
# Added also nvidia-drm since on some machines it didn't get loaded
# automatically, which resulted in Wayland sessions falling back
# to simpledrm (slow!), external monitors and switcherooctl not
# working at all.
softdep nvidia post: nvidia-drm nvidia-uvm
# Enable custom Nvidia device ownership:
options nvidia NVreg_DeviceFileUID=0
options nvidia NVreg_DeviceFileGID=483
options nvidia NVreg_DeviceFileMode=0660
# Enable complete power management. From:
# file:///usr/share/doc/packages/nvidia-common-G06/html/powermanagement.html
options nvidia NVreg_TemporaryFilePath=/var/tmp
options nvidia NVreg_EnableS0ixPowerManagement=1
options nvidia NVreg_PreserveVideoMemoryAllocations=1
# Nvidia modesetting support. Set to 0 or comment to disable kernel modesetting
# and framebuffer console support. This must be disabled in case of SLI Mosaic
# on X.
options nvidia-drm modeset=1
The result for cat /proc/driver/nvidia/params is
ResmanDebugLevel: 4294967295
RmLogonRC: 1
ModifyDeviceFiles: 1
DeviceFileUID: 0
DeviceFileGID: 483
DeviceFileMode: 432
InitializeSystemMemoryAllocations: 1
UsePageAttributeTable: 4294967295
EnableMSI: 1
EnablePCIeGen3: 0
MemoryPoolSize: 0
KMallocHeapMaxSize: 0
VMallocHeapMaxSize: 0
IgnoreMMIOCheck: 0
EnableStreamMemOPs: 0
EnableUserNUMAManagement: 1
NvLinkDisable: 0
RmProfilingAdminOnly: 1
PreserveVideoMemoryAllocations: 1
EnableS0ixPowerManagement: 1
S0ixPowerManagementVideoMemoryThreshold: 256
DynamicPowerManagement: 3
DynamicPowerManagementVideoMemoryThreshold: 200
RegisterPCIDriver: 1
EnablePCIERelaxedOrderingMode: 0
EnableResizableBar: 0
EnableGpuFirmware: 18
EnableGpuFirmwareLogs: 2
RmNvlinkBandwidthLinkCount: 0
EnableDbgBreakpoint: 0
OpenRmEnableUnsupportedGpus: 1
DmaRemapPeerMmio: 1
ImexChannelCount: 2048
CreateImexChannel0: 0
GrdmaPciTopoCheckOverride: 0
CoherentGPUMemoryMode: ""
RegistryDwords: ""
RegistryDwordsPerDevice: ""
RmMsg: ""
GpuBlacklist: ""
TemporaryFilePath: "/var/tmp"
ExcludedGpus: ""
The result for lsinitrd | grep -Ei "nouveau | nvidia" is
Bad news?
As to BIOS updates - how do I do that? Sorry. This is purely running on Opensuse. Do I install fwupmgr? or similar app?
Thank you.
I added the boot option and sadly still the same. 
I should have bought AMD. sigh.
@malcolmlewis I also did run Fwupd for updates and no update. Thanks.
So on my system I donāt see the nouveau driversā¦
You have a/usr/lib/dracut/dracut.conf.d/60-nvidia.conf file?
For BIOS updates, you need to see what the maufacturer provides. What is the date/version of your BIOS, is there an update on the Lenovo site?
@malcolmlewis yes it does:
01-dist.conf 10-unblacklist.conf 50-sg3_utils.conf 60-nvidia.conf dm-parts.conf multipath.conf
As to BIOS updates, I will re-check but Lenovo does not have an update the last time I checked. This is an old laptop. Thanks.
@BLP Not that old it has a RTX2060ā¦ So my Dell has a similar Intel GPU, itās update was last year (via fwupd) ā¦
Mobo: Dell model: 0CWR57 v: A02 serial: <filter> part-nu: 0863 UEFI: Dell v: 1.37.0
date: 06/30/2025
Do I reinstall everything? @malcolmlewis I am happy to do it.
@BLP Well nvidia drivers, remove everything related and drop back to the nouveau driver and check itās working. Then maybe try the hard way to see if that helps.
Install Windows and checkā¦
Create a live Tumbleweed USB (suggest the rescue one) and checkā¦
1 Like
@malcolmlewis Sadly, the problem is hardware. The issue persists even in Windows. I have updated all the drivers using Lenovo Vantage and all the updates and drivers from Windows 11 and the problem remain. Sigh. Tough Luck, I reckon. Thank you to you and to all how helped but this is a no go.
It feels the quality of Lenovo Legion is a far cry compared to Thinkpad. Anyway, I will reformat the laptop and go back to Opensuse Leap 16 and use it as is - without NVIDIA GPU.
@BLP Leave Windows on it and hit their support forums to see if there is something to be done, could just be a setting to activate itā¦
On a side note: I see the following from https://www.nvidia.com/en-us/drivers/details/254665/
Downgraded an error message āFailed to allocate NvKmsKapiDeviceā to an informational message āNUMA was not set up yet; ignoring this deviceā when initializing nvidia-drm in cases where initialization is expected to fail due to NUMA not being online.
One wonders is setting EnableUserNUMAManagement to zero would make a change?
Also @BLP were you running the open driver? If not, suggest trying that.
@malcolmlewis I installed the driver version equivalent in Windows, and it did not fix the issue. So, I am now thinking to just remove Windows on this laptop and take my loss and live without NVIDIA running. Sad man.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.