Turris OS 5.3.4 is released!

Dear Turris users,

We released Turris OS 5.3.4 from the testing branch after 4 RC versions. It includes several improvements related to Turris MOX and its SFP module, Turris 1.x routers and schnapps, etc.

Release notes:

* Updated kernel to version 4.14.262
* Updated mac80211 to version 4.19.221
* Updated several packages such as zsh, domoticz
* Fixed RTC issue on Turris 1.x routers
* Fixed remote storages in schnapps
* Fixed initial SFP configuration for Turris MOX
* Security fixes
  * PostgreSQL
  * c-ares

This update will be downloaded and applied automatically. If not, I suggest you check reForis to approve the update.

If you found any regression, don’t hesitate to reach our technical support department.

We appreciate any feedback regarding this release.

8 Likes

Very interesting and valuable release. What is your experiences with MOX hangs after restart?

1 Like

List of known bugs:

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 the solution with the manufacturer of SoC (Marvell). In the meantime, you can try this workaround .
2 Likes

Next limitation is possibility to create only three (not four) SSID with SDIO wi-fi card in MOX A. Or has it already been fixed?

That’s fixed in HBL and HBD branches. It is going to be part of Turris OS 6.0. More details are in the commit message:

3 Likes

Thank you! It might be a good idea to update the documentation, even temporarily.

At the same time, I recommend mentioning SDIO limitations in hardware distribution, but I’ve said that before. After all, the card is not cheap and many people then would prefer mPCIe.

“Restartgate” is not solved for me. Workaround Marvel does not solve it for me.
Otherwise I have no problem.
MOX A+G+F+C and 5.3.4

3 Likes

The workaround did not solve the restart problem for me neither. (Mox Classic)

1 Like

TO2020, seems no issues but just noticed below error from kernel. Can’t remember if was there from previous reboots, device was up more than month already.

Jan 25 21:02:25 turris kernel: [   12.150069] pci 0000:00:02.0: enabling device (0140 -> 0142)
Jan 25 21:02:25 turris kernel: [   12.155802] ath10k_pci 0000:02:00.0: enabling device (0140 -> 0142)
Jan 25 21:02:25 turris kernel: [   12.162356] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Jan 25 21:02:25 turris kernel: [   12.395055] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
Jan 25 21:02:25 turris kernel: [   12.405806] ath10k_pci 0000:02:00.0: Falling back to user helper
Jan 25 21:02:25 turris kernel: [   12.678378] firmware ath10k!pre-cal-pci-0000:02:00.0.bin: firmware_loading_store: map pages failed
Jan 25 21:02:25 turris kernel: [   12.687539] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
Jan 25 21:02:25 turris kernel: [   12.697928] ath10k_pci 0000:02:00.0: Falling back to user helper
Jan 25 21:02:25 turris kernel: [   12.708591] firmware ath10k!cal-pci-0000:02:00.0.bin: firmware_loading_store: map pages failed
Jan 25 21:02:25 turris kernel: [   12.717391] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2
Jan 25 21:02:25 turris kernel: [   12.728146] ath10k_pci 0000:02:00.0: Falling back to user helper
Jan 25 21:02:25 turris kernel: [   12.738686] firmware ath10k!QCA988X!hw2.0!firmware-6.bin: firmware_loading_store: map pages failed
Jan 25 21:02:25 turris kernel: [   12.756006] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
Jan 25 21:02:25 turris kernel: [   12.765266] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
Jan 25 21:02:25 turris kernel: [   12.774798] ath10k_pci 0000:02:00.0: firmware ver 10.2.4-1.0-00047 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 35bd9258
Jan 25 21:02:25 turris kernel: [   12.819594] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
Jan 25 21:02:25 turris kernel: [   12.830061] ath10k_pci 0000:02:00.0: Falling back to user helper
Jan 25 21:02:25 turris kernel: [   12.840821] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
Jan 25 21:02:25 turris kernel: [   12.850854] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
Jan 25 21:02:25 turris kernel: [   13.989997] ath10k_pci 0000:02:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1

You should use search button here on forum to see if it was not reported already. You will see that it was, but it is harmless. :slight_smile:

1 Like

MOX classic 0.5 GB, 2x WiFi, HBS branch, Sentinel, Haas, simple config. Reboot problem persisting, HaaS not working. Other OK.
TO 2GB, 2x WiFi, HBK branch, Sentinel, HaaS, RIPE Atlas, simple config. HaaS not working. Other OK.

1 Like

2 posts were split to a new topic: Boot loop after reboot issue workaround

Despite update to 5.3.3 sounded like the reboot issue was about to be gone, the reboot after updating to 5.3.4 failed again for both PAB(WLE1216v5-20) and A(SDIO)B(WLE1216v5-20).

Yet the bigger issue is Wi-Fi SSIDs do not come up for both WLE1216v5-20-cards. Therefore I need to rollback and maybe have to do a troubleshooting sometime in the futures as I do not have the time right now.
Did anyone else install a WLE1216v5-20 in his/her MOX and SSIDs came up just as expected after this update?

1 Like

MOX still in pain. I do not consider this hardware to be stable for production environments.

1 Like

There is an example of the production use of Turris MOX router:
https://www.turris.com/en/news/news-list/kingdom-of-railways/

2 Likes

@Nones How do they handle the reboot-stall issue on that production setup?
Not manually I guess?

Perhaps a timer on a poe switch delivering power to all moxes?

Anyhow, is there any reports on reboot issues if you run a mox in netboot mode, booting from an omnia?

My guess is that a system like that ( mox ) is def not using autoupdate…

and Turris MOX with external antennas takes role of Wi-Fi access points

So it seems it was heavily tweaked and is not standard hardware…

And probably disabled updates and restarts via fuses.

I also once dreamed of the Omnia as the controller and connected MOXes as an AP. I even bought the appropriate hardware and I still have it. But it’s utopia.

Many years in touch with vendor of chipset, four versions of workaround and nothing. Try to deploy MOX with your customers and wait for calls.

1 Like