Turris OS 5.1.1 is out

Community office
, , , ,
1

Dear Turris users,

It is a pleasure to announce to you that we released Turris OS 5.1.1 from the Testing branch to all of you!

The most interesting change in this release is that is based on top of OpenWrt 19.07.4, which was released a few days ago. There are fixes for Sentinel logging and suppressed error message in logs about /proc/cmdline while using Foris/ReForis and a few fixes for security vulnerabilities found in ffmpeg, zmq, libxml2.

As always, we appreciate any feedback for this release.

4 Likes
3

runtime: [string “requests”]:417: [string “utils”]:422: Unable to finish URI (https://repo.turris.cz/hbs/omnia/lists/pkglists/reforis.lua): Download failed

Just installed, flapped link on all devices connected via ethernet…

And the above, also nowhere in the notification does it mention it was updated to version 5.1.1. Super weird.

4

MOX Classic 1/2 GB, HBK, updated by CLI pkgupdate, seems OK. reForis looping with blank starting page, LuCI seems OK.
Only hoping you’ll sort reboot problem, sometimes it takes more than 3 attempts :frowning:

5

I am thinking do you have your own custom lighttpd configuration?

6

No, only basic config with WiFi.

7

“fixes for Sentinel logging”

is probably the reason why device detection started working after the update. I had forgotten, that I checked that box after updating to 5.1, because there was simply nothing happening; now I get emails for devices showing up, sweet.
+1; for team turris.

8

Sorry, it was caused by old Android and Google browser version on tablet, I realised this only later. On PC with Win 10 and actual browser reForis is OK.

9

Thanks for letting us know. I’m glad that it works for you.

10

syslog-ng is outputting a warning to syslog on each log rotation. Bug filed here: https://gitlab.nic.cz/turris/turris-os-packages/-/issues/673 Issue seems to be that syslog-ng was updated but its configuration files were not.

11

I know, I forgot about it. Mea culpa. :frowning:
It is harmless. I will fix this once guys from syslog ng release a new version.

12
13

Upgraded this afternoon (medkit upgrade, previously using 3.11). Basic configuration (including wifi) is working flawlessly. Now experimenting with WireGuard, and restoring the msata disk mount.

14

Sensors shows the temperature for d0032004mdiomii01-mdio-1 higher than normal. Used to be around 60°C but since reboot it has increased to 90°C. Could also be that the network is used more than usual today. Anyone else seeing the same thing after the latest upgrade?

15

this is what i get with ~# sensors Omnia 5.1.1

x@x:~# sensors
mv88e6xxx102-mdio-2
Adapter: MDIO adapter
temp1: +79.0°C (crit = +100.0°C)

mv88e6xxx100-mdio-0
Adapter: MDIO adapter
temp1: +79.0°C (crit = +100.0°C)

f1072004mdiomii01-mdio-1
Adapter: MDIO adapter
temp1: +57.0°C (crit = +100.0°C)

mv88e6xxx103-mdio-3
Adapter: MDIO adapter
temp1: +79.0°C (crit = +100.0°C)

mv88e6xxx101-mdio-1
Adapter: MDIO adapter
temp1: +79.0°C (crit = +100.0°C)

armada_thermal-virtual-0
Adapter: Virtual device
temp1: +77.0°C

mv88e6xxx104-mdio-4
Adapter: MDIO adapter
temp1: +79.0°C (crit = +100.0°C)

and mox on 5.1.1

x@x:~# sensors
socinternalregsd0000000mdio32004switch02mdio14-mdio-e
Adapter: MDIO adapter
temp1: +22.0°C (crit = +100.0°C)

socinternalregsd0000000mdio32004switch02mdio12-mdio-c
Adapter: MDIO adapter
temp1: +22.0°C (crit = +100.0°C)

d0032004mdiomii01-mdio-1
Adapter: MDIO adapter
temp1: +62.0°C (crit = +100.0°C)

ath10k_hwmon-pci-0200
Adapter: PCI adapter
temp1: +43.0°C

socinternalregsd0000000mdio32004switch02mdio13-mdio-d
Adapter: MDIO adapter
temp1: +22.0°C (crit = +100.0°C)

socinternalregsd0000000mdio32004switch02mdio11-mdio-b
Adapter: MDIO adapter
temp1: +22.0°C (crit = +100.0°C)

16

Are there any known bugs left - e.g. the MOX reboot issue?

1 Like
18

Unfortunately, some of the known bugs are still there. If I am not mistaken, but not many and this should be the list.

Upstream issues, which affects Turris OS as well:

Turris HW known bugs:

  • In some cases, Turris MOX and Turris Shield are not correctly rebooted. You could try to remove the power supply and plug it back. We are working to have a workaround/solution with the manufacturer of SoC (Marvell).
3 Likes