Turris OS 5.3.4 is released!

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

Yeah, “great”. One location of ours got offline because of that. I need to take a plane to reboot router now. We’re getting rid of turris omnias because of latest upgrade issues, where locations are randomly cut off from internet. That’s not what we expect from professional network devices.

1 Like

That’s your decision, and it is up to you. I see that you posted a similar comment one month ago. It is possible that you might edit a file, which you should not have. Also, it is good to mention that you are using Bird, which is not included in our default configuration.

As I don’t know the exact configuration of your router, it is hard to do some troubleshooting or help you.

Turris Omnia does not suffer from a reboot issue described here. Did you check the tools which are available on the router to see what is going to be overwritten by the upcoming router? Did you reboot your router after the major update (migration process) and once you configured it as you would like?

As you can see, there were no breaking changes in this update based on the changelog and you can list all the changes and do the diffs in repositories which have been changed.

Since you posted it here, I’d expect that you want to get some help. Please, visit our documentation.

//Edit: What I am thinking is that if you are using Bird. Isn’t possible that you are using something different for DNS/DHCP as well?

1 Like

@Pepe maybe one nice feature for these far-away setups would be another update mode - delayed with confirmation of success. So you’d basically install a cron job to revert the update before executing it, and the user would need to manually connect to the router and click a button in Reforis to confirm the update went well. If not, the router would automatically revert the update and reboot after some time. Of course, that’s not the best idea with MOX, but on Omnia, it could be pretty useful (I’m myself doing something similar manually).

3 Likes

And nobody other can use two led restart? And what recovery USB with older configured TOS? What about remote access?

The problems I describe are related to the original MOX A module, certainly not Omnia.

1 Like

Hi Pepe,

I have posted it here not to ask for help, but just to give you feedback, so maybe you can consider better testing of new releases. Indeed, we had problem in december with one router, and after this release - with a second router.

We’re using bird, but it’s not a critical component - ie. it should not prevent router from restarting and getting a public IP address. It is used to advertise private networks for ipsec tunnels (we use ipsec w/ VTI, to connect between locations and public cloud providers like AWS). For DHCP/DNS, there weren’t any significant changes, everything was configured using luci.

Regarding bird being “not included in default configuration” - I’ve seen BGP advertised in official product data sheet and this was a key decision point when we considered platform to buy, so (only in my humble opinion) it should not be treated as “non-default”.

Router has been rebooted last time a few weeks ago (beginning of December, if I recall properly) and it came up succesfully.

Best!

1 Like

Sorry, but I don’t take a feedback as “we get rid of routers, because they suck”. If you would like to help or give us feedback, then there is a better way of doing it. :wink:

I am thinking loud wasn’t Turris OS 5.3.4 in the Testing branch for almost 2 weeks?

In LuCI, you can configure anything what you want since you have a root access even not valid configurations.

What are the symptoms you are observing exactly with the omnia, if I might ask?

2 Likes

Could you anwer to my questions above @pwgen?

That would also interest me.

1 Like