Djfe
commented
1 year ago Update, the device runs, we might open a PR at some point. Mesh on 5GHz isn't working though so that will probably need some fixes and I don't want to create a draft PR that sits around for ages. It could be related to https://github.com/openwrt/openwrt/issues/10784 techtimo's device has 4MiB NOR-Flash instead of 16MiB like the one that was originally added. other's have 8MiB. NAND-Flash can be either 256 or 128MiB, see Wiki
I'm not sure whether the art partition contains garbage though: nbg6716-art.zip Maybe someone can take a look at it to tell me
excerpt from logread when I run wifi down&wifi up full log
Mon May 8 03:34:41 2023 kern.info kernel: [39930.224544] ath10k_pci 0000:00:00.0: mac flush vdev 0 drop 0 queues 0x1 ar->paused: 0x0 arvif->paused: 0x0
Mon May 8 03:34:41 2023 kern.warn kernel: [39930.255284] ath10k_pci 0000:00:00.0: could not get mac80211 beacon, vdev_id: 0 addr: d6:9e:0b:a3:60:90
Mon May 8 03:34:41 2023 kern.info kernel: [39930.271348] ath10k_pci 0000:00:00.0: mac flush vdev 0 drop 0 queues 0x1 ar->paused: 0x0 arvif->paused: 0x0
Mon May 8 03:34:41 2023 kern.info kernel: [39930.311951] ath10k_pci 0000:00:00.0: mac flush null vif, drop 0 queues 0xffff
[...]
Mon May 8 03:37:44 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy client0) --> new PHY
Mon May 8 03:37:46 2023 kern.warn kernel: [40115.239867] ath10k_pci 0000:00:00.0: 10.1 wmi init: vdevs: 4 peers: 96 tid: 256
Mon May 8 03:37:46 2023 kern.info kernel: [40115.255996] ath10k_pci 0000:00:00.0: wmi print 'P 97 V 4 T 371'
Mon May 8 03:37:46 2023 kern.info kernel: [40115.262392] ath10k_pci 0000:00:00.0: wmi print 'msdu-desc: 1424 sw-crypt: 0 ct-sta: 0'
Mon May 8 03:37:46 2023 kern.info kernel: [40115.270565] ath10k_pci 0000:00:00.0: wmi print 'alloc rem: 41968 iram: 50724'
Mon May 8 03:37:46 2023 kern.warn kernel: [40115.335907] ath10k_pci 0000:00:00.0: pdev param 0 not supported by firmware
Mon May 8 03:37:46 2023 kern.info kernel: [40115.359921] ath10k_pci 0000:00:00.0: rts threshold -1
AiyionPrime
oakey-dev
GoliathLabs
@NeoRaider's recent contribution of the network regeneration got merged (thanks to all involved!) and if I'm not mistaken, we've agreed on testing the devices that were gone again, as if we'd be adding new support for them.
That's arguably an effort, but hopefully one divided on several shoulders.
Below is a list of devices that got dropped with the target ar71xx, which hadn't been marked as tiny back then and was not within the mikrotik subtarget. I think that would be a solid start for the migration.
I'll order them in ongoing, todo and done. Please sue
ctrl+fto find the device you are interested in.Testing the devices is not only flashing from stock and via sysupgrade, but sysupgrading from an old ar71xx image as well. You do not need to build an ar71xx image for this, as hanover has them available here and will provide you with access to its VPN infrastructure. If possible let us know when you're done with the key.
Testing will result in failures for some devices due to unhandled migrations for now.
Thanks for your help, Aiyion.
in progress
todo
@rotanid just showed me a (shorter?) list of devices to migrate, which includes tiny targets as well. I extracted the parts, where someone announced he would be willing to test the device. For now I wont update from that list on a regular basis, but just this once. If somebody wants to test a device, submit a PR draft to gluon and I'll update this accordingly. Thanks for the hint.
done
unlikely/wontfix
as tasklist for actual progress tracking
in progress
todo
done
wontfix