Hello, Since more than 1 week and intense use, I found iwlwifi on AX201 stable:
- regularly iperf3 tests directly to router: OK, constant bitrate - no more crashes NOTE: As a side note, iwx driver was always stable on my machine. Now I can use one of the two without noticing diffs between. Very happy here. Thanks, Bjoern A. Zeeb <[email protected]> escreveu (segunda, 6/10/2025 à(s) 15:13): > On Tue, 23 Sep 2025, Oleg Nauman wrote: > > Hi, > > brief update. > > > On Fri, Sep 5, 2025 at 5:08 PM Bjoern A. Zeeb <[email protected]> wrote: > >> > >> On Fri, 5 Sep 2025, Oleg Nauman wrote: > >> > >>> On Wed, Sep 3, 2025 at 12:06 AM Bjoern A. Zeeb <[email protected]> wrote: > >>>> > >>>> Hi, > >>>> > >>>> with the changes (especially for scanning--rtw88) and all the other > >>>> minor details gone in the last days I would love to ask people to test > >>>> as much as they can on main before I'll merge to stable/14 and also > >>>> given stable/15 is imminent. > >>> > >>> Unfortunately rtw88 now ( CURRENT revision d3462294c1f0 ) can't > >>> associate with access points while It was working in 659962f96a15 ( > >>> Jul 29 ) > >>> > >>> rtw880@pci0:2:0:0: class=0x028000 rev=0x00 hdr=0x00 vendor=0x10ec > >>> device=0xc821 subvendor=0x1a3b subdevice=0x3040 > >>> vendor = 'Realtek Semiconductor Co., Ltd.' > >>> device = 'RTL8821CE 802.11ac PCIe Wireless Network Adapter' > >>> class = network > >>> > >>> wlan2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > 1500 > [...] > >> ... > >> > >> This is like net80211 battling against itself. Starts a connection and > >> then (likely wpa_supplicant) triggers a new one and the previous one > >> gets abandoned. It's the very old problem which kept iwlwifi from > >> working so long (along with the fact that we have to unlock/re-lock). > >> > >> Can you check wpa_supplicant logging what it says? Authentication > timed out? > > > > Please let me remind > > > > Output of wpa_supplicant log provided below > > > [...] > > > >> > >>> Sep 5 08:41:41 kernel: [95] rtw880: lkpi_stop_hw_scan: failed to > cancel scan: 35 (0xfffffe011439f240, 0xfffffe01155d0f00) > >> > >> What wonders me a lot more is this. > > It's on releng's open issues list now [1] as I notified them. > > I also just strated a clean main build to look into it as time permits; > please stay tuned. > > /bz > > > [1] https://wiki.freebsd.org/Releng/15.0ISSUES > > -- > Bjoern A. Zeeb r15:7 -- Nuno Teixeira FreeBSD UNIX: <[email protected]> Web: https://FreeBSD.org
