Turris OS 6.1.0 is now in the HBK branch

At the same time as we were polishing Turris OS 6.0.4, we were also preparing Turris OS 6.1.0. Now when Turris OS 6.0.4 is released, we are introducing Turris OS 6.1.0 to the testing branch. The changes include VLAN support, 5.15 kernel on Turris 1.x, Nextcloud 23 and many more.

:boom: Breaking Changes

  • Nextcloud now uses PHP 8
  • PHP 8 doc_root changed to /srv/www

:rocket: New Features

  • VLAN support for WAN interface in reForis
  • Credentials (username, password) support in OpenVPN reForis client

:bug: Bug Fixes

  • Fixed missing PHP 8 performance tuning
  • Fixed missing PHP 8 lighttpd config file
  • Fixed automatic Nextcloud updates without user approval in the UI
  • Fixed Turris Netboot to work with Turris OS 6
  • Fixed Rainbow not saving brightness when set with the button
  • Fixed builds of apr-util and subversion

:pushpin: Updates

  • Linux kernel on Turris 1.X updated from 5.10 to 5.15
  • Nextcloud updated to 23.0.11
  • reForis updated to 1.4.1
  • Foris Controller updated to 5.4.0
  • Turris HW updated to 0.10.0
  • reForis OpenVPN updated to 1.6.0
  • Foris Controller openvpn_client module updated to 0.7.0

If you would like to test this release, please follow Early access - Turris Documentation to switch your branch to hbk.

As always, if you find any issues, please don’t hesitate to reach out to us.

7 Likes

Great feature for beginners! :dizzy:

4 Likes

Turris Omnia - branch switched from HBT. After the reboot, there were no LAN ports visible, but access through Wi-Fi worked. Manual run of pkgupdate performed another upgrade of the system.

Queue upgrade of kernel/core/5.15.84-3-a959515bba2f3252aa25c92c34d26059[5.15.82-3-a959515bba2f3252aa25c92c34d26059]
...

The second reboot took longer, Wi-Fi was connected but it took a long time to receive a DHCP response.

Updated reForis OpenVPN module is great!

Glad to hear you’ve managed to fix the long boot. What was the culprit?

You were incredibly lucky since you encountered this issue because it was there for almost an hour. During that window, you shouldn’t reboot your router until there is a new build with a newer kernel version, and once you installed it, it should be alright.

I was removing hacks, which ensured that Marvell switches on Turris Omnia and Turris MOX were working as there was some issue in Linux kernel 5.15, that prevented to have working Marvell switches.

1 Like

MOX classic, HBK branch, .5 GB, 2x WiFi, simple config, all seems OK. (*)(%)(+)
(*) for my simple case is rainbow working
(%) except SDIO WiFi.
(+) USB 3 flash not recognized - it seems nobody noticed thread Turris Mox USB (from module A) not working any more (for mass storage) after TOS 6.0 upgrade :-((

Note: syslog & kernel log are full of error messages regarding not functioning SDIO WiFi card, e.g.
kernel log
[54503.809384] mwifiex_sdio mmc1:0001:1: Failed to start AP
[54509.819633] mwifiex_sdio mmc1:0001:1: CMD_RESP: cmd 0xb1 error, result=0x1
[54509.826778] mwifiex_sdio mmc1:0001:1: Failed to start the BSS
syslog
Dec 20 07:00:03 MOXjp kernel: [42756.615445] mwifiex_sdio mmc1:0001:1: CMD_RESP: cmd 0xb1 error, result=0x1
Dec 20 07:00:03 MOXjp kernel: [42756.622624] mwifiex_sdio mmc1:0001:1: Failed to start the BSS
Dec 20 07:00:03 MOXjp kernel: [42756.628576] mwifiex_sdio mmc1:0001:1: Failed to start AP

Moreover, there are a lot of errors (is full of them) like following one in syslog, even though guest network is nowhere enabled
Dec 19 23:12:04 MOXjp odhcpd[1900]: Failed to send to ff02::1%guest_turris@br-guest_turris (Address not available)

One note more: AFAIK nobody commented one new LuCI feature - WiFi channel analysis… it’s very nice & helpfull feature.

I upgraded my turris 1.0 today at 9:20 and encountered similar problem. Short-term fix was to unplug/plug the cable from turris, but after some time it broke again. At the same time I had problems running schnaps (list, rollback hanging in D-state), but after reboot I was able to roll-back to 6.0.4

That’s the different one.We will need to take a look at it. Could you send us diagnostics, please?