btw, if you or anyone else does exhaustive tests comparing ath10k with ath10k-ct i would be very interested in seeing that data. we went for ath10k-ct mostly because "everyone else is doing it"... but it might not have been the right choice (as i already said, i no longer have access to one, so i can't test it myself)
2 Likes
I have not tested the LAN speeds on AC, only internet speeds, so it can be some WLAN-LAN passtrough issue also.
I gave a shot for basically all channel setings, speed never went over 250, so my first guess is driver limitation, the secound would be the passtrough.
Nevertheless, when we will get official support and opkg kmods available I'll do a deeper test run with both drivers, including LAN/N/AC speeds.
Dumb question don't laugh: factory driver couldn't be extracted and used under openwrt, right?
possibly... you'd want to monitor cpu usage to see if maybe the cpu is max'ing out, if so that might be your culprit.
just a heads-up: even when the PR gets integrated and openwrt officially supports the ac2350, it will be available as a snapshot and it's still going to be tricky to install kmods (since they're really build/compile specific, so the kernel from yesterday (or a few hours ago) won't work without re-upgrading the system)
the quick answer is: no. not if you mean "lets copy the kernel module from stock and use it"... stock is based on a much older kernel version. no chance.
while porting the MIR3P i spent quite a bit of time trying to build a "leaked" official wifi driver from mediatek (this is before openwrt had support for mt7615)... it worked, yeah. but it was utter shite. as soon as an open source driver became available i moved to it. i wouldn't recommend anyone trying.
i'd test WLAN/LAN speeds (they're the real measure of how the wifi driver is performing), and possibly try some tweaking if the speeds are a lot lower than expected.
having said that, that wasn't my experience.
Hi!
I saw in @eisaev 's PR that the IoT radio (QCA6006) is listed as unusable and that everything usb-related was removed from the dts. Firstly, does anyone know why the IoT radio is unusable? And secondly, shouldn't USB be included so the dts is complete and maybe in the future if we are able to use that radio another PR doesn't have to be made?
Hello, is there any way to upgrade kernel from 5.4.110-1-7aa47d49adc91ebadd72da084dba9632 to 5.4.128-1-b6998ccc799a5b3cc240af2c022b575b? I cannot install packages, but I need some. :S
Have you seen open source drivers for QCA6006?
I'm not sure if they're compatible with the QCA6006 but I found theese:
ath6k-firmware:
kmod-ath6kl: https://openwrt.org/packages/pkgdata/kmod-ath6kl
kmod-ath6kl-usb: https://openwrt.org/packages/pkgdata/kmod-ath6kl-usb
kmod-ath6kl-sdio:
https://openwrt.org/packages/pkgdata/kmod-ath6kl-sdio
So please click on two last links and read the description. Note that QCA != AR
Oh, ok. That's a shame. The third radio would be useful as a guest or IoT wifi.
What kind of speeds/performance is it possible to get out of the AIOT AC2350 with the current github image? is it stable enough for daily use?
from dmesg:
[ 35.560000] <6>ath6kl: 3VAP/1, P2P enable, concurrent on , with dedicate p2p-device, multi-channel-concurrent enable, p2p-compat disable, sta-p2p-ie removed, p2p_wise_scan enable
[ 35.600000] ath6kl: Get firmware ath6k/AR6006/hw1.1/bdata.bin !!
[ 35.600000] ath6kl: Get firmware ath6k/AR6006/hw1.1/fw.ram.bin !!
[ 35.610000] <6>ath6kl: target's subtype is 0x1, HT20-only 1SS Dual-band
[ 35.630000] <6>ath6kl: debugfs init 84a00000
[ 35.630000] ipaccount: ifname [wlan0] event[16]
[ 35.660000] ipaccount: ifname [wlan0] event[5]
[ 35.660000] <6>ath6kl: Create HTC cookie, type 1 num 1640, loc 0 0
[ 35.670000] <6>ath6kl: Create HTC cookie, type 2 num 66, loc 0 0
[ 35.670000] <6>ath6kl: RX aggregation drop disabled
[ 35.680000] <6>ath6kl: Using driver's regdb.
[ 37.070000] <6>ath6kl: MAC ADDRESS xx:xx:xx:xx:xx:xx
[ 37.070000] <6>ath6kl: ar6006 hw 1.1 usb fw 5.1.0.9999
[ 37.110000] <6>ath6kl: Create dedicated p2p interface
[ 37.110000] ipaccount: ifname [p2p0] event[16]
[ 37.120000] usbcore: registered new interface driver ath6kl_usb
https://git.rigado.com/vesta/linux-fslc-imx-4.1-1.0/blob/381aaa4daf725b00edbae72d5f8ccc2e059cd746/drivers/net/wireless/ath/ath6kl/core.h
Seems I was wrong. Sorry!
Does it work with the ath6k packages from openwrt? If not, how do I install the appropriate ones?
Info from wireless wiki, ar6006 is not even listed
https://wireless.wiki.kernel.org/en/users/drivers/ath6kl
the only reference that I could find that has ar6006 in it
https://git.rigado.com/vesta/linux-fslc-imx-4.1-1.0/blob/381aaa4daf725b00edbae72d5f8ccc2e059cd746/drivers/net/wireless/ath/ath6kl/core.h
any benchmarks on this device with the current snapshot?
Could someone please provide me the output of iwinfo on openwrt?
Also, could someone please confirm if this is correct on openwrt:
vlan1: eth0.1 LAN
vlan2: eth0.2 WAN
Could someone also please provide the output of cat /proc/mtd ?
Finally, sorry for all the edits , can someone give me a bootlog with openwrt installed?
Im setting up the wiki page for the ac2350 and need this info since i dont have access to my ac2350 at this time
1 Like
What do you think of the wiki page? Ive almost finished it and just need the info in the above post. [OpenWrt Wiki] Xiaomi AIoT Router AC2350
4 Likes
# iwinfo
wlan0 ESSID: "chome_5G"
Access Point: 88:C3:97:F1:26:16
Mode: Master Channel: 44 (5.220 GHz)
Center Channel 1: 42 2: unknown
Tx-Power: 20 dBm Link Quality: unknown/70
Signal: unknown Noise: -107 dBm
Bit Rate: unknown
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11nac
Hardware: 168C:0046 168C:CAFE [Qualcomm Atheros QCA9984]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy0
wlan1 ESSID: "chome"
Access Point: 88:C3:97:F1:26:17
Mode: Master Channel: 1 (2.412 GHz)
Center Channel 1: 1 2: unknown
Tx-Power: 20 dBm Link Quality: 58/70
Signal: -52 dBm Noise: -95 dBm
Bit Rate: 81.1 MBit/s
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11bgn
Hardware: 168C:0033 168C:9560 [Qualcomm Atheros QCA9560]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy1
This is correct.
# cat /proc/mtd
dev: size erasesize name
mtd0: 00030000 00010000 "Bootloader"
mtd1: 00010000 00010000 "Nvram"
mtd2: 00010000 00010000 "Bdata"
mtd3: 00010000 00010000 "crash"
mtd4: 00010000 00010000 "art"
mtd5: 00020000 00010000 "cfg_bak"
mtd6: 00170000 00010000 "overlay"
mtd7: 00e00000 00010000 "firmware"
mtd8: 00200000 00010000 "kernel"
mtd9: 00c00000 00010000 "rootfs"
mtd10: 00680000 00010000 "rootfs_data"
I'm sorry, but I have a build with usbcore enabled 
dmesg
2 Likes
Thank you! I will add this info to the wiki page.
Edit: info added
1 Like