[SOLVED] Nvidia DKMS doesn't work with latest zen kernel

inxi -Faz

System:
  Kernel: 5.17.5-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=d149fcea-bf8d-4e87-a8e2-b5694e640756 rw [email protected]
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3 nvidia-drm.modeset=1
  Desktop: Budgie v: 10.6.1 info: budgie-panel wm: budgie-wm dm: LightDM
    v: 1.30.0 Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: TOSHIBA product: SATELLITE P50-C v: PSPT2E-01000WEN
    serial: <superuser required>
  Mobo: FF50 model: 06F3 v: Type2 - Board Version
    serial: <superuser required> UEFI: INSYDE v: 1.70 date: 07/05/2017
Battery:
  ID-1: BAT1 charge: 25.7 Wh (100.0%) condition: 25.7/44.1 Wh (58.3%)
    volts: 16.6 min: 14.8 model: Panasonic PA5195U-1BRS type: Li-ion
    serial: N/A status: full cycles: 198
CPU:
  Info: model: Intel Core i7-6500U bits: 64 type: MT MCP arch: Skylake
    family: 6 model-id: 0x4E (78) stepping: 3 microcode: 0xEC
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 500 min/max: 400/3100 scaling: driver: intel_pstate
    governor: powersave cores: 1: 500 2: 500 3: 500 4: 500 bogomips: 20799
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
    mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Toshiba driver: i915
    v: kernel ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:1916 class-ID: 0300
  Device-2: NVIDIA GM108M [GeForce 930M] vendor: Toshiba driver: nvidia
    v: 510.68.02 alternate: nouveau,nvidia_drm pcie: gen: 1 speed: 2.5 GT/s
    lanes: 4 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.0
    chip-ID: 10de:1346 class-ID: 0302
  Device-3: IMC Networks TOSHIBA Web Camera - HD type: USB driver: uvcvideo
    bus-ID: 1-7:4 chip-ID: 13d3:5652 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.1
    compositor: budgie-wm driver: X: loaded: modesetting gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: LG Display 0x044f built: 2014 res: 1920x1080
    hz: 60 dpi: 141 gamma: 1.2 size: 345x194mm (13.58x7.64")
    diag: 396mm (15.6") ratio: 16:9 modes: 1920x1080
  OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 22.0.3
    direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Toshiba
    driver: snd_hda_intel v: kernel alternate: snd_soc_skl bus-ID: 00:1f.3
    chip-ID: 8086:9d70 class-ID: 0403
  Sound Server-1: ALSA v: k5.17.5-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: Intel Wireless 3165 driver: iwlwifi v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:3165 class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Toshiba driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-6:3 chip-ID: 8087:0a2a class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 2 state: up address: <filter>
Drives:
  Local Storage: total: 238.47 GiB used: 56.14 GiB (23.5%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: THNSNJ256GVNU
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 0101 scheme: GPT
Partition:
  ID-1: / raw-size: 238.17 GiB size: 238.17 GiB (100.00%)
    used: 56.14 GiB (23.6%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 576 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 238.17 GiB size: 238.17 GiB (100.00%)
    used: 56.14 GiB (23.6%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 238.17 GiB size: 238.17 GiB (100.00%)
    used: 56.14 GiB (23.6%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 238.17 GiB size: 238.17 GiB (100.00%)
    used: 56.14 GiB (23.6%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.46 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 57.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 233 Uptime: 6m wakeups: 1 Memory: 15.46 GiB
  used: 2.79 GiB (18.0%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.2.0 clang: 13.0.1 Packages: 1401 pacman: 1365 lib: 338 flatpak: 36
  Shell: nu running-in: wezterm-gui inxi: 3.3.15

Report everything you have already attempted to solve your problem.
nvidia-dkms (used with optimus-manager) does not work with linux-zen-5.17.5.zen1-2-x86_64 (+ linux-zen-headers of same version). When running the command prime-offload followed by optimus-manager --switch nvidia, I get an error saying that "module nvidia is not available for the current kernel".

This issue is fixed by reverting to linux-zen-5.17.5.zen1-1-x86_64 (+ linux-zen-headers of same version) with pacman -U, then adding it to the ignore list in /etc/pacman.conf, so technically the issue is fixed, however I doubt that reverting only the kernel and keeping it on an older version is stable. Are there any better solutions, or does anyone know when this will be fixed?

Tthe current zen kernel is linux-zen 5.17.5.zen1-1. The nvidia-dkms should catch up before the release of the referenced kernel.

extra/linux-zen 5.17.5.zen1-1 [installed]
    The Linux ZEN kernel and modules
extra/linux-zen-headers 5.17.5.zen1-1 [installed]
    Headers and scripts for building modules for the Linux ZEN kernel

Ah yes, it seems that this was an issue with me enabling testing repos. Not only that, but I seem to have screwed up my pacman.conf. I re-arranged the order of mirrors to fix most issues. Thanks for helping me realise that testing repos are causing me pain!

Not a problem just ru-

.. you should run garuda-update remote fix to fix it properly >.>

1 Like

Also, in the future please use garuda-inxi rather than inxi -Faz for posting your system specs.

Welcome to the Garuda community.