I spent over an hour composing a more detailed reply, but an errant click wiped it all away. I started over from scratch, and memory is lacking in my old age, interfering with attempted reconstruction.
didier gaumet composed on 2025-03-12 08:34 (UTC+0100): > So, as David has already pointed to a linux 6.1 available in Bullseye > Backports, to install it should probably suffice? As indicated in OP, that is the most recent properly working kernel installed: [quote] Latest available backport kernel: bullseye-backports 6.1.90-1 from 2024-05 works as expected. [/quote] And it's 10 months old (released last May). Why is explained here: https://backports.debian.org/Instructions/ [quote] While old stable releases may have Long Term Support, old-stable-backports are only made available for a period of one year after a new Debian stable release has been made....Packages in old-stable-backports must track the versions in stable (or stable/updates for security fixes). [/quote] # cat /etc/apt/sources.list deb http://deb.debian.org/debian bullseye main non-free contrib deb http://deb.debian.org/debian-security/ bullseye-security main non-free contrib deb http://deb.debian.org/debian bullseye-updates main non-free contrib deb http://deb.debian.org/debian bullseye-proposed-updates main non-free contrib deb http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.1.x bullseye main deps deb http://deb.debian.org/debian bullseye-backports-sloppy main contrib non-free # dpkg-query -W linux-image\* linux-image-5.10.0-34-amd64 5.10.234-1 linux-image-5.10.0-34-amd64-unsigned linux-image-6.1.0-0.deb11.21-amd64 6.1.90-1~bpo11+1 linux-image-6.1.0-0.deb11.21-amd64-unsigned linux-image-amd64 5.10.234-1 linux-image-generic # ls -gGh /boot/vmlinuz* -rw-r--r-- 1 6.8M Feb 23 20:11 /boot/vmlinuz-5.10.0-34-amd64 -rw-r--r-- 1 7.8M May 6 2024 /boot/vmlinuz-6.1.0-0.deb11.21-amd64 # aptitude search linux-image-amd64 i linux-image-amd64 - Linux for 64-bit PCs (meta-package) p linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration p linux-image-amd64-signed-template - Template for signed linux-image packages # apt list -a linux-image-amd64 Listing... Done linux-image-amd64/oldstable-security,now 5.10.234-1 amd64 [installed] linux-image-amd64/oldstable 5.10.223-1 amd64 # apt-cache madison linux-image-amd64 linux-image-amd64 | 5.10.234-1 | http://deb.debian.org/debian-security bullseye-security/main amd64 Packages linux-image-amd64 | 5.10.223-1 | http://deb.debian.org/debian bullseye/main amd64 Packages # apt policy linux-image-amd64 linux-image-amd64: Installed: 5.10.234-1 Candidate: 5.10.234-1 Version table: *** 5.10.234-1 500 500 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages 100 /var/lib/dpkg/status 5.10.223-1 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages # apt list linux-image\* | grep amd64 | wc -l 110 # Among the 110 results, latest and most alike last May's 6.1 seems to be: linux-image-6.1.0-0.deb11.31-amd64-unsigned # apt-get install -d linux-image-6.1.0-0.deb11.31-amd64-unsigned ... The following NEW packages will be installed: linux-image-6.1.0-0.deb11.31-amd64-unsigned ... Download complete and in download only mode # Is proceeding to install linux-image-6.1.0-0.deb11.31-amd64-unsigned the optimal way forward? If yes, where on debian.org is it explained how I should have come to such a conclusion instead of stumbling through upteen package management actions and man pages? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
