Leo-PL
October 24, 2024, 5:58pm
265
MasMat:
[ 22.590320] ath10k_pci 0000:00:00.0: qca9888 hw2.0 target 0x01000000 chip_id 0x00000000 sub 0000:0000
[ 22.599906] ath10k_pci 0000:00:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[ 22.619093] ath10k_pci 0000:00:00.0: firmware ver 10.4b-ct-9888-fW-13-5ae337bb1 api 5 features mfp,peer-flow-ctrl,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 59e741e7
[ 22.651458] ath10k_pci 0000:00:00.0: invalid calibration data length in nvmem-cell 'pre-calibration': 2116 != 12064
[ 22.939547] ath10k_pci 0000:00:00.0: Loading BDF type 0
[ 22.964592] ath10k_pci 0000:00:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0056,subsystem-vendor=0000,subsystem-device=0000 from ath10k/QCA9888/hw2.0/board-2.bin
[ 23.416061] ath10k_pci 0000:00:00.0: failed to fetch board-2.bin or board.bin from ath10k/QCA9888/hw2.0
[ 23.425826] ath10k_pci 0000:00:00.0: failed to fetch board file: -12
[ 23.448540] ath10k_pci 0000:00:00.0: could not probe fw (-12)
Not correct, but I see the culprit. Can you dump the "caldata" MTD partition and upload it somewhere for me to check? I think we need some device tree tweaks to actually make it work. Too bad I don't have such a weird device to test myself.
Edit: please try this image: https://drive.google.com/drive/folders/1z5K_PF4asc8zQ0HG68eUsnfwhq1Cb2gn?usp=drive_link
If it works - i.e. both interfaces probe, I'll submit the fix upstream.