[Resolved] MWIFIEX bugs on EspressoBin-ULTRA

MWIFIEX bugs on EspressoBin Board MVEBU in OpenWrt 21.02 RC2 and RC3 !
Any advice will be welcome...

Yep, legacy rates need to be enabled.
That was the default in 19.07 but not anymore as unless you really need that you dont want to enable them.

Not sufficient !

This only help to make the Access Point visible and available...

But clients may still have issues, like Apples clients (iOS iPAD and iPhone) which get no access to the AP...
With WPA or WPA2 I get errors and without encryption I get no IP...

This is also removed by any LUCI modification of the WiFi in the 21.02...

I test it now also by removing wpad and replacing it by hostapd-openssl

uci set wireless.radio0.legacy_rates='1'
uci commit

iw wlan0 set power_save off

added in /etc/rc.local

now I have 4 clients on it...
BUT only without encryption...
If I enable WPA2 I get now only one client again, the others get faulty with dmesg error logged :

[   63.388904] mwifiex_pcie 0000:01:00.0: CMD_RESP: cmd 0x5e error, result=0x1
[   63.396413] mwifiex_pcie 0000:01:00.0: crypto keys added
[   64.764481] mwifiex_pcie 0000:01:00.0: CMD_RESP: cmd 0x5e error, result=0x1
[   64.771723] mwifiex_pcie 0000:01:00.0: crypto keys added
[   66.169967] mwifiex_pcie 0000:01:00.0: CMD_RESP: cmd 0x5e error, result=0x1
[   66.177264] mwifiex_pcie 0000:01:00.0: crypto keys added
[   70.810310] mwifiex_pcie 0000:01:00.0: CMD_RESP: cmd 0x5e error, result=0x1
[   70.817755] mwifiex_pcie 0000:01:00.0: crypto keys added
[   75.478474] mwifiex_pcie 0000:01:00.0: CMD_RESP: cmd 0x5e error, result=0x1
[   75.485768] mwifiex_pcie 0000:01:00.0: crypto keys added

The option is back again... since the commit https://github.com/openwrt/luci/commit/119701cce302b6475e2fe900d2fff6c5dad16416
thanks @jow-
issue https://github.com/openwrt/luci/issues/5234 resolved !

For now I am using a later firmware than the NXP !

[   11.057868] mwifiex_pcie 0000:01:00.0: info: MWIFIEX VERSION: mwifiex 1.0 (16.68.1.p195) 
[   11.066409] mwifiex_pcie 0000:01:00.0: driver_version = mwifiex 1.0 (16.68.1.p195)

which looks like more stable on this...

partially fixed !
May need a NXP feedback on the firmware... but they not answered my mail ! nor GlobalScale (about this particularly issue)...

Still got issue while restarting network, which may hang WiFi and require a reboot !

I am now testing an older version of the firmware...

NXP give great feedback :

1/ NXP (who acquired Marvell Wi-Fi/BT chipsets) post official releases on codeaurora (driver part), and GitHub (firmware part):

Wifi driver CodeAurora: mwifiex​
https://source.codeaurora.org/external/nxpwifi/mwifiex Lastest offical release is 8649a841364622db5cc36c71563f96f070b44142 (master)
Wifi FW GitHub - NXP/imx-firmware
Latest offical release is 7d33d0fc437437457fb400d14ae44a02441f6167 (lf-5.10.y_2.0.0 branch)
2/ Open source community upstream some driver and firmware version to the Linux kernel
(unfortunately NXP does not upstream its official releases to the Linux kernel)

Wifi driver https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git drivers/net/wireless/marvell/mwifiex/
Wifi FW https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git mrvl

So I give a tests only on firmwares, and open an issue at NXP...

resolved by using the latest imx firmware, as said and proposed by NXP :

Regarding supported data rates, 88W8997 is supporting the following MCS:

  • 802.11ac: MCS 0~9
  • 802.11n: MCS 0~15 and MCS32
    It is expected that latest firmware from NXP official repo (https://github.com/NXP/imx-firmware) is the most stable one, as it includes NXP latest fixes.
    WlanCalData_ext_DB-W8997QFN-DB3A_V3.0_Rev-A.conf is not necessary for that FW.
    You just need to provide "cal_data_cfg=none" when insmod'ing the moal.ko driver.

@erdoukki Nice to see that the PCI model issues are resolved.
I am having issues with the USB model, after heavy load it will just stop responding and passing traffic and there is no updated FW available.
Do you mind if I piggyback of your issue ticket?

Do, if you think it can help... :+1:

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.