I have a Pi4 running Bullseye and would like to move it to Bookworm. I built a Bookworm disk with everything installed as it should be, but running into the dreaded -7 error from rtl_test -t on Bookworm.
I’ve tried two different SDR devices, both with the same failure mode.
apt update/upgrade done. I’m really confused because I read several places that the underlying RasPiOS iissue was fixed.
Appreciate any pointers/hints as to how to resolve. Thx!
What is your kernel version? Run uname -a to check.
Did you reboot after updating?
Nov 30 17:02:19 skypi piaware[1055]: your system info is: Linux skypi 6.1.0-rpi4-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.54-1+rpt2 (2023-10-05) aarch64 GNU/Linux
Yes, rebooted after updating. Thx
I believe that’s still the old kernel - you need 1:6.1.58-1+rpt2 (2023-10-27) or newer
Apparently! But I thought I read that the fix was available via ‘apt update’, and this system is fully updated.
Did I misunderstand the state of the fix for this? My Pi5 has kernel 1:6.1.58-1+rpt2, but that’s not my piaware system. 
If you do a:
sudo apt update
sudo apt full-upgrade
you should get the new kernel. (IIRC you won’t get it with just a simple upgrade as it needs to remove some packages and upgrade won’t do that)
(avoid using rpi-update unless you want bleeding-edge stuff, it bypasses the usual package management)
I tried both full-upgrade and dist-upgrade, and neither of them coughed up a new kernel.
I’m with you on avoiding rpi-update, not because it’s bleeding edge, but because I want to set it up and forget about it.
The good news is that there’s a new RasPiOS Bookworm IMG coming soon, and it has kernel 6.1.63-1+rpt1.
I’ll wait for that and give it another go. Meanwhile my Bullseye piaware keeps on chugging.
Thanks for the inputs, really appreciated.
sudo apt full-upgrade (Done)
sudo rpi-update (NOT done)
No issues, working OK
Click on Screenshot to See Larger Size
You are using an old image (see dates).
If you re-image using Raspberry Pi Imager, you will get latest image with latest kernel which does not have this issue.
Debian 1:6.1.58-1+rpt2 (2023-10-27) aarch64 GNU/Linux
are you sure? the latest image on raspberrypi.com is still the 10/10 image which has the old kernel.
(nb: the date in uname -a is the date that the particular kernel was built/packaged; it’s not the same as the date the sdcard image was put together; the image dates are necessarily >= the date of the kernel they include)
As of yesterday (my time) Raspberry Pi Imager installs the following:
Linux pi42 6.1.0-rpi4-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.54-1+rpt2 (2023-10-05) aarch64
sudo apt update
sudo apt upgrade
installs 37 packages and results in:
Linux pi42 6.1.0-rpi6-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.58-1+rpt2 (2023-10-27) aarch64
When used, the Raspberry Pi imager downloads the latest image and does two things with this image:
When next time it is started, the Raspi Imager checks the latest version available at servers of Raspberrypi Orgnization. If it is same as the cached version from previous use, it does not download the image. Instead it uses the cached copy. If the version available at Raspberry Pi servers is newer, it downloads the new version, writes new version to microSD card, as well as replaces the old cached version by new one.
In rare case that when you start Raspberry Pi imager and at that time Raspberry Pi server is down, or your internet connection is poor, It cannot check the latest version, and uses cached version to write the image to microSD card.
To avoid this situation, before imaging, I always clear Raspberry Pi Imager’s cache by deleting all files & folders inside the “cache” folder.
The location of cache is shown in screenshot below:
Click on Screenshot to See Larger Size
Thanks, both of you. @abcd567 is correct, and working through this has uncovered an omission (OK, it’s a freaking nasty bug) in my IMG prep stuff.
Working on the fix now, as well as sorting out how to resuscitate systems that the prep tool has borked.
After that, onwards to Bookworm with piaware!
Thanks again.
