I have used my Pisound 1.0 in the past with good success using the beta Patchbox image or even in openSUSE Tumbleweed on RPi4 as I wrote in another post a few years ago.
After about 6 months of pausing that, while I put it on top of a RPi 4 instead and tried all kinds of other stuff on the 5, today I refitted it and the Pisound isn’t available anymore after boot.
I don’t have the active cooler installed, but rather a massive aluminium passive cooling plate that lets the Pisound just fit at a slight angle so I can’t really use the acrylic case but that’s fine for me while testing stuff. And this generally works ok even though it seems a bit hot.
I attach the output of “journalctl | grep pisound” for just today’s boot, if I can do anything to shed light on this, please tell. journalctl-pisound.txt (18.5 KB)
EDIT: I’ll add that I tested the same SD card and Pisound on the RPi 4 after seeing this, and it’s detected and available just fine there.
Patchbox OS updated to current, tried both with an older and then with latest firmware from Dec 8th and both “normal” and RT kernel.
I managed to update the pisound firmware to 1.03 and confirmed that it succeded by reading /sys/kernel/pisound/version, on a freshly installed bullseye raspios (full as lite didn’t give me the initial create user wizard…
But now I’m still stuck as none of my Patchbox systems can find the pisound kernel module, I also tried on a pristine raspios-full trixie 64bit install (where I write from now).
I see
How to go on from here? Both my PatchboxOS beta SDs show the same kernel versions and errors. I’ve updated all of the systems and autoremoved old kernels.
dmesg has nothing related to pisound, and journalctl gives this:
ed@raspberrypi:~ $ journalctl | grep pisound
Dez 18 15:15:51 raspberrypi systemd[1]: Started pisound-btn.service - Pisound button daemon autostart.
Dez 18 15:15:51 raspberrypi pisound-btn[911]: Reading Pisound serial failed, Pisound is possibly not attached. Continuing anyway.
Dez 18 15:15:51 raspberrypi pisound-btn[911]: Reading Pisound id failed, Pisound is possibly not attached. Continuing anyway.
Dez 18 15:15:51 raspberrypi pisound-btn[911]: Reading Pisound version failed, Pisound is possibly not attached. Continuing anyway.
Dez 18 15:15:51 raspberrypi systemd[1]: pisound-ctl.service - Bluetooth service for Pisound companion app. was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/pisound).
Dez 18 15:16:21 raspberrypi sudo[1765]: ed : TTY=pts/0 ; PWD=/home/ed ; USER=root ; COMMAND=/usr/sbin/modprobe pisound
And just after sending the log above, I shut down, mounted the Pisound and put that same SD card into a Pi4, just to confirm to myself again that it’s found there.
It seems I have managed to solve my problem, yesterday evening.
I reattached the Pisound to the RPi5, booted up PatchboxOS, and it was the same as before.
I previously had wondered why there are no entries in config.txt for the various models and what pisound overlays should be loaded, and at the time had thought “oh well, if it works on Pi4…”
Then yesterday I tried and got it to be recognized, first in my testing openSUSE TW install, by adding a [pi5] section like this
So I did the same in Patchbox OS (just before [all] near bottom of config.txt), and after rebooting Pisound is found and available, and HDMI audio as well thanks to the vc4-kms-v3d-pi5 entry.
I also added “pisound” there just because I don’t know whether pisound-pi5 is a replacement or depends on it, and would try to remove that again as a next step. I just don’t understand why it works on RPi4 without any special entry in config.txt. I’ve compared it to the upstream version contained in patchbox-os-gen, to make sure it’s not just this SD card which I’ve tinkered with in the past, but config.txt was the same in both…
BTW, I can’t seem to find how to mark this post as the solution to the thread…
The appropriate dtoverlay should get loaded automatically from Pisound’s EEPROM, and Raspberry Pi OS has some logic for autodetecting that it has to load the pisound-pi5 too when running on Pi 5. Your solution forces the same to happen, so it’s a good workaround in case something goes wrong with the automatic route.
pisound-pi5 is an addition to pisound as a base, so both should be loaded, -pi5 going after the base pisound.
Yes, that fixed it for me back when I wrote the post… but, just now, I tried and commented it out again, then rebooted, to confirm the issue is still there, and surprise, Pisound is visible and working.
No idea what happened at that occasion, but all is fine now.