I know that schnapps update-factory is working, I used it on both Omnia and MOX as well, before, to keep it up to date, sometimes. Here I wanted to check new reForis feature
To answer your question: by using schnapps update-factory in CLI, factory image was updated to latest version 6.5.0 on my MOX. Unfortunately, during update there was so much info displayed, which my SSH client was not able to keep and copy
Last lines were:
./etc/updater/hook_reboot_required/
./etc/updater/hook_reboot_required/50-create-notification.sh
Delete subvolume (commit): â/mnt/.snapshots/@factory-oldâ
Your factory image was updated!
Most indy models had rc-9 dated 2015 or something?. So according to whatâs published here (depending on your config ) the risk should be low?
Mine had the original first U-boot, and here it worked using the how to written by Mionica?
I would like to say exact day and time, but unfortunately I am not sitting in HQ of Turris and working partly and remotely for Turris team and this reported issue needs more cooperation with kernel guys⊠etc. You can ask @miska regarding this.
Yes apparently not, but solution how to make the router work again you can find in this forum (and yes it is not easy and for everyone) and firmware update is marked as experimental and that means, it can break your router and it is suggested to advanced users, thatâs why it is labeled experimental. If you want to be sure, that will not break your router just wait until experimental label will be removed.
Another one here with broken site to site VPN, I have OpenVPN between Turris Omnia and Mikrotik. Had to rollback because forwarding between sites does not work anymore
Update after a few days of helpless attempts to find the root of this problem:
The problem HAS NOT disapeared. Since the upgrade described in the previous post my Turris 1.0 stays in a strange state where the problem with LANs randomly appears and after some time (in hours) disappears, regardless of any manual intervention (reboots etc.). The outage typically takes ~10 hours, the longest interval in working state was about 1,5 day.
Any ideay where to look?
@tuomaz - similar to mine? Any ideas? Iâm really getting crazy. I occurs completelly randomly and the same way after a few hours randomly disappears. Not a single message in logâŠ
Yes. Installed 6.5.0, upgraded firmware. Everything went smoothly and seemed to work fine. After a couple of hours I got a random reboot, and after that is has just increased and now Iâm getting 10-20 reboots per day. Once in a while it crashes and get stuck (no reboot), and becomes unavailable.
Iâve tried to factory reset, same issue again. Iâve removed all wifi cards, same issue. Next step is to remove my mSATA disk and try with no additional software.
Iâve tried to debug through serial console, but not getting good data, will try with another serial cable. I can see traces of a stacktrace though.
So, once more - which problems exactly ???
I donât know if you are kidding me, or what âŠ
You wrote âKernel 5.15 still not ready for Turris 1.x.â so I asked you âWhat exactly is not ready ?â
My Turris 1.0 has been runnig for 2 days without any problem on the kernel 5.15 ⊠so I asked to know what exact problems I should expect ⊠You write like an âexpertâ on Turris OS, but on a clear question you arenât able write exact answerâŠ
What about UBOOT & FW update on the original 1.x Turris?
The one that doesnât have support BTRFS in NAND and has to boot off a BTRFS ”SD card? I have long since migrated to BTRFS ”SD boot, will it know and boot off the card, or fail?
Will they work there, or fail to boot like in @tomskra 's post above, due to âsomething something btrfs not foundâ?
You might have tagged the UBOOT & FW as âexperimentalâ, but without providing any details what devices might it even experimentally work on. Would be much appreciated.
Iâd rather not brick my Turris 1.x, especially as reâflashing it via serial likely wonât help â whatâs the last available factory image anyway? As older factory images like TOS 3.7 donât work on Cetinâs network and donât even support WPA for possibly sharing a hotspot from my phone, making the factory reset or reâflashed 1.x possibly totally unable to update itself to 3.11 or later, where one could start BTRFS migration again, and finally update to 6.5.
It was a bit of a Catchâ22, as the reset router doesnât connect to WAN, therefore cannot update to latest 3.xx, therefore cannot migrate to BTRFS boot therefore cannot update to 6.5.
Whatâs the last version of Turris 1.x TOS 3.xx factory image one can download? The version isnât noted there. I can reâflash it using serial if something goes wrong, but if thatâs still the unworkable 3.7, that wonât help. Last time I had to lug the whole device to a different ISP in a different location, so the old factory 3.7 could even connect and update itself.
Viktore, delas si z lidi rad srandu? Tvoje prispevky, obzvlaste tento, jsou uz za hranou. Eviddentne nemas Turris 1.x a presto se snazis schazovat lidi, kteri ho maji a po aktualizaci na novy kernel nemaji zadne problemy. To te evidentne seâŠe. Proc to?
Kdyz uz zminujes minulost, mel bys taky priznat, zer uz jednou jsi byl v tomto foru zabanovan. Procpak asi?
