Re: New iwlwifi driver seems to be good on AX200

On Thu, Mar 31, 2022 at 6:05 PM Bjoern A. Zeeb <
bzeeb-lists@lists.zabbadoz.net> wrote:

> On Mon, 28 Mar 2022, Kevin Oberman wrote:
>
> > Updated to table/13-n250140-4cf0cc507f3 and the network seems good.
> >
> > A couple of oddities:
> >
> > First, the network is quite slow to start. The driver is loaded from
> > rc.conf and seems to be up in about the same time as before the update.
> The
>
> That should no longer be needed.  devmatch should do the right.
>
>
> > ifconfig after the network start  looks good and I get:
> > wlan0: Ethernet address: 6c:6a:77:ed:ce:d9
> > wlan0: link state changed to UP
> > on the console, but, after the startup completes and I have a login
> prompt,
> > Mar 28 17:54:26 ptavv ntpd[1946]: error resolving pool
> > 0.freebsd.pool.ntp.org: Name does not resolve (8)
> > Mar 28 17:54:26 ptavv dhclient[1335]: send_packet: No buffer space
> > available                             Mar 28 17:54:26 ptavv syslogd: last
> > message repeated 1 times
> >
> > I'm guessing that these messages were generated during the network
> startup,
> > but no sent to the console until after getty started. This is not a
> > problem, but seems odd and I have never seen it before.
>
> dmesg -a   should show the order in which things appear more clearly
> than syslog.
>
> i'd also check wpa_supplicant logs to see if a deassoc/deauth happened
> (still happens sometimes to me right after UP) which could explain why
> packets do not immediately get out.
>
>
>
> > Second, when the driver loads, I see failure to load both version 70 and
> 69
> > of the firmware. 68 loads fine. I suspect that this is normal but it
> seemed
> > odd that a newer version of firmware would not load on a fairly new
> device.
> > (AX200)
>
> That is normal as at the time of import the driver was aware of newer
> firmware but the firmware wasn't released yet.
> It is out now for some but I didn't want to update everything in one
> go again as then we'd not know where problems come from.
>
> The messages are harmless, very much like the yoyo you may or may not
> see too failing to load.
>
>
> > Neither of these impacts operation an everything seems to be running
> fine.
> >
> > Previously my system would crash on certain high data operations and I
> will
> > be testing this later when I can deal with the system needing to reboot.
>
> Glad to hear and thanks a lot for testing and reporting back.
>
> Lots of health,
> Bjoern
>
> --
> Bjoern A. Zeeb                                                     r15:7
>

OK. Looking at the actual console output during boot, I see the following
regarding network startup:
iwlwifi0: <iwlwifi> mem 0xd1300000-0xd1303fff at device 0.0 on pci2
iwlwifi0: could not load firmware image 'iwlwifi-cc-a0-70.ucode'
iwlwifi0: File size way too small!
iwlwifi0: could not load firmware image 'iwlwifi-cc-a0-69.ucode'
iwlwifi0: File size way too small!
[Unrelated messages (acpi_wmi) elided]
iwlwifi0: successfully loaded firmware image 'iwlwifi-cc-a0-68.ucode'
iwlwifi0: api flags index 2 larger than supported by driver
iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
iwlwifi0: loaded firmware version 68.01d30b0c.0 cc-a0-68.ucode op_mode
iwlmvm
iwlwifi0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
lo0: link state changed to UP
iwlwifi0: Detected RF HR B3, rfid=0x10a100
iwlwifi0: base HW address: 6c:6a:77:ed:ce:d9
wlan0: Ethernet address: 6c:6a:77:ed:ce:d9
wlan0: link state changed to UP
[Many non-network related lines elided]
lan0: link state changed to DOWN
wlan0: link state changed to UP

The timing is not available on those messages, but the messages log shows
one second between UP and DOWN and then:
Apr  8 23:00:08 ptavv kernel: wlan0: link state changed to DOWN
Apr  8 23:00:08 ptavv wpa_supplicant[1325]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=14:c0:3e:ec:a3:48 reason=0
Apr  8 23:00:08 ptavv ntfs-3g[1934]: Version 2017.3.23 external FUSE 29
Apr  8 23:00:08 ptavv ntfs-3g[1934]: Mounted /dev/ntfs/Windows (Read-Only,
label "Windows", NTFS 3.1)
Apr  8 23:00:08 ptavv ntfs-3g[1934]: Cmdline options:
rw,uid=9381,gid=15,norecover,noatime
Apr  8 23:00:08 ptavv ntfs-3g[1934]: Mount options:
rw,allow_other,nonempty,noatime,ro,default_permissions,fsname=/dev/ntfs/Windows
Apr  8 23:00:08 ptavv ntfs-3g[1934]: Global ownership and permissions
enforced, configuration type 1
Apr  8 23:00:08 ptavv ntpd[1954]: ntpd 4.2.8p15-a (1): Starting
Apr  8 23:00:08 ptavv kernel: Security policy loaded: MAC/ntpd (mac_ntpd)
Apr  8 23:00:08 ptavv ntpd[1954]: Command line: /usr/sbin/ntpd -p
/var/db/ntp/ntpd.pid -c /etc/ntp.conf -f /var/db/ntp/ntpd.drift -g
[ntpd startup elided]
Apr  8 23:00:09 ptavv wpa_supplicant[1325]: wlan0: Trying to associate with
14:c0:3e:ec:a3:48 (SSID='babcom' freq=2462 MHz)
Apr  8 23:00:09 ptavv ntpd[1955]: error resolving pool
0.freebsd.pool.ntp.org: Name does not resolve (8)
Apr  8 23:00:09 ptavv kernel: .
Apr  8 23:00:09 ptavv kernel: wlan0: link state changed to UP
Apr  8 23:00:09 ptavv wpa_supplicant[1325]: wlan0: Associated with
14:c0:3e:ec:a3:48
Apr  8 23:00:09 ptavv dhclient[1344]: send_packet: No buffer space available
Apr  8 23:00:09 ptavv syslogd: last message repeated 1 times
Apr  8 23:00:09 ptavv wpa_supplicant[1325]: wlan0: WPA: Key negotiation
completed with 14:c0:3e:ec:a3:48 [PTK=CCMP GTK=CCMP]
Apr  8 23:00:09 ptavv wpa_supplicant[1325]: wlan0: CTRL-EVENT-CONNECTED -
Connection to 14:c0:3e:ec:a3:48 completed [id=1 id_str=]
[Approx: 1700 lines of "log in vain" messages from failed DNS lookups while
the network was running DHCP client.  All failures were loopback requests
(127.0.0.1 or ::1 for both source and destination.]
 Apr  8 23:00:12 ptavv kernel: Connection attempt to UDP [::1]:53 from
[::1]:20629
Apr  8 23:00:12 ptavv dhclient[2240]: New Subnet Mask (wlan0): 255.255.255.0
Apr  8 23:00:12 ptavv dhclient[2244]: New Broadcast Address (wlan0):
192.168.1.255
Apr  8 23:00:12 ptavv dhclient[2248]: New Routers (wlan0): 192.168.1.1

At this point, the network is up and appears stable. SInce hte last update,
I have had no loss of association or other problems.

I have hit another VERY annoying shutdown issue, but I will cover this in a
separate message when I have collected data.

Hope this is useful. Again AX200 on stable/13-n250140-4cf0cc507f3 amd64.

As soon as I can do a backup of the system, I will be updating the OS to
today's 13-stable. I'll let you know if there are changes after this update.
-- 
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683