SDIO wifi stopped working after update to turris OS 6 on MOX

MOX hardware MOX HW problems
1

I have recently updated the MOX to:
|reForis version|1.3.1|
|Turris OS version|6.0.3|
Kernel version 5.15.78

And as a result my SDIO wifi card stopped working:
root@turris:~# dmesg | grep mwifiex
[ 11.617478] mwifiex_sdio mmc1:0001:1: WLAN is not the winner! Skip FW dnld
[ 12.097216] mwifiex_sdio mmc1:0001:1: WLAN FW is active
[ 12.168877] mwifiex_sdio mmc1:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (16.68.1.p197)
[ 12.177324] mwifiex_sdio mmc1:0001:1: driver_version = mwifiex 1.0 (16.68.1.p197)
[ 17.266062] mwifiex_sdio mmc1:0001:1: CMD_RESP: cmd 0x20 error, result=0x1
[ 28.612432] mwifiex_sdio mmc1:0001:1: CMD_RESP: cmd 0xb1 error, result=0x1
[ 28.619994] mwifiex_sdio mmc1:0001:1: Failed to start the BSS
[ 28.625947] mwifiex_sdio mmc1:0001:1: Failed to start AP
[ 33.242525] mwifiex_sdio mmc1:0001:1: CMD_RESP: cmd 0xb0 error, result=0x1
[ 33.249792] mwifiex_sdio mmc1:0001:1: Failed to set AP configuration
[ 33.256375] mwifiex_sdio mmc1:0001:1: Failed to start AP
[ 39.282638] mwifiex_sdio mmc1:0001:1: CMD_RESP: cmd 0xb0 error, result=0x1
[ 39.289923] mwifiex_sdio mmc1:0001:1: Failed to set AP configuration
[ 39.296503] mwifiex_sdio mmc1:0001:1: Failed to start AP
[ 45.312278] mwifiex_sdio mmc1:0001:1: CMD_RESP: cmd 0xb0 error, result=0x1
[ 45.319519] mwifiex_sdio mmc1:0001:1: Failed to set AP configuration
[ 45.326077] mwifiex_sdio mmc1:0001:1: Failed to start AP
…

Can you suggest what can be done to solve this?

2

Use the forum search function. There’s been a lot of discussion on this topic. TOS 6 is not yet supported on MOX with SDIO wifi.

3

I have searched the forums, I saw many issues related to the SDIO wifi in MOX, I am in the HBS branch currently so it should be supported.
I saw that the post that say that the dmesg are the issue (way before TOS 6) but I didn’t find a solution.
In the forums I didn’t see any claims that TOS 6 is not supported on MOX or that TOS 6 does not support SDIO, can you direct me for such issues?

4

I certainly remember this one: Turris OS 5.4.5 (MOX only)

5

And this Turris OS 6.0 is released - #2 by Pepe

6

Ok, so the issue is probably that I skipped 5.4.5 since I had it in manual update mode and wanted to update to TOS 6 in order to get support for AW7915-NP1.

7

Hey
Following the gitlab thread (MOX SDIO not working on TOS 6 (HBL) (#341) · Issues · Turris / Turris OS / Turris Build · GitLab) I’d suggest some users test to disable automatic channel selection, and set legacy_rates (if you’re on 2.4GHz) in /etc/config/wireless:

option legacy_rates '1'

If that works, we might get SDIO functionality back…?!

1 Like
8

I’ll be damned, it actually works!

It can also be set from LuCi:

image
image1054×362 43.9 KB

I’m getting 144Mbps rates and around 30Mbps actual performance… Not bad, certainly enough for IoT stuff…

Edit: LuCi also does not report the rates of connected clients properly, it shows all zeroes:

image
image1211×364 39.6 KB

1 Like
9

Its not working for me :frowning:

Screenshot from 2022-12-16 19-14-16
Screenshot from 2022-12-16 19-14-16850×410 65.9 KB

same errors in System and Kernel Log

[46471.153209] mwifiex_sdio mmc1:0001:1: CMD_RESP: cmd 0xb0 error, result=0x1
[46471.160378] mwifiex_sdio mmc1:0001:1: Failed to set AP configuration
[46471.166934] mwifiex_sdio mmc1:0001:1: Failed to start AP

10

Try with just wpa2-psk (not wpa3)

1 Like
11

changing the encryption does not change the behaviour, still the same doesnt matter what i change it to

12

Here’s my config:

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'platform/soc/soc:internal-regs@d0000000/d00d0000.sdhci/mmc_host/mmc1/mmc1:0001/mmc1:0001:1'
	option country 'CZ'
	option band '2g'
	option cell_density '0'
	option disabled '0'
	option legacy_rates '1'
	option htmode 'HT20'
	option txpower '11'

config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option encryption 'psk2+ccmp'
	option wpa_group_rekey '86400'
	option key 'password'
	option disabled '0'
	option ssid 'ssid'
6 Likes
13

thanks for your config, it works now! :+1:

2 Likes
14

Wow, awesome!

Side note: You can safely ignore the txpower config, it worked also with the default value there. I am using lower power, since mox is only covering one room…

1 Like
15

Doesnt work for me. The config is

config wifi-device 'radio1'
	option type 'mac80211'
	option macaddr 'MA:CC:AD:DD:RE:SS'
	option disabled '0'
	option hwmode '11g'
	option country 'CZ'
	option cell_density '0'
	option legacy_rates '1'
	option channel '4'


config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option disabled '0'
	option ssid 'SSID'
	option wpa_group_rekey '86400'
	option key '12345678'
	option encryption 'psk2+ccmp'
16

Oh your code block looks weird, i think its only one section, but then i see horizontal scrollbar. Ill give another try :slight_smile:

1 Like
17

my bad, formatting fixed :wink:
looks like the following is missing from your config

option path 'platform/soc/soc:internal-regs@d0000000/d00d0000.sdhci/mmc_host/mmc1/mmc1:0001/mmc1:0001:1'
1 Like
18

As apache2 server said … It works !

1 Like
19

@pschonmann Mark that as solution

20

Thanks for the tip with path, it works! In more detail:

  • 5 GHz only needs to add path.

  • 2.4 GHz needs to add path and legacy_rates. It does not need to set channel manually.

In both cases, you might need to reboot before the wifi starts working. On 5 GHz, give the AP a bit more time - if a DFS channel is chosen, the router has to wait about a minute before advertising the SSID.

Having legacy_rates set to 1 is not ideal, as it slows down the whole network including non-legacy devices (it basically says to use the slowest possible rates for collision avoidance messaging, so that the slow legacy devices can easily understand what’s going on in the air).

3 Likes