TurrisOS 3.10.6 in RC

release

#1

Dear Turris users,

we just released new version of Turris OS into RC. As usual, it contains just bunch of fixes and few updates that seems small and isolated. Full release notes are as follows:

  • kernel, tiff: security update
  • openssh, nextcloud, lighttpd, libpcap, openssl, ath10k-ct, minidlna, wireguard: updates
  • pakon: more robust recovery from broken database
  • storage: fix support for partitionless drives
  • procd: minor compatibility fixes
  • lxc: more prominent warning about container usage

As always, we welcome any feedback regarding regressions.


LXC: lxc-create fails due to missing SSL
#2

Mam několik LXC kontejnerů na 64GB SD kartě ze které mi bootuje celý Turris, když SD karta odejde vyhodím ji a koupím novou, bylo by možné tu hlášku zobrazovat opravdu pokud LXC běží z interní paměti routeru ?

Error notifications

You are running container debian from internal memory which is not recommended and can severally damage your router! This is not covered by warranty! Please use storage module in Foris to move it somewhere else!


#3

Dtto varování, pokud klekne fleška nasměrovaná pomocí “Storage”


#4

Everything works fine on my Turris 1.0 blue router


#5

Many thanks for the long awaited Wireguard package update.
I hope it can stay up to date in the future releases as well.

When did Omnia switch to ath10k-ct by default?
I don’t remember such change.

The reason im asking is because there are many stability issues with it in the past,
including some topics here on the forum, and the last time I tried it randomly crashed on
5GHz for me as well. Since using ath10k non-ct I had very stable both 2.4Ghz and 5GHz wireless.


#6

It did not switch, we just updated the package that was always available as an option and there are people using it because it works better for them.


#7

unbound 1.8 https://gitlab.labs.nic.cz/turris/turris-os-packages/issues/220 with plenty of bug fixes is not going to make it?


#8

Hello,

thank you for your suggestion. @miska looked what he can do with it and here it is:


#9

Few more changes, LXC notification should work as expected on old Turris, included ucollect workaround for some corner-cases and new kernel came out in the meantime :slight_smile:


#10

How can I do the ath10k replacement by the ath10k-ct?

I’m facing to the problem hidden somewhere in updater. I’m not able to persuade it to remove kmod-ath10k together with its firmware and install kmod-ath10k-ct with a corresponding FW.

See my user.lua file with pkgupdate output below.

Thanks.

root@turris:~# cat /etc/updater/conf.d/user.lua
Uninstall("ath10k-firmware-qca988x", "kmod-ath10k", { priority = 60 })
Install("ath10k-firmware-qca988x-ct-htt", "kmod-ath10k-ct", { priority = 70 })
root@turris:~# pkg
pkg_check  pkgupdate
root@turris:~# pkgupdate
WARN:Script file:///usr/share/updater/localrepo/localrepo.lua not found, but ignoring its absence as requested
WARN:Requested package luci-i18n-ddns-en that is missing, ignoring as requested.
WARN:Request not satisfied to uninstall package: ath10k-firmware-qca988x
WARN:Request not satisfied to uninstall package: kmod-ath10k
INFO:Queue install of kmod-ath10k-ct/turris/4.4.150+2017-05-16-1-0a333a8e606ab056173befac424900d2-1
INFO:Queue install of ath10k-firmware-qca988x-ct-htt/turris/2018-05-12-952afa4949cb34193040cd4e7441e1aee50ac731-1
Press return to continue, CTRL+C to abort

INFO:Executing preupdate hooks...
INFO:Subprogram output: /etc/updater/hook_preupdate/05_schnapps.sh:
Snapshot number 105 created

INFO:End of subprogram output
INFO:Unpacking download packages
INFO:Checking for file collisions between packages
line not found
line not found
line not found
line not found
line not found
line not found
DIE:
[string "transaction"]:317: [string "transaction"]:146: Collisions:
• /lib/modules/4.4.150-0a333a8e606ab056173befac424900d2-1/ath10k_core.ko: kmod-ath10k (existing-file), kmod-ath10k-ct (new-file)
• /lib/modules/4.4.150-0a333a8e606ab056173befac424900d2-1/ath10k_pci.ko: kmod-ath10k (existing-file), kmod-ath10k-ct (new-file)
Aborted

#11

@vookimedlo1

There should be a very “good” reason for you to try ath10k-ct.
At first I thought it would be a better implementation of the closed source ath10k as well,
since Candella got NDA for the source from Qualcomm and were intended to improve it,
especially I liked the promising factor that you can apparently report bugs and have a
discussion with a real person, rather than mailing your issues to a huge chip manufacturer
that gives little to zero priority to any open source non-hardware issues.

Turns out the bugs and crashes were even more significant, and you can as well see it on this
forum where various people had multiple issues with ath10k-ct.

I’d keep stock unless somehow you managed to already get better and stable performance with ct.


#12

And there is also this :wink:
https://git.openwrt.org/?p=openwrt/staging/blogic.git;a=commit;h=f9ccc8f64670e3e15b160cffb19f1ef1a8519e97


#13

I think it should be sufficient to go without your user.lua and just call

opkg remove kmod-ath10k
opkg remove ath10k-firmware-qca988x
opkg install kmod-ath10k-ct
opkg install ath10k-firmware-qca988x-ct

kmod-ath10k-ct provides kmod-ath10k, so everythinng should be satisfied…


#14

@turrisuser
My motivation was caused by the buggy ath10k module, which crashes under the heavy wifi load. You made me nervous about the “ct” module stability and also Miska’s information about deprecating the original ath10k. I’m trapped somehow, because I need to restart my router every week.

@miska
Thanks for the help. But it seems that “ct” module is not compatible with the omnia kernel.

root@turris:~# dmesg
[   20.408910] ath10k_core: Unknown symbol ath10k_thermal_event_temperature (err 0)
[   20.467331] ath10k_core: Unknown symbol ath10k_thermal_unregister (err 0)
[   20.474320] ath10k_core: Unknown symbol ath10k_thermal_register (err 0)
[   20.481013] ath10k_core: Unknown symbol ath10k_thermal_set_throttling (err 0)
[   20.488206] ath10k_core: Unknown symbol ath10k_thermal_event_temperature (err 0)
[   20.551560] ath10k_core: Unknown symbol ath10k_thermal_unregister (err 0)
[   20.558529] ath10k_core: Unknown symbol ath10k_thermal_register (err 0)
[   20.565225] ath10k_core: Unknown symbol ath10k_thermal_set_throttling (err 0)
[   20.572430] ath10k_core: Unknown symbol ath10k_thermal_event_temperature (err 0)
[   20.627294] ath10k_core: Unknown symbol ath10k_thermal_unregister (err 0)
[   20.634282] ath10k_core: Unknown symbol ath10k_thermal_register (err 0)
[   20.640959] ath10k_core: Unknown symbol ath10k_thermal_set_throttling (err 0)
[   20.648166] ath10k_core: Unknown symbol ath10k_thermal_event_temperature (err 0)
[   20.709579] ath10k_core: Unknown symbol ath10k_thermal_unregister (err 0)
[   20.716582] ath10k_core: Unknown symbol ath10k_thermal_register (err 0)
[   20.723276] ath10k_core: Unknown symbol ath10k_thermal_set_throttling (err 0)
[   20.730468] ath10k_core: Unknown symbol ath10k_thermal_event_temperature (err 0)
[   20.787393] ath10k_core: Unknown symbol ath10k_thermal_unregister (err 0)
[   20.794383] ath10k_core: Unknown symbol ath10k_thermal_register (err 0)
[   20.801077] ath10k_core: Unknown symbol ath10k_thermal_set_throttling (err 0)
[   20.808269] ath10k_core: Unknown symbol ath10k_thermal_event_temperature (err 0)
[   20.853936] fuse init (API version 7.23)
[   20.874235] ath10k_core: Unknown symbol ath10k_thermal_unregister (err 0)
[   20.881230] ath10k_core: Unknown symbol ath10k_thermal_register (err 0)
[   20.887910] ath10k_core: Unknown symbol ath10k_thermal_set_throttling (err 0)
[   20.895119] ath10k_core: Unknown symbol ath10k_thermal_event_temperature (err 0)
[   20.959514] ath10k_core: Unknown symbol ath10k_thermal_unregister (err 0)
[   20.966513] ath10k_core: Unknown symbol ath10k_thermal_register (err 0)
[   20.973208] ath10k_core: Unknown symbol ath10k_thermal_set_throttling (err 0)
[   20.980401] ath10k_core: Unknown symbol ath10k_thermal_event_temperature (err 0)
[   21.028721] usbcore: registered new interface driver cdc_wdm
[   21.037131] Ebtables v2.0 registered

#15

@miska wrote:
“There is one know issue - ath10k-ct driver is not working, missing one more fix. We know about that and we will address it in next release but as it wasn’t working till now and therefor most likely everybody is using the official one, we decided to release nevertheless.”

it’s possible provide us missing fix?


#16

If I am not mistaken it should be fixed in nightly branch and it will be part of Turris OS 3.10.7.

Closing as 3.10.6 was released for everybody yesterday.