Re: iwlwifi 11n/11ac testing - and update
- Reply: Bjoern A. Zeeb: "Re: iwlwifi 11n/11ac testing - and update"
- In reply to: Bjoern A. Zeeb: "Re: iwlwifi 11n/11ac testing - and update"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 09 Apr 2025 03:25:24 UTC
Hey Bjoern, I'll need to get back to you with the results. But yea that was a typo, the sysctl values should be fully inverted for all 3. Jonathan Vasquez PGP: 34DA 858C 1447 509E C77A D49F FB85 90B7 C4CA 5279 Sent with ProtonMail Secure Email On Tuesday, April 8th, 2025 at 20:49, Bjoern A. Zeeb <bz@FreeBSD.org> wrote: > On Wed, 9 Apr 2025, Jonathan Vasquez wrote: > > > Hey Bjoern, > > > > I tested it but the AX210 wasn't able to connect to either of my networks (2.4 ghz / 5 ghz). I was able to successfully transition to fwget based firmware, and I did see that the sysctl transitioned automatically before/after reboot post fwget install. > > > > Before: > > > > compat.linuxkpi.80211.hw_crypto: 0 > > compat.linuxkpi.iwlwifi_11n_disable: 1 > > compat.linuxkpi.iwlwifi_disable_11ac: 1 > > > > After: > > > > compat.linuxkpi.80211.hw_crypto: 0 > > compat.linuxkpi.iwlwifi_11n_disable: 1 > > compat.linuxkpi.iwlwifi_disable_11ac: 1 > > > I assume that's a mis-paste as they should be ^ 1. > > > You can take a look at a few dmesg / ifconfig wlan0 here: > > https://xyinn.org/freebsd/files/iwlwifi-results-1.txt > > > That's really helpful! Please keep the file there for the moment. > > So you got associated constantly (you made it to RUN) but then you didn't hear > any beacons and dropped off again. Rince and repeat. > > What's more important is what's following: > ieee80211_sta_join: BSS c8:7f:54:b5:d5:f0: 2GHz channel, VHT info; ignoring > and the firmware crash following with the 0x5/0xf hcmd. > > Can you please send me your AP details (in private if you want). > Also if you disable 11ac and 11n again, can you then > ifconfig -v wlan0 list scan > and give the output for your 2.4Ghz and 5GHz SSID(s)? > > I intially thought it was a channel switch from 5Ghz to 2.4Ghz which > causes the problem for the firmware panic; could very well be that the > APs supporting VHT on 2Ghz causing the trouble (or both). > > Lots of health, > Bjoern > > -- > Bjoern A. Zeeb r15:7