Intel AX210 on Ai-64

update:

Just re-installed into emmc the official Debian image.

debian@BeagleBone:~$ uname -a
Linux BeagleBone 5.10.120-ti-arm64-r64 #1bullseye SMP Tue Sep 27 18:52:35 UTC 2022 aarch64 GNU/Linux

Have not touched any thing other than enable nmcli and the apt updates.
enabled NetworkManager

Am I missing a step, I have turned on the radio and it still does not scan.

sudo lspci -vv

01:00.0 Network controller: Intel Corporation Device 2725 (rev 1a)
	Subsystem: Intel Corporation Device 0024
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 494
	Region 0: Memory at 18100000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [c8] Power Management version 3
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [40] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 5GT/s, Width x1, ASPM L1, Exit Latency L1 <8us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM Disabled; RCB 64 bytes, Disabled- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 5GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range B, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Via WAKE#, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp- ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 16ms to 55ms, TimeoutDis- LTR+ OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkCap2: Supported Link Speeds: 2.5-5GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
		Vector table: BAR=0 offset=00002000
		PBA: BAR=0 offset=00003000
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [14c v1] Latency Tolerance Reporting
		Max snoop latency: 0ns
		Max no snoop latency: 0ns
	Capabilities: [154 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=30us PortTPowerOnTime=18us
		L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-
			   T_CommonMode=0us LTR1.2_Threshold=262144ns
		L1SubCtl2: T_PwrOn=26us
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

update:

It is now working after installing gnome network manager and a reboot.

also nmcli wifi list now works too.

Including network-manager-gnome in the next official image would make getting wifi up and running easier.

sudo apt install network-manager-gnome
sudo reboot now

Here is the amazon listing, this one has both antennas.

https://www.amazon.com/dp/B088M5CK5K

Just found out how I broke it.

Changed hosts and hostname and it does not work.

Seems like more exists.

Here is some more information.











● NetworkManager.service - Network Manager
     Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-08-07 13:25:12 UTC; 2min 7s ago
       Docs: man:NetworkManager(8)
   Main PID: 499 (NetworkManager)
      Tasks: 3 (limit: 2418)
     Memory: 12.3M
        CPU: 323ms
     CGroup: /system.slice/NetworkManager.service
             └─499 /usr/sbin/NetworkManager --no-daemon

Aug 07 13:25:59 BeagleBone NetworkManager[499]: <warn>  [1659878759.7846] device (wlan0): re-acquiring supplicant interface (#4).
Aug 07 13:25:59 BeagleBone NetworkManager[499]: <warn>  [1659878759.7850] device (SoftAp0): re-acquiring supplicant interface (#4).
Aug 07 13:25:59 BeagleBone NetworkManager[499]: <error> [1659878759.8796] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
Aug 07 13:25:59 BeagleBone NetworkManager[499]: <error> [1659878759.8821] device (SoftAp0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
Aug 07 13:26:09 BeagleBone NetworkManager[499]: <warn>  [1659878769.7746] device (wlan0): re-acquiring supplicant interface (#5).
Aug 07 13:26:09 BeagleBone NetworkManager[499]: <warn>  [1659878769.7750] device (SoftAp0): re-acquiring supplicant interface (#5).
Aug 07 13:26:09 BeagleBone NetworkManager[499]: <error> [1659878769.8639] device (wlan0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
Aug 07 13:26:09 BeagleBone NetworkManager[499]: <info>  [1659878769.8640] device (wlan0): supplicant interface keeps failing, giving up
Aug 07 13:26:09 BeagleBone NetworkManager[499]: <error> [1659878769.8655] device (SoftAp0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError: wpa_supplicant couldn't grab this interface.
Aug 07 13:26:09 BeagleBone NetworkManager[499]: <info>  [1659878769.8656] device (SoftAp0): supplicant interface keeps failing, giving up
~

update 10/27/22:

fred@dev2:~/Desktop$ grep -a 'iw' ai64-boot
[   10.832406] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[   11.309615] iwlwifi 0000:01:00.0: api flags index 2 larger than supported by driver
[   11.317430] iwlwifi 0000:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28
[   11.336829] iwlwifi 0000:01:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm
[   11.463898] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[   11.717732] iwlwifi 0000:01:00.0: base HW address: c4:03:a8:87:59:4c

Did a search for “api flags index 2 larger than supported by driver” and this seems to be a common problem regardless of the distro. So trying to debug this wifi board might be a huge waste of time since the problems are numerous.

Found one posted in the intel support forum and that poster had it working then it would not.
They mentioned running kernel 5.10, mine is 5.10.120

1 Like

I was able to get the AX200 running although i experienced a bug where it would no longer be recognized after a shutdown + unplugging the power source.

The solution was either unplugging and re-plugging in the miniDP to DP Monitor or removing and re-seating the AX200 card.

Maybe it’s a localized case but I 've since switched to the older Intel 9260NGW and it no longer suffers the same bug. (It worked out-of-box with Nov 1 Edge AI image)

Best, Mat

Thank you for sharing that, I am ordering that one and see how it goes.

well unusure if it helps, the AX201NGW is a no show too …

I’m using an AX210NGW and it is working pretty well. A couple of times I have had to use wpagui when it lost or forgot how to connect to my network. Also sometimes I have to issue a ’ sudo nmcli radio wifi on’ command, I don’t know why it’s not automatic.

debian@BeagleBone:~$ lspci
00:00.0 PCI bridge: Texas Instruments Device b00d
01:00.0 Network controller: Intel Corporation Device 2725 (rev 1a)
debian@BeagleBone:~$ uname -r
5.10.153-ti-arm64-r86

My BBAI-64 is enclosed in a case and I don’t want to open it to read the specific information on the WiFi card but I purchased this one.

https://www.amazon.com/gp/product/B09WQSNMCT/ref=ppx_yo_dt_b_asin_title_o09_s01?ie=UTF8&psc=1

There are many types of M.2 ports.
They look the same, but they have different functions.

AI-64 supports M.2 port PCI-E interface.

AX200, AX210 is PCI-E
AX201, AX211 is CNVio2 (intel system ONLY)

1 Like

Thanks very much for your update, that now makes more sense to me.

Would be nice if people with access to the wiki make good on the threat futher up the thread, and put your post info on said ‘Supported Devices’ page.

After a further $50aud+ outlay, I’ve got one that works (ax200ngw).