Bug#1040199: It was xtrx
So, ended up purging all xtrx-related packages. As expected, kernel packages were able to be properly installed and configured. GRUB configuration is also back to normal. Like Diederik said, this is actually the same issue as in bugs.debian.org/1038003, which makes this bug report a duplicate. FWIW, I will be paying a lot more attention to my upgrades from now, especially when sleep-deprived ; sorry for the inconvenience.
Bug#1040199: (no subject)
On 03/07/2023 12:59, Diederik de Haas wrote: On Monday, 3 July 2023 12:27:12 CEST julienbenja...@free.fr wrote: invoke DKMS to remove the module from installed kernel versions... and it failed with xtrx on 6.3.0-1-amd64. ``` 0 upgraded, 0 newly installed, 1 to remove and 42 not upgraded. 4 not fully installed or removed. You may want to look into this ^^ I would like to, but apt won't, because dpkg cannot configure those 4 same culprits: dpkg: error processing package linux-image-6.3.0-1-amd64 (--configure): installed linux-image-6.3.0-1-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-amd64: linux-headers-amd64 depends on linux-headers-6.3.0-1-amd64 (= 6.3.7-1); however: Package linux-headers-6.3.0-1-amd64 is not configured yet. dpkg: error processing package linux-headers-amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-amd64: linux-image-amd64 depends on linux-image-6.3.0-1-amd64 (= 6.3.7-1); however: Package linux-image-6.3.0-1-amd64 is not configured yet. dpkg: error processing package linux-image-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-headers-6.3.0-1-amd64 linux-image-6.3.0-1-amd64 linux-headers-amd64 linux-image-amd64 I did not try to go the "purge xrtx package route" for now ; but it might solve this all package management, which, for all I know, could be the source of the issue. DKMS make.log for xtrx-0.0.1+git20190320.5ae3a3e-3.2 for kernel 6.3.0-1-amd64 (x86_64) Mon 3 Jul 12:16:24 CEST 2023 make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64' CC [M] /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.o /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c: In function 'xtrxfd_mmap': /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c:1075:31: error: assignment of read-only member 'vm_flags' 1075 | vma->vm_flags |= VM_LOCKED; | ^~ /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c:1090:31: error: assignment of read-only member 'vm_flags' 1090 | vma->vm_flags |= VM_IO; | ^~ /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/xtrx.c:1115:31: error: assignment of read-only member 'vm_flags' 1115 | vma->vm_flags |= VM_LOCKED; | ^~ Kinda confused at this point ; if this is unrelated, I can submit another bug report against the proper package. Looks like https://bugs.debian.org/1038003 and https://github.com/myriadrf/xtrx_linux_pcie_drv/issues/16 It could be the cause of the issue or just another thing you should look into. Having 42 not upgraded packages is usually not a good sign, so bringing that down to ideally 0 would be my first step. Thanks for the link, will check it out. Again, this system not being up to date is a consequence, although it might not be a problem seeing which packages are not updated: ``` fonts-liberation2/unstable,unstable 1:2.1.5-2 all [upgradable from: 2.1.5-1] fonts-liberation/unstable,unstable 1:2.1.5-2 all [upgradable from: 1:1.07.4-11] intel-media-va-driver/unstable 23.2.3+dfsg1-1 amd64 [upgradable from: 23.1.2+dfsg1-1] intel-media-va-driver/unstable 23.2.3+dfsg1-1 i386 [upgradable from: 23.1.2+dfsg1-1] libigdgmm12/unstable 22.3.7+ds1-1 amd64 [upgradable from: 22.3.6+ds1-1] libncurses-dev/unstable 6.4+20230625-1 amd64 [upgradable from: 6.4-4] libncurses6/unstable 6.4+20230625-1 amd64 [upgradable from: 6.4-4] libncurses6/unstable 6.4+20230625-1 i386 [upgradable from: 6.4-4] libncursesw6/unstable 6.4+20230625-1 amd64 [upgradable from: 6.4-4] libncursesw6/unstable 6.4+20230625-1 i386 [upgradable from: 6.4-4] libodbc2/unstable 2.3.11-4 amd64 [upgradable from: 2.3.11-2] libodbc2/unstable 2.3.11-4 i386 [upgradable from: 2.3.11-2] libodbccr2/unstable 2.3.11-4 amd64 [upgradable from: 2.3.11-2] libodbccr2/unstable 2.3.11-4 i386 [upgradable from: 2.3.11-2] libodbcinst2/unstable 2.3.11-4 amd64 [upgradable from: 2.3.11-2] libreoffice-base-core/unstable 4:7.5.4-4 amd64 [upgradable from: 4:7.4.5-3] libreoffice-base-drivers/unstable 4:7.5.4-4 amd64 [upgradable from: 4:7.4.5-3] libreoffice-base/unstable 4:7.5.4-4 amd64 [upgradable from: 4:7.4.5-3] libreoffice-calc/unstable 4:7.5.4-4 amd64 [upgradable from: 4:7.4.5-3] libreoffice-common/unstable 4:7.5.4-4 all [upgradable from: 4:7.4.5-3] libreoffice-core/unstable 4:7.5.4-4 amd64 [upgradable from: 4:7.4.5-3] libreoffice-draw/unstable 4:7.5.4-4 amd64 [upgradable from: 4:7.4.5-3] libreoffice-evolution/unstable 4:7.5.4-4 amd64 [upgradable from: 4:7.4.5-3] libreoffice-gnome/unstable 4:7.5.4-4 amd64 [upgradable from: 4:7.4.5-3] libreoffice-gtk3/unstable 4:7.5.4-4 amd64 [upgradable from: 4:7.4.5-3] libreoffice-help-common/unstable 4:7.5.4-4 all
Bug#1040199: Maybe linked to grub?
I noticed, when inspecting GRUB config, that the root partition
identification changed from using UUID to device name (/dev/sda1 is the
root filesystem and its UUID is indeed
4bd0920b-1e9e-412a-992d-b7392017d1a7).
Not sure that it is related to the problem at hand, but it seems odd
that this happens on the same version causing a root mounting issue.
```
cat /boot/grub/grub.cfg | grep boot
set boot_once=true
set boot_once=true
if [ -z "${boot_once}" ]; then
linux/boot/vmlinuz-6.3.0-1-amd64 root=/dev/sda1 ro quiet
linux/boot/vmlinuz-6.3.0-1-amd64 root=/dev/sda1 ro quiet
linux/boot/vmlinuz-6.3.0-1-amd64 root=/dev/sda1 ro single
linux/boot/vmlinuz-6.1.0-9-amd64
root=UUID=4bd0920b-1e9e-412a-992d-b7392017d1a7 ro quiet
initrd/boot/initrd.img-6.1.0-9-amd64
linux/boot/vmlinuz-6.1.0-9-amd64
root=UUID=4bd0920b-1e9e-412a-992d-b7392017d1a7 ro single
initrd/boot/initrd.img-6.1.0-9-amd64
linux/boot/vmlinuz-5.18.0-4-amd64
root=UUID=4bd0920b-1e9e-412a-992d-b7392017d1a7 ro quiet
initrd/boot/initrd.img-5.18.0-4-amd64
linux/boot/vmlinuz-5.18.0-4-amd64
root=UUID=4bd0920b-1e9e-412a-992d-b7392017d1a7 ro single
initrd/boot/initrd.img-5.18.0-4-amd64
```
JB
Bug#1040199: Maybe linked to xtrx?
Hello again, After filing this bug, I tried to remove an unecessary firmware "firmware-atheros", and it happened to invoke DKMS to remove the module from installed kernel versions... and it failed with xtrx on 6.3.0-1-amd64. Here is the standard output: ``` apt purge firmware-atheros Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: fonts-fork-awesome gcc-10-base:i386 gcc-12-base:i386 golang-1.19-go golang-1.19-src libdmapsharing-3.0-2 libexecs0 libfilezilla34 libgdal32 libgeos3.11.1 libixml10 liblc3-0 libmongocrypt0 libmujs2 libosp5 libostyle1c2 libre2-9 libsdl-image1.2 libstd-rust-1.63 libupnp13 libyara9 linux-headers-6.1.0-8-amd64 linux-headers-6.1.0-8-common openjade python3-enrich python3-tenacity texlive-formats-extra texlive-games texlive-humanities texlive-music texlive-publishers Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: firmware-atheros* 0 upgraded, 0 newly installed, 1 to remove and 42 not upgraded. 4 not fully installed or removed. After this operation, 60.4 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 883659 files and directories currently installed.) Removing firmware-atheros (20230515-2) ... Setting up linux-headers-6.3.0-1-amd64 (6.3.7-1) ... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.3.0-1-amd64. Sign command: /usr/lib/linux-kbuild-6.3/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j16 KERNELRELEASE=6.3.0-1-amd64 -C /lib/modules/6.3.0-1-amd64/build M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e -3.2/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.3.0-1-amd64 (x86_64) Consult /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log for more information. dkms autoinstall on 6.3.0-1-amd64/x86_64 succeeded for nvidia-current v4l2loopback dkms autoinstall on 6.3.0-1-amd64/x86_64 failed for xtrx(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.3.0-1-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.3.0-1-amd64.postinst line 11. dpkg: error processing package linux-headers-6.3.0-1-amd64 (--configure): installed linux-headers-6.3.0-1-amd64 package post-installation script subprocess returned error exit status 1 Setting up linux-image-6.3.0-1-amd64 (6.3.7-1) ... /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.3.0-1-amd64. Sign command: /usr/lib/linux-kbuild-6.3/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... make -j16 KERNELRELEASE=6.3.0-1-amd64 -C /lib/modules/6.3.0-1-amd64/build M=/var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e -3.2/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.3.0-1-amd64 (x86_64) Consult /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log for more information. dkms autoinstall on 6.3.0-1-amd64/x86_64 succeeded for nvidia-current v4l2loopback dkms autoinstall on 6.3.0-1-amd64/x86_64 failed for xtrx(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.3.0-1-amd64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.3.0-1-amd64 (--configure): installed linux-image-6.3.0-1-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-amd64: linux-headers-amd64 depends on linux-headers-6.3.0-1-amd64 (= 6.3.7-1); however: Package linux-headers-6.3.0-1-amd64 is not configured yet. dpkg: error processing package linux-headers-amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-amd64: linux-image-amd64 depends on linux-image-6.3.0-1-amd64 (= 6.3.7-1); however: Package linux-image-6.3.0-1-amd64 is not configured yet. dpkg: error processing package linux-image-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-headers-6.3.0-1-amd64 linux-image-6.3.0-1-amd64 linux-headers-amd64 linux-image-amd64 ``` Output of xtrx module building log in /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log: $ cat /var/lib/dkms/xtrx/0.0.1+git20190320.5ae3a3e-3.2/build/make.log ``` DKMS make.log for xtrx-0.0.1+git20190320.5ae3a3e-3.2 for kernel 6.3.0-1-amd64 (x86_64) Mon 3
Bug#1032647: Keeping 525.105.17-1 for bookworm?
Since Debian 12 entered in full freeze, I guess this issue will stay open for the entirety of Bookwork lifetime?
Bug#1032647: 525.105.17-1/530.41.03-1 testing
Sorry for the late answer, For the record, the "official" driver I downloaded when I encountered the issue was the 530.30.02 version (the installer was NVIDIA-Linux-x86_64-530.30.02.run). I retried the 525.105.17-1 version from unstable, but the issue was still present. I tried the 530.41.03-1 version from experimental (while tracking unstable for all other packages now, instead of testing before) ; I can confirm that this version makes the issue disappears. Again, sorry for delay in experimenting, I had not much time to try it before. Cheers, JB
Bug#1032647: Testing with official Nvidia driver 530.30.02
Good morning, Quick update: in a moment of despair, I tried what felt like the last resort, which was installing the latest driver, from the Nvidia website. (I know, I know) Long story short, I stopped the X server, unloaded Nouveau, and ran the installation wizard ; it almost ran without issues (a weird little issue with DKMS, which I did not set up in the end), and finally ended up with the 530.30.02 installed. After having rebooted, the machine does not exhibit the same black screen flickering (depending on what's being drawn on screen e.g. tilix is set to fullscreen). I cannot be sure after such a short test, but it would seem that the latest version (530.30.02) of the Nvidia driver makes this issue disappear., at least on kernel version 6.1.0.5. Speaking of which, just to keep track of things, when updating to 525.89.02-1, I was on kernel 6.1.0.3 (package version: 6.1.8-1) and updating at the same time to kernel version 6.1.0-5 (package version: 6.1.12-1). Cheers, JB
