[RESPONDED] Wi-Fi dropouts on Ubuntu 22.04

Framework Laptop Linux
#1

I’ve had an issue with the Wi-Fi on my 12th gen Intel Framework since I got it a few months ago. I’ve been busy so I’ve mostly just been using an ethernet cable and avoiding the issue, but I need to get this sorted now.

I dual boot Ubuntu 22.04.2 and Windows 11 but I only use Windows very occasionally. I followed all the steps in the Ubuntu 22.04 setup guide, including the bit about /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf.

I tried some different kernel versions in the hope that it would solve the issue. It didn’t help so I’ve now removed them and gone back to the recommended OEM kernel.

Kernel version:

uname -r
5.17.0-1028-oem

Wifi stuff during boot:

sudo dmesg | grep iw
[    8.034435] iwlwifi 0000:a6:00.0: enabling device (0000 -> 0002)
[    8.041560] iwlwifi 0000:a6:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-69.ucode failed with error -2
[    8.043057] iwlwifi 0000:a6:00.0: api flags index 2 larger than supported by driver
[    8.043072] iwlwifi 0000:a6:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36
[    8.043347] iwlwifi 0000:a6:00.0: loaded firmware version 68.01d30b0c.0 ty-a0-gf-a0-68.ucode op_mode iwlmvm
[    8.375633] iwlwifi 0000:a6:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[    8.568216] iwlwifi 0000:a6:00.0: loaded PNVM version 05a8dfca
[    8.582725] iwlwifi 0000:a6:00.0: Detected RF GF, rfid=0x10d000
[    8.656697] iwlwifi 0000:a6:00.0: base HW address: bc:09:1b:f3:a5:e3
[    8.697358] iwlwifi 0000:a6:00.0 wlp166s0: renamed from wlan0

When I’m on a 5GHz network, the connection drops quite frequently and dmesg gets flooded with this happening in a loop:

[  +4.317827] wlp166s0: authenticate with 14:49:bc:51:94:69
[  +0.013615] wlp166s0: send auth to 14:49:bc:51:94:69 (try 1/3)
[  +0.097003] wlp166s0: authenticate with 14:49:bc:51:94:69
[  +0.000014] wlp166s0: send auth to 14:49:bc:51:94:69 (try 1/3)
[  +0.105452] wlp166s0: authenticated
[  +0.001477] wlp166s0: associate with 14:49:bc:51:94:69 (try 1/3)
[  +0.039381] wlp166s0: RX AssocResp from 14:49:bc:51:94:69 (capab=0x111 status=0 aid=3)
[  +0.006123] wlp166s0: associated
[  +0.149235] IPv6: ADDRCONF(NETDEV_CHANGE): wlp166s0: link becomes ready
[  +0.022263] wlp166s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 14:49:bc:51:94:69
[ +24.387599] wlp166s0: Connection to AP 14:49:bc:51:94:69 lost
[  +2.560136] wlp166s0: authenticate with 14:49:bc:51:94:69
[  +0.012979] wlp166s0: send auth to 14:49:bc:51:94:69 (try 1/3)
[  +0.040378] wlp166s0: authenticated
[  +0.001395] wlp166s0: associate with 14:49:bc:51:94:69 (try 1/3)
[  +0.033559] wlp166s0: RX AssocResp from 14:49:bc:51:94:69 (capab=0x111 status=0 aid=3)
[  +0.005645] wlp166s0: associated
[  +0.094938] wlp166s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 14:49:bc:51:94:69
[Mar10 14:35] wlp166s0: Connection to AP 14:49:bc:51:94:69 lost
[  +2.798838] wlp166s0: authenticate with 14:49:bc:51:94:69
[  +0.011536] wlp166s0: send auth to 14:49:bc:51:94:69 (try 1/3)
[  +0.040228] wlp166s0: authenticated
[  +0.001537] wlp166s0: associate with 14:49:bc:51:94:69 (try 1/3)
[  +0.029250] wlp166s0: RX AssocResp from 14:49:bc:51:94:69 (capab=0x111 status=0 aid=3)
[  +0.011219] wlp166s0: associated
[  +0.062081] wlp166s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 14:49:bc:51:94:69
[Mar10 14:36] wlp166s0: Connection to AP 14:49:bc:51:94:69 lost
[  +2.991269] wlp166s0: authenticate with 14:49:bc:51:94:69
[  +0.011711] wlp166s0: send auth to 14:49:bc:51:94:69 (try 1/3)
[  +0.040760] wlp166s0: authenticated
[  +0.007739] wlp166s0: associate with 14:49:bc:51:94:69 (try 1/3)
[  +0.031819] wlp166s0: RX AssocResp from 14:49:bc:51:94:69 (capab=0x111 status=0 aid=3)
[  +0.005636] wlp166s0: associated
[  +0.069804] wlp166s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 14:49:bc:51:94:69
[  +0.042000] iwlwifi 0000:a6:00.0: Unhandled alg: 0x707
[  +0.009509] iwlwifi 0000:a6:00.0: Unhandled alg: 0x707

On 2.4GHz I see more of the above, with the addition of some lines about ‘session protection’:

[Mar10 15:18] wlp166s0: authenticate with 16:49:bc:41:94:69
[  +0.000044] wlp166s0: 80 MHz not supported, disabling VHT
[  +0.010499] wlp166s0: send auth to 16:49:bc:41:94:69 (try 1/3)
[  +0.030554] wlp166s0: authenticated
[  +0.005736] wlp166s0: associate with 16:49:bc:41:94:69 (try 1/3)
[  +0.005434] wlp166s0: RX AssocResp from 16:49:bc:41:94:69 (capab=0x411 status=30 aid=2895)
[  +0.000031] wlp166s0: 16:49:bc:41:94:69 rejected association temporarily; comeback duration 1024 TU (1048 ms)
[  +0.000846] iwlwifi 0000:a6:00.0: Unhandled alg: 0x707
[  +1.077699] wlp166s0: associate with 16:49:bc:41:94:69 (try 2/3)
[  +0.107889] wlp166s0: associate with 16:49:bc:41:94:69 (try 3/3)
[  +0.104052] wlp166s0: association with 16:49:bc:41:94:69 timed out
[  +2.837358] wlp166s0: authenticate with 16:49:bc:41:87:60
[  +0.000033] wlp166s0: 80 MHz not supported, disabling VHT
[  +0.006301] wlp166s0: send auth to 16:49:bc:41:87:60 (try 1/3)
[  +0.899069] iwlwifi 0000:a6:00.0: Not associated and the session protection is over already...
[  +0.000073] wlp166s0: Connection to AP 16:49:bc:41:87:60 lost
[  +1.162321] wlp166s0: send auth to 16:49:bc:41:87:60 (try 2/3)
[  +0.898955] iwlwifi 0000:a6:00.0: Not associated and the session protection is over already...
[  +0.000073] wlp166s0: Connection to AP 16:49:bc:41:87:60 lost
[  +1.116593] wlp166s0: send auth to 16:49:bc:41:87:60 (try 3/3)
[  +0.899123] iwlwifi 0000:a6:00.0: Not associated and the session protection is over already...
[  +0.000081] wlp166s0: Connection to AP 16:49:bc:41:87:60 lost
[  +0.024041] wlp166s0: aborting authentication with 16:49:bc:41:87:60 by local choice (Reason: 3=DEAUTH_LEAVING)
[  +3.767852] wlp166s0: authenticate with 16:49:bc:41:94:69
[  +0.000024] wlp166s0: 80 MHz not supported, disabling VHT
[  +0.006352] wlp166s0: send auth to 16:49:bc:41:94:69 (try 1/3)
[  +0.037856] wlp166s0: authenticated
[  +0.007792] wlp166s0: associate with 16:49:bc:41:94:69 (try 1/3)
[  +0.005390] wlp166s0: RX AssocResp from 16:49:bc:41:94:69 (capab=0x411 status=53 aid=6)
[  +0.000016] wlp166s0: 16:49:bc:41:94:69 denied association (code=53)
[  +0.044146] wlp166s0: authenticate with 16:49:bc:41:94:69
[  +0.000039] wlp166s0: 80 MHz not supported, disabling VHT
[  +0.005724] wlp166s0: send auth to 16:49:bc:41:94:69 (try 1/3)
[  +0.108466] wlp166s0: authenticate with 16:49:bc:41:94:69
[  +0.000016] wlp166s0: send auth to 16:49:bc:41:94:69 (try 1/3)
[  +0.106286] wlp166s0: authenticated
[  +0.001999] wlp166s0: associate with 16:49:bc:41:94:69 (try 1/3)
[  +0.013888] wlp166s0: RX AssocResp from 16:49:bc:41:94:69 (capab=0x411 status=0 aid=6)
[  +0.006902] wlp166s0: associated
[ +12.745241] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7

Do the Limiting TX power to 30 (30 - 0) dBm as advertised by ... lines mean that powersaving hasn’t been disabled?

I hope someone can help!

#2

Please visit

Scroll to If you’re dealing with lag or speed issues and paste the entire block of code into a terminal, press enter. Then please shot or copy paste the results.

Ignore wifi fixer script as it wouldn’t apply in this situation.

If you’re dual booting, heard Windows can do weird things to wifi state. But let’s start here first.

That code will give us a lot of helpful environmental background info on how your wifi card is behaving.

To check power saving state, drop this into a terminal.

cat /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

Then post the results as well.

#3

Thanks for getting back to me. I didn’t know about that troubleshooting guide!

Is it normal to see Direct firmware load for iwlwifi-ty-a0-gf-a0-69.ucode failed with error -2 from dmesg during boot?

On 2.4GHz:

        Interface: wlp166s0
        Signal strength: -20
        Signal quality: Mbit/s
        Signal bars: ▂▄▆█
        Wi-Fi Speed: 270 Mbit/s
        Wi-Fi Channel: 1
        Wi-Fi Noise, Link and Quality Level: Link: 70. Level: -20. Noise: -256

On 5GHz:

        Interface: wlp166s0
        Signal strength: -31
        Signal quality: 270
        Signal bars: ▂▄▆█
        Wi-Fi Speed: 270 Mbit/s
        Wi-Fi Channel: 36
        Wi-Fi Noise, Link and Quality Level: Link: 70. Level: -30. Noise: -256

This is when the computer is less than a meter from this access point - VigorAP 903 | DrayTek
Speed tests are always very good, but the connection drops out roughly every 5-10 minutes which causes pings to fail. It seems to be more likely to occur when the connection is under more load.
I think it’s slightly more frequent on 5GHz but not by much. Most of the AP’s settings are on default: on 2.4GHz, channel width is auto (20/40MHz) but it always uses 20MHz with my computer; on 5GHz, channel width is auto (20/40/80MHz) and it always uses 80MHz with my computer.

cat /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
[connection]
wifi.powersave = 2

What do the different values for wifi.powersave mean?

This morning when doing a speed test I got something new from dmesg:

[ +15.170242] iwlwifi 0000:a6:00.0: Microcode SW error detected. Restarting 0x0.
[  +0.000432] iwlwifi 0000:a6:00.0: Start IWL Error Log Dump:
[  +0.000009] iwlwifi 0000:a6:00.0: Transport status: 0x0000004A, valid: 6
[  +0.000008] iwlwifi 0000:a6:00.0: Loaded firmware version: 68.01d30b0c.0 ty-a0-gf-a0-68.ucode
[  +0.000006] iwlwifi 0000:a6:00.0: 0x00000942 | ADVANCED_SYSASSERT          
[  +0.000007] iwlwifi 0000:a6:00.0: 0x000002F0 | trm_hw_status0
[  +0.000005] iwlwifi 0000:a6:00.0: 0x00000000 | trm_hw_status1
[  +0.000004] iwlwifi 0000:a6:00.0: 0x004DAF86 | branchlink2
[  +0.000005] iwlwifi 0000:a6:00.0: 0x0000193C | interruptlink1
[  +0.000005] iwlwifi 0000:a6:00.0: 0x0000193C | interruptlink2
[  +0.000004] iwlwifi 0000:a6:00.0: 0x0019FFF8 | data1
[  +0.000004] iwlwifi 0000:a6:00.0: 0x6D002000 | data2
[  +0.000005] iwlwifi 0000:a6:00.0: 0x02200631 | data3
[  +0.000004] iwlwifi 0000:a6:00.0: 0x6A413E53 | beacon time
[  +0.000005] iwlwifi 0000:a6:00.0: 0x1BC221B5 | tsf low
[  +0.000005] iwlwifi 0000:a6:00.0: 0x0000009D | tsf hi
[  +0.000004] iwlwifi 0000:a6:00.0: 0x00000000 | time gp1
[  +0.000005] iwlwifi 0000:a6:00.0: 0x2FC445DF | time gp2
[  +0.000004] iwlwifi 0000:a6:00.0: 0x00000001 | uCode revision type
[  +0.000005] iwlwifi 0000:a6:00.0: 0x00000044 | uCode version major
[  +0.000005] iwlwifi 0000:a6:00.0: 0x01D30B0C | uCode version minor
[  +0.000004] iwlwifi 0000:a6:00.0: 0x00000420 | hw version
[  +0.000005] iwlwifi 0000:a6:00.0: 0x00C89002 | board version
[  +0.000005] iwlwifi 0000:a6:00.0: 0x80B3FD27 | hcmd
[  +0.000005] iwlwifi 0000:a6:00.0: 0x00021000 | isr0
[  +0.000005] iwlwifi 0000:a6:00.0: 0x01400000 | isr1
[  +0.000004] iwlwifi 0000:a6:00.0: 0x48F00002 | isr2
[  +0.000005] iwlwifi 0000:a6:00.0: 0x00C30008 | isr3
[  +0.000005] iwlwifi 0000:a6:00.0: 0x00200000 | isr4
[  +0.000005] iwlwifi 0000:a6:00.0: 0xA799009D | last cmd Id
[  +0.000004] iwlwifi 0000:a6:00.0: 0x004C78EA | wait_event
[  +0.000005] iwlwifi 0000:a6:00.0: 0x000000D4 | l2p_control
[  +0.000005] iwlwifi 0000:a6:00.0: 0x00000000 | l2p_duration
[  +0.000005] iwlwifi 0000:a6:00.0: 0x00000007 | l2p_mhvalid
[  +0.000006] iwlwifi 0000:a6:00.0: 0x00000000 | l2p_addr_match
[  +0.000004] iwlwifi 0000:a6:00.0: 0x00000009 | lmpm_pmg_sel
[  +0.000005] iwlwifi 0000:a6:00.0: 0x00000000 | timestamp
[  +0.000005] iwlwifi 0000:a6:00.0: 0x0000E0D0 | flow_handler
[  +0.000297] iwlwifi 0000:a6:00.0: Start IWL Error Log Dump:
[  +0.000005] iwlwifi 0000:a6:00.0: Transport status: 0x0000004A, valid: 7
[  +0.000007] iwlwifi 0000:a6:00.0: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL
[  +0.000007] iwlwifi 0000:a6:00.0: 0x00000000 | umac branchlink1
[  +0.000006] iwlwifi 0000:a6:00.0: 0x8045E21C | umac branchlink2
[  +0.000006] iwlwifi 0000:a6:00.0: 0x804804AE | umac interruptlink1
[  +0.000005] iwlwifi 0000:a6:00.0: 0x804804AE | umac interruptlink2
[  +0.000006] iwlwifi 0000:a6:00.0: 0x00000002 | umac data1
[  +0.000005] iwlwifi 0000:a6:00.0: 0x804804AE | umac data2
[  +0.000006] iwlwifi 0000:a6:00.0: 0x00000000 | umac data3
[  +0.000005] iwlwifi 0000:a6:00.0: 0x00000044 | umac major
[  +0.000005] iwlwifi 0000:a6:00.0: 0x01D30B0C | umac minor
[  +0.000006] iwlwifi 0000:a6:00.0: 0x2FC4477E | frame pointer
[  +0.000005] iwlwifi 0000:a6:00.0: 0xC088625C | stack pointer
[  +0.000006] iwlwifi 0000:a6:00.0: 0x00E7019C | last host cmd
[  +0.000005] iwlwifi 0000:a6:00.0: 0x00000000 | isr status reg
[  +0.000264] iwlwifi 0000:a6:00.0: IML/ROM dump:
[  +0.000005] iwlwifi 0000:a6:00.0: 0x00000B03 | IML/ROM error/state
[  +0.000261] iwlwifi 0000:a6:00.0: 0x00007B00 | IML/ROM data1
[  +0.000065] iwlwifi 0000:a6:00.0: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
[  +0.000059] iwlwifi 0000:a6:00.0: Fseq Registers:
[  +0.000158] iwlwifi 0000:a6:00.0: 0x60000000 | FSEQ_ERROR_CODE
[  +0.000163] iwlwifi 0000:a6:00.0: 0x80440005 | FSEQ_TOP_INIT_VERSION
[  +0.000162] iwlwifi 0000:a6:00.0: 0x00080009 | FSEQ_CNVIO_INIT_VERSION
[  +0.000163] iwlwifi 0000:a6:00.0: 0x0000A652 | FSEQ_OTP_VERSION
[  +0.000163] iwlwifi 0000:a6:00.0: 0x00000002 | FSEQ_TOP_CONTENT_VERSION
[  +0.000163] iwlwifi 0000:a6:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[  +0.000164] iwlwifi 0000:a6:00.0: 0x00400410 | FSEQ_CNVI_ID
[  +0.000163] iwlwifi 0000:a6:00.0: 0x00400410 | FSEQ_CNVR_ID
[  +0.000164] iwlwifi 0000:a6:00.0: 0x00400410 | CNVI_AUX_MISC_CHIP
[  +0.000166] iwlwifi 0000:a6:00.0: 0x00400410 | CNVR_AUX_MISC_CHIP
[  +0.000165] iwlwifi 0000:a6:00.0: 0x00009061 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[  +0.000198] iwlwifi 0000:a6:00.0: 0x00000061 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[  +0.000433] iwlwifi 0000:a6:00.0: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
[  +0.000012] ieee80211 phy0: Hardware restart was requested

It reconnected automatically a second later though.

#4

Everything looks really good. Power save is set to 2 which means powersave is turned off, which also helps with drop off.

Let’s check a few things. What’s the output from:

dmesg | grep microcode

Also the results from:

ls /lib/firmware | grep iwlwifi-ty-a0-gf-a0-69.ucode
or
ls /lib/firmware | grep iwlwifi-ty-a0

Did you do anything unusual outside of the guide with wifi setup? Backports, other firmware downloads, etc?

#5 
sudo dmesg | grep microcode
Place your right index finger on the fingerprint reader
[    0.000000] microcode: microcode updated early to revision 0x429, date = 2023-01-11
[    1.761367] microcode: sig=0x906a3, pf=0x80, revision=0x429
[    1.762014] microcode: Microcode Update Driver: v2.2

ls /lib/firmware | grep iwlwifi-ty-a0-gf-a0-69.ucode is empty

ls /lib/firmware | grep iwlwifi-ty-a0 gives me:

iwlwifi-ty-a0-gf-a0-59.ucode
iwlwifi-ty-a0-gf-a0-62.ucode
iwlwifi-ty-a0-gf-a0-63.ucode
iwlwifi-ty-a0-gf-a0-66.ucode
iwlwifi-ty-a0-gf-a0-67.ucode
iwlwifi-ty-a0-gf-a0-68.ucode
iwlwifi-ty-a0-gf-a0-71.ucode
iwlwifi-ty-a0-gf-a0-72.ucode
iwlwifi-ty-a0-gf-a0.pnvm

A couple of weeks ago I tried installing the linux-generic-hwe-22.04 and linux-modules-iwlwifi-generic-hwe-22.04 packages in the hope that it would help, but when it made no difference I removed them and went back to the OEM kernel. I haven’t installed any backports per see and haven’t installed any firmware directly.

I don’t know if this is related at all, but when I first got the computer I had a bizarre issue where the screen would flicker rapidly when the wifi card was under load, but only on Windows (never on Ubuntu), and only the internal screen (rather than one on HDMI).

On the recommendation of someone on the Framework support team, I reseated the wifi card and re-connected the antennas and connections and shielding around the monitor panel. This seemed to solve the flickering issue, but I wonder if there is something still underlying?

#6

This could related, I recommend using this kernel option for 22.04:

sudo apt install linux-oem-22.04

Please give this a try, verify you’ve selected it with uname -r once rebooted.

#7

Thanks for continuing to follow up on this.

linux-oem-22.04 is already the newest version (5.17.0.1028.26)

In the first post on this thread I said

I tried some different kernel versions in the hope that it would solve the issue. It didn’t help so I’ve now removed them and gone back to the recommended OEM kernel.

Kernel version:

uname -r
5.17.0-1028-oem
#8

Ah, I see it. Sorry I missed that.

Re-reading this, I don’t believe this would be the direct issue. With wifi, usually it’s either there or it’s not. Wifi drops, etc, are usually OS/power settings related.

In your case, your reported speed and signal strength looks fine. Visually speaking in terms of the reported output.

Your set up with power save being off, which should prevent drop off.

At this point, the next two things I’d do if this was my own system are:

  • I’d do speed testing on a completely unrelated network, to make sure there isn’t something else locally happening. This will feel silly, but I can tell you I’ve seen instances where every single device in a home works great, one doesn’t. Take said problem device to a new network, poof, problem isn’t there and the network was to blame. Causes varied in my experience from QoS to vlan stuff.

  • I’d also like to see this tested with a vanilla, standard uninstalled Live USB of Ubuntu. Just for a comparable. I’d like to see this tested on the existing network and also tested on literally any other network.

The goal here is to say whether or not this is a bad card, bad card connection, or something with the existing OS config.

#9

Hi @Vilasamuni, just chiming in to try narrow down the issue, you said this is a dual boot setup? have you had the chance to use windows for 2 days or more to see if no dropouts happening on that side? Also have you tried other access points other than the ones you’re using now? Is it reproduceable when say, you’re using a mobile hotspot?

1 Like
#10

Thanks - I appreciate having some guidance to narrow down the variables. I’ve done testing on several different networks with a second laptop alongside my Framework. I was going in circles a bit because the issue is intermittent and only happens with particular combinations of hardware, software and AP.

Computer hardware Operating System Router/AP WiFi stable?
Framework - 12th gen Intel CPU; Intel Wi-Fi 6 AX210 Ubuntu 22.04.2 - kernel 5.17.0-1028-oem Draytek VigorAP 903 N
Framework - 12th gen Intel CPU; Intel Wi-Fi 6 AX210 Ubuntu 22.04.2 booted from Live USB - kernel 5.19.0-32-generic Draytek VigorAP 903 N
Framework - 12th gen Intel CPU; Intel Wi-Fi 6 AX210 Windows 11 Draytek VigorAP 903 Y
Framework - 12th gen Intel CPU; Intel Wi-Fi 6 AX210 Ubuntu 22.04.2 - kernel 5.17.0-1028-oem BT Hub 5 Y
Framework - 12th gen Intel CPU; Intel Wi-Fi 6 AX210 Ubuntu 22.04.2 booted from Live USB - kernel 5.19.0-32-generic BT Hub 5 Y
Framework - 12th gen Intel CPU; Intel Wi-Fi 6 AX210 Windows 11 BT Hub 5 Y
Framework - 12th gen Intel CPU; Intel Wi-Fi 6 AX210 Ubuntu 22.04.2 - kernel 5.17.0-1028-oem BT Hub 6 Y
Framework - 12th gen Intel CPU; Intel Wi-Fi 6 AX210 Ubuntu 22.04.2 booted from Live USB - kernel 5.19.0-32-generic BT Hub 6 Y
Framework - 12th gen Intel CPU; Intel Wi-Fi 6 AX210 Windows 11 BT Hub 6 Y
Framework - 12th gen Intel CPU; Intel Wi-Fi 6 AX210 Ubuntu 22.04.2 - kernel 5.17.0-1028-oem Netgear DGND3700v2 Y
Framework - 12th gen Intel CPU; Intel Wi-Fi 6 AX210 Ubuntu 22.04.2 booted from Live USB - kernel 5.19.0-32-generic Netgear DGND3700v2 Y
Framework - 12th gen Intel CPU; Intel Wi-Fi 6 AX210 Windows 11 Netgear DGND3700v2 Y
Novatech Nspire - 11th gen Intel CPU; Intel Wireless-AC 9462 Ubuntu 22.04.2 - kernel Draytek VigorAP 903 N
Novatech Nspire - 11th gen Intel CPU; Intel Wireless-AC 9462 Windows 11 Draytek VigorAP 903 Y
Novatech Nspire - 11th gen Intel CPU; Intel Wireless-AC 9462 Ubuntu 22.04.2 - kernel BT Hub 5 Y
Novatech Nspire - 11th gen Intel CPU; Intel Wireless-AC 9462 Ubuntu 22.04.2 - kernel BT Hub 6 Y
2021 Apple iMac - M1 CPU MacOS 13.2.1 Draytek VigorAP 903 Y
2021 Apple iMac - M1 CPU MacOS 13.2.1 BT Hub 6 Y