ORAM 2405: fresh installation but ERROR

I have this HW:
• Raspberry RPi5 4GB
• 5" TFT LCD display Capacitive Touch Screen DSI Connector 800x480
• PiFi DAC+ v2.0

I did a fresh installation of ORAM 2405, and update.
After boot screen with Zynthian ERROR this is what the screen shows:

[ 1.728112] systemd[1]: failed to start backlight.service - Turn on/off Display Backlight.
Debian GNU/Linux 12 zynthian tty1

System reboots in a loop.

Do you have any suggestions?

HARDWARE

HARDWARE

Raspberry Pi 5 Model B Rev 1.0
Audio: HifiBerry DAC+
Display: MPI5008 800x480
Wiring: DUMMIES
I2C: Not detected
Profile:

SYSTEM

Debian GNU/Linux 12 (bookworm)
Build Date: 2024-03-01
Memory: 7% (321M/4045M)
SD Card: 91% (13G/15G)
Temperature: 70.8ºC
Overclock: None

MIDI & UI

Tuning: 440 Hz
Master Channel: Off
Preload Presets: On
ZS3 (SubSnapShots): On
Power Save: 60 minutes
Audio Levels on Snapshots: On

SOFTWARE

zyncoder: oram (84612a6)
zynthian-ui: oram (7b5ea12)
zynthian-sys: oram (7c9dfd3)
zynthian-data: oram (db0355a)
zynthian-webconf: oram (3b48f5c)

LIBRARY

Snapshots: 12
User Presets: 1
User Soundfonts: 0
Audio Captures: 0
MIDI Captures: 0

NETWORK

Hostname: zynthian
Wifi: ON
IP: 192.168.32.17
VNC: Off
MIDI Services:

You have to configure audio and display from webconf. Please, note that autodetection only work for well know hardware configurations, aka official kits.

Regards

You have to configure audio and display from webconf

I did it because I read your suggestion in previous posts:

audio: Hifiberry Dac+ (I believe it is ok)
screen: I tried MPI DSI 800x480, MPI5008 800x480 and custom device adding 800x480 and Framebuffer: /dev/fb1 but … the result is still ERROR

Maybe it can be fixed if I can “Turn on/off Display Backlight” as written on screen
but I have no idea about how to do it

I verified that installing Ubuntu 24.04 LTS on this HW the LCD works perfectly.

Hi @piattica !

If you see the error in the zynthian screen, then the display is working mate! :wink:
The problem is not the display. Please, send the UI logs.

And be careful with your fingers if you touch the Pi5:

Temperature: 70.8ºC

:sweat_smile:

Regards,

you are right :slight_smile:
here the log:

May 18 08:05:33 zynthian startx[7985]: ZynCore->setup_zyncoder(1, 17, 17): Can’t configure zyncoder on a single pin!
May 18 08:05:33 zynthian startx[7985]: ZynCore->setup_zyncoder(2, 17, 17): Can’t configure zyncoder on a single pin!
May 18 08:05:33 zynthian startx[7985]: ZynCore->setup_zyncoder(3, 17, 17): Can’t configure zyncoder on a single pin!
May 18 08:05:33 zynthian startx[7985]: ZynCore->gpiod_start_callbacks: Callback thread created successfully
May 18 08:05:33 zynthian startx[7985]: Cannot connect to server socket err = No such file or directory
May 18 08:05:33 zynthian startx[7985]: Cannot connect to server request channel
May 18 08:05:33 zynthian startx[7990]: jackdmp 1.9.21
May 18 08:05:33 zynthian startx[7990]: Copyright 2001-2005 Paul Davis and others.
May 18 08:05:33 zynthian startx[7990]: Copyright 2004-2016 Grame.
May 18 08:05:33 zynthian startx[7990]: Copyright 2016-2022 Filipe Coelho.
May 18 08:05:33 zynthian startx[7990]: jackdmp comes with ABSOLUTELY NO WARRANTY
May 18 08:05:33 zynthian startx[7990]: This is free software, and you are welcome to redistribute it
May 18 08:05:33 zynthian startx[7990]: under certain conditions; see the file COPYING for details
May 18 08:05:33 zynthian startx[7990]: JACK server starting in realtime mode with priority 10
May 18 08:05:33 zynthian startx[7990]: self-connect-mode is “Don’t restrict self connect requests”
May 18 08:05:33 zynthian startx[7990]: audio_reservation_init
May 18 08:05:33 zynthian startx[7990]: Acquire audio card Audio0
May 18 08:05:33 zynthian startx[7990]: creating alsa driver … hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
May 18 08:05:33 zynthian startx[7990]: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
May 18 08:05:33 zynthian startx[7990]: JackTemporaryException : now quits…
May 18 08:05:33 zynthian startx[7990]: Released audio card Audio0
May 18 08:05:33 zynthian startx[7990]: audio_reservation_finish
May 18 08:05:33 zynthian startx[7990]: Cannot initialize driver
May 18 08:05:33 zynthian startx[7990]: JackServer::Open failed with -1
May 18 08:05:33 zynthian startx[7990]: Failed to open server
May 18 08:05:34 zynthian startx[7985]: Cannot connect to server socket err = No such file or directory
May 18 08:05:34 zynthian startx[7985]: Cannot connect to server request channel
May 18 08:05:35 zynthian startx[7985]: Cannot connect to server socket err = No such file or directory
May 18 08:05:35 zynthian startx[7985]: Cannot connect to server request channel
May 18 08:05:36 zynthian startx[7985]: Cannot connect to server socket err = No such file or directory
May 18 08:05:36 zynthian startx[7985]: Cannot connect to server request channel
May 18 08:05:37 zynthian startx[7985]: Cannot connect to server socket err = No such file or directory
May 18 08:05:37 zynthian startx[7985]: Cannot connect to server request channel
May 18 08:05:38 zynthian startx[7985]: Cannot connect to server socket err = No such file or directory
May 18 08:05:38 zynthian startx[7985]: Cannot connect to server request channel
May 18 08:05:39 zynthian startx[7985]: jack server is not running or cannot be started
May 18 08:05:39 zynthian startx[7985]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
May 18 08:05:39 zynthian startx[7985]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
May 18 08:05:39 zynthian startx[7985]: ZynMidiRouter: Error connecting with jack server.
May 18 08:05:40 zynthian startx[7985]: Started libzynaudioplayer using libsndfile-1.2.0
May 18 08:05:40 zynthian startx[7985]: Cannot connect to server socket err = No such file or directory
May 18 08:05:40 zynthian startx[7985]: Cannot connect to server request channel
May 18 08:05:40 zynthian startx[7985]: jack server is not running or cannot be started
May 18 08:05:40 zynthian startx[7985]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
May 18 08:05:40 zynthian startx[7985]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
May 18 08:05:40 zynthian startx[7985]: libzynmixer: Failed to start jack client: 17
May 18 08:05:40 zynthian startx[7985]: libzynaudioplayer exiting… done!
May 18 08:05:40 zynthian startx[8012]: /zynthian/config/img/fb_zynthian_message.png is 800x480 PNG image, color type RGB_ALPHA, 8 bit
May 18 08:05:40 zynthian startx[8012]: Zooming image by 100%…done
May 18 08:05:40 zynthian startx[8012]: Merging…done
May 18 08:05:40 zynthian startx[8012]: Building XImage…done
May 18 08:05:42 zynthian startx[7934]: xinit: connection to X server lost
May 18 08:05:42 zynthian startx[7934]:
May 18 08:05:43 zynthian startx[7934]: waiting for X server to shut down
May 18 08:05:43 zynthian startx[7935]: (II) Server terminated successfully (0). Closing log file.
May 18 08:05:43 zynthian startx[7934]: xinit: unexpected signal 15
May 18 08:05:43 zynthian systemd[1]: zynthian.service: Main process exited, code=exited, status=1/FAILURE
May 18 08:05:45 zynthian systemd[1]: zynthian.service: Failed with result ‘exit-code’.
May 18 08:05:45 zynthian systemd[1]: Stopped zynthian.service - Zynthian User Interface.
May 18 08:05:45 zynthian systemd[1]: zynthian.service: Consumed 1.820s CPU time.

Hi @piattica the error you get comes from a bad audio config => jackd won’t start => zynthian-ui won’t start => ERROR message

This could be jackd parameter hw:0 meaning “hey jack, use the first audio device in the list” but the way devices (these could be also USB midi gears) are listed may change. Eg. Starting Zynthian with all USB devices already pluged in or first start Zynthian and then plug the different USB devices

Using ssh or webconf built in terminal type

aplay -l

This will give you the name of the device (“sndrpihifiberry” I guess). Then change hw:0 to hw:device_name and reboot.

If it doesn’t solve your issue, maybe “HifiBerryDAC+” isn’t the the good one

1 Like

problem of restart loop was solved with your help thanks when I changed setting audio to HIFIBerry DAC+ light

but when I play, on mixer screen volume bars move but no sound from output.

If I type aplay - l:
root@zynthian://zynthian# aplay -l this is the result:

root@zynthian://zynthian# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dac], device 0: HifiBerry DAC HiFi pc
m5102a-hifi-0 [HifiBerry DAC HiFi pcm5102a-hifi-0]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0

Check the audio levels view that output level is up. Does the main mixbus meter show audio level or just the channel strips? Have you checked the audio connection is good and actually making audio in your amp, e.g. touch the jacks and hear the hum?

Hmmmm …
I wonder if it half works because pcm5102a driver is loaded but this PiFi dac use pcm5122 (wich has, I think so, some software controls through I2C).

you are right

so what I can do?
Is there some audio option that uses pcm5122 ?

I’ll be back home soon and will be more confortable to investigate.

1 Like

no you have to use HIFIBerry Dac+ : that one has pcm5122 on board, while HIFIBerry Dac Light has pcm5102