On Sat, 12 Feb 2022, Krzysztof Piecuch wrote: Hi,
thanks for all the great work you're doing here.
Thanks should go to the Foundation for iwlwifi.
I've got an Intel Corporation Wi-Fi 6 AX201 and I'd be super excited to have it running. I tried snapshot tarballs from 2022-02-10 downloaded from https://download.freebsd.org/snapshots/amd64/14.0-CURRENT/ with a partial success. First time I booted into the new system everything went smoothly. It automatically connected to the network, synced ntp, I installed a bunch of packages with expected speed of 20Mbps and turned off the machine.
Great! And thanks a lot for testing things out!
When shutting down, the kernel cried about iwlwifi but I couldn't see what went wrong and the logs weren't saved to disk because syslog was already off.
Yeah doing this on Laptops directly is a pain these days.
When I turned the machine back on wifi managed to connect and get an IP address but claimed the network is unrechable when trying to ping 1.1.1.1 Power cycling the box a couple of times to no avail.
Do you actually power cycle the box (turn it off, wait a few seconds and turn it back on) or do you just reboot? For some re-initialisation that makes a difference these days sadly.
I would be happy to do some extra work to help debug this but I'm new to FreeBSD.
In the below dmesg the firmware crashed during boot and everything after is a follow-up error (that shouldn't be related to power-cycling). If I remmeber the magic numbers correctly from the top of my head the error seems to be due to a scan command. The real problem is in the last line of these:
Feb 12 00:00:39 freezgroza kernel: iwlwifi0: lkpi_sta_scan_to_auth: waiting for 5 queues to be allocated by driver Feb 12 00:00:39 freezgroza kernel: wifi: link state changed to UP Feb 12 00:00:39 freezgroza kernel: iwlwifi0: No beacon heard and the session protection is over already...
What seems to happen is that we go through a full auth/assoc cycle to running but the firmware/driver decide for some reason they haven't heard a beacon and tear us down again and then things go south currently. I am currently still trying to get fixes out and committed for other things which may also help this. Can you keep an eye on notifications here and then update and try again. I'll be happy to spend more time on this if the next batch of changes doesn't help this particular issue. Happy weekend, Bjoern -- Bjoern A. Zeeb r15:7
