Tech

DeepDayze

Been unable to build the nVidia driver on latest Liquorix.

Doing some digging shows the Liquorix kernel have been built with (gcc (Debian 15.2.0-3) and 15.2.0-4 is now in unstable. This new update for GCC seems to be different enough to break new nvidia kernel driver builds at least on unstable.

:: Code ::

Linux version 6.16.11-1-liquorix-amd64 (steven@liquorix.net) (gcc (Debian 15.2.0-3) 15.2.0, GNU ld (GNU Binutils for Debian) 2.45) #1 ZEN SMP PREEMPT_DYNAMIC liquorix 6.16-10.1~sid (2025-10-06)

Relevant line from nvidia-installer.log:

:: Code ::

ERROR: Unable to load the kernel module 'nvidia-drm.ko'. This happens most frequently when this kernel module was built against the wrong or improperly configured kernel sources, with a version of gcc that differs from the one used to build the target kernel, or if another driver, such as nouveau, is present and prevents the NVIDIA kernel module from obtaining ownership of the NVIDIA device(s), or no NVIDIA device installed in this system is supported by this NVIDIA Linux graphics driver release.

gcc -v:

:: Code ::

~# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/15/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 15.2.0-4' --with-bugurl=file:///usr/share/doc/gcc-15/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2,rust,cobol,algol68 --prefix=/usr --with-gcc-major-version-only --program-suffix=-15 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/reproducible-path/gcc-15-15.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/reproducible-path/gcc-15-15.2.0/debian/tmp-gcn/usr --enable-offload-defaulted --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=3
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 15.2.0 (Debian 15.2.0-4)

Is it possible to have your Unstable build box updated to gcc-15.2.0-4?
Back to top

damentz

Yep, this is just bad timing. The maintainer for GCC works with the kernel team to push out updates whenever they bump versions. I only learn after reports like yours that DKMS builds stop working for GCC version mismatches.

A kernel rebuild is in progress, you'll get an update in the next hour or so.
Back to top

DeepDayze

That's exactly what I figured as well as even with the standard Debian kernel the nvidia drivers also fail to build as well as that kernel was built with gcc 14 still. I thought about setting up alternatives so that I can select the gcc version to match the kernel compiler version by merely changing the alternatives but that might cause more issues than it solves.

Thanks, damentz!
Back to top

DeepDayze

Okay got the new rebuild installed and the bad news it still fails to build with same error as previously mentioned in my first post.

Verified that kernel was built with latest gcc for unstable:

:: Code ::

Linux version 6.16.11-1-liquorix-amd64 (steven@liquorix.net) (gcc (Debian 15.2.0-4) 15.2.0, GNU ld (GNU Binutils for Debian) 2.45) #1 ZEN SMP PREEMPT_DYNAMIC liquorix 6.16-10.2~sid (2025-10-06)

Checked to be sure I had the matching headers installed too.

Also noted there were no new updates for gcc today.

I am out of ideas as to what the deeper issue is.

Inxi graphics info (Note I am running nouveau until can find a fix for the nvidia build issues):

:: Code ::

~$ inxi -Gxxx
Graphics:
Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: Gigabyte
driver: nouveau v: kernel arch: Pascal pcie: speed: 2.5 GT/s lanes: 16
ports: active: DVI-D-2 empty: DP-1,DVI-D-1,HDMI-A-1 bus-ID: 09:00.0
chip-ID: 10de:1c03 class-ID: 0300 temp: 61.0 C
Device-2: Microdia PC-LM1E driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-1:2 chip-ID: 0c45:636d
class-ID: 0102 serial: PC-LM1E
Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: swrast gpu: nouveau 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: DVI-D-2 model: HP 24uh serial: CNK92100N0 res: mode: 1920x1080
hz: 60 scale: 100% (1) dpi: 92 size: 531x299mm (20.91x11.77")
diag: 609mm (24") modes: max: 1920x1080 min: 720x400
API: EGL v: 1.5 platforms: device: 1 drv: swrast gbm: drv: kms_swrast
surfaceless: drv: swrast x11: drv: swrast inactive: wayland,device-0
API: OpenGL v: 4.5 vendor: mesa v: 25.2.4-1 glx-v: 1.4 direct-render: yes
renderer: llvmpipe (LLVM 19.1.7 256 bits) device-ID: ffffffff:ffffffff
API: Vulkan Message: No Vulkan data available.
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
xdpyinfo, xprop, xrandr

If any other logs or anything else let me know and I'll provide them!

Thanks for all you do, Damentz.

PS: Has anyone else reported build issues as well for Debian Unstable?
Back to top

damentz

It's definitely showing the correct version in the uname output: gcc (Debian 15.2.0-4) 15.2.0

This lines up with the latest version listed here: packages.debian.org/sid/gcc-15

I'm also at a loss, these builds are performed using the latest docker image published by Debian, with a apt-get dist-upgrade to bring it up to date on every run. At this point I suspect maybe you have something different on your system, maybe a mix of Debian Testing or Experimental that's causing this?

EDIT: Unrelated but: Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB]

The 10 series GPUs are now considered legacy. I'd recommend finding an AMD card to replace it so you don't have to deal with this mess nvidia created with their DKMS driver.
Back to top

DeepDayze

Thanks for the reply and maybe you are right. The earlier 580 builds worked for my card however. I might try downgrading to the 575 series.
Back to top

DeepDayze

Okay...looks like I will consider replacing my card as I backed up stuff and did a clean clean reinstall with just the basic KDE and building even the 575 series driver did not build on either your kernel or the Debian standard kernel.

Thanks for your help on this.
Back to top

DeepDayze

Alright, for time being I was able to go install Trixie instead and still unable to build the nVidia driver for the latest Liquorix but however was successful in building the 575.64.05 version on the stock 6.12 kernel in Trixie. To me there must be something that is in 6.16.11 (affecting both LQX and standard Debian 6.16 kernels) that's breaking DKMS installs for Unstable and Trixie.
Back to top

cotton

Not sure if this will help on Debian but Arch Linux users are in the same boat as you for keeping your <now-considered-legacy> card operational, see the comments on: https://aur.archlinux.org/packages/nvidia-550xx-dkms
(there are associated packages for nvidia-550xx-utils and opencl-nvidia-550xx).

FWIW I'm successfully running an even older GeForce 650Ti using the nvidia-470xx-dkms package with 6.15.9-lqx1-1-lqx

I agree with Linus Torvald's explicit statement about Nvidia!
I will never buy another Nvidia card whilst their drivers remain proprietary.
The advice you were given is correct, AMD don't have this problem.
Back to top

DeepDayze

FWIW, the nvidia 575 driver built successfully on today's update of the lqx kernel when I felt it didn't. Go figure. I'm not going to make any more changes as don't want to break it again :-)
Back to top

Tech

Tech

patterns.com

tech forums