Hi All – I just received and built a new Zynthian 4.5 kit.
Build seemed to go pretty smoothly and it boots up, but I’m stuck on the Zynthian splash screen. No progress after that but no error messages either. The instrument doesn’t respond to button or encoder pushes.
I’m using the latest stable release dated 2021-09-25
Any tips for diagnosing what might be the problem?
How long did you leave it? The first boot takes a long time to complete its setup.
A couple of minutes…Should I let it go longer?
Also, I’m looking for a checksum for the latest distribution to make sure my download wasn’t corrupted. I can’t seem to find this. Is this available somewhere?
Thanks!
Yep! It can take quite a few minutes. I have been worried that it has failed but a bit of patience paid off. The images are here including their MD5 checksums. If you are seeing the splash screen then I expect the image has installed okay. If you have a standard kit then it should start up okay after a few minutes.
Can it really take tens of minutes? I’m about 20 mins in and I’m not seeing any indication that something is happening. Is there a way to see the boot messages so I can potentially troubleshoot?
Could a large microSD size contribute to slowness? I’m using a 200GB SanDisk USH-I card
There have been reports of large SD causing Zynthian builds to fail. It is possible that resizing the image could be taking a long time. If the whole disk had to be written (which sounds unlikely) it would take over 30 minutes to write. Can you try with a smaller SD?
I tried it with a 32GB card as well. Same symptoms –
*Boots to splash screen
*Reboots once (I didn’t notice this with the 200GB card the first time, but I confirmed it does reboot once)
I’ve ordered a micro-HDMI to HDMI converter for more hands on troubleshooting. Hopefully that will provide some insight…
I’ve gotten a hold of a micro-HDMI cable so I’m able to provide more diagnostic info.
What I’m seeing during the boot messages is repeated starting and stopping of the Zynthian User Interface. Eventually it gets to the login prompt, but both the Zynthian screen and the HDMI output repeatedly blink on and off. Note that the Zynthian display stays on the splash screen.
Does sound like a familiar bug? I’ve disconnected the 3.5" screen and that doesn’t seem to change the blinking HDMI output. Any help would be greatly appreciated before I initiate a return of my kit, as it seems like some part must be faulty.
An additional bit of info: I just installed the default Raspberry Pi OS – everything boots fine, I get the standard GUI, wifi tests out, etc. This is with the same microSD card as I was trying with the Zynthian OS. So I think I can eliminate the Pi itself or a bad microSD card as the source of the problem.s
And some more info – I tried the 2021-05-18 build and this time I was at least able to get past the Zynthian Splash screen to the “Error/IP:” screen. Tried to use the webconf interface but the system kept resetting so wasn’t able to login.
If you have console access (HDMI + USB keyboard or ssh) then log in as user “root” and password “raspberry” then type journalctl -ru zynthian and report the first few dozen lines. It is easier to do this by copying and paste from a ssh session. With Windows 10, MacOS or Linux:
ssh root@zynthian.local
Note: Some operating systems do not resolve zynthian.local so you may need to replace with the IP address of the box. If you are not reaching the error screen then knowing the IP can be awkward but if you can log in with HDMI and USB keyboard you can type ip address which should show the IP address of the box (with some other gumph).
Post the results and we may be able to see what is going wrong.
For completeness here’s my system info (note I found the 10-10 build under the /test directory at os.zynthian.org):
########################## ----------------------------------------
# # ZynthianOS: Built on os.zynthian.org
# ## # Timestamp: 2021-10-10
# ## # # ## # Optimized: Raspberry Pi 3 Model B Plus
# # # # # # # # ----------------------------------------
### # # # # # # ### Kit: V4
# # # # # # # # # # Display: ZynScreen 3.5 (v1)
# ## # # # # ## # Soundcard: HifiBerry DAC+ ADC PRO
# ## ## # Wiring Layout: MCP23017_ZynScreen
# # ----------------------------------------
##########################
zynthian-ui: stable (478b6a)
zynthian-webconf: stable (39b61b)
zyncoder: stable (7c0973)
zynthian-sys: stable (e33fd3)
zynthian-data: stable (006a07)
And here’s the first 48 lines of output from journalctl -ru zynthian :
-- Logs begin at Wed 2020-05-27 08:27:57 BST, end at Wed 2020-05-27 08:34:07 BST. --
May 27 08:34:07 zynthian systemd[1]: Started Zynthian User Interface.
May 27 08:34:07 zynthian systemd[1]: Stopped Zynthian User Interface.
May 27 08:34:07 zynthian systemd[1]: zynthian.service: Failed with result 'exit-code'.
May 27 08:34:07 zynthian systemd[1]: zynthian.service: Main process exited, code=exited, status=1/FAILURE
May 27 08:34:07 zynthian startx[8443]: xinit: unexpected signal 15
May 27 08:34:06 zynthian startx[8443]: waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
May 27 08:34:06 zynthian startx[8443]: [1B blob data]
May 27 08:34:06 zynthian startx[8443]: xinit: connection to X server lost
May 27 08:34:06 zynthian systemd[1]: Stopping Zynthian User Interface...
May 27 08:34:05 zynthian startx[8443]: Building XImage...done
May 27 08:34:05 zynthian startx[8443]: done
May 27 08:34:05 zynthian startx[8443]: Merging...didn't find evidence of prior run.
May 27 08:34:05 zynthian startx[8443]: Zooming image by 100%...done
May 27 08:34:05 zynthian startx[8443]: /zynthian/config/img/fb_zynthian_boot.png is 480x320 PNG image, color type PALETTE, 8 bit
May 27 08:34:04 zynthian startx[8443]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
May 27 08:34:04 zynthian startx[8443]: (==) Using config directory: "/etc/X11/xorg.conf.d"
May 27 08:34:04 zynthian startx[8443]: (==) Log file: "/var/log/Xorg.0.log", Time: Wed May 27 08:34:04 2020
May 27 08:34:04 zynthian startx[8443]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
May 27 08:34:04 zynthian startx[8443]: (++) from command line, (!!) notice, (II) informational,
May 27 08:34:04 zynthian startx[8443]: Markers: (--) probed, (**) from config file, (==) default setting,
May 27 08:34:04 zynthian startx[8443]: to make sure that you have the latest version.
May 27 08:34:04 zynthian startx[8443]: Before reporting problems, check http://wiki.x.org
May 27 08:34:04 zynthian startx[8443]: Current version of pixman: 0.36.0
May 27 08:34:04 zynthian startx[8443]: xorg-server 2:1.20.4-1+rpt3+deb10u3 (https://www.debian.org/support)
May 27 08:34:04 zynthian startx[8443]: Build Date: 19 April 2021 03:23:36PM
May 27 08:34:04 zynthian startx[8443]: Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 smsc95xx.macaddr=E4:5F:01:0E:C2:4A vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
May 27 08:34:04 zynthian startx[8443]: Current Operating System: Linux zynthian 5.10.63-v7l+ #1457 SMP Tue Sep 28 11:26:14 BST 2021 armv7l
May 27 08:34:04 zynthian startx[8443]: Build Operating System: Linux 5.10.17-v8+ aarch64 Raspbian
May 27 08:34:04 zynthian startx[8443]: X Protocol Version 11, Revision 0
May 27 08:34:04 zynthian startx[8443]: X.Org X Server 1.20.4
May 27 08:34:04 zynthian systemd[1]: Started Zynthian User Interface.
May 27 08:34:04 zynthian systemd[1]: Stopped Zynthian User Interface.
May 27 08:34:04 zynthian systemd[1]: zynthian.service: Failed with result 'exit-code'.
May 27 08:34:04 zynthian systemd[1]: zynthian.service: Main process exited, code=exited, status=1/FAILURE
May 27 08:34:04 zynthian startx[8379]: xinit: unexpected signal 15
May 27 08:34:03 zynthian startx[8379]: waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
May 27 08:34:03 zynthian startx[8379]: [1B blob data]
May 27 08:34:03 zynthian startx[8379]: xinit: connection to X server lost
May 27 08:34:03 zynthian systemd[1]: Stopping Zynthian User Interface...
May 27 08:34:02 zynthian startx[8379]: Building XImage...done
May 27 08:34:02 zynthian startx[8379]: done
May 27 08:34:02 zynthian startx[8379]: Merging...didn't find evidence of prior run.
May 27 08:34:02 zynthian startx[8379]: Zooming image by 100%...done
May 27 08:34:02 zynthian startx[8379]: /zynthian/config/img/fb_zynthian_boot.png is 480x320 PNG image, color type PALETTE, 8 bit
May 27 08:34:01 zynthian startx[8379]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
May 27 08:34:01 zynthian startx[8379]: (==) Using config directory: "/etc/X11/xorg.conf.d"
May 27 08:34:01 zynthian startx[8379]: (==) Log file: "/var/log/Xorg.0.log", Time: Wed May 27 08:34:01 2020
From the logs it looks like the xinit is failing and there’s an infinite loop of startx calls. I have no idea of the init scripts that get run when Zynthian boots, but does that make sense?
Another tidbit. I don’t know if this is relevant but I did notice these lines when examining the output of dmesg – I think these pcm512x lines have to do with the DAC?
[ 3.483852] pcm512x 1-004d: supply AVDD not found, using dummy regulator
[ 3.483987] pcm512x 1-004d: supply DVDD not found, using dummy regulator
[ 3.484039] pcm512x 1-004d: supply CPVDD not found, using dummy regulator
[ 3.485173] ads7846 spi0.1: touchscreen, irq 67
[ 3.485582] input: ADS7846 Touchscreen as /devices/platform/soc/fe204000.spi/spi_master/spi0/spi0.1/input/input1
[ 3.492178] pcm512x 1-004d: Failed to reset device: -121
[ 3.496532] pcm512x: probe of 1-004d failed with error -121
[ 3.939477] graphics fb1: fb_ili9486 frame buffer, 480x320, 300 KiB video memory, 32 KiB buffer memory, fps=33, spi0.0 at 64 MHz
Check that you have connected the ribbon cables correctly. Some common mistakes are to reverse the connections, offset by a row or column and not fully insert.
Hi @pmags !
This:
[ 3.492178] pcm512x 1-004d: Failed to reset device: -121
[ 3.496532] pcm512x: probe of 1-004d failed with error -121
could be due to soundcard failure. If it’s the case, i will send you a replacement ASAP.
Could you check if jackd is running? Type this from the console:
# journalctl -u jack2
Regards,
Hi @jofemodo
Here’s the first 50 lines of output of journalctl -u jack2. It looks like the jack2 service is also continuously restarting:
root@zynthian:~# journalctl -u jack2 | head -n 50
-- Logs begin at Wed 2020-05-27 09:10:26 BST, end at Wed 2020-05-27 09:13:04 BST. --
May 27 09:10:28 zynthian systemd[1]: Started JACK2 Audio Server.
May 27 09:10:28 zynthian jackd[455]: jackdmp 1.9.14
May 27 09:10:28 zynthian jackd[455]: Copyright 2001-2005 Paul Davis and others.
May 27 09:10:28 zynthian jackd[455]: Copyright 2004-2016 Grame.
May 27 09:10:28 zynthian jackd[455]: Copyright 2016-2019 Filipe Coelho.
May 27 09:10:28 zynthian jackd[455]: jackdmp comes with ABSOLUTELY NO WARRANTY
May 27 09:10:28 zynthian jackd[455]: This is free software, and you are welcome to redistribute it
May 27 09:10:28 zynthian jackd[455]: under certain conditions; see the file COPYING for details
May 27 09:10:28 zynthian jackd[455]: JACK server starting in realtime mode with priority 70
May 27 09:10:28 zynthian jackd[455]: self-connect-mode is "Don't restrict self connect requests"
May 27 09:10:29 zynthian jackd[455]: creating alsa driver ... hw:sndrpihifiberry|hw:sndrpihifiberry|256|2|44100|0|0|nomon|swmeter|-|32bit
May 27 09:10:29 zynthian jackd[455]: ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
May 27 09:10:29 zynthian jackd[455]: ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
May 27 09:10:29 zynthian jackd[455]: Failed to open server
May 27 09:10:29 zynthian systemd[1]: jack2.service: Main process exited, code=exited, status=255/EXCEPTION
May 27 09:10:29 zynthian systemd[1]: jack2.service: Failed with result 'exit-code'.
May 27 09:10:30 zynthian systemd[1]: jack2.service: Service RestartSec=1s expired, scheduling restart.
May 27 09:10:30 zynthian systemd[1]: jack2.service: Scheduled restart job, restart counter is at 1.
May 27 09:10:31 zynthian systemd[1]: Stopped JACK2 Audio Server.
May 27 09:10:31 zynthian systemd[1]: Started JACK2 Audio Server.
May 27 09:10:32 zynthian jackd[598]: jackdmp 1.9.14
May 27 09:10:32 zynthian jackd[598]: Copyright 2001-2005 Paul Davis and others.
May 27 09:10:32 zynthian jackd[598]: Copyright 2004-2016 Grame.
May 27 09:10:32 zynthian jackd[598]: Copyright 2016-2019 Filipe Coelho.
May 27 09:10:32 zynthian jackd[598]: jackdmp comes with ABSOLUTELY NO WARRANTY
May 27 09:10:32 zynthian jackd[598]: This is free software, and you are welcome to redistribute it
May 27 09:10:32 zynthian jackd[598]: under certain conditions; see the file COPYING for details
May 27 09:10:32 zynthian jackd[598]: JACK server starting in realtime mode with priority 70
May 27 09:10:32 zynthian jackd[598]: self-connect-mode is "Don't restrict self connect requests"
May 27 09:10:32 zynthian jackd[598]: creating alsa driver ... hw:sndrpihifiberry|hw:sndrpihifiberry|256|2|44100|0|0|nomon|swmeter|-|32bit
May 27 09:10:32 zynthian jackd[598]: ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
May 27 09:10:32 zynthian jackd[598]: ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
May 27 09:10:32 zynthian jackd[598]: Failed to open server
May 27 09:10:32 zynthian systemd[1]: jack2.service: Main process exited, code=exited, status=255/EXCEPTION
May 27 09:10:32 zynthian systemd[1]: jack2.service: Failed with result 'exit-code'.
May 27 09:10:33 zynthian systemd[1]: jack2.service: Service RestartSec=1s expired, scheduling restart.
May 27 09:10:33 zynthian systemd[1]: jack2.service: Scheduled restart job, restart counter is at 2.
May 27 09:10:35 zynthian systemd[1]: Stopped JACK2 Audio Server.
May 27 09:10:35 zynthian systemd[1]: Started JACK2 Audio Server.
May 27 09:10:35 zynthian jackd[676]: jackdmp 1.9.14
May 27 09:10:35 zynthian jackd[676]: Copyright 2001-2005 Paul Davis and others.
May 27 09:10:35 zynthian jackd[676]: Copyright 2004-2016 Grame.
May 27 09:10:35 zynthian jackd[676]: Copyright 2016-2019 Filipe Coelho.
May 27 09:10:35 zynthian jackd[676]: jackdmp comes with ABSOLUTELY NO WARRANTY
May 27 09:10:35 zynthian jackd[676]: This is free software, and you are welcome to redistribute it
May 27 09:10:35 zynthian jackd[676]: under certain conditions; see the file COPYING for details
May 27 09:10:35 zynthian jackd[676]: JACK server starting in realtime mode with priority 70
May 27 09:10:35 zynthian jackd[676]: self-connect-mode is "Don't restrict self connect requests"
May 27 09:10:35 zynthian jackd[676]: creating alsa driver ... hw:sndrpihifiberry|hw:sndrpihifiberry|256|2|44100|0|0|nomon|swmeter|-|32bit
It looks like the sound card is not working. Check the cables as I mentioned earlier. It is easy to get this bit wrong. Many of us have done it!
Even if it looks right, post some pictures of the connections and cabling. We may notice something subtle.
Hi @riban – I have indeed checked this several times and removed all the ribbon cables, checked their orientation, and reseated them.
It does indeed seem like I might have a bum sound card, but would a non-working sound card lead to the continual restarting of X windows ?
Yep! Zynthian service launches the X server which will stop if Zynthian core fails. Zynthian core friends on jack so if Jack is not running then Zynthian and hence X won’t run. Jack won’t start of it’s soundcard is not available.
Thanks. That’s very helpful!
Does there exist a “big picture” document that explains how the various subsystems of Zynthian work together? I was browsing the code under zynthian-sys on the github repository, and that helps me get part of the picture but I was looking for the 10,000 ft view before trying to grok individual shell scripts and python libraries.