Radio3 is designed only for low 5GHz channels, 36-64(or just 48? idk), see the antenna layout:
You can only select other channels if you replace BDF, but it will fail to start up. (at least in my case it was not working)
1 Like
Well, at least it's clear going forward that this won't work given the hardware limitation. Would there be a chance for radio1 to go into the 160MHz or is this also limited to 80MHz by hardware?
I don't remember clearly, but I think i've seen 160mhz option in stock firmware, so if it's present there, it should work.
This was so cool! Needle approach rocks. Box is still intact. Warranty in place.
3 Likes
hello good
I have a doubt if you can solve it for me.
What speed does this router get as a wireguard client?
New builds are located here instead. This has been changed since around 15 June.
1 Like
I have a problem with the latest builds, after installing, I try to update packages with opkg update and I get an error, I can only solve it by doing:
echo "nameserver 8.8.8.8" | tee -a /etc/resolv.conf
Although when I restart the router the problem returns, does anyone else experience this problem?
the https://github.com/quic/upstream-wifi-fw/tree/main/ath11k-firmware released yesterday both for the ipq8074 and qcn9074 the test firmware WLAN.HK.2.9.0.1-01832 with "Bug fixes, stability improvements from previous release are present" will be worth testing if there are any true improvements
2 Likes
I'm sure robi will update when he finds time but you might not notice any differences from the current version. Issue from last version that was later reverted is fixed now but that's all I noticed.
2 Likes
i posted my reply to @Soromeister upvote request ...the existing ath11k firmware is already using the quic upstream repo and version 2.9 ... my original posting was for people that are able to test the latest firmware to feedback on this forum and provide confidence to @robimarko to update the release
@Crect are you saying that WLAN.HK.2.9.0.1-01832 fixed the issue on 01713?
1 Like
Yes, interface stays up with the latest version. I've been using it for almost a day, as I currently need to build my own firmware amyway because of the vlan patch, and no issues so far
If you wanted to test with the official snapshot build, you could also just replace the firmware on the device and reboot.
2 Likes
If it doesnt crash like the previous point release then its rather easy to bump it
1 Like
i am using the latest firmware on the dynalink (also the ax9000) since it was posted with no issues i guess we may want more people testing it ...
as i have just seen now 23.05.0-rc1 (r23069-e2701e0f33) is out for the AX9000 as its a Release not a Snapshot, does it mean everything and all the hardware drivers are working now? i mean the fan is working and we no longer need to replace the BDF file for the lower band 5Ghz or what?
and is it better to use the Release or the Snapshot? i was thinking of using the Snapshot because it gets updated more frequently that the Release regardless of the potential bugs
Just tried updating to the release version, but it still shows SNAPSHOT in the luci interface. Any hints on what I'm doing wrong? I downloaded openwrt-23.05.0-rc1-ipq807x-generic-xiaomi_ax9000-squashfs-sysupgrade.bin and uploaded it in the web interface.
As far as I'm aware the fan isn't working still but mainly because it's really not an issue. That and it's a driver issue. The router works fine without it and I'm a pretty heavy WiFi user haven't noticed it running hot or anything. The BDF does still need to be replaced. But for me personally overall it's been very stable. I'm been running it since the day it was released (roughly June 9th) and haven't rebooted it until today.
I had to flash the update a few times before it would finally go through. So i'd give that a shot.
Please notice the file extension, it is not a tar file. Im not sure whether openwrt tar can handle the gzip files.
Looks like Attended Sysupgrade stopped to work after the target rename (https://github.com/openwrt/openwrt/commit/f02f6aaa8d4e1025ab4aa9f569123e57f689f4e5)
Is there a procedure how to fix it - I have some additional packages installed and configured?
2 Likes
1 Like