and why this problem does not occur when I do the test on the wire?
root@OpenWrt:~# iw phy0 info
Wiphy phy0
wiphy index: 0
max # scan SSIDs: 4
max scan IEs length: 2247 bytes
max # sched scan SSIDs: 0
max # match sets: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Device supports T-DLS.
Available Antennas: TX 0x4 RX 0x4
Supported interface modes:
* managed
* AP
* AP/VLAN
* monitor
* mesh point
Band 2:
Capabilities: 0x106f
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT Max RX data rate: 450 Mbps
HT TX/RX MCS rate indexes supported: 0-23, 32
VHT Capabilities (0x33837930):
Max MPDU length: 3895
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
SU Beamformer
SU Beamformee
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 1170 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 1170 Mbps
VHT extended NSS: not supported
Frequencies:
* 5180 MHz [36] (23.0 dBm)
* 5200 MHz [40] (23.0 dBm)
* 5220 MHz [44] (23.0 dBm)
* 5240 MHz [48] (23.0 dBm)
* 5260 MHz [52] (20.0 dBm) (radar detection)
* 5280 MHz [56] (20.0 dBm) (radar detection)
* 5300 MHz [60] (20.0 dBm) (radar detection)
* 5320 MHz [64] (20.0 dBm) (radar detection)
* 5500 MHz [100] (26.0 dBm) (radar detection)
* 5520 MHz [104] (26.0 dBm) (radar detection)
* 5540 MHz [108] (26.0 dBm) (radar detection)
* 5560 MHz [112] (26.0 dBm) (radar detection)
* 5580 MHz [116] (26.0 dBm) (radar detection)
* 5600 MHz [120] (26.0 dBm) (radar detection)
* 5620 MHz [124] (26.0 dBm) (radar detection)
* 5640 MHz [128] (26.0 dBm) (radar detection)
* 5660 MHz [132] (26.0 dBm) (radar detection)
* 5680 MHz [136] (26.0 dBm) (radar detection)
* 5700 MHz [140] (26.0 dBm) (radar detection)
* 5720 MHz [144] (13.0 dBm) (radar detection)
* 5745 MHz [149] (13.0 dBm)
* 5765 MHz [153] (13.0 dBm)
* 5785 MHz [157] (13.0 dBm)
* 5805 MHz [161] (13.0 dBm)
valid interface combinations:
* #{ AP } <= 16, #{ mesh point } <= 1, #{ managed } <= 1,
total <= 16, #channels <= 1, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Supported extended features:
* [ RRM ]: RRM
* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
* [ SCAN_RANDOM_SN ]: use random sequence numbers in scans
* [ SCAN_MIN_PREQ_CONTENT ]: use probe request with only rate IEs in scans
* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
root@OpenWrt:~#
thanks, this driver still have problem with DFS
also regdomain is not good at all
WiFi and Ethernet are 2 different technologies, and Ethernet has full duplex (no CSMA/CD).
Wifi is based on CSMA/SA.
It also depends on the quality of your card.
Even your test, which doesn't really, I don't reproduce, certainly, I have high ping, but no ping drop.
I haven't incorporated any changes to the txpower in order to preserve your hardware.
@jbsky so do you have a solution for wpa3? if so i have a solution for DFS, we can make this better, give me two tree days, i need take out of the box the wrt 3200,it is sleeping for one year now.
1 Like
@jbsky Unfortunately, my luck with the next-8864 driver on my WRT3200 was unsuccessful.
Installation was successful. The problem was that the driver would never come up on boot.
Regarding /etc/modules.d/50-mwlwifi:
I tried booting with the default line mwlwifi and the testing line mwlwifi options: feature=0x30 and both methods failed to load the driver when rebooting the driver.
I did notice some mwlwifi errors in the system log:
Mon Sep 18 22:04:38 2023 kern.info kernel: [ 12.293590] ieee80211 phy0: device node: pcie@1,0
Mon Sep 18 22:04:38 2023 kern.err kernel: [ 12.298330] ieee80211 phy0: driver data is not enough: 17 (16)
Mon Sep 18 22:04:38 2023 kern.err kernel: [ 12.304195] ieee80211 phy0: mwlwifi: fail to initialize TX
Mon Sep 18 22:04:38 2023 kern.err kernel: [ 12.309705] ieee80211 phy0: mwlwifi: init fail
Mon Sep 18 22:04:38 2023 kern.err kernel: [ 12.314169] ieee80211 phy0: fail to initialize host interface
Mon Sep 18 22:04:38 2023 kern.err kernel: [ 12.319939] ieee80211 phy0: init fail
Mon Sep 18 22:04:38 2023 kern.err kernel: [ 12.323617] ieee80211 phy0: fail to initialize wireless lan
Mon Sep 18 22:04:38 2023 kern.warn kernel: [ 12.329228] mwlwifi: probe of 0000:01:00.0 failed with error -5
Mon Sep 18 22:04:38 2023 kern.info kernel: [ 12.335274] pci 0000:00:02.0: enabling device (0140 -> 0142)
Mon Sep 18 22:04:38 2023 kern.info kernel: [ 12.341019] rate_adapt_mode: 0, dwds_stamode: 1, optimization_level: 1, dump_hostcmd: 0, feature: 0
Mon Sep 18 22:04:38 2023 kern.debug kernel: [ 12.350150] ieee80211 phy1: priv->pcmd_buf = 8a9d6418 priv->pphys_cmd_buf = 7e39f08b
Mon Sep 18 22:04:38 2023 kern.debug kernel: [ 12.356691] ieee80211 phy1: fw download start
Mon Sep 18 22:04:38 2023 kern.debug kernel: [ 12.356699] ieee80211 phy1: ddr init: download start
Mon Sep 18 22:04:38 2023 kern.debug kernel: [ 12.357081] ieee80211 phy1: ddr init: download complete
Mon Sep 18 22:04:38 2023 kern.debug kernel: [ 12.498101] ieee80211 phy1: FwSize = 451040 downloaded Size = 451040 curr_iteration 65526
Mon Sep 18 22:04:38 2023 kern.debug kernel: [ 13.693559] ieee80211 phy1: fw download complete
Mon Sep 18 22:04:38 2023 kern.info kernel: [ 13.693594] ieee80211 phy1: device node: pcie@2,0
Mon Sep 18 22:04:38 2023 kern.err kernel: [ 13.698331] ieee80211 phy1: driver data is not enough: 17 (16)
Mon Sep 18 22:04:38 2023 kern.err kernel: [ 13.704194] ieee80211 phy1: mwlwifi: fail to initialize TX
Mon Sep 18 22:04:38 2023 kern.err kernel: [ 13.709702] ieee80211 phy1: mwlwifi: init fail
Mon Sep 18 22:04:38 2023 kern.err kernel: [ 13.714167] ieee80211 phy1: fail to initialize host interface
Mon Sep 18 22:04:38 2023 kern.err kernel: [ 13.719937] ieee80211 phy1: init fail
Mon Sep 18 22:04:38 2023 kern.err kernel: [ 13.723615] ieee80211 phy1: fail to initialize wireless lan
Mon Sep 18 22:04:38 2023 kern.warn kernel: [ 13.729226] mwlwifi: probe of 0000:02:00.0 failed with error -5
I don't know if any of that information is helpful or not. But I have reverted to the previous driver for now. Please let me know if there is anything else to test.
1 Like
I tried both packages under this link, with my WRT3200ACM (23.05-RC3), both are failed to install with "Malformed package" error
Collected errors:
* pkg_init_from_file: Malformed package file kmod-mwlwifi_5.15.127%2B2023-09-18-5bbb5be-1_arm_cortex-a9_vfpv3-d16.ipk.
@WildByDesign
Thanks for the test, and I can see what's missing. If you don't mind, I'll give it another try.
https://github.com/jbsky/mwlwifi/raw/testing/next-8864/ipk/kmod-mwlwifi_5.15.127%2B2023-09-18-324076b-1_arm_cortex-a9_vfpv3-d16.ipk
@all
For those who have installation problems, please follow these commands
wget https://github.com/jbsky/mwlwifi/raw/testing/next-8864/ipk/kmod-mwlwifi_5.15.127%2B2023-09-18-324076b-1_arm_cortex-a9_vfpv3-d16.ipk
opkg install kmod-mwlwifi_5.15.127+2023-09-18-324076b-1_arm_cortex-a9_vfpv3-d16.ipk --force-downgrade
And don't forget to add the for option when loading the module to test WPA3.
Thank you in advance,
Jbsk
2 Likes
You're welcome. No problem, I am willing to try as many times as possible.
Thank you for the quick fix. I will try closer to the end of the day when I generally do and I will have some details for you by tomorrow morning.
1 Like
@jbsky This most recent driver today is causing more significant problems for WRT3200/32X and I think that the download should be pulled for now.
It is causing boot loops and it won’t even fully boot into OpenWrt operating system. I am still recovering a bit right now and reverted to the other working partition on the WRT3200.
Due to the constant boot loops, I was unable to obtain any details about the cause of failure, unfortunately.
I will reinstall RC3 again later today to prepare for further testing if needed.
1 Like
Okay, it's off.
Well, it's going to be complicated for the wrt32X.
Thanks for your feedback.
No problem. I am always happy to help.
We may just have to wait until you get your hands on WRT3200/32X hardware.
Regardless, I am extremely thankful for your time and effort in this. It will definitely be worth it.
The only downside is that you can’t really merge these changes to main mwlwifi repo. You have a lot of great changes (amazing, actually) for 8864 users. But that would harm all of the 8964 users right now.
Could it be possible to split the driver and have a different driver for each chipset? Or would that be too much unnecessary effort?
Sorry for the inconvenience.
When you did the test, did you set the option?
1 Like
No need to apologize.
Yes, I did set the option. This time I never tried to boot without the option set. So I don’t know if the option triggered the OS boot loop or not.
Should I try again without the option? Or would you expect that to crash too?
Also, I wonder if I should try to boot without a pre-configured etc/config/wireless config. Although I don’t know if the previously working config would trigger crash or not. The crash seemed pretty early during init.
You guys need a test bed? I have four 3200ACM and another two WRT32X. I can set them up rather quickly.
3 Likes
Hi there @jbsky , just came across your thread from the (lengthy) Divested-WRT build post - it was suggested you can provide some hope for these abysmally-supported marvel wifi drivers.
bit about me, I have a WRT32x as my main router that i just deployed last week (it's been sitting in storage for well over a year and now i had new internet installed so figure it's time to put it to work).
I'm generally semi-new to OpenWRT (<3 month of looking/researching it) but not at all new to Linux - I also created a workflow and regularly rebuild my customized version of Divested-WRT using a containerized shell scripts I wrote (based on the official buildroot process but tweaked to work on Alpine) - so i can include the test wifi drivers in my next recompilation of the firmware (as for me that's preferable to an ipkg package, as i don't use opkg add (and any kernel mods fail anyway since i'm using the latest kernel not yet in an official openwrt release), i'd rather bundle all packages/configs in the firmware to have a designed-to-be-immutable image and just flash that)..
so basically, I'm happy to give testing your driver a go, but could use some pointers on how to plug it into the openwrt source tree (where) or even better, if there's a git-am compatible patch, i could throw that in before i get to any 'make' commands.
1 Like
that's a wicked set up.. curious how you use/deploy all those ??