# Latest Oram update (04/11/24) not completed on custom Pi5 \[SOLVED!\]

**URL:** <https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457>\
**Category:** Software\
**Created:** [November 4, 2024, 4:39pm UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457 "2024-11-04T16:39:00Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aethermind](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/aethermind/32/9208_2.png) [@Aethermind](https://discourse.zynthian.org/u/Aethermind)\
**Post date:** [November 4, 2024, 4:39pm UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/1 "2024-11-04T16:39:00Z")

</div>

Hi everybody,

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.

Thanks!

---

<div class="post-metadata">

**Author:** ![Aethermind](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/aethermind/32/9208_2.png) [@Aethermind](https://discourse.zynthian.org/u/Aethermind)\
**Post date:** [November 4, 2024, 11:01pm UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/2 "2024-11-04T23:01:41Z")

</div>

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.

Best regards

---

<div class="post-metadata">

**Author:** ![riban](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/riban/32/2331_2.png) [@riban](https://discourse.zynthian.org/u/riban)\
**Post date:** [November 5, 2024, 6:05am UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/3 "2024-11-05T06:05:22Z")

</div>

@jofemodo it looks like the updated scripting that you commented should be disabled is not actually disabled!

---

<div class="post-metadata">

**Author:** ![Aethermind](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/aethermind/32/9208_2.png) [@Aethermind](https://discourse.zynthian.org/u/Aethermind)\
**Post date:** [November 5, 2024, 6:50am UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/4 "2024-11-05T06:50:02Z")

</div>

Hi @riban, thanks for chiming in 🙂

As an update, my custom Oram system does not even start now. Just a passing red blink in the on/off led, and a dead Pi5 thereafter.

I will try to reset the bootloader with a recovery uSD later in the evening, after work, and will get back to the thread to report.

I hope not to have lost the Oram installation again!

Best regards

---

<div class="post-metadata">

**Author:** ![fussl](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/f/d07c76/32.png) [@fussl](https://discourse.zynthian.org/u/fussl)\
**Post date:** [November 5, 2024, 10:15am UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/5 "2024-11-05T10:15:53Z")

</div>

> [@Aethermind](#):
>
> Hifiberry DAC 8X

Could be due to the 8X using up GPIO pins normally used for Zynthian, which then irritates the auto-config.

[HiFiBerry DAC8x GPIOs 18-27 (pins 12, 13, 15, 16,18, 22, 35, 37, 38 and 40) are used for the sound interface. You can’t use these for any other purpose.](https://www.hifiberry.com/docs/hardware/gpio-usage-of-hifiberry-boards/)

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.

---

<div class="post-metadata">

**Author:** ![jofemodo](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/jofemodo/32/2_2.png) [@jofemodo](https://discourse.zynthian.org/u/jofemodo)\
**Post date:** [November 5, 2024, 11:03am UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/6 "2024-11-05T11:03:54Z")

</div>

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.

Thanks!

---

<div class="post-metadata">

**Author:** ![Aethermind](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/aethermind/32/9208_2.png) [@Aethermind](https://discourse.zynthian.org/u/Aethermind)\
**Post date:** [November 5, 2024, 2:47pm UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/7 "2024-11-05T14:47:19Z")

</div>

Thanks @fussl,

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 🙂

---

<div class="post-metadata">

**Author:** ![Aethermind](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/aethermind/32/9208_2.png) [@Aethermind](https://discourse.zynthian.org/u/Aethermind)\
**Post date:** [November 5, 2024, 2:50pm UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/8 "2024-11-05T14:50:17Z")

</div>

Thank you @jofemodo 👍

When I get my hands on the Zynthian, later this evening, I will try your patch, providing I manage to boot it 😉

---

<div class="post-metadata">

**Author:** ![Aethermind](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/aethermind/32/9208_2.png) [@Aethermind](https://discourse.zynthian.org/u/Aethermind)\
**Post date:** [November 5, 2024, 5:44pm UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/9 "2024-11-05T17:44:59Z")

</div>

Hi @jofemodo,

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.

Any suggestions? 🙂

---

<div class="post-metadata">

**Author:** ![jofemodo](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/jofemodo/32/2_2.png) [@jofemodo](https://discourse.zynthian.org/u/jofemodo)\
**Post date:** [November 5, 2024, 6:20pm UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/10 "2024-11-05T18:20:55Z")

</div>

Sorry, this command:

> cd $ZYNTHIAN\_SYS\_DIR; git pull

---

<div class="post-metadata">

**Author:** ![Aethermind](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/aethermind/32/9208_2.png) [@Aethermind](https://discourse.zynthian.org/u/Aethermind)\
**Post date:** [November 5, 2024, 6:46pm UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/11 "2024-11-05T18:46:54Z")

</div>

👍 Thank you @jofemodo. No problem 😀. Will try ASAP!

---

<div class="post-metadata">

**Author:** ![Aethermind](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/aethermind/32/9208_2.png) [@Aethermind](https://discourse.zynthian.org/u/Aethermind)\
**Post date:** [November 5, 2024, 9:18pm UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/12 "2024-11-05T21:18:29Z")

</div>

I can confirm that the patch has worked as expected, and that my custom Z system is now reliable again 👍 Thanks @jofemodo 🌈

---

<div class="post-metadata">

**Author:** ![Lanfranco](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/lanfranco/32/8094_2.png) [@Lanfranco](https://discourse.zynthian.org/u/Lanfranco)\
**Post date:** [November 23, 2024, 12:48pm UTC](https://discourse.zynthian.org/t/latest-oram-update-04-11-24-not-completed-on-custom-pi5-solved/10457/13 "2024-11-23T12:48:22Z")

</div>

I had the same problem for the update… With the patch from @jofemodo now everything works perfectly with the Raspberry P4 8Gb. Thanks