Hello, after using ORAM on Pi4 V5 kit for a while I tried today with a Pi5, using IQAudIO DAC Pro. Except for a HDMI monitor, mouse and keyboard, nothing else is connected to the Pi5. This soundcard uses the PCM5242. I tried to pre-define the iqaudio-dacplus or iqaudio-dac overlay in config.txt, but no chance to start. Everytime I get the red error screen, then rebooting. What can I do? Webconf is not possible due to the permanent rebooting. The first time I started latest ORAM Zynthian image, the Pi5 was bricked with blinking green power LED, so, I needed to reflash with a rescue image.
Hi @travelrec I’ve got the same DAC and it was working peefectly fine 3 or 4 weeks ago on Pi3 and Pi4 with up To date Oram.
I can have Ă look at it tomorrow.
Hi @travelrec!
Have you tried to connect preemptively an USB audio interface of whatever model and brand? (any inexpensive class-compliant type should work out-of-the-box also in Debian).
They tend to be rather reliable, and the Zynthian is quite flexible and ready to recognise them as audio system devices, if you disconnect your audio board beforehand and select the “dummy” profile in webconf/hardware/audio, then switch to Generic USB and reboot with your USB interface hooked.
Thereafter, you can possibly exclude any other system malfunctions, if Oram starts correctly, and try and solve with configuration lines the potential hardware compatibility problem with your DAC.
Hi @Aethermind
thank you fot the advice. Please note that I´m on Pi5, not Pi4 or 3 - on the Pi4 there is no problem.
I will try what you said.
Anyway, the PCM5242 card is supported by the RaspiOS without any modification of files and is working flawlessly.
OK, doesn´t work at all, also with USB audio device. Use Creative Extigy device. Works flawlessly with RaspiOS.
Re-flashed the SD-Card once again, Zynthcore build sucessfully, after 2nd startup IP: Audio/MIDI ERROR → Reboot over and over again. Used the USB card from the beginning.
Hi!
Yes, I was referring indeed to a similar Rpi5 FrankenZynth scenario, which I am running successfully.
I suggest using, if possible, a very general-market USB audio interface of proven reliability, nothing too exotic or cheap (I honestly do not know your device 
), in order to get solid drivers and good internal firmware.
Since you seem to be just fine on Raspberry OS with your Pi5, I guess that the culprits could either be a possibly low-transfer/not-so-fast SD disliked by Oram or an audio interface intrinsically incompatible with Zynthian.
Just guessing…
Thanks for your help, but I doubt the card is the problem, it´s Class 10 Sandisk Ultra or Sandisk Extreme I use for all of my Raspberries. Maybe someone of the proramming gurus has an idea. Since I have a running V5, it´s not too urgent. I like to have a P5 Zynthian too some day.
My mvme Pi5 Oram runs in fact significantly faster and more fluidly than my other Pi4 Zynthians on SD.
The wait will not be long anyway: they say around September at Zynthian Labs, for the release of the V5.1 Rpi5 revision. 
All good luck!
NVMe is the next step in my Raspi experience ;-).
1 Like
Have you updated the RPi firmware? When I got my RPi5 it needed a firmware update before it would run Zynthian. You can do this with an image on a uSD card that applies the firmware in seconds.
Hi @riban
since the first ORAM start crashed the RPi (blinking green LED), I needed to re-flash (restore) the RPi firmware with the Imager rescue tool. So, I think the firmware is OK now. Unless you tell me something different.
What are your jackd parameters from the wenconf audio options?
For the V5 integrated soundcard, that is based in the PCM5242, i have to use something like this:
-P 70 -s -S -d alsa -d hw:sndrpihifiberry -r 48000 -p 128 -n 2 -i 2 -o 2 -X raw
The Pi5 is more picky than the Pi4 with jackd parameters. It seems the new I2S subsystem integration is not yet 100% perfect.
You could try with something like:
-P 70 -s -S -d alsa -d hw:IQaudIODAC -r 48000 -p 128 -n 2 -o 2 -X raw
or perhaps:
-P 70 -s -S -d alsa -d hw:sndrpihifiberry -r 48000 -p 128 -n 2 -i 2 -o 0 -X raw
The best!
1 Like
I have also had problems with some jackd settings on Pi5. Both with the Hifiberry and and an external USB card. Changing the -p value between -p 256 and -p 128 seems to have solved the problems.
… Except for some strange out-of-sync/going-crazy sound issues sometimes, which seem to be a problem of the USB soundcard (that I probably already experienced long time ago as well). Actually, it is one of the three functionalities of my old Novation X-Station that I have now used also to embed my Zynthian into. Eventually, I have embedded it together with the Hifiberry to avoid its problematic functionality of “external sound card”. Fortunately, it seems to work well at least as an USB MIDI controller (and interface).
Hi @jofemodo
How should I access to the webconf, when the Pi5 is rebooting permanently in a loop? I used a fresh SD image from ORAM 2024-06-26. Either with the PCM5242 soundcard or with USB card or with nothing connected, the Pi5 will not start the Zynthian to a stable condition. So, no IP to access to.
Is the machine actually rebooting or is the UI restarting? If the former then it will be a challenge to do anything with it and the underlying fault needs to be rectified. If it is the latter then the webconf is likely to be running and network manager should be running so you could connect a PC directly to the Zynthian via Ethernet cable and try http:\zynthian.local which is the mDNS address that Zynthian advertises on by default.
Hi again,
not sure about this. I see the Error screen, then it disappears, then the login message can be seen for a short moment, then Error screen again. I can try to conncet the PI with network cable to the PC this evening and then I will reply again. Thank you so far.
1 Like
That sounds like the UI restarting, not the Zynthian rebooting. We are trying to improve this behaviour and have added some context to the error screen that is displayed but Zynthian will restart if it has a fatal error which is what seems to be happening here. Does the Zynthian show an error screen and if so, does that have any context info?
“IP: Audio/MIDI” is the only context.
Looks like an issue with audio config. You will need to gain access to webconf to set your audio device.