MX Linux Forum

Here is the log for the dkms. Same failure cause for 28 and 33 kernels: can't find vmlinux:

Skipping BTF generation for /var/lib/dkms/nvidia/570.133.07/build/nvidia-peermem.ko due to unavailability of vmlinux
BTF [M] /var/lib/dkms/nvidia/570.133.07/build/nvidia-drm.ko
Skipping BTF generation for ...

I managed to get Nvidia driver version 5.7.0 installed and working after a 12 hr session of troubleshooting / investigation with the help of chatGPT. The build / install of that driver (which I obtained directly from Nvidia; I'll have to review but IIRC I chose the open, not proprietary version ...

You might try purging and reinstalling dkms


That failed miserably with tons of errors. I am winning to try such drastic suggestions b/c I can restore from a backup, which is probably necessary after this.

The following packages were automatically installed and are no longer required ...

I'm using a brand new i9 system today, and having difficulties getting the nvidia drivers loaded. Here's my current QSI:
Snapshot created on: 20231002_0747
System:
Kernel: 6.1.0-33-amd64 [6.1.133-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/vmlinuz-6.1.0-33-amd64 root ...

However, when I ran the update today it still wants the 6.1 kernel headers, despite purging 6.1 from my system. I ran the update-initram -U (iirc the name of the cmd to do that) so it wasn't in the initram or in /boot. What else might be bring in a dependency of an old kernel version? 6.1 isn't even ...

Thanx, that cleaned things up nicely.

I hate to admit it, but I'm trying to setup a dual boot system with MX and Windows 10 and MX doesn't detect Windows.

I'm using Dolphin's systemd only respin, which I know from previous posts has a few things omitted. However, it does have the os-prober script. There are comments in grub.cfg for it ...

Thank you! Perfect.

Well, perhaps not perfect. I installed docker.io remotely via ssh and I saw a line complaining it couldn't open the display which makes sense. I didn't see the success message you posted, but I see docker & containerd is running so the install did work, but I'll need to look ...

I ran into frustrations when I attempted this on MX-21 last year and punted the effort. Last year I tried to follow the install guide for debian 11 on the docker website. I wasn't surprised it failed, since most Linux systems these days assume systemd init. I just didn't have the time to figure out ...

Ok, I see your point now. Not sure when the behavior of su without options changed, but I'd be willing to bet I got conditioned to seeing a root path (with sbin) as the default and sometime around debian 9 or 10 that changed.