[SOLVED] Missing 5GHz radio on Dlink DAP-2680

Installing and Using OpenWrt
42

this one is with kmod-ath10k:

root@OpenWrt:~# dmesg|grep ath10k
[   13.096181] ath10k_pci 0000:00:00.0: enabling device (0000 -> 0002)
[   13.102813] ath10k_pci 0000:00:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[   14.830890] ath10k_pci 0000:00:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
[   14.840991] ath10k_pci 0000:00:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   14.861378] ath10k_pci 0000:00:00.0: firmware ver 10.4-3.9.0.2-00156 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 2570f4c7
[   17.218560] ath10k_pci 0000:00:00.0: board_file api 2 bmi_id 0:1 crc32 826c8c57
[   20.991700] ath10k_pci 0000:00:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
[   48.881803] ath10k_pci 0000:00:00.0: Unknown eventid: 36933
[  370.248053] ath10k_pci 0000:00:00.0: DFS region 0x0 not supported, will trigger radar for every pulse
[  370.261189] ath10k_pci 0000:00:00.0: Unknown eventid: 36933
[  432.471757] ath10k_pci 0000:00:00.0: Unknown eventid: 36933

this one with kmod-ath10k-ct:

root@OpenWrt:~# dmesg|grep ath10k
[   13.441962] ath10k 5.15 driver, optimized for CT firmware, probing pci device: 0x46.
[   13.450998] ath10k_pci 0000:00:00.0: enabling device (0000 -> 0002)
[   13.457668] ath10k_pci 0000:00:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[   16.283444] ath10k_pci 0000:00:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
[   16.293555] ath10k_pci 0000:00:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   16.313917] ath10k_pci 0000:00:00.0: firmware ver 10.4-3.9.0.2-00156 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 2570f4c7
[   18.605867] ath10k_pci 0000:00:00.0: Loading BDF type 0
[   18.672864] ath10k_pci 0000:00:00.0: board_file api 2 bmi_id 0:1 crc32 826c8c57
[   22.342923] ath10k_pci 0000:00:00.0: 10.4 wmi init: vdevs: 16  peers: 528  tid: 102
[   22.350732] ath10k_pci 0000:00:00.0: msdu-desc: 2500  skid: 32
[   22.464122] ath10k_pci 0000:00:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
[   50.017389] ath10k_pci 0000:00:00.0: 10.4 wmi init: vdevs: 16  peers: 528  tid: 102
[   50.025171] ath10k_pci 0000:00:00.0: msdu-desc: 2500  skid: 32
[   50.232185] ath10k_pci 0000:00:00.0: Unknown (10.4) eventid: 36933
[   50.239572] ath10k_pci 0000:00:00.0: rts threshold -1
[   50.245328] ath10k_pci 0000:00:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[   50.545582] ath10k_pci 0000:00:00.0: Unknown (10.4) eventid: 36933
[   51.002701] ath10k_pci 0000:00:00.0: NOTE:  Firmware DBGLOG output disabled in debug_mask: 0x10000000

I can see both radios in luci and in /etc/config/wireless

root@OpenWrt:~# cat /etc/config/wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option path 'platform/ahb/18100000.wmac'
        option band '2g'
        option htmode 'HT20'
        option cell_density '0'
        option country 'GB'
        option txpower '20'
        option channel '13'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'OpenWrt'
        option encryption 'none'

config wifi-device 'radio1'
        option type 'mac80211'
        option path 'pci0000:00/0000:00:00.0'
        option channel '36'
        option band '5g'
        option htmode 'VHT80'
        option country 'VE'
        option cell_density '0'
        option txpower '21'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'OpenWrt'
        option encryption 'none'

tmp_iw
tmp_iw962×507 63.5 KB

1 Like
43

Thanks for confirming.

I can't comment any further on the transmit power, but if you search the forum you'll find similar reports. Maybe someone else can help you with that, but I'm not sure there's a way to fix it.

44

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.

1 Like
45

It is higher level.

To me, everything done prior, up to and including iw, indicated a reflash...

...which appears to have been part of the solution.

I could have done without your "lecture" on checking low level stuff.

If you wanted to see logread and dmesg output, all you had to do was simply ask the OP...and been done with it.

46

Well, first things I tried before asking there, were flashing and reflashing the ap, as suggested in the DAP 2680 flashing guide. And to switch from ct to normal drivers.

47

I'm rather sure it did not make a difference. The image was wrongly configured from the get-go, reflashing doesn't change anything about that.

Apologies if I came across harsh, wasn't my intention.

48

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.