one of my omnia update 30 min ago and other still dont get notification for update/restart just wait
@darei my last attempt it ran for 45 minutes and errored out. i rebooted it and had tons of error messages. rolled back again. i’ll wait for 3.6 i think.
wow 3.5 is not very good… web administration crashing sometimes… firewal logs dont send to CZnic… and 5ghz wifi is unstable time for rollback
Thanks for the tip man, when the email about the update arrived the internet (PPPoE) went down immediately and stayed that way even after the reboot. I had to roll back too.
Make sure you unplug your wan cable before you restart after the roll back, for me it updated to 3.5 already by the time I managed to disable the auto update. I had to roll back again 
.
i got sneaky, i threw exit 0 as the second line of /usr/bin/updater.sh
3.5 broke 5GHz on my TO. Disabling the interface, removing kmod-ath10k + firmware, rebooting, running updater and enabling interface brought it back to life. So far, so good. It was probably due to me messing around with the non-ct and ct kmod/firmware.
To all the people with problems, why don’t you try a medkit image aka a clean slate?
Also, really looking forward to the next release! The changelog in the test branch states we can expect this:
- cznic-cacert-bundle: Drop old ucollect certificate (server already switched)
- kernel: updated to the last available version
- lighttpd: updated and cleaned up, disabled mod_mysql_vhost
- foris-openvpn-plugin: new plugin which helps to perform a simple openvpn server setting on your router
- nuci: ca-gen plugin added - it is used to generate CA, dhparams and certificates (could be used by e.g. openvpn server/client)
- nuci: openvpn-client plugin added - it should be able to generate client config based on server configuration from uci
Keep up the good work @team NIC.CZ!
3 Likes
V 3.5 broke my Lte.
Installed ok with wifi (2.4 & 5) offline. After bringing wifi up (2.4 & 5), TO rebooted and Lte connection is lost.
I reverted back to the snap before the update but Lte does not connect.
Any help is appreciated.
**** Update: I had to switch off the router and plug it again for the Lte to connect again. I will see if this will happen again if I bringing the wifi up later today ********
root@Mik2:/# dmesg | grep -i error
[ 19.893288] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[ 19.922912] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[ 19.951812] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/fwcfg-pci-0000:02:00.0.txt failed with error -2
[ 19.981078] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-5.bin failed with error -2
[ 20.020557] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-4.bin failed with error -2
[ 20.060087] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-3.bin failed with error -2
[ 20.168145] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
root@Mik2:/# dmesg | grep -i Qualcom
[ 14.697296] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 29.942247] usbserial: USB Serial support registered for Qualcomm USB modem
[ 29.955817] qcserial 1-1:1.0: Qualcomm USB modem converter detected
[ 29.962231] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
[ 29.970325] qcserial 1-1:1.1: Qualcomm USB modem converter detected
[ 29.976798] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB1
[ 29.984345] qcserial 1-1:1.2: Qualcomm USB modem converter detected
[ 29.990767] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB2
[ 29.998195] qcserial 1-1:1.3: Qualcomm USB modem converter detected
[ 30.004647] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB3
root@Mik2:/# ls -l /dev/cdc-wdm0
crw-r--r-- 1 root root 180, 176 Jan 13 03:47 /dev/cdc-wdm0
root@Mik2:/# uqmi -d /dev/cdc-wdm0 --get-signal-info
{
"type": "hdr",
"rssi": -125,
"ecio": 5,
"io": -106,
"type": "lte",
"rssi": -55,
"rsrq": -10,
"rsrp": -83,
"snr": 84
}
root@Mik2:/# cat /sys/kernel/debug/usb/devices
..........
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=05c6 ProdID=9215 Rev= 2.32
S: Manufacturer=Quectel
S: Product=Quectel LTE Module
C:* #Ifs= 5 Cfg#= 1 Atr=a0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=qcserial
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=qcserial
E: Ad=83(I) Atr=03(Int.) MxPS= 10 Ivl=32ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=qcserial
E: Ad=85(I) Atr=03(Int.) MxPS= 10 Ivl=32ms
E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=qcserial
E: Ad=87(I) Atr=03(Int.) MxPS= 10 Ivl=32ms
E: Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
E: Ad=89(I) Atr=03(Int.) MxPS= 64 Ivl=32ms
E: Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
root@Mik2:/# cat /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd50:197b:87c3::/48'
config interface 'lan'
option force_link '1'
option type 'bridge'
option proto 'static'
option netmask '255.255.255.0'
option ipaddr '10.0.10.1'
option delegate '0'
option _orig_ifname 'eth0 eth2 wlan0 radio1.network1'
option _orig_bridge 'true'
option ifname 'eth0 eth2'
config interface 'wan'
option _orig_ifname 'eth1'
option _orig_bridge 'false'
option username '***********'
option password '*******'
option ipv6 'auto'
option metric '10'
option proto 'static'
option ipaddr '192.168.10.15'
option netmask '255.255.255.0'
option gateway '192.168.10.1'
option ifname 'eth1'
option dns '217.31.204.130 8.8.8.8'
config interface 'wan6'
option ifname '@wan'
option proto 'none'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 5'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '4 6'
config interface 'Lte'
option proto '3g'
option service 'umts'
option pincode '*****'
option ipv6 'auto'
option metric '20'
option apn 'gint'
option peerdns '0'
option dns '8.8.4.4 8.8.8.8'
option delegate '0'
option username 'root'
option password '*******'
option device '/dev/ttyUSB2'
config route
option target '192.168.10.0'
option netmask '255.255.255.0'
option metric '0'
option interface 'wan'
option gateway '192.168.10.1'All Omnia routers check for updates twice a day by default. You can enforce it by running updater.sh manually in shell.
Ok, I have it now, thanks.
This is an interaction between opkg and updater… and the updater does have a real resolver, but there are two things interacting here:
- If you install something by hand, it is marked as required locally. So updater tries to install it/keep it up to date.
- We still need to go through all the packages and mark the ones that block each other ‒ OpenWRT just doesn’t do that. It’s better now than with just opkg, which simply overwrote files of one package with files from another and didn’t care, but there’s still some place to improve.
This looks like broken /usr/lib/opkg/state. The way to „fix“ that is to open it and delete the last incomplete block. Then opkg and, in turn, updater, should start working again. However, back up your configuration first, just in case (you may have lost information about some installed packages and there’s a chance the default configuration from such a lost package could overwrite yours).
Forris option “System - NTP” after update
the change in setting up NTP servers - some strange ?
I think (info from forum admins) the whole section of the NTP in the future disappears and will be addressed in the background outside the LuCI
Update 3.5 has problems…
At first I’ve noticed that the updater installed some packages and than failed. I’ve logged in and restarted the device, than another packages and requests reboot.
The problem now is that the Omnia doesn’t react on any soft reboot command. I’ve tried from issue reboot from Forris - nothing, than from LuCI - Omnia ignored me and finally from ssh -nothing.
Simply after Update 3.5 SW reboot command doesn’t work.
Update:
Now Omnia sends me following emails:
Restart is needed
The OS kernel has been updated to version 4.4.39+3-1-80079e1c1e5f9ca7ad734044462a761a-3. Please reboot the device.
The device will be restarted automatically on Monday, January 16 at 03:30 AM.
Error notifications
Updater failed:
[string “backend”]:1330: [string “backend”]:1321: Failed to lock the lock file //var/lock/opkg.lock: Resource temporarily unavailable
News announcements
•ath10k: use standard ath10k WiFi drivers as default instead of Candela Technologies drivers
• mac80211, hostapd: fixes and updates of drivers, enabled FST (Fast Session Transfer)
• lighttpd: does not block boot when kernel reports low entropy
• openssh: updated to version 7.4p1
• knot-resolver: support forwarding to multiple upstream DNS servers
• foris: returned data sending status to About page, better tolerance for NETCONF server crashes
• nuci: fixed configuration restore and errors that could lead to ocassional crashes
• opkg: fixed crashes during package installation
• ebtables: fixed application crashes
• fstrim: new package
It seems 3.5 has a lot of really serious problems. Is there a way to delay the upgrade or will it be done automatically?
Hi,
the error you sent means that updater is already running. Solution? Just wait
Hi,
could you describe those really serious problems you are talking about? There is no need to worry, 3.5 is running smoothly.
Now I have another message from Turris:
Updater failed:
[string “transaction”]:344: Unfinished journal exists
and still is not possible to reboot Turris by SW command from Forris, LuCi and using “reboot” from command line. Works only hard restart “reboot -f”
What happens when you do reboot? Does the command finish successfully? Or does it write something?
As with the unfinished journal… every time the updater does something potentially dangerous, it keeps track of it in a journal. When the router boots, the journal is checked and the operation is finished. You can’t start a new „dangerous“ operation if there’s a journal of unfinished one.
So, I have two theories. One is, you might be really impatient. You boot the router, it starts replaying the journal and performing the needed operations (some of them once more, because it doesn’t record everything immediatelly ‒ like possibly generating the „please reboot“ message). As the replay of the journal is part of the boot process, you can’t reboot or shut down before it finishes booting. If you just wait long enough, the reboot would start working and it would reboot cleanly next time (likely the reboot is no longer actually necessary, it just generates the message just to be sure to do all the necessary steps and doesn’t remember it already done so).
The other option is there’s a problem with replaying the journal (after all, it’s hard to test interrupting the update in all possible moments reliably, so there might be a bug). So, if you think you waited long enough (unless there’s some problem with your router, you can give it an hour or more, just to be sure), try running opkg-trans -j and see if it produces any error (other than there’s no journal to replay).
The history is following
Yesterday I had obtained from Omnia email
Error notifications
Updater failed: Unknown error
Today I had logged to Foris and there was request for reboot. So I made restart and obtained following email
Restart is needed
The OS kernel has been updated to version 4.4.39+3-1-80079e1c1e5f9ca7ad734044462a761a-3. Please reboot the >device.
The device will be restarted automatically on Monday, January 16 at 03:30 AM.
Error notifications
Updater failed:
[string “backend”]:1330: [string “backend”]:1321: Failed to lock the lock file //var/lock/opkg.lock: Resource temporarily unavailable
News announcements
•ath10k: use standard ath10k WiFi drivers as default instead of Candela Technologies drivers
• mac80211, hostapd: fixes and updates of drivers, enabled FST (Fast Session Transfer)
• lighttpd: does not block boot when kernel reports low entropy
• openssh: updated to version 7.4p1
• knot-resolver: support forwarding to multiple upstream DNS servers
• foris: returned data sending status to About page, better tolerance for NETCONF server crashes
• nuci: fixed configuration restore and errors that could lead to ocassional crashes
• opkg: fixed crashes during package installation
• ebtables: fixed application crashes
• fstrim: new package
Since then SW reboot doesn’t work.
I was able to correct
Failed to lock the lock file //var/lock/opkg.lock: Resource temporarily unavailable
by opkg.lock file delete.
But all other problems remain: reboot doesn’t work and “Unfinished journal exists”