linux-image-6.3.3-1-siduction-amd64 + nvidia

Started by michaa7, 2023/05/22, 14:29:08

Previous topic - Next topic
Print
Go Down Pages1
User actions

michaa7

2023/05/22, 14:29:08

Problem mit linux-image-6.3.3-1-siduction-amd64 und nvidia 470 modul


QuoteBuilding module:                                                                     
Cleaning build area...                                                               
env NV_VERBOSE=1 make -j2 modules KERNEL_UNAME=6.3.3-1-siduction-amd64..........      ............(bad exit status: 2)                                                     
Error! Bad return status for module build on kernel: 6.3.3-1-siduction-amd64 (x8      6_64)                                                                                 
Consult /var/lib/dkms/nvidia-tesla-470/470.182.03/build/make.log for more inform      ation.                                                                               
Error! One or more modules failed to install during autoinstall.                     
Refer to previous errors for more information.                                       
dkms: autoinstall for kernel: 6.3.3-1-siduction-amd64 failed!                         
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11                     
dpkg: Fehler beim Bearbeiten des Paketes linux-image-6.3.3-1-siduction-amd64 (--      configure):                                                                           
»installiertes post-installation-Skript des Paketes linux-image-6.3.3-1-siduction-amd64«-Unterprozess gab den Fehlerwert 1 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-headers-siduction-amd64:
linux-headers-siduction-amd64 hängt ab von linux-headers-6.3.3-1-siduction-amd64 (= 6.3-3); aber:
  Paket linux-headers-6.3.3-1-siduction-amd64 ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes linux-headers-siduction-amd64 (--configure):
Abhängigkeitsprobleme - verbleibt unkonfiguriert
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-image-siduction-amd64:




Quote$ inxi -G
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 710] driver: nvidia v: 470.182.03
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
    resolution: 1680x1050~60Hz
  API: OpenGL v: 4.6.0 NVIDIA 470.182.03 renderer: NVIDIA GeForce GT
    710/PCIe/SSE2


Hier gibt es beim modulbau wohl Fehler ( /var/lib/dkms/nvidia-tesla-470/470.182.03/build/make.log )

Quotemodule /var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-p2p.o
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c: In function 'nvidia_mmap_helper
':
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c:599:23: error: assignment of rea
d-only member 'vm_flags'
  599 |        vma->vm_flags |= VM_IO | VM_PFNMAP | VM_DONTEXPAND;
      |                      ^~
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c:666:23: error: assignment of rea
d-only member 'vm_flags'
  666 |        vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
      |                      ^~
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c:667:23: error: assignment of rea
d-only member 'vm_flags'
  667 |        vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
      |                      ^~
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c:673:23: error: assignment of rea
d-only member 'vm_flags'
  673 |        vma->vm_flags &= ~VM_WRITE;
      |                      ^~
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c:674:23: error: assignment of rea
d-only member 'vm_flags'
  674 |        vma->vm_flags &= ~VM_MAYWRITE;
      |                      ^~
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c: In function 'nv_encode_caching'
:
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c:348:16: warning: this statement
may fall through [-Wimplicit-fallthrough=]
  348 |            if (NV_ALLOW_CACHING(memory_type))
Gibt es anderes was ich aus dem langen log posten sollte? Mit "error:" war es das, siehe:
Quote$ more /var/lib/dkms/nvidia-tesla-470/470.182.03/build/make.log | grep error:
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c:599:23: error: assignment of read-only member 'vm_flags'
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c:666:23: error: assignment of read-only member 'vm_flags'
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c:667:23: error: assignment of read-only member 'vm_flags'
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c:673:23: error: assignment of read-only member 'vm_flags'
/var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.c:674:23: error: assignment of read-only member 'vm_flags'

Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Geier0815

#1
2023/05/22, 15:20:58
Quotedpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-headers-siduction-amd64:
linux-headers-siduction-amd64 hängt ab von linux-headers-6.3.3-1-siduction-amd64 (= 6.3-3); aber:
  Paket linux-headers-6.3.3-1-siduction-amd64 ist noch nicht konfiguriert.
Da würde ich mal mein Augenmerk drauf legen.
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

towo

#2
2023/05/22, 16:51:10
Das Problem ist. Nvidia 470 braucht einen Patch, damit er mit Kernel 6.3 funktioniert.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

michaa7

#3
2023/05/23, 00:55:49
Ok, danke für den Hinweis. Das Übliche also. Dann eben warten und den vorletzten Kernel booten ...
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

towo

#4
2023/05/23, 09:07:20
Ich habe im Fixes-Repo einen gepatchten 470er Nvidia hochgeladen.
Darf gerne getestet werden, ich kann es, mangels Nvidia-Hardware, nicht.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

michaa7

#5
2023/05/23, 11:43:13 Last Edit: 2023/05/26, 22:34:52 by michaa7
Die gefixte Version (470.182.03-2) führt zu einem fehlerfreien Modulbau. Kernel bootet mit funktionierender Graphik.

Danke towo.

Darfst ein "Tested by: michaa7" anhängen ;-)

Ok, you can't code, but you still might be able to write a bug report for Debian's sake

vayu

#6
2023/05/23, 21:16:41
Quote from: towo on 2023/05/23, 09:07:20
Ich habe im Fixes-Repo einen gepatchten 470er Nvidia hochgeladen.
Darf gerne getestet werden, ich kann es, mangels Nvidia-Hardware, nicht.
Thanks, after enabling the fixes repo, 6.3 now compiles and boots with NVidia 470 for me.

Pip

#7
2023/05/25, 21:49:12
Not such happy new for me. For 6.3.3-1 the error message from apt was
Code Select
env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.3.3-1-siduction-amd64.....(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.3.3-1-siduction-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-tesla-470/470.182.03/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.

with the errors in the make.log being

Code Select
make[2]: *** [scripts/Makefile.build:257: /var/lib/dkms/nvidia-tesla-470/470.182.03/build/nvidia/nv-mmap.o] Error 1


Code Select
make[1]: *** [Makefile:2038: /var/lib/dkms/nvidia-tesla-470/470.182.03/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.3.3-1-siduction-amd64'
make: *** [Makefile:80: modules] Error 2


It couldn't build for 6.3.4-1 either.

Have I failed to download something?

Code Select
apt list --installed | grep nvidia

glx-alternative-nvidia/unstable,now 1.2.2 amd64 [installed,automatic]
libgl1-nvidia-tesla-470-glvnd-glx/unstable,now 470.182.03-1 amd64 [installed,automatic]
libglx-nvidia-tesla-470-0/unstable,now 470.182.03-1 amd64 [installed,automatic]
libnvidia-tesla-470-cfg1/unstable,now 470.182.03-1 amd64 [installed,automatic]
libnvidia-tesla-470-cuda1/unstable,now 470.182.03-1 amd64 [installed,automatic]
libnvidia-tesla-470-eglcore/unstable,now 470.182.03-1 amd64 [installed,automatic]
libnvidia-tesla-470-glcore/unstable,now 470.182.03-1 amd64 [installed,automatic]
libnvidia-tesla-470-ml1/unstable,now 470.182.03-1 amd64 [installed,automatic]
libnvidia-tesla-470-ptxjitcompiler1/unstable,now 470.182.03-1 amd64 [installed,automatic]
nvidia-detect/unstable,now 525.105.17-1 amd64 [installed]
nvidia-installer-cleanup/unstable,now 20220217+2 amd64 [installed,automatic]
nvidia-kernel-common/unstable,now 20220217+2 amd64 [installed,automatic]
nvidia-modprobe/unstable,now 530.30.02-2 amd64 [installed,automatic]
nvidia-persistenced/unstable,now 525.85.05-1 amd64 [installed,automatic]
nvidia-settings-tesla-470/unstable,now 470.161.03-1 amd64 [installed,automatic]
nvidia-support/unstable,now 20220217+2 amd64 [installed,automatic]
nvidia-tesla-470-alternative/unstable,now 470.182.03-1 amd64 [installed,automatic]
nvidia-tesla-470-kernel-dkms/unstable,now 470.182.03-1 amd64 [installed,automatic]
nvidia-tesla-470-kernel-support/unstable,now 470.182.03-1 amd64 [installed,automatic]
nvidia-tesla-470-smi/unstable,now 470.182.03-1 amd64 [installed,automatic]
nvidia-tesla-470-vdpau-driver/unstable,now 470.182.03-1 amd64 [installed,automatic]
xserver-xorg-video-nvidia-tesla-470/unstable,now 470.182.03-1 amd64 [installed,automatic]


Geier0815

#8
2023/05/25, 22:38:33
Code Select
deb      https://packages.siduction.org/fixes unstable main contrib non-free

is in one of your source-lists?
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

Pip

#9
2023/05/26, 08:13:00

Code Select
deb [ signed-by=/usr/share/keyrings/fixes-archive-keyring.gpg] http://ftp.uni-stuttgart.de/siduction/fixes unstable main

without contrib and non-free. That was where I was going wrong.

Thanks for the pointer, all good now.
Print
Go Up Pages1
User actions