Re: rtwn: RTL8811AU and RTL8821AU status report

On Wed, 30 Apr 2025 at 07:16, Adrian Chadd <adrian@freebsd.org> wrote:

>
>
> On Wed, 30 Apr 2025 at 06:45, Adrian Chadd <adrian@freebsd.org> wrote:
>
>>
>>
>> On Wed, 30 Apr 2025 at 06:42, Bjoern A. Zeeb <bz@freebsd.org> wrote:
>>
>>> On Wed, 30 Apr 2025, Adrian Chadd wrote:
>>>
>>> > On Wed, 30 Apr 2025 at 03:45, Nuno Teixeira <eduardo@freebsd.org>
>>> wrote:
>>> >
>>> >> Hello,
>>> >>
>>> >> main-n276868-cbe50f7c20cf-dirty: Tue Apr 29
>>> >>
>>> >> sys/dev/rtwn/usb/rtwn_usb_rx.c
>>> >> -       m = m_get2(totlen, M_NOWAIT, MT_DATA, M_PKTHDR);
>>> >> +       m = m_get3(totlen, M_NOWAIT, MT_DATA, M_PKTHDR);
>>> >>
>>> >> On both amd64 and aarch64, connection is stable but it only connects
>>> >> with VHT20 instead VHT80 tested a few days ago.
>>> >> Am I missing some config option?
>>> >>
>>> >
>>> > I haven't changed anything recently that should affect that.
>>> > (I'm not running today's head either, I can update today though!)
>>> >
>>> > bz@ ? Any ideas?
>>>
>>> We have multiple reports from people which suddenly started to have
>>> weird media mode reports or channel settings.  At least the media mode I
>>> would have thought comes from the TXparam changes as I had suggested to
>>> you.
>>>
>>
>> Yeah, the media reports I'm looking at locally.
>>
>> But the width negotiation shouldn't have been affected by the txparam
>> work.
>>
>> Nuno - I'll go upgrade my laptop to today's head and report back.
>>
>
> I just updated to -HEAD ( 7ca3db1999cd967f9d6d7b259aa7af54aae14a5f) and
> tested. VHT20 and VHT40 detect fine. I'll enable VHT80 at home later this
> morning
> when no-one's around and test VHT80 for you and report back.
>

I think there's a bug in whether I'm /transmitting/ VHT80 frames due to
some net80211
code I wrote recently, and I'll go fix that soon.

But, ifconfig shows it detects fine for me with rtwn with today's -HEAD:

$ ifconfig wlan0
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=200001<RXCSUM,RXCSUM_IPV6>
        ether 54:af:97:ec:0a:e6
        inet 192.168.0.110 netmask 0xffffff00 broadcast 192.168.0.255
        inet6 fe80::56af:97ff:feec:ae6%wlan0 prefixlen 64 scopeid 0x2
        groups: wlan
        ssid CACHEBOY_HOME channel 161 (5805 MHz 11a vht/80-) bssid
9c:53:22:c7:43:9d
        regdomain FCC country US authmode WPA2/802.11i privacy ON
        deftxkey UNDEF AES-CCM 3:128-bit txpower 17 bmiss 7 mcastrate 6
        mgmtrate 6 scanvalid 60 ampdulimit 64k shortgi -stbc ldpctx -ldpcrx
        -uapsd vht vht40 vht80 -vht160 -vht80p80 wme roaming MANUAL
        parent interface: rtwn0
        media: IEEE 802.11 Wireless Ethernet VHT mode 11ac
        status: associated
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>

.. i wonder if there is something odd going on for non-VHT operating modes?
Or other drivers that aren't setting ni_txrate? Hm.




-adrian


> Thanks!
>
>
>
> -adrian
>
>
>>
>>
>> -adrian
>>
>>
>>>
>>> I Cc:ed you on another report here with iwlwifi a few days ago.
>>>
>>> The channel settings I do not know.
>>>
>>> Given this one is at least coherent, the only other things I can think
>>> off is eduardo trying the experimental regdomain.xml file  and that
>>> being wrong somewhere but we had reports before that was published so...
>>>
>>> /bz
>>>
>>> --
>>> Bjoern A. Zeeb                                                     r15:7
>>>
>>