I have installed the version r0-964130e in the AX3600. I cannot update it with luci on the newest version. Tried about 10 times. It seems, that the new version does not load. Can anyone help me ?
I also updated (from your version to the last one) and it works.
Try this way:
https://forum.openwrt.org/t/adding-openwrt-support-for-xiaomi-ax3600/55049/9151
i test with ea3e7af
i changed all files here "/lib/firmware/IPQ8074" with "https://github.com/kvalo/ath11k-firmware/tree/master/IPQ8074/hw2.0/2.7.0.1/WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1"
Log after boot
Wed Dec 14 17:17:25 2022 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Wed Dec 14 17:17:25 2022 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy1.conf (phy phy1-ap0) --> new PHY
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] qcom-q6v5-wcss-pil cd00000.q6v5_wcss: fatal error received:
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] QC Image Version: QC_IMAGE_VERSION_STRING=WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] Image Variant : IMAGE_VARIANT_STRING=8074.wlanfw.eval_v2Q
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036]
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] :Excep :0 Exception detectedparam0 :zero, param1 :zero, param2 :zero.
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] Thread ID : 0x00000069 Thread name : WLAN RT0 Process ID : 0
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] Register:
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] SP : 0x4bfacdc0
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] FP : 0x4bfacdd8
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] PC : 0x4b18d338
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] SSR : 0x00000001
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] BADVA : 0x009c9d7e
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] LR : 0x4b18d2b8
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036]
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] Stack Dump
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] from : 0x4bfacdc0
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036] to : 0x4bfad400
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.718036]
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.764626] remoteproc remoteproc0: crash detected in cd00000.q6v5_wcss: type fatal error
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.786865] remoteproc remoteproc0: handling crash #1 in cd00000.q6v5_wcss
Wed Dec 14 17:17:25 2022 daemon.info dnsmasq[1]: read /etc/hosts - 4 addresses
Wed Dec 14 17:17:25 2022 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses
Wed Dec 14 17:17:25 2022 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 14.795032] remoteproc remoteproc0: recovering cd00000.q6v5_wcss
Wed Dec 14 17:17:25 2022 kern.info kernel: [ 14.827769] remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcss
Wed Dec 14 17:17:25 2022 kern.warn kernel: [ 14.827962] ath11k c000000.wifi: failed to find peer 9c:9d:7e:75:d9:fd on vdev 1 after creation
Wed Dec 14 17:17:25 2022 kern.warn kernel: [ 14.834083] ath11k c000000.wifi: failed to find peer vdev_id 1 addr 9c:9d:7e:75:d9:fd in delete
Wed Dec 14 17:17:25 2022 kern.warn kernel: [ 14.842519] ath11k c000000.wifi: failed peer 9c:9d:7e:75:d9:fd delete vdev_id 1 fallback ret -22
Wed Dec 14 17:17:25 2022 kern.warn kernel: [ 14.851195] ath11k c000000.wifi: failed to vdev 1 create peer for AP: -2
Wed Dec 14 17:17:25 2022 kern.warn kernel: [ 14.860221] ath11k c000000.wifi: failed to submit WMI_VDEV_DELETE_CMDID
Wed Dec 14 17:17:25 2022 kern.warn kernel: [ 14.866889] ath11k c000000.wifi: failed to delete WMI vdev 1: -108
Wed Dec 14 17:17:25 2022 kern.err kernel: [ 15.074971] ath11k c000000.wifi: failed to clear rx_filter for monitor status ring: (-108)
Wed Dec 14 17:17:25 2022 daemon.notice netifd: Wireless device 'radio2' is now up
Wed Dec 14 17:17:26 2022 daemon.err hostapd: Could not set interface phy1-ap0 flags (UP): No such file or directory
Wed Dec 14 17:17:26 2022 daemon.err hostapd: nl80211: Could not set interface 'phy1-ap0' UP
Wed Dec 14 17:17:26 2022 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Wed Dec 14 17:17:26 2022 daemon.err hostapd: nl80211 driver initialization failed.
Wed Dec 14 17:17:26 2022 daemon.notice hostapd: phy1-ap0: CTRL-EVENT-TERMINATING
Wed Dec 14 17:17:26 2022 daemon.err hostapd: hostapd_free_hapd_data: Interface phy1-ap0 wasn't started
Wed Dec 14 17:17:26 2022 daemon.notice netifd: Wireless device 'radio1' set retry=0
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): Command failed: ubus call hostapd config_add {"iface":"phy1-ap0", "config":"/var/run/hostapd-phy1.conf"} (Invalid argument)
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): Usage: ubus [<options>] <command> [arguments...]
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): Options:
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): -s <socket>: Set the unix domain socket to connect to
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): -t <timeout>: Set the timeout (in seconds) for a command to complete
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): -S: Use simplified output (for scripts)
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): -v: More verbose output
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): -m <type>: (for monitor): include a specific message type
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): (can be used more than once)
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): -M <r|t> (for monitor): only capture received or transmitted traffic
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604):
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): Commands:
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): - list [<path>] List objects
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): - call <path> <method> [<message>] Call an object method
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): - subscribe <path> [<path>...] Subscribe to object(s) notifications
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): - listen [<path>...] Listen for events
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): - send <type> [<message>] Send an event
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): - wait_for <object> [<object>...] Wait for multiple objects to appear on ubus
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): - monitor Monitor ubus traffic
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604):
Wed Dec 14 17:17:26 2022 daemon.notice netifd: radio1 (2604): Device setup failed: HOSTAPD_START_FAILED
Wed Dec 14 17:17:26 2022 daemon.crit netifd: Wireless device 'radio1' setup failed, retry=0
Wed Dec 14 17:17:26 2022 daemon.notice netifd: Wireless device 'radio1' is now down
so wifi is down...
Thank you - that it was !
Robi and all orhers: many thanks für your work. I follow this thread since over 2 yers. hence, there where patches that did work or not in a period form weeks, now we get new patches in few days. sometimes several patches in one day. My question is: how far are we away form official openwrt support or, same question but in other words: what are the main differences betwenn this prereleases and official support ?
I have noticed drastic speed reduction since installing openwrt on both wifi and ethernet.
The reported bitrate on wireless is ~1200mbit for most of my devices on 160mhz ax
All tests towards speedtest have given me ~500 down and 500-600mbit up since installing openwrt
With the original firmware I was able to get constant 960-970 down and 960-970 upload. My line is a 2.5gbit/1gbit and is setup like this:
fiber -> ont 2.5gbit -> ax3600 gigabit -> vlan -> pppoe -> bridge to lan
I am open to running any tests if necessary as long as they do not interrupt my internet access.
I should also note that I am running OpenWrt SNAPSHOT r0-a56980f / LuCI Master git-22.325.41248-fa17c15 (sorry, could not find a link to it) because I do not know if and how I should upgrade.
I want a system that is as stable as possible with as many features as possible while having the configuration options of openwrt
The details about this have been discussed in this thread, yes it's long, but it's all in there (in short, no NSS offloading, not going to happen).
Then you picked the wrong hardware and need something (much) faster.
2 Likes
Today's build, r0-302893d, added about 100Mbps to the fastest wireless speed test I've had! I also changed channels after I flashed it, so that could be a factor as well.
Either way, WOOO HOO. 
How exactly can 2.7 be tested? Doesn't it require a regdb blob anymore for the firmware to initialize?
no issues with the new board-2.bin + 2.7 firmware on the dynalink & qnap
no ... you either change the ath11k Makefile (package/firmware/ath11k-firmware/Makefile) to point to the 2.7 kvalo repo or just copy the files from his repo to tyour router
check the posting from @stixi above
If you mean that post, then yeah I saw it but the log obviously indicates it's not working
1 Like
@tiagogaspar8 I am now resyncing the ipq807x with the ath11k from the PR and so I had to drop the encap/decap enablement by default.
They are not liking it as long as its breaking WDS, has anybody reported this issue upstream so far?
It's exactly what @slh said, still you can improve your (PPoE) speed with these in luci gui:
luci->network->firewall->
Software flow offloading = Enable.
Hardware flow offloading = Disable.
luci->network->interfaces->global network options->
Packet Steering=Enable (Had to reboot after changing Enable or Disable to take effect).
I read that there are a few more tweaks that help PPoE speed:
Changing governor to ondemand or even performance.
IRQ tweaks.
Search this thread for @dchard posts, you'll find the details and his speed tests with PPoE.
2 Likes
And finally managed to update the Github actions to get rid of the warnings and non-maintained workflows.
It also took a while to get the new release action working so it would actually post it as the latest release and not just hide it.
5 Likes
I update to the latest sources and self compiled it, after I flash the firmware, I got bootloop.
no ... there is a new board-2.bin on kvalo repo indeed but I haven't changed the build process that I understand uses ipq-wifi Makefile. There are separate board files for each device.
I guess it was a PITA considering all the changes
PITA is testing the workflow as it takes a while