Arch Linux

accipter

Member

Registered: 2022-07-07

Posts: 4

[SOLVED] Predicting arch-zen and nvidia-dkms conflicts

Today I updated my system with 'pacman -Syu' and rebooted only to discover the display manager wouldn't start. After going through the logs and poking around a bit, I discovered the issue was incompatibility between the latest versions of arch-zen kernel and the nvidia-dkms package. Is there anyway that this could have been identified earlier (say before or immediately package install)? I resolved the problem by using the default linux kernel and the nvidia package.

Last edited by accipter (2022-07-07 17:40:55)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,267

Re: [SOLVED] Predicting arch-zen and nvidia-dkms conflicts

This does not - as a statement like that - make sense. There should not be a conflict between the two packages and there are plenty of people that use the combination, so what "exactly" was/is your problem? Post your logs. Note that a base requirement for DKMS anything to work is that the headers of the kernel in question are properly installed so linux-zen-headers in this case and they need to match the version of the linux-zen package you intend to boot into (and you need to boot into that actual kernel). If you pay attention during the pacman process you should see (and relevantly react) if the DKMS build fails for any reason.

The only thing you can generally "predict" is that there "might" be breakage when the major kernel version get's updated, so 5.18 -> 5.19 "might" be incompatible with the nvidia blob. In the vast majority of cases nvidia and the Arch packagers make sure that 1) an updated driver is out before a new stable kernel is declared and 2) a move to the stable repos delayed/patches applied if there's something that can be done from that side.

Something you also likely need to do currently regardless of used kernel is pass the ibt=off parameter, make sure you do that for both the standard and the zen kernel.

Also in general, if something like this was a widespread issue you would most likely not be the first person to report it, it's always safer and more likely to gather useful responses to assume an issue to be specific to your system and structure you posts accordingly and provide relevant information instead of making sweeping statements that assume that this problem must be affecting everyone.

Last edited by V1del (2022-07-07 11:22:13)

accipter

Member

Registered: 2022-07-07

Posts: 4

Re: [SOLVED] Predicting arch-zen and nvidia-dkms conflicts

Your point regarding assuming it is a widespread issue is well taken. That has usually been the case in the 18 years of using Arch so I was rather surprised when things suddenly didn't work.

Using linux-zen and nvidia-dkms (and ibt=off), I get the following errors at boot:

Jul 07 08:26:24 falco systemd-modules-load[318]: Failed to find module 'v4l2loopback'
Jul 07 08:26:24 falco systemd-modules-load[318]: Failed to find module 'nvidia-uvm'
Jul 07 08:26:25 falco kernel: usb 3-1.1.4: device descriptor read/64, error -32
Jul 07 08:26:25 falco kernel: usb 3-1.1.4: device descriptor read/64, error -32
Jul 07 08:26:26 falco kernel: usb 3-1.1.4: device descriptor read/64, error -32
Jul 07 08:26:26 falco kernel: usb 3-1.1.4: device descriptor read/64, error -32
Jul 07 08:26:27 falco kernel: usb 3-1.1.4: device not accepting address 9, error -71
Jul 07 08:26:27 falco kernel: usb 3-1.1.4: device not accepting address 10, error -71
Jul 07 08:26:27 falco kernel: usb 3-1.1-port4: unable to enumerate USB device

Here are my dmesg http://sprunge.us/cBnfYS and my journal -k http://sprunge.us/1xZdug.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,267

Re: [SOLVED] Predicting arch-zen and nvidia-dkms conflicts

You're at least booting the logically correct kernel, failing to load module for two distinct and not technically related but external modules suggest either a "bigger" dkms issue or a header/kernel mismatch

dkms status
pacman -Q linux-zen{,-headers}

Last edited by V1del (2022-07-07 16:37:55)

accipter

Member

Registered: 2022-07-07

Posts: 4

Re: [SOLVED] Predicting arch-zen and nvidia-dkms conflicts

dkms status:

nvidia/515.57: added
v4l2loopback/0.12.5: added

pacman -Q linux-zen{,headers}:

linux-zen 5.18.9.zen1-1
linux-zen-headers 5.18.9.zen1-1

loqs

Member

Registered: 2014-03-06

Posts: 18,967

Re: [SOLVED] Predicting arch-zen and nvidia-dkms conflicts

What is the output of

# dkms autoinstall

accipter

Member

Registered: 2022-07-07

Posts: 4

Re: [SOLVED] Predicting arch-zen and nvidia-dkms conflicts

Running `dkms autoinstall` identified the problem! I used pyenv to use multiple python environments. Despite activating the system python environment, the dkms script still located a gcc version inside one of the python environments. To solve the problem I did the following:

# sudo bash
$ PATH=$(getconf PATH)
$ dkms autoinstall
$ reboot

In doing this process, dkms also reported that the `sha512` was not found as reported here: https://github.com/dell/dkms/issues/229