Turris OS 6.0.4 is in the testing branch

[moeller0]

@mvasilek

We are mostly interested in the librespeed client CLI which doesn’t apply this overhead compensation factor.

Ah, good then. Thanks for taking the time to respond.

[ssdnvv]

@Pepe

One package contains Wi-Fi firmware for AsiaRF AW7916-NPD, otherwise it was required to download firmware manually and put it to the correct folder.

I just placed our 3rd collective purchase order, which includes 9 AW7916-NPD-cards, so there are 7 more useres out there testing it soon

[mattventura]

Hmm, I’m still having the LED issue I posted about here.

[michalko58]

Omnia 2GB (Indiegogo) with two same wifi 6 cards. Today after auto-restart 5GHz wifi stopped working. Both cards are visible in reforis or LuCi, but 5GHz wifi is not working. Restart didn´t helped, there was no time to investigate it further.

LED still don´t remember brigthness. thanks this I have noticed problem with 5GHz wifi

[michalko58]

lspci command seems to return that everything is ok both 6.0.3 and 6.0.4

root@turris:~# lspci
00:01.0 PCI bridge: Marvell Technology Group Ltd. 88F6820 [Armada 385] ARM SoC (rev 04)
00:02.0 PCI bridge: Marvell Technology Group Ltd. 88F6820 [Armada 385] ARM SoC (rev 04)
00:03.0 PCI bridge: Marvell Technology Group Ltd. 88F6820 [Armada 385] ARM SoC (rev 04)
01:00.0 Unclassified device [0002]: MEDIATEK Corp. MT7915E 802.11ax PCI Express Wireless Network Adapter
02:00.0 Unclassified device [0002]: MEDIATEK Corp. MT7915E 802.11ax PCI Express Wireless Network Adapter
03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)

Rollback to 6.0.3 helped with this wifi problem, so I will stay definitely on HBS for now.

[Shulyaka]

Hi! I have a problem with OOM-killer with kernel 5.15.80. Turris might want to hold 6.0.4 for HBS.
I solved it by reverting to 6.0.3 (5.15.78).

More details if you want them:

Unprovoked OOM mass killing

Hi! I need some community help. My Omnia (2Gb RAM, HBT) a couple of days ago suddenly started to reboot every few hours. The reason appears to be the oom-killer, but I fail to see the reason. The logs say that a random process invokes oom-killer, then it shoots one process after another, until it kills something that triggers a reboot. Now, I confess that I do run a lot on my omnia. The most notable is an lxc container with Home Assistant and a mariadb database. But the memory consumption ne…

[cech]

Just upgraded turrix1 from previous 6.0.4 rc - kernel 5.10.156-> 5.10.158-2 and nothing works - no WAN/LAN/WLAN network. Boot process seems OK - LED go 5->1

[Pepe]

We didn’t release new RC version since last week. It’s scheduled to be released this week. I think you are talking about our HBK branch, where there could be occasional bugs.

[cech]

Could be. Bellow the output from console. That is everything I get.

BOOT NAND
reading zImage
5611700 bytes read in 299 ms (17.9 MiB/s)
wdt status 00000003
reading fdt
13486 bytes read in 13 ms (1012.7 KiB/s)
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 02100000 ...
   Image Name:   Linux-5.10.158
   Created:      2022-12-12  14:20:02 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    5611636 Bytes = 5.4 MiB
   Load Address: 00c00000
   Entry Point:  00c00290
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
   Booting using the fdt blob at 0x2000000
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 03ff9000, end 03fff4ad ... OK
WARNING: could not find compatible node fsl-usb2-dr

[Pepe]

Yep, I know, what’s going on. Will be fixed in a new HBK build, thanks for reporting!

[cech]

Great. Hope nobody else has the same luck.
Now to manually rollback the kernel …

Edit: was not so bad

[ChrisDeath]

Shouldn’t a drop a of a feature not be at least a minor version instead of a patch version? For my understanding major can change a lot and break things, minor can add new features (and maybe break things), but patches are always save and are intended to repair things instead of harming something. Or am i wrong? Software versioning - Wikipedia

And no…i am not using ISDN anymore

[Pepe]

Turris OS 6.0.4 RC3 is out!

• Added Snowflake
• Wi-Fis are now working
• Updated Linux, golang, cronie
  and many more…

[jada4p]

Applied RC3 of OS 6.0.4

MOX classic, HBK branch, .5 GB, 2x WiFi, simple config, all seems OK. (*)(%)(+)

(*) for my simple case is rainbow working - heartbeat during day, off during night
(%) except SDIO WiFi.
(+) USB 3 flash not recognized

[peci1]

RC2->RC3 update ok, no unintended wifi or internet downtime. Restart needed.

---

Turris Omnia 2017, 1 GB RAM, dead eMMC, system running from mSATA SSD, original wifi cards. Storage plugin enabled, LXC containers, tor relay, USB HDD shared over samba4 and minidlna, SQM, Hardwario gateway + MQTT IoT bridge, OpenVPN, PPtP VPN, morce.

[Pepe]

Another RC is out!

• Release notes:
  • added several kmod packages

Hopefully, the final one.

[peci1]

RC3->RC4 update ok, no unintended wifi or internet downtime. Restart needed.

---

Turris Omnia 2017, 1 GB RAM, dead eMMC, system running from mSATA SSD, original wifi cards. Storage plugin enabled, LXC containers, tor relay, USB HDD shared over samba4 and minidlna, SQM, Hardwario gateway + MQTT IoT bridge, OpenVPN, PPtP VPN, morce.

[mvasilek]

Yes, but in this case it’s not dropping a feature. isdn4linux was removed from the kernel in 5.3, Turris OS 6.0 uses 5.10 (Turris 1.x) and 5.15 (MOX, Omnia), so this package was empty. We decided to remove it now to fix this situation and it’s only marked as a breaking change because it will break the update for people who have that package installed. This is also dropped upstream in OpenWrt.

[Pepe]

Ok, guys, this is the final RC before this goes out to everyone tonight.

Turris OS 6.0.4 RC5:

• Disabled MGLRU, which should fix Unprovoked OOM mass killing
  • It was only enabled for Turris OS 6.0.4, thus nothing to miss
    • Don’t worry, but we will give it another try in the future!