Image update RPI-5 (5.12 image)

[pa3gsb]

Hi All,

I have updated the image with the latest trixie version.

Beside the trixie update i also update the pihpsdr.

https://github.com/pa3gsb/Radioberry-2.x/releases/tag/radioberry%40rpi5

Enjoy

73 Johan

PA3GSB

[Duane's Mind]

Many thanks Johan,

I'm having some trouble trying to get QSSTV and wsjtx audio to work. 

I only get the audio to work if I don't open pIhpsdr but when I open pihpsdr then theres no audio in pihpsdr.

I could always get it to work with Pi4 but maybe something I'm doing wrong?

Regards,

Duane

[Jatteau Marc]

Hi Johan
Thanks a lot for this new image, it works perfectly here.
It's a shame we have to reconfigure it with our personal settings.

73 Marc F6GKG

[pa3gsb]

Duane,

Hard to understand your issue; looked into the manual of pihpsdr:

From the manual:

2.2.2 The RX spectrum looks fine, but I hear no RX
signal
Many radios do not have built-in audio codecs. In this case, you must choose
local audio output in the RX menu.
(this section will be extended if other ,,frequent problems” are reported to
me.)

 https://github.com/dl1ycf/pihpsdr/releases/download/v2.5/piHPSDR-Manual-v2.5.pdf

Hope this helps,

73 Johan

PA3GSB

Op maandag 23 februari 2026 om 14:59:05 UTC+1 schreef duane...@gmail.com:

[Frank Thomsen]

Great stuff Johan, thanks for the update! I have picked it up, but travelling on business, so I'll stick it on a card next weekend.

I upgraded to Christophs early February piHPSDR release, to, among other things, get PPM frequency correction instead Hz. 

On the RadioBerry unit I have using Hz produces an inaccuracy of +/-120Hz per 5MHz. 

I have had no issues with that early February version of Christophs, so I think it's a good choice.

My FT8 5 band monitor (80-20 night time, 20-10 day time) @48KHz/band, uses SparkSDR and it works fine, I simply offset the frequency slightly - it tickles my OCD though ;-)

Started with RadioBerry because I had a pi4 lying around doing nothing and thought "why not"... 

And then you came out with this pi5 update and I didn't think "why not" I thought "must have" :-D

Cheers and happy experimenting.

73

OZ5ACI - Frank

On Monday, 23 February 2026 at 09:26:07 UTC+1 pa3gsb wrote:

[Dan Habecker]

Thanks for the new image.  I tried it out this morning and I seem to have an audio issue as well.  Something changed with the recieve setup in piHPSDR.  The 'Loca Audio Output' check box is missing.  I know I need to check this to get audio.  Also my HDMI audio is working okay, as I tried playing a YouTube video on the Raspberry Pi with the new image and all worked okay with that.

73,

Dan W9EQ

[pa3gsb]

Duane,

Just select your audio device

I think you have selected the NR3 option without an antenna signal it will be quite.

Hope this helps (i do have audio).

73 Johan

PA3GSB

Op maandag 23 februari 2026 om 14:59:05 UTC+1 schreef duane...@gmail.com:

Many thanks Johan,

[Dan Habecker]

That did it for me.  Either I selected NR3 unknowingly or it was on by default.  Anyway, I hear audio now.

TNX & 73,

Dan W9EQ

[Duane's Mind]

Hi Johan,

Ok let me try clarify the audio issue I had with using wsjtx or QSSTV and Pihpsdr at the same time on the PI5

I select my USB sound card in Pihpsdr which works like it should. If I then go and open wsjtx and try select the USB sound card then it says it's busy.

If I close PIhpsdr then I'm able to get the sound card working in wsjtx or QSSTV. If I then open up Pih[sdr then I'm unable to select the USB sound card.

On my Pi4 I was able to run Pihsdr and wsjtx or QSSTV at the same time and share the same sound card.

What I done now is install 2 USB sound cards, 1 for Pihpsdr and the other for wsjtx which works fine as a workaround. 

Regards,

Duane

[pa3gsb]

Duane,

You are using your device on rpi-5 different ; more exclusive . I think you use default alsa on your rpi-4.

This is not an image issue but the improvement of  the new operation system, trixie.

There are multiple ways of solving this problem.

1. Use virtual audio cable as described in  https://github.com/dl1ycf/pihpsdr/releases/download/v2.5/piHPSDR-Manual-v2.5.pdf

2. Use sparksdr which is also provided on the  image .

3.  use default device (if using hw:card type of selections your are using it exclusive with problems you described)

4. Keep it as you setup is working.

Have fun 

73 Johan

PA3GSB

Op donderdag 26 februari 2026 om 11:39:55 UTC+1 schreef duane...@gmail.com:

[Mario Vano]

HI Johan!

I seem to be having some trouble with the 5.12 image. I've downloaded it twice and tested it on two different Radioberrys - both of which work fine with the 5.02 image.

After several attempts to get this going, I've set up a minimal system with a pi500, a Radioberry, a monitor and mouse. Here's a picture of the setup and a screen capture. This was a freshly installed image with NO other installations, updates or setting changes. I did this twice and the results are exactly the same in both cases.

I've tried turning NB3 off and it makes no difference. I've built several radioberry radios and used them with piHpsdr in the field extensively, so I don't think it's something I'm doing wrong.

The same unbelievably high noise level also appears in SparkSDR.

As I said, all setups work fine with the 5.02 image. I've tested on the pi500 and on the standard pi5 with exactly the same results.

I've reviewed everything I can think of, but have had to go back to 5.02. Do you have any idea what's going on?

[pa3gsb]

Hi,

Would you be so kind to give the following info:

- Which FPGA are you using? CL016 or CL025

- sudo modinfo radioberry 

- sudo systemctl stop radioberry and than sudo radioberry

I only do have an CL025 and will later start with a download and a fresh image.

I will make soon some new images with the latest changes.

73 Johan

PA3GSB

Op maandag 6 april 2026 om 18:44:28 UTC+2 schreef mpv...@gmail.com:

[pa3gsb]

Problem solved ; please for others download new images are available for download CL016 and CL025

pihphsdr Release 2.6

trixie 13.4

gateware 75.2 firmware 5.06 and driver 5.54.

Enjoy,

73 Johan

PA3GSB

Op dinsdag 7 april 2026 om 11:45:13 UTC+2 schreef pa3gsb:

[Mario Vano]

Thanks Johan, working great so far...

M

[Mario Vano]

Hey Johan! Here's something that's causing confusing behavior: the image you generated has a Trixie bug causing a wacky new system for startup called "cloud-init" to be permanently enabled. It's not supposed to be enabled. Unfortunately it's very hard to disable. It's supposed to be fixed in the next release.

Because of cloud-init some important settings are being overwritten every time you boot. In particular, the Host name is being reset. This means you cannot change the host name! There may be other problems I didn't encounter as well.

There's more information about the problem here: https://github.com/raspberrypi/trixie-feedback/issues/26

For a temporary workaround try this:

             sudo touch /etc/cloud/cloud-init.disabled

and then reboot.

This seems to have worked for me. It really caused me a problem as I have more than one test machine on my network.

If this file is present, cloud-init is supposed to be completely disabled I don't know what other problems this may cause, but it seems to be working here. cloud-init is supposed to be "fixed" in the next release - but who knows when this will settle down.

M

[pa3gsb]

Mario,

If for you the hostname is important you can solve this as follows:

•   remove from /boot/firmware/user-data  the line  hostname: radioberry

followed by a :

• sudo reboot

followed by:

• sudo hostnamectl set-hostname <your hostname>

Another remark : you can update your system as long the update does not contain a kernel update.

73 Johan

PA3GSB

Op vrijdag 17 april 2026 om 16:46:14 UTC+2 schreef mpv...@gmail.com:

[Mario Vano]

Thanks Johan, but I don't think that it's  completely true that you can update your system as long as there's no kernel update.

Using "apt upgrade" supposedly guarantees that the kernel will not be touched. Kernel upgrades use apt "full-upgrade".

I just did "sudo apt upgrade" and lost my driver. I suspect the "firmware" portion of the update did it. 

There was NO kernel update involved. This situation is a major nuisance. I now have to redo weeks of customization and testing.

Has your kernel patch been rejected or is there a chance we will someday be able to install your driver without rebuilding the kernel?

This REALLY makes the pi 5 impractical with radioberry.

Do you have a script to fix this image or do I have to start all over?

thanks,

M

[pa3gsb]

Mario,

You’re right that avoiding version mismatches requires being a bit more precise.

1. Check what will be updated

Before running any upgrade, always check which relevant packages are involved:

apt list --upgradable 2>/dev/null | grep -E "kernel|firmware|eeprom" 2. Prevent breaking changes

If there is no kernel update, but you do see raspi-firmware or rpi-eeprom in the list, you should exclude them from the upgrade:

sudo apt-mark hold raspi-firmware rpi-eeprom

This prevents changes in device tree, overlays, and boot firmware, which can affect the driver even when the kernel itself remains unchanged.

---

3. Recover the current setup

First verify that the running kernel is still the expected one:

uname -r

If it is still:

6.12.79-v8-16k+

then the kernel module should still be compatible, and the issue is most likely in the device-tree overlay.

In that case, rebuild and reinstall the overlay:

git clone https://github.com/pa3gsb/Radioberry-2.x.git cd Radioberry-2.x/SBC/rpi-5/device_driver/pio-mode/driver dtc -@ -I dts -O dtb -o radioberry.dtbo radioberry-overlay.dts sudo cp radioberry.dtbo /boot/firmware/overlays/ sudo reboot

---

4. Important note

This works because the kernel version has not changed.
If the kernel does change, the module (radioberry.ko) may also need to be rebuilt.

---

This approach should allow you to restore the current setup and avoid similar issues in future updates.

73 Johan

PA3GSB

Op woensdag 29 april 2026 om 16:06:04 UTC+2 schreef mpv...@gmail.com:

[Mario Vano]

Johan, when you get a chance,  I think it's time for another image update. Trixie is highly unstable and your current image requires many essential service updates that force a kernel update when you try to install them. SSH and ALSA are both broken and require updating.

Note also that you seem to be using an obsolete program to generate the image that does not properly set Trixie options like cloud-init features.

thanks,

M