Turris OS 6.5.0 is released!

Community office
, , ,
106

Finally also updated the flash. Omnia 2020. 2 wifis, 1TB SSD.

root@turris:~# nor-update
Verifying /dev/mtd0 against uboot ...
a3a04aa6143fe437e00b96fbcc8cd20f - /dev/mtd0
a3a04aa6143fe437e00b96fbcc8cd20f - uboot
Success
Verifying /dev/mtd1 against rescue ...
550b8eb1766f9348fe928ebcbbd3aa49 - /dev/mtd1
550b8eb1766f9348fe928ebcbbd3aa49 - rescue
Success
root@turris:~# strings /dev/mtd0 | grep U-Boot
U-Boot SPL 2022.10-rc4-OpenWrt-r16653+119-44ce70f0e2 (Sep 15 2022 - 18:21:35 +0000)
U-Boot
** Invalid partition type "%.32s" (expect "U-Boot")
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
U-Boot.armv7
U-Boot
U-Boot 2022.10-rc4-OpenWrt-r16653+119-44ce70f0e2 (Sep 15 2022 - 18:21:35 +0000)
:U-Boot
root@turris:~#

After reboot only leds not lit. Otherwise I haven’t yet observed any other problem. Anyway this doesn’t have priority.

Edit: After trying set brightness with rainbow cmd leds lit, but all white. Restarting rainbow doesn’t make a change.

I don’t know much about env cfg, mine looks like below, is it allright?

root@turris:~# fw_printenv
Read error on /dev/mtd0: Attempted to read 65536 bytes but got 0
root@turris:~#
root@turris:~# cat /etc/fw_env.config
/dev/mtd0 0xC0000 0x10000 0x40000
/dev/mtd0 0xf0000 0x10000 0x10000
root@turris:~#
root@turris:~#
root@turris:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 000f0000 00010000 "U-Boot"
mtd1: 00700000 00010000 "Rescue system"
mtd2: 00010000 00010000 "u-boot-env"
root@turris:~#
108

I have problem with notifications about new mac address on my Turris, after update to 6.5.0. Every 5 minutes come new mail report with one or tens of records with new mac address on my LAN.
When I go back to 6.4.5, no notifications are send.

The worst problem, I can’t find, where I this feature turn ON. :slight_smile: Any adea, please? :smiley: Thank you

109

@iron-maiden This should fix print env:

110

Updated but didn’t help, does it require a reboot?

root@turris:~#
root@turris:~# cat /etc/fw_env.config
/dev/mtd2 0x00000 0x10000 0x10000
root@turris:~#
root@turris:~#
root@turris:~# fw_printenv
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200
root@turris:~#
111

@iron-maiden :slight_smile:

It was mentioned here in the topic before in case of CRC error by @mionica

1 Like
112

Many thanks, this worked, it also corrected the leds.

Don’t use below(it doesn’t work)

echo '/dev/mtd2 0x00000 0x10000 0x10000' > /etc/fw_env.config

But use

echo '/dev/mtd2 0x0 0x10000 0x10000' > /etc/fw_env.config

Although the value in both is 0 those trailing zeros make a problem(probably can’t parse).

So it seems nor_update script leaves the system not fully configured. It needs an update.

113

hi, just brick my turris 2019 by updating the firmware.
6.5 was installed for over 1 week with no issues.

114

ordered an serial cable, keep you in touch

1 Like
116

Worked like a charm, thanks!

117

hello,
I have updated both the firmware as well but all the leds are now always off. It only turns on all (makes the rainbow) when the router is rebooted.
I’ve tried what you said but it’s still the same, anyone else?
Model Turris Omnia CZ11NIC13

118

Just push the button on the front lol.

4 Likes
119

Today Turris 1.0 updated smoothly without any issue

120

Why do you write in Czech in the English part of the forum and you are vugar?

121

The time for closing this topic has come …
TurrisOS 6.5.1 was released

1 Like