we just released Turris OS 7.0.3. This release is focused on Turris Omnia, so no changes for the rest of you.
There is added support for upcoming 5G kit for Turris Omnia. It should appear in retail in October, so we are preparing the software part.
But the other related part of the update is updated U-Boot. We did some changes for better compatibility with various RAM chips and added another reset mode - 10 LEDS which decreases RAM speed for better compatibility. You can now pretty safely update your U-Boot and if you encounter DDR training issues or instabilities, you can use this type of reset to resolve it by yourself. Big thanks to everybody who helped us test various U-Boot versions on various devices that we produced over the time!
Note: Due to the staged updates, not everybody will get it instantly, but the actual deployment to your routers will be spread over next few days.
Thatās wonderful news. The U-boot in Omnia has been dealt with for many years. Still, I have a feeling it will brick some devices, even if I donāt wish it to. When is the automatic U-boot update planned for the all Omniaās?
wowā¦just got this version, but now i have many of these rrdtool errors ?
Sep 25 11:30:12 turristhuis collectd[25111]: rrdtool plugin: rrd_update_r failed: /srv/rrd/turristhuis/memory/memory-buffered.rrd: opening ā/srv/rrd/turristhuis/memory/memory-buffered.rrdā: Read-only file system
edit, some more errors. nOOb here, but me think this update did something with read write permission on my ext USB drive ( Srv ) ?
Sep 25 11:59:54 turristhuis adblock.sh[24621]: /usr/bin/adblock.sh: line 813: canāt create /srv/adb_list.smarttv_tracking.gz: Read-only file system
Sep 25 14:05:12 turristhuis syslog-ng[5459]: Error suspend timeout has elapsed, attempting to write again; fd=ā17ā
Sep 25 14:05:12 turristhuis syslog-ng[5459]: I/O error occurred while writing; fd=ā17ā, error=āRead-only file system (30)ā
Hi, we are sorry for the inconvenience. Could you contact our support desk at info@turris.cz and send the diagnostics file. Support - Turris Documentation
Best regards
Marcela Turris Support Team
one moment, now busy with removing and formatting the USB drive, but it will not format it.
Trying a diff USB drive now, see what happens.
edit, that solved at least the fact that the ext drive is read only. adblock does see ( with a new USB drive) the /srv part.
I did uninstall the rrd tool part, to see if a re install would solve it, but now re installed it, but it is gone in Luciā¦
ok, i will send you the diag, rdd tools seems to be gone in Luci:)
Updated. With my patched kernel freshly build. Updated U-Boot and MCU firmware. All fine. My second Omnia running as dumb AP is still waiting until tomorrow but I guess it should go as smooth. Thanks!
root@ap:~# pkgupdate
WARN:There is a newer version available, but upda
te is scheduled after another 17.5 hours. If you
want the latest and greatest all the time, switch
to one of the development branches.
INFO:Target Turris OS: 7.0.2
Read-only filesystem is usually the error you get when the filesystem is damaged. You would see that in /var/log/messages near the boot time. Look for things like filesystem error.
not sure what happened, but that USB stick is un formatable, and basically dead after the update. any other machine here gives a nogo on formatting, Omnia does see it, but computer-says-no when i want to format it on the omnia.
so itis in the trash bin.
So, now i do see āstatisticsā in Luci, but it keeps telling that i should config collected . ( no RDD data)
No clue here, but collectd is running, ( system>startup)
and this is what U boot check is telling meā¦
root@xxxxx:~# strings /dev/mtd0 | grep U-Boot
U-Boot SPL 2024.10-rc3-OpenWrt-r20343+127-4e1d1b7df0 (Sep 13 2024 - 01:38:50 +0000)
U-Boot
** Invalid partition type ā%.32sā (expect āU-Bootā)
U-Boot
Device ā%sā not supported by U-Boot image
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
Burning U-Boot image ā%sā from ā%sā to ā%sā
U-Boot
U-Boot 2024.10-rc3-OpenWrt-r20343+127-4e1d1b7df0 (Sep 13 2024 - 01:38:50 +0000)
1U-Boot
So I updated second Omnia running as dumb AP. With U-Boot update. I saw there is also new command omnia-eeprom so Iāve set some values using it. All fine.
At least for my hardware there is no need for legacy_ram_training. Its running stable on default frequency. So no need to limit that. YMMV
I tried to update an Omnia Wifi 6 on HBS which had the experimental FW package list already from an earlier time.
I faced the exact same error as Turris OS 7.0.3 is in RC! - #25 by julien113 . In htop, I saw there is a fw_printenv process hogging one core. When I killed the process, the updater was able to finish and flash the new u-boot correctly.
My DDR speed in the eeprom: (empty, defaults to 1600K)
So far no problems, not 10 LED reset.
is your Wi-Fi Region set in the eeprom? mine is **
Just curious.
We ended up doing ** everywhere. Originally, we thought that we might be forced by various certification bodies to restrict the bands on routers sold in specific regions, but in the end, restricting it based on user settings was so far enough and we didnāt have to use this option.
Mmmh, that worked wellā¦ I jumped the shark and also (manually) updated u-boot and the mcu firmware (was a bit surprised that Marvel apparently controls their cinematic universe from my omnia, but that might explain why Marvel movies occasionally feel a bit below par, i bet this is when my network is loaded and hence my omnia has less time to control the mcuā¦)
Back to seriousness, both updates worked smooth and without apparent issues, and two reboots later all is well.
U-boot update on my first (Indiegogo-TO) has been spooky - first all leds were blinking green before reboot, then the device rebooted and the power led came onā¦ and then went out for good!
ā¦
Few seconds after that fortunately reForis was available again and I was relieved
edit: should one check only one of the 3 options for the update or am I allowed to check all three?