Zur Info.
Ein DU heute Morgen schlug mit folgender Fehlermeldung fehl:
Quote
/etc/kernel/postinst.d/dkms exited with return code 1
dpkg: Fehler beim Bearbeiten des Paketes linux-image-6.15.3-1-siduction-amd64 (--configure):
»installiertes post-installation-Skript des Paketes linux-image-6.15.3-1-siduction-amd64«-Unterprozess gab den Fehlerwert 1 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-image-siduction-amd64:
linux-image-siduction-amd64 hängt ab von linux-image-6.15.3-1-siduction-amd64 (= 6.15-3); aber:
Paket linux-image-6.15.3-1-siduction-amd64 ist noch nicht konfiguriert.
Es liegt wohl mal wieder am Nvidia- Paket?! Die Fixes- Quellen sind aktiviert gewesen.
Der Kernel 6.14.10-1-siduction-amd64 läuft aber noch.
Confirmed. Same error here.
Ein gepatchter Nvidia-Treiber liegt seit eben im fixes-Repo.
Quote from: towo on 2025/06/20, 13:33:06
Ein gepatchter Nvidia-Treiber liegt seit eben im fixes-Repo.
Works like a charm! Thanks, towo!
jupp- wieder alles auf Reihe. @towo- aller besten Dank und ein schönes Sommer-WE.
Hi towo,
es scheint dass der Fix nicht für nvidia-470 taugt, oder es ist ein anderer Fehler:
Der relevante Teil beim Bau des Moduls:
QuoteAutoinstall of module nvidia-tesla-470/470.256.02 for kernel 6.15.3-1-siduction-amd64 (x86_64)
Applying patch cc_version_check-gcc5.patch... done.
Applying patch bashisms.patch... done.
Applying patch 0001-some-power-management-features-were-not-yet-in-Linux.patch... done.
Applying patch 0033-refuse-to-load-legacy-module-if-IBT-is-enabled.patch... done.
Applying patch 0034-fix-typos.patch... done.
Applying patch 0037-import-pfn_valid-w-o-GPL-rcu_read_lock-unlock-from-v.patch... done.
Applying patch 0042-Log-an-error-message-when-nv_mem_client_init-fails-d.patch... done.
Applying patch 0043-backport-follow_pfn-changes-from-550.90.07.patch... done.
Applying patch 0045-let-the-virt_addr_valid-macro-use-nv_pfn_valid-on-pp.patch... done.
Applying patch 0046-virt_addr_valid-wants-a-void-argument.patch... done.
Applying patch kernel-6.12.patch... done.
Applying patch kernel-6.13.patch... done.
Applying patch nvidia-470xx-fix-linux-6.14.patch... done.
Applying patch fragile-ARCH.patch... done.
Applying patch conftest-verbose.patch... done.
Applying patch use-kbuild-compiler.patch... done.
Applying patch use-kbuild-flags.patch... done.
Applying patch conftest-prefer-arch-headers.patch... done.
Building module(s).............(bad exit status: 2)
Failed command:
env NV_VERBOSE=1 make -j4 modules KERNEL_UNAME=6.15.3-1-siduction-amd64
Error! Bad return status for module build on kernel: 6.15.3-1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-tesla-470/470.256.02/build/make.log for more information.
Autoinstall on 6.15.3-1-siduction-amd64 failed for module(s) nvidia-tesla-470(10).
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: Fehler beim Bearbeiten des Paketes linux-image-6.15.3-1-siduction-amd64 (--configure):
»installiertes post-installation-Skript des Paketes linux-image-6.15.3-1-siduction-amd64«-Unterprozess gab den Fehlerwert 1 zurück
libqt6dbus6:amd64 (6.8.2+dfsg-7) wird eingerichtet ...
libqt6concurrent6:amd64 (6.8.2+dfsg-7) wird eingerichtet ...
libglx-mesa0:amd64 (25.1.4-0siduction1) wird eingerichtet ...
libglx-mesa0:i386 (25.1.4-0siduction1) wird eingerichtet ...
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-image-siduction-amd64:
linux-image-siduction-amd64 hängt ab von linux-image-6.15.3-1-siduction-amd64 (= 6.15-3); aber:
Paket linux-image-6.15.3-1-siduction-amd64 ist noch nicht konfiguriert.
dpkg: Fehler beim Bearbeiten des Paketes linux-image-siduction-amd64 (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
libqt6gui6:amd64 (6.8.2+dfsg-7) wird eingerichtet ...
qt6-gtk-platformtheme:amd64 (6.8.2+dfsg-7) wird eingerichtet ...
libqt6network6:amd64 (6.8.2+dfsg-7) wird eingerichtet ...
bind9-dnsutils (1:9.20.10-1) wird eingerichtet ...
qt6-qpa-plugins:amd64 (6.8.2+dfsg-7) wird eingerichtet ...
libqt6opengl6:amd64 (6.8.2+dfsg-7) wird eingerichtet ...
libqt6widgets6:amd64 (6.8.2+dfsg-7) wird eingerichtet ...
libqt6openglwidgets6:amd64 (6.8.2+dfsg-7) wird eingerichtet ...
libqt6printsupport6:amd64 (6.8.2+dfsg-7) wird eingerichtet ...
Trigger für hicolor-icon-theme (0.18-2) werden verarbeitet ...
Trigger für libc-bin (2.41-9) werden verarbeitet ...
Trigger für glx-alternative-mesa (1.2.2) werden verarbeitet ...
Trigger für man-db (2.13.1-1) werden verarbeitet ...
Trigger für siduction-dynamic-dms (2021.3.0-1) werden verarbeitet ...
Trigger für menu (2.1.51) werden verarbeitet ...
Trigger für mailcap (3.74) werden verarbeitet ...
Trigger für desktop-file-utils (0.28-1) werden verarbeitet ...
Trigger für libc-bin (2.41-9) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
linux-headers-6.15.3-1-siduction-amd64
linux-headers-siduction-amd64
linux-image-6.15.3-1-siduction-amd64
linux-image-siduction-amd64
needrestart is being skipped since dpkg has failed
Fehler: Sub-process /usr/bin/dpkg returned an error code (1)
Auszug aus dem Log folgt gleich (*ab Block oberhalb des ersten Fehlers*):
---Snip----
# CC [M] nvidia/nv-cray.o
gcc -Wp,-MMD,nvidia/.nv-cray.o.d -nostdinc -I/usr/src/linux-headers-6.15.3-1-siduction-amd64/arch/x86/include -I/usr/src/linux-headers-6.15.3-1-siduction-amd64/arch/x86/include/generated -I/usr/src/linux-headers-6.15.3-1-siduction-amd64/include -I/usr/src/linux-headers-6.15.3-1-siduction-amd64/include -I/usr/src/linux-headers-6.15.3-1-siduction-amd64/arch/x86/include/uapi -I/usr/src/linux-headers-6.15.3-1-siduction-amd64/arch/x86/include/generated/uapi -I/usr/src/linux-headers-6.15.3-1-siduction-amd64/include/uapi -I/usr/src/linux-headers-6.15.3-1-siduction-amd64/include/generated/uapi -include /usr/src/linux-headers-6.15.3-1-siduction-amd64/include/linux/compiler-version.h -include /usr/src/linux-headers-6.15.3-1-siduction-amd64/include/linux/kconfig.h -include /usr/src/linux-headers-6.15.3-1-siduction-amd64/include/linux/compiler_types.h -D__KERNEL__ -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE -fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -march=x86-64 -mtune=generic -mno-red-zone -mcmodel=kernel -mstack-protector-guard-reg=gs -mstack-protector-guard-symbol=__ref_stack_chk_guard -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 -fstack-protector-strong -fomit-frame-pointer -fno-stack-clash-protection -fmin-function-alignment=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check -fconserve-stack -fno-builtin-wcslen -Wall -Wextra -Wundef -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs -Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations -Wmissing-prototypes -Wframe-larger-than=2048 -Wno-main -Wno-dangling-pointer -Wvla -Wno-pointer-sign -Wcast-function-type -Wno-array-bounds -Wno-stringop-overflow -Wno-alloc-size-larger-than -Wimplicit-fallthrough=5 -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wenum-conversion -Wunused -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-packed-not-aligned -Wno-format-overflow -Wno-format-truncation -Wno-stringop-truncation -Wno-override-init -Wno-missing-field-initializers -Wno-type-limits -Wno-shift-negative-value -Wno-maybe-uninitialized -Wno-sign-compare -Wno-unused-parameter -I././nvidia -DNVIDIA_UNDEF_LEGACY_BIT_MACROS -UDEBUG -U_DEBUG -DNDEBUG -DMODULE -DKBUILD_BASENAME='"nv_cray"' -DKBUILD_MODNAME='"nvidia"' -D__KBUILD_MODNAME=kmod_nvidia -c -o nvidia/nv-cray.o nvidia/nv-cray.c ; /usr/src/linux-headers-6.15.3-1-siduction-amd64/tools/objtool/objtool --hacks=jump_label --hacks=noinstr --hacks=skylake --orc --retpoline --rethunk --sls --static-call --uaccess --prefix=16 --module nvidia/nv-cray.o
nvidia/nv.c:11:10: fatal error: nvmisc.h: Datei oder Verzeichnis nicht gefunden
11 | #include "nvmisc.h"
| ^~~~~~~~~~
compilation terminated.
make[4]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/scripts/Makefile.build:208: nvidia/nv.o] Fehler 1
make[4]: *** Es wird auf noch nicht beendete Prozesse gewartet ...
nvidia/nv-acpi.c:13:10: fatal error: os-interface.h: Datei oder Verzeichnis nicht gefunden
13 | #include "os-interface.h"
| ^~~~~~~~~~~~~~~~
compilation terminated.
make[4]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/scripts/Makefile.build:208: nvidia/nv-acpi.o] Fehler 1
nvidia/nv-cray.c:13:10: fatal error: os-interface.h: Datei oder Verzeichnis nicht gefunden
13 | #include "os-interface.h"
| ^~~~~~~~~~~~~~~~
compilation terminated.
make[4]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/scripts/Makefile.build:208: nvidia/nv-cray.o] Fehler 1
nvidia/nv-pci.c:12:10: fatal error: nv-pci-types.h: Datei oder Verzeichnis nicht gefunden
12 | #include "nv-pci-types.h"
| ^~~~~~~~~~~~~~~~
compilation terminated.
make[4]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/scripts/Makefile.build:208: nvidia/nv-pci.o] Fehler 1
make[3]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/Makefile:2027: .] Fehler 2
make[2]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/Makefile:260: __sub-make] Fehler 2
make[2]: Verzeichnis ,,/var/lib/dkms/nvidia-tesla-470/470.256.02/build" wird verlassen
make[1]: *** [Makefile:260: __sub-make] Fehler 2
make[1]: Verzeichnis ,,/usr/src/linux-headers-6.15.3-1-siduction-amd64" wird verlassen
make: *** [Makefile:80: modules] Fehler 2
# exit code: 2
# elapsed time: 00:00:31
----------------------------------------------------------------
Ähm, ich habe keinen gepatchten 470er irgendwo hochgeladen.
Ich hatte eh' nicht verstanden welche Pakete genau du gepatched hast. Ich hatte zwar angenommen dass sich das auf die akttuelle Version bezieht, aber das war nicht offensichtlich.
Kannst du für den 470 was machen?
QuoteKannst du für den 470 was machen?
Vermutlich.
In Kbuild ist an entsprechender Stelle
ccflags-y = $(EXTRA-CFLAGS)
zu ergänzen und
"del_timer-sync" & Co. ist durch "timer_delete_sync"
in den C-files zu ersetzen. Mit diesen Patches sollte es laufen.
Ach ja, in:
nvidia-drm-connector.c
ist noch Zeile 305 durch
static enum drm_mode_status nv_drm_connector_mode_valid(struct drm_connector *connector, const struct drm_display_mode *mode)
und jeweils wie gehabt an entsprechender Stelle
+#include <linux/version.h>
+
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(6, 15, 0)
+#define nv_vm_flags_set(v, f) vm_flags_reset((v), (v)->vm_flags | (f))
+#define nv_vm_flags_clear(v, f) vm_flags_reset((v), (v)->vm_flags & ~(f))
+#endif
zu patchen.
Quote from: towo on 2025/06/20, 15:03:38
QuoteKannst du für den 470 was machen?
Vermutlich.
Und ... wirst du etwas machen? :-) 8)
What I get in # CC [M] nvidia/nv-dma.o if I understand it correctly is a failure for nv.c to include nvmisc.h. The former is in /usr/src/nvidia-tesla-470-470.256.02/nvidia, the latter in /usr/src/nvidia-tesla-470-470.256.02/common/inc. My apologies for what is undoubtably a stupid question, but is it just a question of changing the directory the include statement has? I put it as
#include "../common/inc/nvmisc.h"
//#include "nvmisc.h"
#include "../common/inc/os-interface.h"
##include "os-interface.h"
#include "../common/inc/nv-linux.h"
//#include "nv-linux.h"
#include "nv-p2p.h"
#include "nv-reg.h"
#include "../common/inc/nv-msi.h"
//#include "nv-msi.h"
#include "nv-pci-table.h"
and it seemed to get past more of the build (though it's now stuck with other files that can't find their include options). I'm trying to find a way to not have to go through each file and I think it's to edit the /usr/src/nvidia-tesla-470-470.256.02/Kbuild file, but I'm not sure where that might be wrong. It has EXTRA_CFLAGS += -I$(src)/common/inc in it, but I'm not sure where (src) is defined.
Any suggestions on that?
Regardless, it might be the wrong approach - I'm not a programmer. Hopefully I don't break anything.
Quote
Any suggestions on that?
The location of the include files didn't change. The question is, why kernel 6.15 ignores
them while kernel 6.14 doesn't. And the reason is that use of EXTRA_CFLAGS in Kbuild
is deprecated a long time ago in favor of ccflags-y. And kernel 6.15 gets serious about the
deprecation. Since the additional include directories are part of EXTRA_CFLAGS (as can be
seen from Kbuild), the build fails.
Without replacing each and every #include line (your approach) or removing EXTRA_CFLAGS
altogether, a much smarter approach is the inclusion of one single line
ccflags-y = $(EXTRA_CFLAGS)
in Kbuild, when all is said and done about EXTRA_CFLAGS.
All other adjustments are just as obvious, but it takes a lot of tedious work to
patch the files at the right place (after all the patches already applied by the deb file
nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.1_amd64.deb.
If you are eager to work it out, follow the steps of the previous post.
But don't expect someone else to do it unless there is heavy demand.
Quote from: Teriarch on 2025/06/21, 17:30:59
But don't expect someone else to do it unless there is heavy demand.
Quite so, and exactly why I started prodding at it on the off-chance I might find something.
I'll gave the ccflags-y = $(EXTRA_CFLAGS) a try and, like you said, it didn't solve things. But it did get a lot further through with lots of warnings, which I was hopeful about, then a lot of
error: control reaches end of non-void function lines and
cc1: some warnings being treated as errors and lots more warnings, ending with
make[3]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/Makefile:2027: .] Error 2
make[2]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/Makefile:260: __sub-make] Error 2
make[2]: Leaving directory '/var/lib/dkms/nvidia-tesla-470/470.256.02/build'
make[1]: *** [Makefile:260: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.15.3-1-siduction-amd64'
make: *** [Makefile:80: modules] Error 2
# exit code: 2I might see if I can get any further with it. After all, what could go wrong?
Quote from: Teriarch on 2025/06/21, 17:30:59
....but it takes a lot of tedious work to
patch the files at the right place (after all the patches already applied by the deb file
nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.1_amd64.deb.
If you are eager to work it out, follow the steps of the previous post.
But don't expect someone else to do it unless there is heavy demand.
Really?
@Pip
Let's give it a try. I installed the deb file,inserted the "ccflags-y =..." at line 85 of Kbuild
and the compilation terminates with error
nvidia/nv.c:3848:5: error: implicit declaration of function 'del_timer_sync' [-Wimplicit-function-declaration]
3848 | del_timer_sync(&nvl->rc_timer.kernel_timer);
Now cd to /var/lib/dkms/nvidia-tesla-470/470.256.02/build (you can always recompile after changes by:
$ sudo env NV_VERBOSE=1 make -j4 modules KERNEL_UNAME=6.15.3-1-siduction-amd64)
Do a
$ grep -r del_timer_sync *
identify the c files containing expression "del_timer_sync" and replace all such occurrences
by "timer_delete_sync". Recompile the sources by the above command and see, where this is getting us!
To be continued...
PS.: Ignore the warnings, they are not part of the problem.
https://gist.github.com/joanbm/def2bf57ed7a799c1d84a67606459314
her is a ready to use patch, i'm not at home so i can't build nvidia-470 with that patch included at the moment.
Hey towo, thanks for telling what's going on. Although I have patched things I avoid it as I need too much help with it. It's not my cup of tea.
I can wait, even for a longer period if neccessary. To get a new siduction Kernel runing with my nvidia card is not important in a timely manner (but I like it ;-) ). The only thing I really would like to avoid is being completely cut off from new kernel development.
Thanks.
sorry, doppelposting
I think I got most of it sorted out, rather clumsily. A major part of what was wrong was del_timer_sync needing to be timer_delete_sync in the new kernel headers. But it still won't install because ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol '__vma_start_write' which I haven't got around - I can give it a value that will get it through, but then it won't be something to share.
Whether what comes out at the end actually works is another matter.
And I see that everyone else has already zipped through it. Sorry I took so long to get back about it.
I do not have an NVIDIA card in my laptop. Whatever the kernel build failes during FU.
# inxi -G
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Barcelo driver: amdgpu v: kernel
Device-2: Luxvisions Innotech HP 5MP Camera driver: uvcvideo type: USB
Display: unspecified server: X.Org v: 21.1.16 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
resolution: 1920x1080~60Hz
API: EGL v: 1.5 drivers: radeonsi,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.1.4-0siduction1
renderer: AMD Radeon Graphics (radeonsi renoir ACO DRM 3.61
6.14.10-1-siduction-amd64)
Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings x11: xdriinfo,
xdpyinfo, xprop, xrandr
┌─[~]
└─># apt update
Fetched 18,1 MB in 9s (2.045 kB/s)
119 packages can be upgraded. Run 'apt list --upgradable' to see them.
┌─[~]
└─># apt full-upgrade
Upgrading:
bind9-dnsutils libblockdev-loop3 libglib2.0-bin libpython3.13-stdlib mesa-va-drivers
bind9-host libblockdev-mdraid3 libglib2.0-data libqt6core6t64 mesa-vdpau-drivers
bind9-libs libblockdev-nvme3 libglx-mesa0 libqt6dbus6 mesa-vulkan-drivers
catdoc libblockdev-part3 libgnome-desktop-3-20t64 libqt6gui6 osinfo-db
cifs-utils libblockdev-swap3 libgnome-desktop-4-2t64 libqt6network6 pci.ids
curl libblockdev-utils3 libgtk-4-1 libqt6opengl6 python3-guestfs
gir1.2-adw-1 libblockdev3 libgtk-4-bin libqt6printsupport6 python3.13
gir1.2-gdkpixbuf-2.0 libc-bin libgtk-4-common libqt6sql6 python3.13-dev
gir1.2-glib-2.0 libc-dev-bin libgtk-4-media-gstreamer libqt6sql6-sqlite python3.13-doc
gir1.2-gnomedesktop-4.0 libc-devtools libguestfs-gfs2 libqt6widgets6 python3.13-minimal
gir1.2-gtk-4.0 libc-l10n libguestfs-jfs libqt6xml6 python3.13-tk
git libc6 libguestfs-nilfs librpm10 python3.13-venv
git-man libc6-dev libguestfs-perl librpmio10 rpm-common
gnome-desktop3-data libcjson1 libguestfs-rescue libudisks2-0 shine-on-xfce-settings
gtk-update-icon-cache libcpupower1 libguestfs-rsync libwin-hivex-perl siduction-manual
guestfish libcurl3t64-gnutls libguestfs-tools linux-cpupower signal-desktop
guestmount libcurl4t64 libguestfs-xfs linux-doc sos
initramfs-tools libegl-mesa0 libguestfs0t64 linux-doc-6.12 sosreport
initramfs-tools-bin libgbm1 libhivex0 linux-headers-siduction-amd64 udisks2
initramfs-tools-core libgdk-pixbuf-2.0-0 libllvm18 linux-image-siduction-amd64 udisks2-btrfs
libadwaita-1-0 libgdk-pixbuf2.0-bin libllvm19 linux-libc-dev xserver-common
libblockdev-btrfs3 libgdk-pixbuf2.0-common libpython3.13 locales xserver-xorg-core
libblockdev-crypto3 libgl1-mesa-dri libpython3.13-dev manpages-de xserver-xorg-legacy
libblockdev-fs3 libglib2.0-0t64 libpython3.13-minimal mesa-libgallium
Installing dependencies:
linux-headers-6.15.3-1-siduction-amd64 linux-image-6.15.3-1-siduction-amd64
Suggested packages:
linux-doc-6.15
Summary:
Upgrading: 119, Installing: 2, Removing: 0, Not Upgrading: 0
Download size: 407 MB
Space needed: 490 MB / 747 GB available
Continue? [Y/n] Y
...
Setting up linux-headers-6.15.3-1-siduction-amd64 (6.15-3) ...
/etc/kernel/header_postinst.d/dkms:
The kernel is built without module signing facility, modules won't be signed
Autoinstall of module tp_smapi/0.44 for kernel 6.15.3-1-siduction-amd64 (x86_64)
Building module(s)...(bad exit status: 2)
Failed command:
make -j16 KERNELRELEASE=6.15.3-1-siduction-amd64 -C /lib/modules/6.15.3-1-siduction-amd64/build M=/var/lib/dkms/tp_smapi/0.44/build HDAPS=1
Error! Bad return status for module build on kernel: 6.15.3-1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/tp_smapi/0.44/build/make.log for more information.
Autoinstall on 6.15.3-1-siduction-amd64 failed for module(s) tp_smapi(10).
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 1
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.15.3-1-siduction-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.15.3-1-siduction-amd64 (--configure):
installed linux-headers-6.15.3-1-siduction-amd64 package post-installation script subprocess returned error exit status 1
Setting up signal-desktop (7.58.0) ...
update-alternatives is /usr/bin/update-alternatives
Setting up sosreport (4.9.2-1) ...
Setting up libblockdev-nvme3:amd64 (3.3.0-2.1) ...
Setting up libblockdev-fs3:amd64 (3.3.0-2.1) ...
Setting up linux-doc-6.12 (6.12.33-1) ...
Setting up python3.13-minimal (3.13.5-1) ...
Setting up git-man (1:2.50.0-1) ...
dpkg: dependency problems prevent configuration of linux-headers-siduction-amd64:
linux-headers-siduction-amd64 depends on linux-headers-6.15.3-1-siduction-amd64 (= 6.15-3); however:
Package linux-headers-6.15.3-1-siduction-amd64 is not configured yet.
dpkg: error processing package linux-headers-siduction-amd64 (--configure):
dependency problems - leaving unconfigured
Setting up libgdk-pixbuf-2.0-0:amd64 (2.42.12+dfsg-3) ...
Setting up linux-doc (6.12.33-1) ...
Setting up curl (8.14.1-2) ...
Setting up xserver-common (2:21.1.16-1.2) ...
Setting up libgtk-4-common (4.18.6+ds-2) ...
Setting up mesa-va-drivers:amd64 (25.1.4-0siduction1) ...
Setting up libhivex0:amd64 (1.3.24-1+b10) ...
Setting up libc-dev-bin (2.41-9) ...
Setting up bind9-host (1:9.20.10-1) ...
Setting up xserver-xorg-legacy (2:21.1.16-1.2) ...
setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
Setting up libpython3.13-stdlib:amd64 (3.13.5-1) ...
Setting up libudisks2-0:amd64 (2.10.1-12.1) ...
Setting up libc-devtools (2.41-9) ...
Setting up libllvm18:amd64 (1:18.1.8-18+b1) ...
Setting up initramfs-tools-bin (0.148.2) ...
Setting up libpython3.13:amd64 (3.13.5-1) ...
Setting up mesa-vulkan-drivers:amd64 (25.1.4-0siduction1) ...
Setting up gtk-update-icon-cache (4.18.6+ds-2) ...
Setting up libqt6core6t64:amd64 (6.8.2+dfsg-7) ...
Setting up libglx-mesa0:amd64 (25.1.4-0siduction1) ...
Setting up libblockdev-mdraid3:amd64 (3.3.0-2.1) ...
Setting up gir1.2-gdkpixbuf-2.0:amd64 (2.42.12+dfsg-3) ...
Setting up libblockdev-crypto3:amd64 (3.3.0-2.1) ...
Setting up python3.13 (3.13.5-1) ...
Setting up libblockdev-swap3:amd64 (3.3.0-2.1) ...
Setting up librpm10:amd64 (4.20.1+dfsg-3) ...
Setting up libblockdev-loop3:amd64 (3.3.0-2.1) ...
Setting up xserver-xorg-core (2:21.1.16-1.2) ...
Setting up libglib2.0-bin (2.84.3-1) ...
Setting up rpm-common (4.20.1+dfsg-3) ...
Setting up libwin-hivex-perl (1.3.24-1+b10) ...
Setting up python3.13-venv (3.13.5-1) ...
Setting up libblockdev3:amd64 (3.3.0-2.1) ...
Setting up libgnome-desktop-3-20t64:amd64 (44.3-3) ...
Setting up libblockdev-part3:amd64 (3.3.0-2.1) ...
Setting up libgnome-desktop-4-2t64:amd64 (44.3-3) ...
Setting up libblockdev-btrfs3:amd64 (3.3.0-2.1) ...
Setting up libguestfs0t64:amd64 (1:1.54.1-2+b1) ...
Setting up libqt6xml6:amd64 (6.8.2+dfsg-7) ...
Setting up libqt6sql6:amd64 (6.8.2+dfsg-7) ...
Setting up libguestfs-xfs:amd64 (1:1.54.1-2+b1) ...
Setting up libqt6sql6-sqlite:amd64 (6.8.2+dfsg-7) ...
Setting up libpython3.13-dev:amd64 (3.13.5-1) ...
Setting up libguestfs-gfs2:amd64 (1:1.54.1-2+b1) ...
Setting up git (1:2.50.0-1) ...
Setting up libgdk-pixbuf2.0-bin (2.42.12+dfsg-3) ...
Setting up libguestfs-nilfs:amd64 (1:1.54.1-2+b1) ...
Setting up libgtk-4-1:amd64 (4.18.6+ds-2) ...
Setting up libc6-dev:amd64 (2.41-9) ...
Setting up libguestfs-perl (1:1.54.1-2+b1) ...
Setting up libgtk-4-bin (4.18.6+ds-2) ...
Setting up gir1.2-gnomedesktop-4.0:amd64 (44.3-3) ...
Setting up bind9-dnsutils (1:9.20.10-1) ...
Setting up initramfs-tools-core (0.148.2) ...
Setting up libguestfs-jfs:amd64 (1:1.54.1-2+b1) ...
Setting up libqt6dbus6:amd64 (6.8.2+dfsg-7) ...
Setting up gir1.2-gtk-4.0:amd64 (4.18.6+ds-2) ...
Setting up udisks2 (2.10.1-12.1) ...
Setting up guestfish (1:1.54.1-2+b1) ...
Setting up python3-guestfs (1:1.54.1-2+b1) ...
Setting up libguestfs-rsync:amd64 (1:1.54.1-2+b1) ...
Setting up udisks2-btrfs (2.10.1-12.1) ...
Setting up initramfs-tools (0.148.2) ...
update-initramfs: deferring update (trigger activated)
Setting up python3.13-dev (3.13.5-1) ...
Setting up libadwaita-1-0:amd64 (1.7.4-2) ...
Setting up libguestfs-rescue:amd64 (1:1.54.1-2+b1) ...
Setting up guestmount (1:1.54.1-2+b1) ...
Setting up libqt6gui6:amd64 (6.8.2+dfsg-7) ...
Setting up libgtk-4-media-gstreamer (4.18.6+ds-2) ...
Setting up libqt6network6:amd64 (6.8.2+dfsg-7) ...
Setting up linux-image-6.15.3-1-siduction-amd64 (6.15-3) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.14.10-1-siduction-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.14.10-1-siduction-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.15.3-1-siduction-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.15.3-1-siduction-amd64
/etc/kernel/postinst.d/dkms:
The kernel is built without module signing facility, modules won't be signed
Autoinstall of module tp_smapi/0.44 for kernel 6.15.3-1-siduction-amd64 (x86_64)
Building module(s)...(bad exit status: 2)
Failed command:
make -j16 KERNELRELEASE=6.15.3-1-siduction-amd64 -C /lib/modules/6.15.3-1-siduction-amd64/build M=/var/lib/dkms/tp_smapi/0.44/build HDAPS=1
Error! Bad return status for module build on kernel: 6.15.3-1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/tp_smapi/0.44/build/make.log for more information.
Autoinstall on 6.15.3-1-siduction-amd64 failed for module(s) tp_smapi(10).
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: error processing package linux-image-6.15.3-1-siduction-amd64 (--configure):
installed linux-image-6.15.3-1-siduction-amd64 package post-installation script subprocess returned error exit status 1
Setting up libqt6opengl6:amd64 (6.8.2+dfsg-7) ...
Setting up gir1.2-adw-1:amd64 (1.7.4-2) ...
Setting up libqt6widgets6:amd64 (6.8.2+dfsg-7) ...
dpkg: dependency problems prevent configuration of linux-image-siduction-amd64:
linux-image-siduction-amd64 depends on linux-image-6.15.3-1-siduction-amd64 (= 6.15-3); however:
Package linux-image-6.15.3-1-siduction-amd64 is not configured yet.
dpkg: error processing package linux-image-siduction-amd64 (--configure):
dependency problems - leaving unconfigured
Setting up libguestfs-tools (1:1.54.1-2+b1) ...
Setting up libqt6printsupport6:amd64 (6.8.2+dfsg-7) ...
Processing triggers for hicolor-icon-theme (0.18-2) ...
Processing triggers for doc-base (0.11.2) ...
Processing 6 changed doc-base files...
Processing triggers for gnome-menus (3.36.0-3) ...
Processing triggers for libc-bin (2.41-9) ...
Processing triggers for systemd (257.6-1) ...
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for dbus (1.16.2-2) ...
Processing triggers for install-info (7.1.1-1+b1) ...
Processing triggers for mailcap (3.74) ...
Processing triggers for desktop-file-utils (0.28-1) ...
Processing triggers for initramfs-tools (0.148.2) ...
update-initramfs: Generating /boot/initrd.img-6.14.10-1-siduction-amd64
I: The initramfs will attempt to resume from /dev/dm-1
I: (/dev/mapper/luks-400d59ef-905b-47cd-9d2b-aa1ccf74c098)
I: Set the RESUME variable to override this.
Errors were encountered while processing:
linux-headers-6.15.3-1-siduction-amd64
linux-headers-siduction-amd64
linux-image-6.15.3-1-siduction-amd64
linux-image-siduction-amd64
Config is in use.
needrestart is being skipped since dpkg has failed
Error: Sub-process /usr/bin/dpkg returned an error code (1)
# cat /var/lib/dkms/tp_smapi/0.44/build/make.log
DKMS (dkms-3.2.0) make.log for tp_smapi/0.44 for kernel 6.15.3-1-siduction-amd64 (x86_64)
So 22. Jun 07:26:43 CEST 2025
Building module(s)
# command: make -j16 KERNELRELEASE=6.15.3-1-siduction-amd64 -C /lib/modules/6.15.3-1-siduction-amd64/build M=/var/lib/dkms/tp_smapi/0.44/build HDAPS=1
make: Entering directory '/usr/src/linux-headers-6.15.3-1-siduction-amd64'
make[1]: Entering directory '/var/lib/dkms/tp_smapi/0.44/build'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: gcc-14 (Debian 14.2.0-19) 14.2.0
You are using: gcc (Debian 14.2.0-19) 14.2.0
CC [M] thinkpad_ec.o
CC [M] tp_smapi.o
CC [M] hdaps.o
hdaps.c: In function 'hdaps_suspend':
hdaps.c:430:9: error: implicit declaration of function 'del_timer_sync' [-Wimplicit-function-declaration]
430 | del_timer_sync(&hdaps_timer);
| ^~~~~~~~~~~~~~
make[3]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/scripts/Makefile.build:208: hdaps.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/Makefile:2027: .] Error 2
make[1]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/Makefile:260: __sub-make] Error 2
make[1]: Leaving directory '/var/lib/dkms/tp_smapi/0.44/build'
make: *** [Makefile:260: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-6.15.3-1-siduction-amd64'
# exit code: 2
# elapsed time: 00:00:01
----------------------------------------------------------------
Quote from: micspabo on 2025/06/22, 07:49:00
I do not have an NVIDIA card in my laptop. Whatever the kernel build failes during FU.
hdaps.c: In function 'hdaps_suspend':
hdaps.c:430:9: error: implicit declaration of function 'del_timer_sync' [-Wimplicit-function-declaration]
430 | del_timer_sync(&hdaps_timer);
| ^~~~~~~~~~~~~~
-------------------------------------------------------
del_timer_sync has been changed in the new kernel to timer_delete_sync. If you grep for it in the module code and swap it over, you'll at least get rid of that error. But if you don't have an nvidia card, do you have any nvidia packages installed that you could get rid of? Or just take the module out of /usr/src?
Quote from: Pip on 2025/06/22, 09:08:29
But if you don't have an nvidia card, do you have any nvidia packages installed that you could get rid of? Or just take the module out of /usr/src?
I cannot find a single nvidia package on my laptop
# dpkg -l | grep ii | grep nvidia | wc -l
0
I don't know which modules I would have to remove and how to start the build process afterwards. :(
# ls -lha /usr/src
drwxr-xr-x 1 root root 296 2025-06-22 07:25 .
drwxr-xr-x 1 root root 94 2023-09-09 21:02 ..
drwxr-xr-x 1 root root 576 2024-06-19 17:31 libdvd-pkg
drwxr-xr-x 1 root root 330 2025-06-12 19:31 linux-headers-6.14.10-1-siduction-amd64
drwxr-xr-x 1 root root 330 2025-05-29 18:17 linux-headers-6.14.9-1-siduction-amd64
drwxr-xr-x 1 root root 330 2025-06-22 07:25 linux-headers-6.15.3-1-siduction-amd64
drwxr-xr-x 1 root root 26 2025-01-10 23:19 python3.13
drwxr-xr-x 1 root root 120 2025-04-11 23:14 tp_smapi-0.44
Maybe the pitfalls will be fixed in the next kernel. Then at least I'll know that I can delete the "/usr/src/linux-headers-6.15.3-1-siduction-amd64" folder :). Until then, I'll try to carefully read the instructions mentioned.
With my limited understanding, I can't see anything you should remove from /usr/src - I have /usr/src/nvidia-tesla-470-470.256.02, which was why I thought it might be relevant. I've no idea why you'd be building the nvidia module if you've nothing that indicates you need it.
Out of curiosity I tried:
# cd /usr/src/linux-headers-6.15.3-1-siduction-amd64/
# grep -r del_timer_sync *
include/linux/timer.h:extern int try_to_del_timer_sync(struct timer_list *timer);
Module.symvers:0x00000000 try_to_del_timer_sync vmlinux EXPORT_SYMBOL
Then I changed the two "del_timer_sync" to "timer_delete_sync", and tried to build it.
# cd build/
# env NV_VERBOSE=1 make -j4 modules KERNEL_UNAME=6.15.3-1-siduction-amd64
make: *** No rule to make target 'modules'. Stop.
I have no idea so far how to correct the build call.
I repeated the search
# cd /usr/src/
# grep -r del_timer_sync *
I changed the two "del_timer_sync" to "timer_delete_sync" from tp_smapi-0.44/hdaps.c as well,
and have now tried the build process through:
# dpkg --configure -a
Setting up linux-headers-6.15.3-1-siduction-amd64 (6.15-3) ...
/etc/kernel/header_postinst.d/dkms:
The kernel is built without module signing facility, modules won't be signed
Autoinstall of module tp_smapi/0.44 for kernel 6.15.3-1-siduction-amd64 (x86_64)
Building module(s)...(bad exit status: 2)
Failed command:
make -j16 KERNELRELEASE=6.15.3-1-siduction-amd64 -C /lib/modules/6.15.3-1-siduction-amd64/build M=/var/lib/dkms/tp_smapi/0.44/build HDAPS=1
Error! Bad return status for module build on kernel: 6.15.3-1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/tp_smapi/0.44/build/make.log for more information.
Autoinstall on 6.15.3-1-siduction-amd64 failed for module(s) tp_smapi(10).
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 1
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.15.3-1-siduction-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.15.3-1-siduction-amd64 (--configure):
installed linux-headers-6.15.3-1-siduction-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-siduction-amd64:
linux-headers-siduction-amd64 depends on linux-headers-6.15.3-1-siduction-amd64 (= 6.15-3); however:
Package linux-headers-6.15.3-1-siduction-amd64 is not configured yet.
dpkg: error processing package linux-headers-siduction-amd64 (--configure):
dependency problems - leaving unconfigured
Setting up linux-image-6.15.3-1-siduction-amd64 (6.15-3) ...
/etc/kernel/postinst.d/dkms:
The kernel is built without module signing facility, modules won't be signed
Autoinstall of module tp_smapi/0.44 for kernel 6.15.3-1-siduction-amd64 (x86_64)
Building module(s)...(bad exit status: 2)
Failed command:
make -j16 KERNELRELEASE=6.15.3-1-siduction-amd64 -C /lib/modules/6.15.3-1-siduction-amd64/build M=/var/lib/dkms/tp_smapi/0.44/build HDAPS=1
Error! Bad return status for module build on kernel: 6.15.3-1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/tp_smapi/0.44/build/make.log for more information.
Autoinstall on 6.15.3-1-siduction-amd64 failed for module(s) tp_smapi(10).
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
dpkg: error processing package linux-image-6.15.3-1-siduction-amd64 (--configure):
installed linux-image-6.15.3-1-siduction-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-siduction-amd64:
linux-image-siduction-amd64 depends on linux-image-6.15.3-1-siduction-amd64 (= 6.15-3); however:
Package linux-image-6.15.3-1-siduction-amd64 is not configured yet.
dpkg: error processing package linux-image-siduction-amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-headers-6.15.3-1-siduction-amd64
linux-headers-siduction-amd64
linux-image-6.15.3-1-siduction-amd64
linux-image-siduction-amd64
# cat /var/lib/dkms/tp_smapi/0.44/build/make.log
DKMS (dkms-3.2.0) make.log for tp_smapi/0.44 for kernel 6.15.3-1-siduction-amd64 (x86_64)
So 22. Jun 13:30:37 CEST 2025
Building module(s)
# command: make -j16 KERNELRELEASE=6.15.3-1-siduction-amd64 -C /lib/modules/6.15.3-1-siduction-amd64/build M=/var/lib/dkms/tp_smapi/0.44/build HDAPS=1
make: Entering directory '/usr/src/linux-headers-6.15.3-1-siduction-amd64'
make[1]: Entering directory '/var/lib/dkms/tp_smapi/0.44/build'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: gcc-14 (Debian 14.2.0-19) 14.2.0
You are using: gcc (Debian 14.2.0-19) 14.2.0
CC [M] thinkpad_ec.o
CC [M] tp_smapi.o
CC [M] hdaps.o
MODPOST Module.symvers
ERROR: modpost: parse error in symbol dump file
make[3]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/scripts/Makefile.modpost:147: Module.symvers] Error 1
make[2]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/Makefile:1977: modpost] Error 2
make[1]: *** [/usr/src/linux-headers-6.15.3-1-siduction-amd64/Makefile:260: __sub-make] Error 2
make[1]: Leaving directory '/var/lib/dkms/tp_smapi/0.44/build'
make: *** [Makefile:260: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-6.15.3-1-siduction-amd64'
# exit code: 2
# elapsed time: 00:00:00
----------------------------------------------------------------
Now it fails as the kernel was build by gcc-14 and dpkg is using the gcc,- otherwise both versions are the same.
Could someone please point me in the right direction to overcome this hurdle?
Thanks in advance.
I didn't make things clear, sorry about that: it was only in the nvidia module where things should change, from what I was doing. Whether it would be needed in tp_smapi-0.44 as well, I couldn't tell you since I don't know the module. timer_delete_sync is how it's meant to be in the kernel, there was nothing in the kernel to change. There was try_to_del_timer_sync, but that should have stayed as was.
Definitely revert the kernel headers to the way they were.
To indicate just how much you should pay attention to what I say, I have now managed to get the nvidia module to build with very few warnings and install. After which, I can't start the system in gui mode with the new kernel. Back at the older kernel now.
@pip: Thank you for your explanations.
Only because the installation of kernel 6.15.3-1-siduction-amd64 failed during full-upgrade,
because the linux-headers-6.15.3-1-siduction-amd64 could not be compiled, I dared to make some changes.
I see that it was not successfull.
At this stage I would just undo the changes from tp_smapi-0.44/hdaps.c,
delete the folder "linux-headers-6.15.3-1-siduction-amd64" from /usr/src/
and hope that the next 6.15 kernel will install as usual.
The first kernel 6.15.3-1 wasn't even installed when it arrived on my laptop.
# dkms status
tp_smapi/0.44, 6.14.10-1-siduction-amd64, x86_64: installed (Original modules exist)
tp_smapi/0.44, 6.14.9-1-siduction-amd64, x86_64: installed (Original modules exist)
I hope my strategy pays off. 8)
To make it clear, there will nothing changed with the next siduction kernel!
The fix has to be in tp_smapi!
I built a beta version
nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.1b_amd64.deb
compatible with all the other packages from the maintainer. Simply do a
$ sudo apt-get install nvidia-tesla-470-driver
and when the original package nvidia-tesla-470-kernel-dkms fails, simply replace it by
$ sudo dpkg -i nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.1b_amd64.deb
If someone is still interested to try it out, here is the link:
<https://wormhole.app/kz5ax2#6gCJh98boqZFh9_tQpjnhA>
md5sum name
da34517c6278756bd358a90c3a04dfa5 nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.1b_amd64.deb
Thanks for that. It came up with an error /var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia-modeset/nvidia-modeset-linux.c: In function 'nvkms_kthread_q_callback':
/var/lib/dkms/nvidia-tesla-470/470.256.02/build/nvidia-modeset/nvidia-modeset-linux.c:721:9: error: implicit declaration of function 'timer_delete_sync' [-Werror=implicit-function-declaration]
721 | timer_delete_sync(&timer->kernel_timer);
I tried changing the nvidia-modeset-linux.c source so that it had #include <linux/timer.h> in it just in case, but the same error turned up. After poking around for a bit, it looks like it is somewhat out of my league. Or would be if I'd every reached a league.
Well, someone is obviously working on it in the meantime
(maybe towo, and hopefully incorporates the patch):
$ apt-get download nvidia-tesla-470-kernel-dkms (now, 23:03h):
nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.3_amd64.deb
$ apt-get download nvidia-tesla-470-kernel-dkms (then, 17:00h):
nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.1_amd64.deb
But it's not working yet:
Applying patch nvidia-470xx-fix-linux-6.14.patch...(bad exit status: 1)
Failed command:
patch -p1 < ./patches/nvidia-470xx-fix-linux-6.14.patch
But I'm sure, he will figure it out. Maybe I'll fix it in the meantime,
make it a race...
...and here we go:
<https://wormhole.app/vbNaAk#XPEJPPIdE2Qb3mN2eayW1Q>
md5sum: filename:
592eca374baacce37bd2e9ac4e3a82b9 nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.3b_amd64.deb
@Pip:
I had no problems installing the 3b version neither with kernel 6.15 nor with 6.14 (and all the other tesla-470 packages).
If it still fails for you, report back with some details...
and just in case (I'm getting ahead of myself...):
https://wormhole.app/5KWzrP#0ojWtHwfQ0MgJbCkzuCU-g
320ef59ed0825db1978c7c221a5b607b nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4b_amd64.deb
https://wormhole.app/nA6apD#Vx3We1pMBLJgDrCFg53CKw
d1f58d1e79f53b9935958bc90ecd3c5d nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.5b_amd64.deb
@towo (or so I guess)
the final patch has still problems (4 vs.4b:
Applying patch use-kbuild-flags.patch...(bad exit status: 1)
Failed command:
patch -p1 < ./patches/use-kbuild-flags.patch
But you are closing in (hint: EXTRA_CCFLAGS in wrong context after 6.15 patch, I guess)
I still have a working 5b version to offer...
with your 5b version, i get:
towo:Defiant> patch -p1 < ./patches/use-kbuild-flags.patch
patching file Kbuild
Hunk #1 FAILED at 108.
1 out of 1 hunk FAILED -- saving rejects to file Kbuild.rej
patching file nvidia/nvidia.Kbuild
Hunk #1 succeeded at 94 (offset 2 lines).
patching file Makefile
patching file nvidia-modeset/nvidia-modeset.Kbuild
Hunk #1 succeeded at 79 (offset 2 lines).
if i apply
cc_version_check-gcc5.patch
bashisms.patch
0001-some-power-management-features-were-not-yet-in-Linux.patch
0033-refuse-to-load-legacy-module-if-IBT-is-enabled.patch
0034-fix-typos.patch
0037-import-pfn_valid-w-o-GPL-rcu_read_lock-unlock-from-v.patch
0042-Log-an-error-message-when-nv_mem_client_init-fails-d.patch
0043-backport-follow_pfn-changes-from-550.90.07.patch
0045-let-the-virt_addr_valid-macro-use-nv_pfn_valid-on-pp.patch
0046-virt_addr_valid-wants-a-void-argument.patch
kernel-6.12.patch
kernel-6.13.patch
nvidia-470xx-fix-linux-6.14.patch
fragile-ARCH.patch
conftest-verbose.patch
use-kbuild-compiler.patch
before.
That's strange. Did you check the 4b version, because last time I checked,
it worked, but let's try again... hang on...
-----------------------------------------------------
Regular 'sudo apt-get sudo apt-get install nvidia-tesla-470-driver' install with
nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4_amd64.deb:
Loading new nvidia-tesla-470/470.256.02 DKMS files...
Building for 6.15.3-1-siduction-amd64
Building initial module nvidia-tesla-470/470.256.02 for 6.15.3-1-siduction-amd64
The kernel is built without module signing facility, modules won't be signed
Applying patch cc_version_check-gcc5.patch... done.
Applying patch bashisms.patch... done.
Applying patch 0001-some-power-management-features-were-not-yet-in-Linux.patch... done.
Applying patch 0033-refuse-to-load-legacy-module-if-IBT-is-enabled.patch... done.
Applying patch 0034-fix-typos.patch... done.
Applying patch 0037-import-pfn_valid-w-o-GPL-rcu_read_lock-unlock-from-v.patch... done.
Applying patch 0042-Log-an-error-message-when-nv_mem_client_init-fails-d.patch... done.
Applying patch 0043-backport-follow_pfn-changes-from-550.90.07.patch... done.
Applying patch 0045-let-the-virt_addr_valid-macro-use-nv_pfn_valid-on-pp.patch... done.
Applying patch 0046-virt_addr_valid-wants-a-void-argument.patch... done.
Applying patch kernel-6.12.patch... done.
Applying patch kernel-6.13.patch... done.
Applying patch nvidia-470xx-fix-linux-6.14.patch... done.
Applying patch nvidia-470xx-fix-linux-6.15.patch... done.
Applying patch fragile-ARCH.patch... done.
Applying patch conftest-verbose.patch... done.
Applying patch use-kbuild-compiler.patch... done.
Applying patch use-kbuild-flags.patch...(bad exit status: 1)
Failed command:
patch -p1 < ./patches/use-kbuild-flags.patch
Error! Application of patch use-kbuild-flags.patch failed.
-----------------------------------------------------
After the error I did a
sudo dpkg -i nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4b_amd64.deb
with the following result:
(Lese Datenbank ... 312816 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4b_amd64.deb ...
Deleting module nvidia-tesla-470/470.256.02 completely from the DKMS tree.
Entpacken von nvidia-tesla-470-kernel-dkms (470.256.02-7.siduction.4b) über (470.256.02-7.siduction.4) ...
nvidia-tesla-470-kernel-dkms (470.256.02-7.siduction.4b) wird eingerichtet ...
Loading new nvidia-tesla-470/470.256.02 DKMS files...
Building for 6.15.3-1-siduction-amd64
Building initial module nvidia-tesla-470/470.256.02 for 6.15.3-1-siduction-amd64
The kernel is built without module signing facility, modules won't be signed
Applying patch cc_version_check-gcc5.patch... done.
Applying patch bashisms.patch... done.
Applying patch 0001-some-power-management-features-were-not-yet-in-Linux.patch... done.
Applying patch 0033-refuse-to-load-legacy-module-if-IBT-is-enabled.patch... done.
Applying patch 0034-fix-typos.patch... done.
Applying patch 0037-import-pfn_valid-w-o-GPL-rcu_read_lock-unlock-from-v.patch... done.
Applying patch 0042-Log-an-error-message-when-nv_mem_client_init-fails-d.patch... done.
Applying patch 0043-backport-follow_pfn-changes-from-550.90.07.patch... done.
Applying patch 0045-let-the-virt_addr_valid-macro-use-nv_pfn_valid-on-pp.patch... done.
Applying patch 0046-virt_addr_valid-wants-a-void-argument.patch... done.
Applying patch kernel-6.12.patch... done.
Applying patch kernel-6.13.patch... done.
Applying patch nvidia-470xx-fix-linux-6.14.patch... done.
Applying patch nvidia-470xx-fix-linux-6.15.patch... done.
Applying patch fragile-ARCH.patch... done.
Applying patch conftest-verbose.patch... done.
Applying patch use-kbuild-compiler.patch... done.
Applying patch conftest-prefer-arch-headers.patch... done.
Applying patch use-kbuild-flags.patch... done.
Building module(s)........................ done.
Installing /lib/modules/6.15.3-1-siduction-amd64/updates/dkms/nvidia-tesla-470.ko
Installing /lib/modules/6.15.3-1-siduction-amd64/updates/dkms/nvidia-tesla-470-modeset.ko
Installing /lib/modules/6.15.3-1-siduction-amd64/updates/dkms/nvidia-tesla-470-drm.ko
Installing /lib/modules/6.15.3-1-siduction-amd64/updates/dkms/nvidia-tesla-470-uvm.ko
Installing /lib/modules/6.15.3-1-siduction-amd64/updates/dkms/nvidia-tesla-470-peermem.ko
Running depmod... done.
------------------------------------------------------------------------------------------
The 5b file is identical to 4b except for the version information in the debian control file.
If I remember correctly I ran into the same error as you did, so I not only corrected
the order of the patches in dkms.conf, but also the content of "use-kbuild-flags.patch" to
account for the context change of the 470xx 6.15 patch (which also was adapted) and make
the hunk succeed.
All the installation was done on a virtualized latest siduction iso image with the latest
changes from debian and siduction. I suggest you unpack the 4b file and have a closer look at
the 6.15 and kbuild patch. They could be different from yours.
@towo:
Got it!
Simply replace line 19 in "use-kbuild-flags.patch"
(of your current nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4_amd64.deb, 15:00h):
NV_CONFTEST_CFLAGS = $(NV_CFLAGS_FROM_CONFTEST) $(EXTRA_CFLAGS) -fno-pie
by
NV_CONFTEST_CFLAGS = $(NV_CFLAGS_FROM_CONFTEST) $(ccflags-y) -fno-pie
and it should work fine!
Sorry for the delay in replying, I'd lost my GUI. Very careless of me.
I did try the latest update and put in place the suggested line 19 change, but it still came back with the error I mentioned in my last post. It's now taken me a while to strip out nvidia and set up/etc/X11/xorg.conf.d/20-nouveau.conf but now I have my GUI back.
Thank you for all the attempts. If nouveau handles things for me, maybe I won't need to worry about this any more.
Hi Pip,
Don't give up so easily, and besides: The nouveau driver offers only restricted functionality.
Proceed a follows:
$ sudo apt-get update
$ sudo apt-get install nvidia-tesla-470-driver
The last command fails on nvidia-tesla-470-kernel-dkms (unless towo applied the patch in the meantime,
hence check for version nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4).
Get the patched version from
https://wormhole.app/08x65v#teV4IvWkirPB-eXLrijzPA
md5sum filename
6acbeb508691f14d481cc44798e748ff nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4c_amd64.deb
(Don't worry about the 4c, it simply contains the latest patch and will reinstall the 4 version, btw: the link is
only valid for the next 24 hours)
Install it:
$ sudo dpkg -i nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4c_amd64.deb
If it fails, please attach the output of the last command in your next message.
Good luck!
PS.: I'd like to see an output like the following with all the gory details:
-----------------------------------------------------
After the error I did a
sudo dpkg -i nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4c_amd64.deb
with the following result:
(Lese Datenbank ... 312816 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4c_amd64.deb ...
Deleting module nvidia-tesla-470/470.256.02 completely from the DKMS tree.
Entpacken von nvidia-tesla-470-kernel-dkms (470.256.02-7.siduction.4b) über (470.256.02-7.siduction.4) ...
nvidia-tesla-470-kernel-dkms (470.256.02-7.siduction.4b) wird eingerichtet ...
Loading new nvidia-tesla-470/470.256.02 DKMS files...
Building for 6.15.3-1-siduction-amd64
Building initial module nvidia-tesla-470/470.256.02 for 6.15.3-1-siduction-amd64
The kernel is built without module signing facility, modules won't be signed
Applying patch cc_version_check-gcc5.patch... done.
Applying patch bashisms.patch... done.
Applying patch 0001-some-power-management-features-were-not-yet-in-Linux.patch... done.
Applying patch 0033-refuse-to-load-legacy-module-if-IBT-is-enabled.patch... done.
Applying patch 0034-fix-typos.patch... done.
Applying patch 0037-import-pfn_valid-w-o-GPL-rcu_read_lock-unlock-from-v.patch... done.
Applying patch 0042-Log-an-error-message-when-nv_mem_client_init-fails-d.patch... done.
Applying patch 0043-backport-follow_pfn-changes-from-550.90.07.patch... done.
Applying patch 0045-let-the-virt_addr_valid-macro-use-nv_pfn_valid-on-pp.patch... done.
Applying patch 0046-virt_addr_valid-wants-a-void-argument.patch... done.
Applying patch kernel-6.12.patch... done.
Applying patch kernel-6.13.patch... done.
Applying patch nvidia-470xx-fix-linux-6.14.patch... done.
Applying patch nvidia-470xx-fix-linux-6.15.patch... done.
Applying patch fragile-ARCH.patch... done.
Applying patch conftest-verbose.patch... done.
Applying patch use-kbuild-compiler.patch... done.
Applying patch conftest-prefer-arch-headers.patch... done.
Applying patch use-kbuild-flags.patch... done.
Building module(s)........................ done.
Installing /lib/modules/6.15.3-1-siduction-amd64/updates/dkms/nvidia-tesla-470.ko
Installing /lib/modules/6.15.3-1-siduction-amd64/updates/dkms/nvidia-tesla-470-modeset.ko
Installing /lib/modules/6.15.3-1-siduction-amd64/updates/dkms/nvidia-tesla-470-drm.ko
Installing /lib/modules/6.15.3-1-siduction-amd64/updates/dkms/nvidia-tesla-470-uvm.ko
Installing /lib/modules/6.15.3-1-siduction-amd64/updates/dkms/nvidia-tesla-470-peermem.ko
Running depmod... done.
------------------------------------------------------------------------------------------
If the patches succeed, it has nothing to do with the deb file, but rather with a somehow broken build
system. We have to know, otherwise we are digging forever...
Hi Teriarch,
your package works for me. NVIDIA GK107GL [Quadro 410], kernel 6.15.3-1-siduction-amd64
@Geier0815:
good to hear, but be aware that any dist-upgrade reinstalls towos version 4 package
because of the siduction's site superior priority. I could circumvent the reinstall
by upgrading the version slightly and declaring an additional "Provides:..." entry in
the Debian control file, but I am counting on towo to apply the patch and upgrading
all tesla packages to version 5 in the meantime. So this is a waste of time.
Now that the drivers are loading doesn't imply they are running smoothly. So feel
free to test them to your heart's content and report back any problems.
@towo
Just out of curiosity and because I want this case closed. The siduction repo still
contains nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4_amd64.deb
from Jun, 22nd 23:44 which fails on kernel 6.15. However, we have a working
solution confirmed by positive feedback from Geier0815. The remaining changes
to the current version are rather minimal compared to the work already done. I
also understand that the interest in the tesla version is rather low and that you
have to keep mainstream changes up to date.
So, are you planning on a recent update to the current version?
And if not, what considerations are holding you back?
Thx in adv
I have no time at the moment to fix that package, maybe until next week i can't do that.
For me, it was
(Reading database ... 490916 files and directories currently installed.)
Preparing to unpack .../nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4c_amd64.deb ...
Deleting module nvidia-tesla-470/470.256.02 completely from the DKMS tree.
Unpacking nvidia-tesla-470-kernel-dkms (470.256.02-7.siduction.4) over (470.256.02-7.siduction.4) ...
Setting up nvidia-tesla-470-kernel-dkms (470.256.02-7.siduction.4) ...
Loading new nvidia-tesla-470/470.256.02 DKMS files...
Building for 6.1.0-1-amd64, 6.1.0-2-amd64, 6.14.9-1-siduction-amd64, 6.14.10-1-siduction-amd64 and 6.15.3-1-siduction-amd64
Building initial module nvidia-tesla-470/470.256.02 for 6.1.0-1-amd64
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Applying patch cc_version_check-gcc5.patch... done.
Applying patch bashisms.patch... done.
Applying patch 0001-some-power-management-features-were-not-yet-in-Linux.patch... done.
Applying patch 0033-refuse-to-load-legacy-module-if-IBT-is-enabled.patch... done.
Applying patch 0034-fix-typos.patch... done.
Applying patch 0037-import-pfn_valid-w-o-GPL-rcu_read_lock-unlock-from-v.patch... done.
Applying patch 0042-Log-an-error-message-when-nv_mem_client_init-fails-d.patch... done.
Applying patch 0043-backport-follow_pfn-changes-from-550.90.07.patch... done.
Applying patch 0045-let-the-virt_addr_valid-macro-use-nv_pfn_valid-on-pp.patch... done.
Applying patch 0046-virt_addr_valid-wants-a-void-argument.patch... done.
Applying patch kernel-6.12.patch... done.
Applying patch kernel-6.13.patch... done.
Applying patch nvidia-470xx-fix-linux-6.14.patch... done.
Applying patch nvidia-470xx-fix-linux-6.15.patch... done.
Applying patch fragile-ARCH.patch... done.
Applying patch conftest-verbose.patch... done.
Applying patch use-kbuild-compiler.patch... done.
Applying patch use-kbuild-flags.patch... done.
Applying patch conftest-prefer-arch-headers.patch... done.
Building module(s).........(bad exit status: 2)
Failed command:
env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.1.0-1-amd64
with the error being the one I mentioned before
Thanks to both of you for trying. I'll see about slipping back into nouveau if my GUI fails to start again.
Maybe a stupid question but for what reason do you need such an old kernel (6.1.0-1 released end of 2022)?
Quote from: towo on 2025/06/24, 18:56:50
I have no time at the moment to fix that package, maybe until next week i can't do that.
Hi towo,
thanks for letting us know!
As far as I am concerned, I am happy when the fix is available in the foreseeable future, in weeks. Thanks for even caring about proprietary legacy drivers.
Quote from: Geier0815 on 2025/06/24, 20:14:50
Maybe a stupid question but for what reason do you need such an old kernel (6.1.0-1 released end of 2022)?
A fine question! I hadn't even noticed that. apt auto-remove and the kernel remover don't think they're there, but the header files certainly are. I'll trim that. Thanks.
@Pip
Thanks to Geier0815 it all makes sense now. I can almost guarantee that after the old kernel
removal everything works fine. Unfortunately the link already expired, so I will renew it for
your convenience. And please report back about success or failure (you are so close now)...
https://wormhole.app/D1x576#VaPpC8kIpQjuecFyK6rblw
md5sum filename
d93464b119ea55f44006614a40848a4c nvidia-tesla-470-kernel-dkms_470.256.02-7.siduction.4c_amd64.deb
@towo
Thanks for clarifying!
I downloaded it before I reported back last time, that was the result with it. I'll give it another try tomorrow without the old headers.
I don't know the state of your installation, but "without something old" does not seem to be the appropriate prerequisite to overcome modul building problems with the newest sources. An up-to-date system without any cruft could be.
Quote from: michaa7 on 2025/06/26, 01:11:30
I don't know the state of your installation, but "without something old" does not seem to be the appropriate prerequisite to overcome modul building problems with the newest sources. An up-to-date system without any cruft could be.
Quite so, quite so. And I didn't really think it would solve anything since the module was being built against the latest kernel with the latest headers.
However...
The module got built, the system is stable again!
Thanks to Teriarch, Geier0815 and towo for putting in the time, effort and "stupid" questions.
Glad to hear that you finally solved your problem (with a little help from your friends...).
And there are no stupid questions, just stupid answers!
Not sure if this thread is pertinent to the problem I am having.
Last working kernel is 6.14.10-1, as both 6.15.3-1 and now even 6.15.4-1 will not allow building nvidia-current module for them, the process will fail.
The following is just an excerpt of what I mean:
Autoinstall of module nvidia-current/550.163.01 for kernel 6.15.4-1-siduction-amd64 (x86_64)
Building module(s)..............(bad exit status: 2)
Failed command:
env NV_VERBOSE=1 make -j12 modules KERNEL_UNAME=6.15.4-1-siduction-amd64
Error! Bad return status for module build on kernel: 6.15.4-1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/550.163.01/build/make.log for more information.
Autoinstall on 6.15.4-1-siduction-amd64 failed for module(s) nvidia-current(10).
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 1
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.15.4-1-siduction-amd64.postinst
line 11.
dpkg: error processing package linux-headers-6.15.4-1-siduction-amd64 (--configure):
installed linux-headers-6.15.4-1-siduction-amd64 package post-installation script subprocess returned error exit stat
us 1
Setting up linux-image-6.15.4-1-siduction-amd64 (6.15-4) ...
I: /initrd.img is now a symlink to boot/initrd.img-6.15.4-1-siduction-amd64
/etc/kernel/postinst.d/dkms:
The kernel is built without module signing facility, modules won't be signed
Autoinstall of module nvidia-current/550.163.01 for kernel 6.15.4-1-siduction-amd64 (x86_64)
Building module(s)..............(bad exit status: 2)
Failed command:
env NV_VERBOSE=1 make -j12 modules KERNEL_UNAME=6.15.4-1-siduction-amd64
For me it got built (for both kernels, the last one today). So there must be something peculiar in your environment.
Problem is: what?
Edit: Corrected the date (today, not yesterday)
I had the GPT guide me, and after sharing the nvidia make.log with it, here's part of its response:
❌ Root Cause:
The build fails due to missing or incompatible kernel symbols in Linux 6.15.x:
/var/lib/dkms/nvidia-current/550.163.01/build/nvidia/nv-dma.c: In function 'nv_dma_map_pages':
... warning: passing argument from incompatible pointer type
...
/var/lib/dkms/nvidia-current/550.163.01/build/nvidia/nv-pci.c: error: implicit declaration of function 'pci_enable_msi'; did you mean 'pci_enable_msix'?
🧨 Most critical error:
error: implicit declaration of function 'pci_enable_msi'
This means that the NVIDIA driver is using kernel APIs that have changed or been removed in kernel 6.15. These changes break compatibility with NVIDIA 550.163.01 — which was last known to support kernels up to ~6.8 or 6.9.
✅ Confirmed: NVIDIA 550.163.01 does not yet support Linux 6.15
As of now:
NVIDIA hasn't updated their proprietary drivers to support Linux 6.15 kernel headers.
The issue is due to removed/changed kernel functions, not your system setup.
Do you have the repo "deb https://packages.siduction.org/fixes unstable main contrib non-free non-free-firmware" activated? If not, do so
...I just discovered that all .list files under /etc/apt/sources.list.d/ have been renamed to *.list.bak so there's that
EDIT: they were just updated into .sources files. I added `contrib non-free non-free-firmware` near to `main` in fixes.sources and it found more packages to update, churning now.
EDIT 2: should I also add `contrib non-free non-free-firmware` to the other repos, for good measure?
EDIT 3: Thanks! I could boot into 6.15.4. Now virtualbox complains about a missing driver ::)
EDIT 4: virtualbox 7.1.10 fixed the issue
@n4ai9i522:
To "EDIT 2": Well, I did so - add the "rest" - and I have not experienced any negative effects from it.
Quote from: towo on 2025/06/24, 18:56:50
I have no time at the moment to fix that package, maybe until next week i can't do that.
Hi towo,
would be nice if you find some time to make a fixed nvidia-470 package.
OTOH, if, as you wrote, the
tp_smapi thing is the package to fix, is there already a DEBIAN bug report and will it get fixed there eventually? As Debian/experimental still provides only an 6.12xx kernel, I think it will last a year until Debian arrives at 6.15 Kernel source and gets aware of this problem.
So, I am in no hurry for a fixed nvidia-driver, but I definitivley would like to not being cut out forever ;-)
BTW: Isn't "tp-smapi" a thinkpad thing? Does this thing influence the nvidia driver for all other computers?
Hi ...
jetzt habe ich mal testweise ein komplettes d-u gemacht ... um zu sehen was stand der Dinge mit dem nvidia-tesla-470-driver ist ... und jetzt stehe ich komplett ohne X da. Selbst für den 6.14.xxx wurde das bestehende modul gelöscht und das neue baut eben nicht.
Ich blicke da nicht durch was da wo gefixt werden muss, weiß aber in diesem Fall auch nicht welche Schrauben (Pakete) ich zurückdrehen müsste um wenigsten mit dem 6.14.xxx noch nach X booten zu können. Dan 6.15.xx und den 6.16.xx Kernel habe ich nun eben gepurged, aber das bislang funktionierende Modul für den 6.14.xxx ist ja wohl nicht mehr da. Wie bekomme ich das? Muss ich dkms downgraden, oder nvidia oder beides?
Wenn ich das richtig verstehe (errate) dann benötige ich nvidia-tesla-470-driver in version 470.256.02-7.siduction.1 (die läuft hier in der parallelinstalltion. Die habe ich aber nicht mehr im archiv.) Woher bekomme ich die nochmals?
Irgendeine Hilfe?
dpkg-reconfigure nvidia-tesla-470-kernel-dkms
danke. Werde ich gleich testen ..
Du stellst keine 470 fixes mehr zur Verfügung?
EDIT:
dpkg-reconfigure nvidia-tesla-470-kernel-dkms ->
"nvidia-tesla-470-kernel-dkms is broken or not fully installed"
Do you know whether it was reported that there was a discrepancy between gcc for the 470 package and the kernel? I rebuilt the package with the new gcc (15) and it fixed things. I've got nvidia-tesla-470-470.256.02.
I've got 6.16.3-1-siduction-amd64. I haven't tried linux-image-6.16.3-2-siduction-amd64 yet. Which release were you having problems with?
sure I knew ... I participated in this thread. (EDIT: No, I have no clue about gcc and problems with modul built)
But today
I did a d-u 'caus I didn't got an answer as to whethter towo provided fixed pakeges or not .. so I tried ... stupid idea.
I know you built your driver on your own, but I do not have the nerves for it ... really not. I think I need the nvidia...siduction.1 driver, not the nvidia...siduction.4, for a downgrade, (for kernel 6.14), but I do not have it in the archives anymore
...and I think the above command did not work because it is *.4 instead of *.1 . I am really screwed now ...
EDIT:
Beim Versuch nvidia-tesla-470-kernel-dkms zu installieren kommt es zu diesem Fehler:
QuoteFailed command:
patch -p1 < ./patches/use-kbuild-flags.patch
Im entsprechenden log steht als einziger Fehler:
QuoteFailed at 108
Why don't you switch to nouveau? I've did it and most things work as expected. If you have an Quadro-card you need firmware-nvidia-graphics and if possible remove nomodeset from /etc/default/grub in the line that starts with GRUB_CMDLINE_LINUX_DEFAULT that will give you a lot more resolutions to choose from
Quote from: Geier0815 on 2025/08/26, 20:35:40
Why don't you switch to nouveau? ..
that's what I won't discuss yet.
Quote from: michaa7 on 2025/08/26, 17:42:16
danke. Werde ich gleich testen ..
Du stellst keine 470 fixes mehr zur Verfügung?
EDIT:
dpkg-reconfigure nvidia-tesla-470-kernel-dkms ->
"nvidia-tesla-470-kernel-dkms is broken or not fully installed"
apt install --reinstall nvidia-tesla-470-kernel-dkms
towo, das habe ich schon mehrfach gemacht. Es geht um die VERSION!
Edit: Das --reinstall läuft nicht durch:
QuoteFehler: Internal error
No file for nvidia-tesla-470-kernel-dkms:amd64
Diese neueste Version war ja auch noch nie voll installiert weil es damit zu Fehlern kam.
Meiner Ansicht nach benötige ich nvidia-tesla-470-driver in version 470.256.02-7.siduction.
1 inkl. nvidia-tesla-470-kernel-dkms in version 470.256.02-7.siduction.
1Die läuft auch hier in meiner parallel installation. Die nvidia ...siduction.
4 wurde heute ja erst drübergebügelt. Die hatte ich seinerzeit ge-downgradet auf die siduction.1 damit es wieder geht. Nur habe ich letztere nicht mehr im Archiv.
Ich hatte oben auch editiert ... zu spät, im dkms install log steht als einziger Fehler:
Quote
Zitat
Failed at 108
:
Bitte, finde entweder diese alten pakete in irgend einer ecke des servers oder , OMG, stelle bitte eine gefixte Version von was auch immer notwendig ist bereit.
Nouveau habe ich probiert, aber der produziert Fehler, hier z.B. gibt es nun keine Städtenamen mehr:
https://www.wetteronline.de/wetterradar/aachen