Your message dated Tue, 12 Mar 2024 16:08:08 +0100
with message-id <[email protected]>
and subject line Re: Bug#1066080: nvidia-driver (525.147.05-10) does not build
against kernel 6.6.15-amd64 on Debian Sid
has caused the Debian Bug report #1066080,
regarding nvidia-driver (525.147.05-10) does not build against kernel
6.6.15-amd64 on Debian Sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1066080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066080
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nvidia-driver
Version: 525.147.05-10
An attempt to upgrade nvidia-driver to current version (have retried this
after a purge remove in an attempt to restart from a clean slate) fails. I
did not have any issues with the previous version of the driver in Sid
(don't know the old version number), so this is not a hardware problem
(lspci output is included) but a driver problem.
However, this is not the first time nvidia-driver has broken with Sid
(which is fine - it is called unstable for a reason), but it has been 5-6
days already since this happened, I am not seeing any movement on the
package tracker. I was hoping that someone had reported this showstopper
already and a fix was on the way.
Details (following https://www.debian.org/Bugs/Reporting suggestions) are
below:
$ sudo apt-get install nvidia-driver firmware-misc-nonfree
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
firmware-misc-nonfree is already the newest version (20230625-2).
...
The following additional packages will be installed:
curl firmware-nvidia-gsp glx-alternative-mesa glx-alternative-nvidia
glx-diversions libcuda1 libcurl4t64 libegl-nvidia0 libgl1-nvidia-glvnd-glx
libgles-nvidia1 libgles-nvidia2 libgles1 libglx-nvidia0 libnss-mymachines
libnss-systemd libnvcuvid1 libnvidia-allocator1 libnvidia-cfg1
libnvidia-egl-gbm1 libnvidia-egl-wayland1 libnvidia-eglcore
libnvidia-encode1 libnvidia-glcore libnvidia-glvkspirv libnvidia-ml1
libnvidia-ptxjitcompiler1 libnvidia-rtcore libpam-systemd libpsl5t64
libssh2-1t64 libsystemd-shared libsystemd0 nvidia-alternative
nvidia-driver-bin nvidia-driver-libs nvidia-egl-common nvidia-egl-icd
nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-dkms
nvidia-kernel-support nvidia-legacy-check nvidia-modprobe
nvidia-persistenced nvidia-settings nvidia-smi nvidia-support
nvidia-suspend-common nvidia-vdpau-driver nvidia-vulkan-common
nvidia-vulkan-icd systemd systemd-container systemd-coredump
systemd-timesyncd update-glx xserver-xorg-video-nvidia
Suggested packages:
nvidia-cuda-mps vulkan-tools systemd-homed systemd-userdbd systemd-boot
systemd-resolved libtss2-mu-4.0.1-0 libtss2-rc0
Recommended packages:
libcuda1:i386 nvidia-driver-libs:i386
The following packages will be REMOVED:
libcurl4 libpsl5 libssh2-1
The following NEW packages will be installed:
firmware-nvidia-gsp glx-alternative-mesa glx-alternative-nvidia
glx-diversions libcuda1 libcurl4t64 libegl-nvidia0 libgl1-nvidia-glvnd-glx
libgles-nvidia1 libgles-nvidia2 libgles1 libglx-nvidia0 libnvcuvid1
libnvidia-allocator1 libnvidia-cfg1 libnvidia-egl-gbm1
libnvidia-egl-wayland1 libnvidia-eglcore libnvidia-encode1 libnvidia-glcore
libnvidia-glvkspirv libnvidia-ml1 libnvidia-ptxjitcompiler1
libnvidia-rtcore libpsl5t64 libssh2-1t64 nvidia-alternative nvidia-driver
nvidia-driver-bin nvidia-driver-libs nvidia-egl-common nvidia-egl-icd
nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-dkms
nvidia-kernel-support nvidia-legacy-check nvidia-modprobe
nvidia-persistenced nvidia-settings nvidia-smi nvidia-support
nvidia-suspend-common nvidia-vdpau-driver nvidia-vulkan-common
nvidia-vulkan-icd update-glx xserver-xorg-video-nvidia
The following packages will be upgraded:
curl libnss-mymachines libnss-systemd libpam-systemd libsystemd-shared
libsystemd0 systemd systemd-container systemd-coredump systemd-timesyncd
10 upgraded, 48 newly installed, 3 to remove and 264 not upgraded.
...
...
Setting up nvidia-kernel-dkms (525.147.05-10) ...
Loading new nvidia-current-525.147.05 DKMS files...
Building for 6.6.15-amd64
Building initial module for 6.6.15-amd64
Error! Bad return status for module build on kernel: 6.6.15-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more
information.
dpkg: error processing package nvidia-kernel-dkms (--configure):
installed nvidia-kernel-dkms package post-installation script subprocess
returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver:
nvidia-driver depends on nvidia-kernel-dkms (= 525.147.05-10) |
nvidia-kernel-525.147.05 | nvidia-open-kernel-525.1
47.05; however:
Package nvidia-kernel-dkms is not configured yet.
Package nvidia-kernel-525.147.05 is not installed.
Package nvidia-kernel-dkms which provides nvidia-kernel-525.147.05 is not
configured yet.
Package nvidia-open-kernel-525.147.05 is not installed.
dpkg: error processing package nvidia-driver (--configure):
dependency problems - leaving unconfigured
...
Contents of the make.log:
DKMS make.log for nvidia-current-525.147.05 for kernel 6.6.15-amd64
(x86_64)
Tue Mar 12 12:26:40 PM IST 2024
make KBUILD_OUTPUT=/lib/modules/6.6.15-amd64/build V=1 -C
/lib/modules/6.6.15-amd64/source M=/var/lib/dkms/nvidia-cu
rrent/525.147.05/build ARCH=x86_64
NV_KERNEL_SOURCES=/lib/modules/6.6.15-amd64/source
NV_KERNEL_OUTPUT=/lib/modules/
6.6.15-amd64/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset
nvidia-drm nvidia-peermem" INSTALL_MOD_DIR=ke
rnel/drivers/video NV_SPECTRE_V2=0 modules
...
... (until last couple of lines in the file)
# cmd_gen_symversions_c
/var/lib/dkms/nvidia-current/525.147.05/build/nvidia-peermem/nvidia-peermem.o
if nm
/var/lib/dkms/nvidia-current/525.147.05/build/nvidia-peermem/nvidia-peermem.o
2>/dev/null | grep -q ' __expo
rt_symbol_'; then gcc-13 -E -D__GENKSYMS__
-Wp,-MMD,/var/lib/dkms/nvidia-current/525.147.05/build/nvidia-peermem/.n
vidia-peermem.o.d -nostdinc
-I/usr/src/linux-headers-6.6.15-common/arch/x86/include
-I./arch/x86/include/generated -
I/usr/src/linux-headers-6.6.15-common/include -I./include
-I/usr/src/linux-headers-6.6.15-common/arch/x86/include/ua
pi -I./arch/x86/include/generated/uapi
-I/usr/src/linux-headers-6.6.15-common/include/uapi
-I./include/generated/uap
i -include
/usr/src/linux-headers-6.6.15-common/include/linux/compiler-version.h
-include /usr/src/linux-headers-6.6
.15-common/include/linux/kconfig.h -include
/usr/src/linux-headers-6.6.15-common/include/linux/compiler_types.h -D__
KERNEL__ -fmacro-prefix-map=/usr/src/linux-headers-6.6.15-common/=
-std=gnu11 -fshort-wchar -funsigned-char -fno-com
mon -fno-PIE -fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow
-mno-avx -fcf-protection=branch -fno-jump-t
ables -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387
-mpreferred-stack-boundary=3 -mskip-rax-set
up -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare
-fno-asynchronous-unwind-tables -mindirect-branch=
thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix
-mfunction-return=thunk-extern -fno-jump-tables
-mharden-sls=all -fpatchable-function-entry=16,16
-fno-delete-null-pointer-checks -O2 -fno-allow-store-data-races -f
stack-protector-strong -ftrivial-auto-var-init=zero
-fno-stack-clash-protection -pg -mrecord-mcount -mfentry -DCC_US
ING_FENTRY -falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow
-fno-stack-check -fconserve-stack -Wall
-Wundef -Werror=implicit-function-declaration -Werror=implicit-int
-Werror=return-type -Werror=strict-prototypes -Wn
o-format-security -Wno-trigraphs -Wno-frame-address
-Wno-address-of-packed-member -Wframe-larger-than=2048 -Wno-main
-Wno-unused-but-set-variable -Wno-unused-const-variable
-Wno-dangling-pointer -Wvla -Wno-pointer-sign -Wcast-functi
on-type -Wno-array-bounds -Wno-alloc-size-larger-than
-Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatibl
e-pointer-types -Werror=designated-init -Wenum-conversion
-Wno-unused-but-set-variable -Wno-unused-const-variable -W
no-restrict -Wno-packed-not-aligned -Wno-format-overflow
-Wno-format-truncation -Wno-stringop-overflow -Wno-stringop
-truncation -Wno-missing-field-initializers -Wno-type-limits
-Wno-shift-negative-value -Wno-maybe-uninitialized -Wno
-sign-compare -g -I/var/lib/dkms/nvidia-current/525.147.05/build/common/inc
-I/var/lib/dkms/nvidia-current/525.147.0
5/build -Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args
-D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=
\"525.147.05\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing
-ffreestanding -mno-red-zone -mcmodel=kerne
l -DNV_UVM_ENABLE -Werror=undef -DNV_SPECTRE_V2=0
-DNV_KERNEL_INTERFACE_LAYER -I/var/lib/dkms/nvidia-current/525.147
.05/build/nvidia-peermem -UDEBUG -U_DEBUG -DNDEBUG
-DNV_BUILD_MODULE_INSTANCES=0 -DMODULE -DKBUILD_BASENAME='"nvid
ia_peermem"' -DKBUILD_MODNAME='"nvidia_peermem"'
-D__KBUILD_MODNAME=kmod_nvidia_peermem /var/lib/dkms/nvidia-current
/525.147.05/build/nvidia-peermem/nvidia-peermem.c |
scripts/genksyms/genksyms -r /dev/null >> /var/lib/dkms/nvidia
-current/525.147.05/build/nvidia-peermem/.nvidia-peermem.o.cmd; fi
make[3]: *** [/usr/src/linux-headers-6.6.15-common/Makefile:1938:
/var/lib/dkms/nvidia-current/525.147.05/build] Error 2
make[2]: *** [/usr/src/linux-headers-6.6.15-common/Makefile:246:
__sub-make] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-6.6.15-amd64'
make[1]: *** [Makefile:246: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.6.15-common'
make: *** [Makefile:82: modules] Error 2
I am using Debian Sid (Unstable) (6.6.15-amd64 #1 SMP PREEMPT_DYNAMIC
Debian 6.6.15-2 (2024-02-04) x86_64 GNU/Linux).
libc6 version:
$ apt show libc6 | grep ^Version
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
Version: 2.37-15.1
lspci:
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen
Core Processor Host Bridge/DRAM Registers
(rev 07)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe
Controller (x16) (rev 07)
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset
Family USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation 100 Series/C230
Series Chipset Family Thermal Subsystem (rev
31)
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series
Chipset Family MEI Controller #1 (rev 31)
00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode]
(rev 31)
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family
PCI Express Root Port #1 (rev f1)
00:1f.0 ISA bridge: Intel Corporation C236 Chipset LPC/eSPI Controller (rev
31)
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset
Family Power Management Controller (rev
31)
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset
Family HD Audio Controller (rev 31)
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family
SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2)
I219-LM (rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation TU117GL [T1000 8GB]
(rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1)
02:00.0 PCI bridge: Texas Instruments XIO2001 PCI Express-to-PCI Bridge
--- End Message ---
--- Begin Message ---
On 12/03/2024 15.35, JON Tauri wrote:
Replying to myself. Your statement about the ongoing 64 bit time_t
transition got me thinking. What if I have a problem there? So, I tried
installing the libelf t64 bit again:
Good to see it solved. The upgrade path should be smoother once
everything is ready to migrate to testing, but right now it's a bumpy
ride in sid. There are a lot of packages still needing updates or at
least being rebuilt to update their dependencies.
The 64-bit time_t transition is so far the biggest transition ever done
in Debian. It is not an ABI change on 64-bit architectures (these
already had 64-bit time_t), but on armel/armhf and other 32-bit
architectures. The packages need to be renamed on all architectures
nevertheless. But it gets a bit smoother on 64-bit architectures by
providing the old library names (w/o t64 suffix), otherwise a
non-minimal sid would be uninstallable until most packages got updated.
The dependency resolution problem (requiring manual interaction)
probably stems from the fact that sid currently has
libelf1 0.190-1+b1
libelf1t64 0.190-1.1
virtual libelf1 provided by libelf1t64
Once the obsolete libelf1 is gone (it will be automatically decrufted
after all packages dropped depenencies on it), apt/aptitude no longer
has the choice between the old and new one (usually preferring the old
installed one) and dependency resolution should be smooth again ...
Current transition state for elfutils:
https://release.debian.org/transitions/html/auto-elfutils.html
(one of about 500-700 currently ongoing t64 related transitions)
Andreas
--- End Message ---
