Package: raspi-firmware
Version: 1.20201022-2
Severity: important
Hi,
[Deliberately reporting again 1.20201022-2 in testing as this seems to
be the case since at least 1st of January 2021 where 1.20201022-3 wasn't
uploaded yet. I only discovered it a few days and first wanted to be
sure that I didn't oversee something, hence only reporting it now.]
For some reason, raspi-firmware doesn't install
/boot/vmlinuz-5.10.0-1-armmp-lpae (none of the two versions so far) into
/boot/firmware/ on my Sid + Experimental installation.
I rebooted several times since the installation of
linux-image-5.10.0-1-armmp-lpae and dpkg-reconfigure'd both,
linux-image-5.10.0-1-armmp-lpae and raspi-firmware before the latest
reboot at least once, but it is still giving me:
# uname -a
Linux c3pio 5.10.0-trunk-armmp-lpae #1 SMP Debian 5.10.2-1~exp1 (2020-12-22)
armv7l GNU/Linux
Could this be wrong sorting ("1" vs "trunk")? Just guessing — this is
weird.
Some more details (please ask for details if I'm missing helpful
information):
# cat /sys/firmware/devicetree/base/model
Raspberry Pi 2 Model B Rev 1.1
# ls -l /boot/vmlinuz-*
-rw-r--r-- 1 root root 3304216 Feb 2 2015 /boot/vmlinuz-3.18.0-trunk-rpi2
-rw-r--r-- 1 root root 4215296 Jun 22 2018 /boot/vmlinuz-4.16.0-2-armmp-lpae
-rw-r--r-- 1 root root 4260352 Aug 18 2018 /boot/vmlinuz-4.17.0-3-armmp-lpae
-rw-r--r-- 1 root root 4309504 Nov 23 2018 /boot/vmlinuz-4.18.0-3-armmp-lpae
-rw-r--r-- 1 root root 4370944 Jul 19 2019 /boot/vmlinuz-4.19.0-5-armmp-lpae
-rw-r--r-- 1 root root 5005824 Dec 31 07:26 /boot/vmlinuz-5.10.0-1-armmp-lpae
-rw-r--r-- 1 root root 5001728 Dec 22 22:22
/boot/vmlinuz-5.10.0-trunk-armmp-lpae
-rw-r--r-- 1 root root 4530688 Oct 6 2019 /boot/vmlinuz-5.2.0-3-armmp-lpae
-rw-r--r-- 1 root root 4588032 Dec 7 2019 /boot/vmlinuz-5.3.0-3-armmp-lpae
-rw-r--r-- 1 root root 4698624 Feb 13 2020 /boot/vmlinuz-5.4.0-4-armmp-lpae
-rw-r--r-- 1 root root 4817408 Mar 30 2020 /boot/vmlinuz-5.5.0-1-armmp-lpae
-rw-r--r-- 1 root root 4821504 Apr 15 2020 /boot/vmlinuz-5.5.0-2-armmp-lpae
-rw-r--r-- 1 root root 4858368 Jun 9 2020 /boot/vmlinuz-5.6.0-2-armmp-lpae
-rw-r--r-- 1 root root 4821504 Aug 23 15:44 /boot/vmlinuz-5.7.0-3-armmp-lpae
-rw-r--r-- 1 root root 4841984 Oct 10 21:40 /boot/vmlinuz-5.8.0-3-armmp-lpae
-rw-r--r-- 1 root root 4887040 Nov 27 22:02 /boot/vmlinuz-5.9.0-4-armmp-lpae
-rw-r--r-- 1 root root 4887040 Dec 17 06:31 /boot/vmlinuz-5.9.0-5-armmp-lpae
# ls -l /boot/firmware/*[^~]
-rwxr-xr-x 1 root root 25693 Jan 6 09:12 /boot/firmware/bcm2711-rpi-4-b.dtb
-rwxr-xr-x 1 root root 12717 Jan 6 09:12
/boot/firmware/bcm2835-rpi-a-plus.dtb
-rwxr-xr-x 1 root root 12597 Jan 6 09:12 /boot/firmware/bcm2835-rpi-a.dtb
-rwxr-xr-x 1 root root 12931 Jan 6 09:12
/boot/firmware/bcm2835-rpi-b-plus.dtb
-rwxr-xr-x 1 root root 12803 Jan 6 09:12
/boot/firmware/bcm2835-rpi-b-rev2.dtb
-rwxr-xr-x 1 root root 12719 Jan 6 09:12 /boot/firmware/bcm2835-rpi-b.dtb
-rwxr-xr-x 1 root root 12795 Jan 6 09:12
/boot/firmware/bcm2835-rpi-cm1-io1.dtb
-rwxr-xr-x 1 root root 13091 Jan 6 09:12
/boot/firmware/bcm2835-rpi-zero-w.dtb
-rwxr-xr-x 1 root root 12637 Jan 6 09:12 /boot/firmware/bcm2835-rpi-zero.dtb
-rwxr-xr-x 1 root root 13639 Jan 6 09:12 /boot/firmware/bcm2836-rpi-2-b.dtb
-rwxr-xr-x 1 root root 13990 Jan 6 09:12
/boot/firmware/bcm2837-rpi-3-a-plus.dtb
-rwxr-xr-x 1 root root 14622 Jan 6 09:12
/boot/firmware/bcm2837-rpi-3-b-plus.dtb
-rwxr-xr-x 1 root root 14250 Jan 6 09:12 /boot/firmware/bcm2837-rpi-3-b.dtb
-rwxr-xr-x 1 root root 13624 Jan 6 09:12
/boot/firmware/bcm2837-rpi-cm3-io3.dtb
-rwxr-xr-x 1 root root 52480 Jan 6 09:08 /boot/firmware/bootcode.bin
-rwxr-xr-x 1 root root 105 Jan 6 09:12 /boot/firmware/cmdline.txt
-rwxr-xr-x 1 root root 227 Jan 6 09:12 /boot/firmware/config.txt
-rwxr-xr-x 1 root root 7289 Jan 6 09:08 /boot/firmware/fixup.dat
-rwxr-xr-x 1 root root 5417 Jan 6 09:08 /boot/firmware/fixup4.dat
-rwxr-xr-x 1 root root 3163 Jan 6 09:08 /boot/firmware/fixup4cd.dat
-rwxr-xr-x 1 root root 8426 Jan 6 09:08 /boot/firmware/fixup4db.dat
-rwxr-xr-x 1 root root 8430 Jan 6 09:08 /boot/firmware/fixup4x.dat
-rwxr-xr-x 1 root root 3163 Jan 6 09:08 /boot/firmware/fixup_cd.dat
-rwxr-xr-x 1 root root 10276 Jan 6 09:08 /boot/firmware/fixup_db.dat
-rwxr-xr-x 1 root root 10278 Jan 6 09:08 /boot/firmware/fixup_x.dat
-rwxr-xr-x 1 root root 24487359 Jan 6 09:12
/boot/firmware/initrd.img-5.10.0-trunk-armmp-lpae
-rwxr-xr-x 1 root root 24264192 Dec 12 07:52
/boot/firmware/initrd.img-5.9.0-4-armmp-lpae
-rwxr-xr-x 1 root root 24268751 Dec 23 08:57
/boot/firmware/initrd.img-5.9.0-5-armmp-lpae
-rwxr-xr-x 1 root root 3304216 Jul 1 2015 /boot/firmware/kernel7.img
-rwxr-xr-x 1 root root 3304216 Jul 1 2015 /boot/firmware/kernel7.img.backup
-rwxr-xr-x 1 root root 165 Dec 9 01:47 /boot/firmware/note.txt
-rwxr-xr-x 1 root root 2949600 Jan 6 09:08 /boot/firmware/start.elf
-rwxr-xr-x 1 root root 2225376 Jan 6 09:08 /boot/firmware/start4.elf
-rwxr-xr-x 1 root root 785532 Jan 6 09:08 /boot/firmware/start4cd.elf
-rwxr-xr-x 1 root root 3728296 Jan 6 09:08 /boot/firmware/start4db.elf
-rwxr-xr-x 1 root root 2985256 Jan 6 09:08 /boot/firmware/start4x.elf
-rwxr-xr-x 1 root root 785532 Jan 6 09:08 /boot/firmware/start_cd.elf
-rwxr-xr-x 1 root root 4800200 Jan 6 09:08 /boot/firmware/start_db.elf
-rwxr-xr-x 1 root root 3708904 Jan 6 09:08 /boot/firmware/start_x.elf
-rwxr-xr-x 1 root root 5001728 Jan 6 09:12
/boot/firmware/vmlinuz-5.10.0-trunk-armmp-lpae
-rwxr-xr-x 1 root root 4887040 Dec 12 07:52
/boot/firmware/vmlinuz-5.9.0-4-armmp-lpae
-rwxr-xr-x 1 root root 4887040 Dec 23 08:57
/boot/firmware/vmlinuz-5.9.0-5-armmp-lpae
-rwxr-xr-x 1 root root 5260344 Dec 9 01:25 /boot/firmware/working-config.txz
# cat /boot/firmware/config.txt
enable_uart=1
upstream_kernel=1
kernel=vmlinuz-5.10.0-trunk-armmp-lpae
# For details on the initramfs directive, see
# https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=10532
initramfs initrd.img-5.10.0-trunk-armmp-lpae
# cat /boot/firmware/cmdline.txt
console=tty0 console=ttyS1,115200 root=/dev/mmcblk0p2 rw fsck.repair=yes
net.ifnames=0 cma=64M rootwait
#
I then tried it on another Raspi (a 4B 8GB) recently installed with
images from raspi.debian.net, then upgraded to Bullseye. It so far only
had Testing in it's sources.list. I added sid to sources.list, upgraded
linux-image-arm64, which pulled in linux-image-5.10.0-1-arm64 (while it
wasn't in testing yet) and there it worked.
Would still fit if the sort order sorts the -trunk kernel after -1,
because in this case there was no -trunk kernel involved.
Setting the severity not to grave/RC as it only seems to happen with
kernels from experimental — but only by chance due to their naming
scheme.
Will do further experiments like manually setting a 5.9 kernel in
config.txt, rebooting, then removing the 5.10 trunk kernel and then
doing a "dpkg-reconfigure raspi-kernel" (if the kernel removal doesn't
trigger it anyways) and check if then the 5.10.0-1 kernel is present in
/boot/firmware/ or not. But I can't/won't do that without reboot and I
don't want to suspend bug reporting and resuming it afterwards, so I'm
sending this now with about ¾ of the information I intent to include.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500,
'buildd-unstable'), (500, 'testing'), (110, 'experimental'), (1,
'experimental-debug'), (1, 'buildd-experimental')
Architecture: armhf (armv7l)
Kernel: Linux 5.10.0-trunk-armmp-lpae (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages raspi-firmware depends on:
ii dosfstools 4.1-2
ii dpkg 1.20.5
raspi-firmware recommends no packages.
raspi-firmware suggests no packages.
-- no debconf information
