What does it mean?
The counter increments itself.
I can’t access by Webconf.
What do you suggest to do?
What does it mean?
The counter increments itself.
I can’t access by Webconf.
What do you suggest to do?
Just a guess: it might be a sort of chronometer.
Something like Oram is expecting to find some missing structural/root/start sector of itself to properly boot.
Could you give us some context, eg are you trying to boot a fresh Zynthian image or did this problem show itself after an update to latest Oram or Vangelis?
Have you tried accessing webconf via the provided IP address? Connected directly to Zynthian’s ethernet port?
If you can simplify the configuration at all, perhaps by disconnecting any non-essential devices till after the boot it might get it to start.
It happened after the today update to latest Vangelis
I tried accessing Webconf via IP and via zynthian.local and via Ethernet without success with Zynthian alone
Is the only possible step to re-flash?
Is the only possible step to re-flash?
It’s the only thing I can think of right now. If you can wait you might get a better answer from someone else.
Thanks Leonard.
Yes, it is my second Zynthian that I use to learn ![]()
If you can ssh info the device, execute
journalctl
Look for any errors.
I got this error.
1/ ssh on to zynth
2/ cd /zynthian/zynthian-sys/scripts
3/ ./update_zynthian.sh
4/ I did this twice
5/ Power cycle
It worked for me.