Turris OS 6.0.1 is now released

[jada4p]

Using CLI:

rainbow brightness 0 (Turris Omnia)

rainbow activity disable (MOX)

Errors could be ignored, or sent to black hole (add 2>/dev/null to command)

[pdm]

I contacted support and it has been confirmed that my version of Mox (from the Indiegogo) doesn’t work with 6.0.1 yet. I was advised to remain on 5.4.4 and to switch to hbs-sdio branch to prevent updates to 6.
No response about Omnia so far.

[peterb]

Is there a way to find out whether a Mox will work with 6.0.1 or not?

Since there are a couple of negative reports of running 6.0 on Mox devices and my Mox is my main router, I would like to avoid complains of the other family members.

Peter

[vcunat]

I believe that’s

Turris OS 5.4.5 (MOX only)

[peterb]

This announcement was only about SDIO support (which I don’t need).

I’m more worried about the unwanted reboots I read about.

[thierry]

Thanks for the workaround. Works fine for me

[KreMic]

Meanwhile I got response from support team. Since lighttpd config files in /etc/lighttpd/conf.d got number prefixes - as mentioned in Turris OS 6.0 release notes - I renamed letsencrypt.conf to 10-letsencrypt.conf and lighttpd starts again without any error.

[thierry]

didn’t saw that.
I just did it, it works.
Thanks a lot.

[skorpil_cz]

Just upgraded Turris 1.x from 5.x directly to 6.0.1. It seems that rainbow is still broken.
After boot all leds say blue without showing any activity, ranbow commands do nothing with leds and only return error:

reader_loop: bad jump: 8388608
Aborting...

The only thread with this problem is closed as solved with upgrade to 6.0.1. Seeking for any advice, help or solution…

[mvasilek]

You are correct that this is not fixed with 6.0.1, but it should be fixed in rainbow now and will be part of 6.0.2.