My custom Pi5 (Argon case with nvme + Waveshare touch 15.6 + Hifiberry DAC 8X) seems unable to successfully complete the latest Oram update routine (as of today’s release).
Everything appears to be built correctly, but in the end the system states: “repository frozen in stable tag release!”.
My repos are indeed in Oram stable mode in webconf. After the message, Oram enters a sort of endless OS update sign loop (perpetual green recycle symbol): the updates attempts do not complete and the system keeps on calling for updates.
Is Oram maybe misinterpreting my custom hardware, as if it implied that I am running a testing Vangelis OS?
EDIT: the VNC-engines visualisation seems now broken, it does not connect with the Zynth. VNC-UI works regularly instead.
By the way, would there be a solution for reinstalling the VNC-engines server separately, just in case it has been corrupted by an update patch?
I can confirm that the installed/activated processors work correctly, but no synth UIs are visible on VNC, since the session does not start and shows a blank grey screen, with an undulating logo waiting for connection.
I’d anyway suggest to disable autoconfig entirely. It would not be too much of a hassle even for the simple minded to configure their kit.
With my custom hardware, I have to unplug pin3 of the 40pin GPIO (SDA) to make first boot of a fresh image run through, then config everything in WebConf and reconnect, then reboot and everything works.
Hi @Aethermind and other zynthianers that updated stable oram in the last 2 days!
I made an error when preparing the next tag-release and your systems are probably “frozen” without possibility of receiving more updates.
To fix it, please, run this command from the webconf terminal:
cd $ZYNTHIAN_SYS_DIR & git pull
Or from the webconf, simply change to the stable tag release “oram-2409” and then back to staging “oram”.
After this, you should be allowed to update again.
Please, note that this has no relation with any VNC issue. AFAIK, VNC is working fine. Anyway, if you have issues with VNC, this should be reported separately.
I am not sure how relevant your otherwise useful DAC 8X GPIO pins usage warning is to my hardware, since it has worked like a charm on the Argon Pi 5 case until now, even after Oram ended locked in a green recycle sign loop with the latest update.
Later at home, if I manage to resurrect the system and boot it, I will possibly investigate
I tried running your patch in my (now alive again) custom Zynthian, both in Terminal and via SSH, but I get the following error message:
[1] 2100
fatal: not a git repository (or any of the parent directories): .git
[1]+ Done cd $ZYNTHIAN_SYS_DIR
The other route that you suggest - I guess setting repos to custom and then choosing Oram-2409 - seems not to be viable, since I see in all OS components (UI, webconf, zyncoder, sys, data) only Stable-2109 or Stable-2308 available, besides quite a few other previous software versions.
. Will try ASAP!