NVIDIA GA106M driver N/A


I tried some stuff but kept coming across people saying "Just use the HW Manager and install the drivers it tells you to and everything will work", so I didn't go too crazy. Did try switching to the lts kernel, but doesn't seem to have made a difference. Any help is much appreciated as Garuda was my daily-driver on my previous laptop (for the last few months anyway), and I like it.

λ inxi -Faz
Kernel: 5.15.15-1-lts x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=fe91b2eb-c119-4b19-9787-1122098c2bc8 rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Type: Laptop System: Dell product: XPS 17 9710 v: N/A
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Dell model: 0J98F4 v: A00 serial: <superuser required> UEFI: Dell
v: 1.5.3 date: 11/13/2021
ID-1: BAT0 charge: 95.1 Wh (100.0%) condition: 95.1/95.1 Wh (100.0%)
volts: 13.1 min: 11.4 model: BYD DELL F8CPG1A type: Li-poly
serial: <filter> status: Full
Info: model: 11th Gen Intel Core i9-11900H bits: 64 type: MT MCP
arch: Tiger Lake family: 6 model-id: 0x8D (141) stepping: 1 microcode: 0x34
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 10 MiB desc: 8x1.2 MiB
L3: 24 MiB desc: 1x24 MiB
Speed (MHz): avg: 975 high: 1250 min/max: 800/4800:4900 scaling:
driver: intel_pstate governor: powersave cores: 1: 1044 2: 801 3: 925
4: 1250 5: 1128 6: 960 7: 801 8: 963 9: 1125 10: 1148 11: 801 12: 897
13: 869 14: 976 15: 789 16: 1135 bogomips: 79872
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Device-1: Intel TigerLake-H GT1 [UHD Graphics] vendor: Dell driver: i915
v: kernel bus-ID: 0000:00:02.0 chip-ID: 8086:9a60 class-ID: 0300
Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Dell
driver: N/A alternate: nouveau bus-ID: 0000:01:00.0 chip-ID: 10de:2520
class-ID: 0300
Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
bus-ID: 3-11:4 chip-ID: 0c45:6a11 class-ID: 0e02
Display: x11 server: X.Org compositor: kwin_x11 driver:
loaded: intel unloaded: modesetting alternate: fbdev,vesa display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 508x317mm (20.0x12.5")
s-diag: 599mm (23.6")
Monitor-1: eDP1 res: 1920x1200 hz: 60 dpi: 132
size: 370x230mm (14.6x9.1") diag: 436mm (17.2")
Message: Unable to show advanced data. Required tool glxinfo missing.
Device-1: Intel Tiger Lake-H HD Audio vendor: Dell
driver: sof-audio-pci-intel-tgl
alternate: snd_hda_intel,snd_sof_pci_intel_tgl bus-ID: 0000:00:1f.3
chip-ID: 8086:43c8 class-ID: 0401
Device-2: NVIDIA vendor: Dell driver: snd_hda_intel v: kernel
bus-ID: 0000:01:00.1 chip-ID: 10de:228e class-ID: 0403
Sound Server-1: ALSA v: k5.15.15-1-lts running: yes
Sound Server-2: JACK v: 1.9.20 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.43 running: yes
Device-1: Intel Tiger Lake PCH CNVi WiFi vendor: Rivet Networks
driver: iwlwifi v: kernel bus-ID: 0000:00:14.3 chip-ID: 8086:43f0
class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 3-14:5 chip-ID: 8087:0026 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:9a0b rev:
class-ID: 0104
Local Storage: total: 953.87 GiB used: 14.87 GiB (1.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: KIOXIA
model: KXG60ZNV1T02 NVMe 1024GB size: 953.87 GiB block-size:
physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 10604107 temp: 40.9 C scheme: GPT
ID-1: / raw-size: 150 GiB size: 150 GiB (100.00%) used: 14.77 GiB (9.8%)
fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-2: /boot/efi raw-size: 200 MiB size: 196 MiB (98.00%)
used: 101.3 MiB (51.7%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 150 GiB size: 150 GiB (100.00%)
used: 14.77 GiB (9.8%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-4: /var/log raw-size: 150 GiB size: 150 GiB (100.00%)
used: 14.77 GiB (9.8%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
ID-5: /var/tmp raw-size: 150 GiB size: 150 GiB (100.00%)
used: 14.77 GiB (9.8%) fs: btrfs dev: /dev/nvme0n1p5 maj-min: 259:5
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.09 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
System Temperatures: cpu: 52.0 C mobo: N/A
Fan Speeds (RPM): N/A
Processes: 326 Uptime: 25m wakeups: 2829 Memory: 31.09 GiB
used: 3.28 GiB (10.6%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 1210 lib: 304 Shell: fish
v: 3.3.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.12

Are the NVIDIA drivers installed?

pacman -Qs nvidia

If the drivers are installed, what does nvidia-smi report?

If not, install them,

sudo pacman -S nvidia-dkms nvidia-settings --needed

Then you can run applications on the dGPU using the prime-run wrapper (which is in the nvidia-prime package).


Hi there, welcome to the community.

Did you boot into Nvidia drivers in live medium? It is working fine here, with same dGPU, out of the box.


Drivers are installed...

λ pacman -Qs nvidia
local/egl-wayland 2:1.1.9+r3+g582b2d3-1
EGLStream-based Wayland external platform
local/garuda-nvidia-config 1.1.4-2
Meta configuration package for nvidia systems on Garuda Linux
local/garuda-optimus-manager-config 1.1.4-2
Meta configuration package for nvidia prime systems on Garuda Linux:
local/gwe 0.15.4-1
A system utility for controlling NVIDIA GPUs
local/lib32-libvdpau 1.4-1
Nvidia VDPAU library
local/lib32-nvidia-utils 495.46-1
NVIDIA drivers utilities (32-bit)
local/lib32-opencl-nvidia 495.46-1
OpenCL implemention for NVIDIA (32-bit)
local/libvdpau 1.4-1
Nvidia VDPAU library
local/libxnvctrl 495.46-2
local/mhwd-nvidia 495.44-1
mhwd-nvidia pci id
local/mhwd-nvidia-390xx 390.143-1
mhwd-nvidia-390xx PCI ID database
local/nvidia-dkms 495.46-2
NVIDIA drivers - module sources
local/nvidia-prime 1.0-4
NVIDIA Prime Render Offload configuration and utilities
local/nvidia-settings 495.46-2
Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 495.46-2
NVIDIA drivers utilities
local/opencl-nvidia 495.46-2
OpenCL implemention for NVIDIA
local/xf86-video-nouveau 1.0.17-2 (xorg-drivers)
Open Source 3D acceleration driver for nVidia cards

And nothing to do, apparently...

λ sudo pacman -S nvidia-dkms nvidia-settings --needed
[sudo] password for dhdanie:
warning: nvidia-dkms-495.46-2 is up to date -- skipping
warning: nvidia-settings-495.46-2 is up to date -- skipping
there is nothing to do

You skipped part of my post.

1 Like

Sorry, sure did...

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

Output of

dkms status


1 Like
[🔴] × dkms status
acpi_call/1.2.2: added
bbswitch/0.8: added
nvidia/495.46: added

Hm. "Added" is not "installed", it should look something like:

nvidia/510.39.01, 5.15.15-lqx1-1-lqx, x86_64: installed
nvidia/510.39.01, 5.16.1-zen1-1-zen, x86_64: installed


sudo dkms autoinstall

and paste any output.

1 Like

Output from the autoinstall.

λ sudo dkms autoinstall

Building module:
cleaning build area...
make -j16 KERNELRELEASE=5.15.15-1-lts KVER=5.15.15-1-lts...
cleaning build area...

Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/

Building module:
cleaning build area...
make -j16 KERNELRELEASE=5.15.15-1-lts KVERSION=5.15.15-1-lts...
cleaning build area...

Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/

Building module:
cleaning build area...
cleaning build area...

Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/

Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/

Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/

Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/

Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /usr/lib/modules/5.15.15-1-lts/updates/dkms/

They're reporting similar to yours now...

❮ dkms status
acpi_call/1.2.2, 5.15.15-1-lts, x86_64: installed
bbswitch/0.8, 5.15.15-1-lts, x86_64: installed
nvidia/495.46, 5.15.15-1-lts, x86_64: installed

I will try to reboot and see if everything is working.

1 Like

Also watch out for any Bumblebee-related issues - you don't need Bumblebee for your dGPU.

1 Like

Reboot now hangs. Going to roll back unless you've got ideas to check?

Loading Linux linix-lts
Loading initial ramdisk

Hi, back to your topic.

Using Linux-LTS maybe source of issue. So try booting into default kernel, that is, Linux-Zen.

Also, boot into live medium and check if it still shows driver N/A. I don't remember for dr460nized, tbh, but in Cinnamon edition, there is nice system tray icon to switch between Nvidia only / hybrid / Integrated GPU, in live medium too.

So, maybe boot into cinnamon live medium might be worth it as well.
And off course, always use the option Boot with Nvidia in live medium

1 Like

This means you did something else to your system at some point, e.g. adding the nvidia drivers modules to /etc/mkinitcpio.conf, or you did a partial upgrade.

You can fix this by chrooting into the system using a live installer environment.

1 Like

Boot with nvidia drivers from installer hangs

Starting Terminate Plymouth Boot Screen

So I booted with open source drivers with the intention of switching to nvidia, after.

The only thing I did to the system after install was a system update (pacman - Syu) which would fail with a conflict between something and pipewire-jack, so I removed pipewire-jack and then update finished successfully. I certainly didn't touch /etc/mkinitcpio.conf.

λ cat /etc/mkinitcpio.conf 
# vim:set ft=sh
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(crc32c-intel intel_agp i915 amdgpu radeon nouveau)
MODULES=(crc32c-intel intel_agp i915 amdgpu radeon nouveau)

# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries

# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.

# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap consolefont plymouth filesystems"

# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.

# Additional options for the compressor

Hmm. I think this will conflict with the nvidia driver so shouldn't be built into the initramfs.

Change this line to

MODULES=(crc32c-intel i915)

then run

sudo mkinitcpio -P

Also ensure there's a file /etc/modprobe.d/nvidia.conf that contains blacklist nouveau .

There's some further detail about enabling KMS on the Arch wiki page, NVIDIA - ArchWiki

1 Like

Also re-run dkms autoinstall to get the three items back to installed?

I don't know what you did since NVIDIA GA106M driver N/A - #12 by nwadave so if you removed the NVIDIA drivers then yes, reinstall them.

I had to restore to a point before the dkms autoinstall to get it to boot again, but will re-run now.

1 Like

Create the file with the content I mentioned above. This should be done by default when you install the NVIDIA driver so I'm not sure what state your system is in.

It might be worth reinstalling and setting things up step-by-step rather than trying to work out what's different... :thinking:

On the other hand, read the wiki page I linked to as it contains all of the necessary information for getting the NVIDIA drivers installed and working, but it boils down to these two steps (which I mentioned above):

1 Like