I'm trying to get a QCN9074-based AX Wifi transceiver working with a Pi 5. I've connected it via a Mini PCIe hat. I'm using an adapter board on that hat and externally powering the transceiver.
With Raspbian, the ath11k drivers are not built with the kernel. I have compiled the latest kernel and enabled the driver. I do see the device via lspci and see that the ath11k driver tries to load.
lspci -k:However, the driver is not loading properly. I see the following error:
dmesg | grep ath11:I have tried using dtparam=pciex1, dtparam=pciex1_gen=3, and dyoverlay=pciex1-compat-pi5,no-mip to no avail.
I'm hoping someone can point me in the right direction on what to do or take a look at next. Is this solved by some device tree overly? Are there some kernel configs I'm missing? Could it be the mini pcie hat? The fact it is detected via lspci has me hoping this can be resolved.
With Raspbian, the ath11k drivers are not built with the kernel. I have compiled the latest kernel and enabled the driver. I do see the device via lspci and see that the ath11k driver tries to load.
lspci -k:
Code:
0000:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21)Kernel driver in use: pcieport0000:01:00.0 Network controller: Qualcomm Technologies, Inc QCN6024/9024/9074 Wireless Network Adapter (rev 01)Subsystem: Qualcomm Technologies, Inc QCN6024/9024/9074 Wireless Network AdapterKernel modules: ath11k_pci0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21)Kernel driver in use: pcieport0001:01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South BridgeKernel driver in use: rp1
dmesg | grep ath11:
Code:
[ 3.775745] ath11k_pci 0000:01:00.0: BAR 0: assigned [mem 0x1b00000000-0x1b001fffff 64bit][ 3.775775] ath11k_pci 0000:01:00.0: enabling device (0000 -> 0002)[ 3.775893] ath11k_pci 0000:01:00.0: arch assigned 64-bit MSI address 0xffffffe000 but device only supports 32 bits[ 3.775930] ath11k_pci 0000:01:00.0: failed to enable msi: -22[ 3.776012] ath11k_pci: probe of 0000:01:00.0 failed with error -22
I'm hoping someone can point me in the right direction on what to do or take a look at next. Is this solved by some device tree overly? Are there some kernel configs I'm missing? Could it be the mini pcie hat? The fact it is detected via lspci has me hoping this can be resolved.
Statistics: Posted by WaveWiz — Fri Jul 05, 2024 8:10 pm