Hi!
Please document what you find out in the compilation guide of the LibreRouterOS repository readme [1] and, hoping that the solution works also for vanilla LibreMesh, on the development page of the LibreMesh website [2] :)
Thanks!!!
Ilario
[1]:
https://gitlab.com/librerouter/librerouteros
[2]: click the "Edit this page" button on the top right corner of
https://libremesh.org/development.html
On August 6, 2022 4:33:55 PM GMT+02:00, Hiure via LibreMesh <libremesh@???> wrote:
>Hi Martin,
>
>Thanks for you answer.
>
>Modifying the firmware to non-Candelatech even the kernel module works for me.
>
>I don't know what these wpad-mesh-wolfssl packs mean but now the archer c5 has joined the mesh and it seems to work fine.
>
>
>Thanks
>
>Hiure
>
>Em 05/08/2022 15:40, Martin Kennedy via LibreMesh escreveu:
>> Hi there,
>>
>> LrOs is not officially[1] built for the C5; if it were, perhaps a
>> tweak could be made so that LrOs' default packages for this target's
>> ath10k card were different; see (if LrOs is a direct fork of OpenWrt)
>> https://github.com/openwrt/openwrt/blob/master/target/linux/ath79/image/generic-tp-link.mk#L55.
>>
>> Other than recompiling from scratch: you have the kmod-ath10k-ct and
>> ath10k-firmware-qca988x-ct packages driving your ath10k (QCA9880-BR1A,
>> probably) radio. These are the default packages for OpenWrt for this
>> board target. These are the Candelatech variants of the drivers and do
>> not support mesh mode[2].
>>
>> To change over to the non-Candelatech packages, you could:
>>
>> - remove kmod-ath10k-ct and ath10k-firmware-qca988x-ct
>> - install ath10k-firmware-qca988x and kmod-ath10k (in that order)
>>
>> .... but I am not that well-versed in LrOs, only OpenWrt. In
>> particular I notice the package manifests only have wpad-basic and not
>> e.g. wpad-mesh-wolfssl. Some custom stuff has happened here that
>> others should speak to.
>>
>> [1]: https://downloads.libremesh.org/librerouteros/releases/1.5/targets/ath79/generic/
>> [2]: https://github.com/greearb/ath10k-ct/issues/174
>>
>> Best,
>>
>> Martin
>>
>> Martin
>>
>>
>> On Fri, Aug 5, 2022 at 7:15 AM Hiure via LibreMesh <libremesh@???> wrote:
>>> Hi folks,
>>>
>>> I have an issue here.
>>>
>>> Trying to build firmware (I use LrOs-v1.5) to diferents firmwares that
>>> we have in our community network , i had a issue with this especific
>>> model (https://deviwiki.com/wiki/TP-LINK_Archer_C5_v1.x),and need some
>>> help to undestand:
>>>
>>> wlan0-mesh ESSID: unknown
>>> Access Point: 30:B5:C2:56:C0:99
>>> Mode: Mesh Point Channel: unknown (unknown)
>>> Tx-Power: 0 dBm Link Quality: unknown/70
>>> Signal: unknown Noise: -101 dBm
>>> Bit Rate: unknown
>>> Encryption: none
>>> Type: nl80211 HW Mode(s): 802.11nac
>>> Hardware: 168C:003C 0000:0000 [Qualcomm Atheros QCA9880]
>>> TX power offset: none
>>> Frequency offset: none
>>> Supports VAPs: yes PHY name: phy0
>>>
>>> in dmesg i found:
>>>
>>> [ 92.111537] overlayfs: upper fs does not support tmpfile.
>>> [ 350.277932] ath10k_pci 0000:01:00.0: 10.1 wmi init: vdevs: 16
>>> peers: 127 tid: 256
>>> [ 350.295439] ath10k_pci 0000:01:00.0: wmi print 'P 128 V 8 T 410'
>>> [ 350.301823] ath10k_pci 0000:01:00.0: wmi print 'msdu-desc: 1424 sw-
>>> crypt: 0 ct-sta: 0'
>>> [ 350.309973] ath10k_pci 0000:01:00.0: wmi print 'alloc rem: 20984
>>> iram: 25656'
>>> [ 350.378714] ath10k_pci 0000:01:00.0: pdev param 0 not supported by
>>> firmware
>>> [ 350.393665] ath10k_pci 0000:01:00.0: set-coverage-class, phyclk: 88
>>> value: -1
>>> [ 350.402059] IPv6: ADDRCONF(NETDEV_UP): tmp.phy0: link is not ready
>>> [ 355.759072] ath10k_pci 0000:01:00.0: 10.1 wmi init: vdevs: 16
>>> peers: 127 tid: 256
>>> [ 355.776571] ath10k_pci 0000:01:00.0: wmi print 'P 128 V 8 T 410'
>>> [ 355.782953] ath10k_pci 0000:01:00.0: wmi print 'msdu-desc: 1424 sw-
>>> crypt: 0 ct-sta: 0'
>>> [ 355.791140] ath10k_pci 0000:01:00.0: wmi print 'alloc rem: 20984
>>> iram: 25656'
>>> [ 355.859763] ath10k_pci 0000:01:00.0: pdev param 0 not supported by
>>> firmware
>>> [ 355.867103] ath10k_pci 0000:01:00.0: must load driver with rawmode=1
>>> to add mesh interfaces
>>>
>>>
>>> Anyone had this issues before?
>>>
>>> thanks
>>> Hiure
>>> --
>>> LibreMesh mailing list
>>> LibreMesh@???
>>> https://www.autistici.org/mailman/listinfo/libremesh
