It is not like the topic title says, it is not a Pi2, but a Pi1. So can only be ARMv6 raspbian, not 64-bit on certain rare Pi2 later revisions.
So Pi1+ rev 1.2, I have the same still as workhorse running raspbian trixie, but just standard repo kernel
6.18.34+rpt-rpi-v6 #1 Raspbian 1:6.18.34-1+rpt1 (2026-06-09) armv6l
AND: standard repo firmware just apt upgraded. Since bookworm, this firmware is in package raspi-firmware and expects boot partition mounted at /boot/firmware
But you can all change that manually if you want to keep stretch userspace.
You need trixie bootcode.bin config.txt start.elf fixup.dat cmdline.txt and copied/renamed vmlinz initrd dtb dacplus.dtbo
The last 4 are kernel and Linux keeps them in /boot and /usr/lib/modules/ (or /usr/lib/linux-image-<$KVER>
Then hook /etc/initramfs/post-update.d/z50-raspi-firmware
put things in place normally, but you need some manual hacks if you want to keep stretch userspace
You could use apt pinning if you want it fully automated/unattended. Make sure you remove/hold old-named firmware and kernel package. I think then you can keep your QT4 stuff.
Currently I see:
# apt list raspi-firmware
raspi-firmware/stable 1:1.20260521-3 all [upgradable from: 1:1.20260521-2]
So Pi1+ rev 1.2, I have the same still as workhorse running raspbian trixie, but just standard repo kernel
6.18.34+rpt-rpi-v6 #1 Raspbian 1:6.18.34-1+rpt1 (2026-06-09) armv6l
AND: standard repo firmware just apt upgraded. Since bookworm, this firmware is in package raspi-firmware and expects boot partition mounted at /boot/firmware
But you can all change that manually if you want to keep stretch userspace.
You need trixie bootcode.bin config.txt start.elf fixup.dat cmdline.txt and copied/renamed vmlinz initrd dtb dacplus.dtbo
The last 4 are kernel and Linux keeps them in /boot and /usr/lib/modules/ (or /usr/lib/linux-image-<$KVER>
Then hook /etc/initramfs/post-update.d/z50-raspi-firmware
put things in place normally, but you need some manual hacks if you want to keep stretch userspace
You could use apt pinning if you want it fully automated/unattended. Make sure you remove/hold old-named firmware and kernel package. I think then you can keep your QT4 stuff.
Currently I see:
# apt list raspi-firmware
raspi-firmware/stable 1:1.20260521-3 all [upgradable from: 1:1.20260521-2]
Statistics: Posted by redvli — Mon Jul 27, 2026 12:20 pm
