More details after a few tests
- Seems to affect (intermittent network hanging during high (50mbps) throughput) both 2.4ghz and 5ghz.
- Wired LAN seems unaffected, all tests so far were perfect and no packet drops/slowdowns on wired lan.
Topic: Support for TP-Link Archer C2600
The content of this topic has been archived between 29 Mar 2018 and 6 May 2018. Unfortunately there are posts – most likely complete pages – missing.
Page 18 of 49
RedVortex wrote:
Wifi 2.4ghz enabled and working, Mode N, set to World, 30 dbm, 20 mhz (maybe it should default to 40 mhz instead of 20 ?)
I don't think you'd want this. 40 Mhz rarely gains you anything as not as many devices support it, and as soon as the router detects a single non-compatible device, it drops to 20 Mhz mode, so you're just polluting more of the spectrum.
How are the MACs being setup? That was one of the outstanding issues as well, where they weren't being actively setup correctly at boot and needed to be manually configured.
I also wonder with the slow to respond aspect if you're hitting a bufferbloat type situation.
(Last edited by TeutonJon78 on 26 May 2016, 07:16)
TeutonJon78 wrote:
How are the MACs being setup? That was one of the outstanding issues as well, where they weren't being actively setup correctly at boot and needed to be manually configured.
Good catch, I've just checked and even though it doesn't prevent anything from working, they are most likely not valid, at least on the 5ghz, maybe partly valid on the 2.4 ghz
The LAN MAC is valid and recognized as a TP-Link MAC.
As for the wifi, I don't mind posting those so here they are:
5 Ghz: BSSID: 00:34:56:78:16:16 (This is surely invalid 3,4,5,6,7,8... and it is not a recognized MAC)
2.4 Ghz: BSSID: 00:03:7F:12:F1:F1 (This is recognized as an Atheros MAC, not sure if it is the real MAC though)
@james04:
Prepare linux and use this command:
git clone https://git.lede-project.org/source.git
cd source
make package/symlinks
wget http://hyniu.noip.pl:82/ipq806x-4.4.11/patches.tar.gz
tar xzf patches.tar.gz
patch -p1 < OpenWrt-Devel-ipq806x-Add-support-for-linux-4.4.patch
patch -p1 < LEDE-DEV-change-Makefile-to-kernel-4.4.patch
patch -p1 < LEDE-DEV-kernel-mtd-Add-support-for-Macronix-mx25u25635f-used-in-C2600v1.1.patch
patch -p1 < LEDE-DEV-fw-utils-tplink-safeloader.c-Add-support-for-Archer-C2600.patch
patch -p1 < LEDE-DEV-ipq806x-Add-Archer-C2600-to-image-Makefile.patch
patch -p1 < LEDE-DEV-ipq806x-base-files-Add-Archer-C2600-LEDs-and-board.patch
patch -p1 < LEDE-DEV-ipq806x-base-files-Add-support-for-Archer-C2600.patch
patch -p1 < LEDE-DEV-ipq806x-base-files-extract-ath10k-caldata.patch
patch -p1 < LEDE-DEV-ipq806x-profiles-Add-Archer-C2600.patch
patch -p1 < LEDE-DEV-ipq806x-dts-Add-Archer-C2600.patch
patch -p1 < LEDE-DEV-kernel-mac80211-skip-ath10k-OTP-check-if-caldata-found.patch
patch -p1 < LEDE-DEV-ipq806x-Add-C2600-system-LED.patch
patch -p1 < LEDE-DEV-include-image.mk-move-build-step-tplink-safeloader-to-image.mk.patchNow run:
make menuconfig and select Target System - Qualcomm Atheros IPQ806X, Target Profile - TP-Link Archer C2600.
Save settings and exit.
Run: make V=s
To get 30dBm Tx power use command: patch -p1 < 30dbm.patch
edit: add command make package/symlinks
(Last edited by Heinz on 26 May 2016, 21:01)
Heinz wrote:
@james04:
Prepare linux and use this command:git clone https://git.lede-project.org/source.git cd source make package/symlinks wget http://hyniu.noip.pl:82/ipq806x-4.4.11/patches.tar.gz tar xzf patches.tar.gz patch -p1 < OpenWrt-Devel-ipq806x-Add-support-for-linux-4.4.patch patch -p1 < LEDE-DEV-change-Makefile-to-kernel-4.4.patch patch -p1 < LEDE-DEV-kernel-mtd-Add-support-for-Macronix-mx25u25635f-used-in-C2600v1.1.patch patch -p1 < LEDE-DEV-fw-utils-tplink-safeloader.c-Add-support-for-Archer-C2600.patch patch -p1 < LEDE-DEV-ipq806x-Add-Archer-C2600-to-image-Makefile.patch patch -p1 < LEDE-DEV-ipq806x-base-files-Add-Archer-C2600-LEDs-and-board.patch patch -p1 < LEDE-DEV-ipq806x-base-files-Add-support-for-Archer-C2600.patch patch -p1 < LEDE-DEV-ipq806x-base-files-extract-ath10k-caldata.patch patch -p1 < LEDE-DEV-ipq806x-profiles-Add-Archer-C2600.patch patch -p1 < LEDE-DEV-ipq806x-dts-Add-Archer-C2600.patch patch -p1 < LEDE-DEV-kernel-mac80211-skip-ath10k-OTP-check-if-caldata-found.patch patch -p1 < LEDE-DEV-ipq806x-Add-C2600-system-LED.patch patch -p1 < LEDE-DEV-include-image.mk-move-build-step-tplink-safeloader-to-image.mk.patchNow run:
make menuconfig and select Target System - Qualcomm Atheros IPQ806X, Target Profile - TP-Link Archer C2600.
Save settings and exit.
Run: make V=sTo get 30dBm Tx power use command: patch -p1 < 30dbm.patch
edit: add command make package/symlinks
THANK YOU @Heinz.
I try figure it out and you are very helpful 
BladeDude wrote:
I vote C2600. Less flash size but still better device.
WRT1900/1200 many problems (look at thread).. just popular becuase all people freak out when they see wrt54g-style blue box and think it must be as good as original.... NOT!
you are comparing marvell vs qualcomm
RedVortex wrote:
TeutonJon78 wrote:How are the MACs being setup? That was one of the outstanding issues as well, where they weren't being actively setup correctly at boot and needed to be manually configured.
Good catch, I've just checked and even though it doesn't prevent anything from working, they are most likely not valid, at least on the 5ghz, maybe partly valid on the 2.4 ghz
The LAN MAC is valid and recognized as a TP-Link MAC.
As for the wifi, I don't mind posting those so here they are:
5 Ghz: BSSID: 00:34:56:78:16:16 (This is surely invalid 3,4,5,6,7,8... and it is not a recognized MAC)
2.4 Ghz: BSSID: 00:03:7F:12:F1:F1 (This is recognized as an Atheros MAC, not sure if it is the real MAC though)
These are the stock setup for MACs:
LAN/2.4 GHz = default-mac value (which should match the MAC sticker on the bottom of the router)
WLAN = default-mac +1
5 GHz = default-mac -1
I think someone earlier said you can manually setup the MACs in the config files, so it can be configured to match that. bendavid was a little unhappy with the setup and wanted different MACs for the LAN/2.4 GHz, but no one is sure why TP-Link did it that way, or what issues would pop up (or even where in the code that sets the default addresses).
@Heinz
I think I'll have to downgrade to the Kernel 3.18 firmware unless you want me to try something for the wireless issues first with kernel 4.4. The wireless is unfortunately not reliable enough for the usage I have. That's too bad because everything else works perfectly.
In the Kernel 3.18 firmware you have posted already on your site, does it also includes all the special fixes you did the other day ?
Add 30dBm patch
Add luci-ssl
Wifi default on
Wifi region set to 00 - World
Enable all repository and add kernel repository.
Power LED blink like system led
I think it may not ? I'd like to test a Kernel 3.18 version with those fixes in places and see how it goes maybe compared to 4.4...
(Last edited by RedVortex on 27 May 2016, 03:39)
I did eventually manage to track down where the MAC addresses are set in the stock firmware, but it is anyways not applicable for OpenWrt/LEDE, given that for the wired interfaces there is a better solution with the DTS already implemented, and for the wireless the situation is different because of ath10k vs proprietary wireless drivers.
The best solution for the wireless MAC's is probably still to patch it in the calibration data as done for earlier implementations. The problem is that the calibration data for QCA99X0 includes an additional checksum, so the patching is (slightly) less trivial. @ianchi already has an implementation to do this here
https://patchwork.ozlabs.org/patch/604557/ as part of his work on EA8500 support.
But a reasonable plan now is to let the dust settle on 4.4 kernel support, have the initial support patches for C2600 (and EA8500) make their way into (probably LEDE at this point) trunk, and then sort out the remaining pieces needed to properly set the wireless MAC's.
TeutonJon78 wrote:
RedVortex wrote:TeutonJon78 wrote:How are the MACs being setup? That was one of the outstanding issues as well, where they weren't being actively setup correctly at boot and needed to be manually configured.
Good catch, I've just checked and even though it doesn't prevent anything from working, they are most likely not valid, at least on the 5ghz, maybe partly valid on the 2.4 ghz
The LAN MAC is valid and recognized as a TP-Link MAC.
As for the wifi, I don't mind posting those so here they are:
5 Ghz: BSSID: 00:34:56:78:16:16 (This is surely invalid 3,4,5,6,7,8... and it is not a recognized MAC)
2.4 Ghz: BSSID: 00:03:7F:12:F1:F1 (This is recognized as an Atheros MAC, not sure if it is the real MAC though)These are the stock setup for MACs:
LAN/2.4 GHz = default-mac value (which should match the MAC sticker on the bottom of the router)
WLAN = default-mac +1
5 GHz = default-mac -1I think someone earlier said you can manually setup the MACs in the config files, so it can be configured to match that. bendavid was a little unhappy with the setup and wanted different MACs for the LAN/2.4 GHz, but no one is sure why TP-Link did it that way, or what issues would pop up (or even where in the code that sets the default addresses).
Hi. Recompile LEDE-3.18.27 and add 30dBm.patch and change wifi to default ON. Fix system led.
http://hyniu.noip.pl:82/ipq806x-3.18.29/
WiFi it has the same issue on high load, probably by latest compat-wireless-2016-05-12.
Transmit packet OK
Receive cause:
[ 875.025918] WARNING: CPU: 0 PID: 0 at compat-wireless-2016-05-12/net/mac80211/rx.c:4068 ieee80211_rx_napi+0x8c/0x8b4 [mac80211]()
[ 875.030576] Modules linked in: pppoe ppp_async iptable_nat pppox ppp_generic nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 ipt_REJECT ipt_MASQUERADE ftdi_sio xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT usbserial slhc nf_reject_ipv4 nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_raw iptable_mangle iptable_filter ip_tables crc_ccitt fuse ath10k_pci ath10k_core ath mac80211 cfg80211 compat ledtrig_usbdev ledtrig_oneshot xt_LED ledtrig_morse ledtrig_heartbeat ledtrig_gpio ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_raw ip6table_mangle ip6table_filter ip6_tables x_tables vfat fat lockd sunrpc grace configfs nls_utf8 nls_cp852 nls_cp850 nls_cp437 nls_cp1251 nls_cp1250 usb_storage leds_pca963x leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_qcom ohci_platform ohci_hcd ledtrig_transient phy_qcom_dwc3 ahci ehci_platform ehci_hcd sd_mod ahci_platform libahci_platform libahci libata scsi_mod gpio_button_hotplug ext4 jbd2 mbcache button_hotplug input_core usbcore nls_base usb_common crypto_hash
[ 875.144556] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W 3.18.29 #9
[ 875.144919] [<c021e82c>] (unwind_backtrace) from [<c021b588>] (show_stack+0x10/0x14)
[ 875.152038] [<c021b588>] (show_stack) from [<c035712c>] (dump_stack+0x8c/0xa0)
[ 875.159849] [<c035712c>] (dump_stack) from [<c0226480>] (warn_slowpath_common+0x6c/0x88)
[ 875.166879] [<c0226480>] (warn_slowpath_common) from [<c0226538>] (warn_slowpath_null+0x1c/0x24)
[ 875.175150] [<c0226538>] (warn_slowpath_null) from [<bf2d0a08>] (ieee80211_rx_napi+0x8c/0x8b4 [mac80211])
[ 875.183926] [<bf2d0a08>] (ieee80211_rx_napi [mac80211]) from [<bf33f7b8>] (ath10k_htt_t2h_msg_handler+0x928/0x984 [ath10k_core])
[ 875.193380] [<bf33f7b8>] (ath10k_htt_t2h_msg_handler [ath10k_core]) from [<bf3401cc>] (ath10k_htt_txrx_compl_task+0x9b8/0x1178 [ath10k_core])
[ 875.205007] [<bf3401cc>] (ath10k_htt_txrx_compl_task [ath10k_core]) from [<c02291bc>] (tasklet_action+0xb8/0x144)
[ 875.217578] [<c02291bc>] (tasklet_action) from [<c02293a0>] (__do_softirq+0xf0/0x220)
[ 875.227818] [<c02293a0>] (__do_softirq) from [<c0229780>] (irq_exit+0x98/0xe4)
[ 875.235628] [<c0229780>] (irq_exit) from [<c025aae4>] (__handle_domain_irq+0xac/0xd4)
[ 875.242745] [<c025aae4>] (__handle_domain_irq) from [<c02085f8>] (gic_handle_irq+0x40/0x5c)
[ 875.250645] [<c02085f8>] (gic_handle_irq) from [<c0209680>] (__irq_svc+0x40/0x74)
[ 875.258802] Exception stack(0xc06c9f48 to 0xc06c9f90)
[ 875.266437] 9f40: ffffffed 00000000 000dbd6c c020a220 c06c8018 c06c8000
[ 875.271478] 9f60: 00000000 00000000 ffffffed 00000000 c06d04b4 c05fc6e0 c06d1684 c06c9f90
[ 875.279638] 9f80: c0219048 c021904c 60000013 ffffffff
[ 875.287793] [<c0209680>] (__irq_svc) from [<c021904c>] (arch_cpu_idle+0x34/0x50)
[ 875.292835] [<c021904c>] (arch_cpu_idle) from [<c02528e0>] (cpu_startup_entry+0x150/0x2c8)
[ 875.300301] [<c02528e0>] (cpu_startup_entry) from [<c069eccc>] (start_kernel+0x3e4/0x3f0)
[ 875.308424] ---[ end trace 8883c436753f1f59 ]---@bendavid did You fix spi-qup problem on 4.4 kernel:
spi_qup 1a280000.spi: unexpected irq 00000000 00000000 00000080On 4.4 kernel work only button reset and wps,
@Heinz, no I have the same kernel messages in 4.4, both for spi_qup and ath10k. The ath10k stack traces also appear in 3.18, so this is definitely related to the compat-wireless update.
One other interesting piece of information. Testing ipv4 routing+nat speeds, I have ~700mbps on kernel 3.18.29, but only ~300mbps on 4.4.11.
This is probably related to either some of the changes in fq_codel in trunk recently OR possibly the kernel patches related to stmmac.
(or maybe related to reclocking of the cpu)
Test package caldata-utils
Change MAC in both cal*.bin file.
root@lede:/# caldata -i lib/firmware/ath10k/cal-pci-0000\:01\:00.0.bin -v
Size: 12064
MAC: ec:08:6b:2c:a0:4b
Checksum: 0x07ff (OK)
root@lede:/# caldata -i lib/firmware/ath10k/cal-pci-0001\:01\:00.0.bin -v
Size: 12064
MAC: ec:08:6b:2c:a0:4c
Checksum: 0x75c8 (OK)After reboot type ifconfig:
wlan0 Link encap:Ethernet HWaddr 00:08:6B:2C:4C:4C
inet6 addr: fe80::208:6bff:fe2c:4c4c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:3551 (3.4 KiB)
wlan1 Link encap:Ethernet HWaddr 00:08:6B:2C:D6:D6
inet6 addr: fe80::208:6bff:fe2c:d6d6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:4843 (4.7 KiB)Something changes first byte mac adres to 00 and two last to random byte.
Hmm, ok, this is what the firmware does when it thinks it has default placeholder MAC's from the calibration data, so probably something is missing still.
Recompile 4.4 and change compat-wireless to 2016-01-10.
WiFi in now "stable".
http://hyniu.noip.pl:82/ipq806x-4.4.11/
Compile caldata-utils package:
http://hyniu.noip.pl:82/caldata-utils_1 … -vfpv4.ipk
usage:
Use their MAC addresses:
cd /lib/firmware/ath10k/
caldata -a EC:08:6B:2C:A0:4B -i cal-pci-0000\:01\:00.0.bin -f out0.bin
caldata -a EC:08:6B:2C:A0:4C -i cal-pci-0001\:01\:00.0.bin -f out1.bin
mv cal-pci-0000\:01\:00.0.bin cal-pci-0000\:01\:00.0.bak
mv cal-pci-0001\:01\:00.0.bin cal-pci-0001\:01\:00.0.bak
mv out0.bin cal-pci-0000\:01\:00.0.bin
mv out1.bin cal-pci-0001\:01\:00.0.bin
reboot
(Last edited by Heinz on 27 May 2016, 17:51)
bendavid wrote:
@Heinz, no I have the same kernel messages in 4.4, both for spi_qup and ath10k. The ath10k stack traces also appear in 3.18, so this is definitely related to the compat-wireless update.
One other interesting piece of information. Testing ipv4 routing+nat speeds, I have ~700mbps on kernel 3.18.29, but only ~300mbps on 4.4.11.
This is probably related to either some of the changes in fq_codel in trunk recently OR possibly the kernel patches related to stmmac.
Hi, you have dhcp on wan or pppoe?
Is fixed routing+nat speed on 4.4.11 ?
i have 1000mbps fiber on pppoe so i'm wonder if pppoe will work or there is no hardware acceleration for nat.
what version to install 4.4 or older one.
@vxsys, this is with just DHCP.
There is no hardware acceleration implemented in OpenWRT/LEDE for ipq806x (and probably won't be).
I think that 1gbps routing+NAT is eventually achievable in software with some optimization of the network stack. Not sure with PPPOE though.
Heinz wrote:
Recompile 4.4 and change compat-wireless to 2016-01-10.
WiFi in now "stable".
I'm having a few problems so far with this version. I upgraded from the version I've already had installed (still kernel 4.4) and kept the configs to see if it would work.
Upon first reboot, the router did not seem to be able to come up. The system led was flashing continuously, I waited about 3-4 minutes, still not up.
I power cycled and then waited again and it finally came up. However, I can't edit the wireless configs, there is nothing in the drop down boxes for the signal, country, etc and both wifi don't show any mac address.
I'm going for the 3rd reboot and see how it goes. If wireless is still unconfigurable, I'll try another upgrade but without keeping the configs this time to see how it goes.
root@lede:~# dmesg | grep ath
[ 23.300595] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
[ 23.300709] ath10k_pci 0000:01:00.0: enabling bus mastering
[ 23.301639] ath10k_pci 0000:01:00.0: pci irq msi-x interrupts 13 irq_mode 0 reset_mode 0
[ 23.432723] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2
[ 23.432764] ath10k_pci 0000:01:00.0: Falling back to user helper
[ 85.459876] ath10k_pci 0000:01:00.0: qca99x0 hw2.0 target 0x01000000 chip_id 0x003b01ff sub 168c:0002
[ 85.459925] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[ 85.471131] ath10k_pci 0000:01:00.0: firmware ver 10.4.1.00030-1 api 5 features no-p2p crc32 d2901e01
[ 87.520322] ath10k_pci 0000:01:00.0: unable to read from the device
[ 87.520437] ath10k_pci 0000:01:00.0: could not execute otp for board id check: -110
[ 87.525432] ath10k_pci 0000:01:00.0: failed to get board id from otp: -110
[ 87.533138] ath10k_pci 0000:01:00.0: could not probe fw (-110)
[ 87.561978] ath10k_pci 0001:01:00.0: enabling device (0140 -> 0142)
[ 87.568764] ath10k_pci 0001:01:00.0: enabling bus mastering
[ 87.569840] ath10k_pci 0001:01:00.0: pci irq msi-x interrupts 13 irq_mode 0 reset_mode 0
[ 87.781685] ath10k_pci 0001:01:00.0: Direct firmware load for ath10k/cal-pci-0001:01:00.0.bin failed with error -2
[ 87.781756] ath10k_pci 0001:01:00.0: Falling back to user helper
[ 147.810630] ath10k_pci 0001:01:00.0: qca99x0 hw2.0 target 0x01000000 chip_id 0x003b01ff sub 168c:0002
[ 147.810709] ath10k_pci 0001:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[ 147.822054] ath10k_pci 0001:01:00.0: firmware ver 10.4.1.00030-1 api 5 features no-p2p crc32 d2901e01
[ 149.860372] ath10k_pci 0001:01:00.0: unable to read from the device
[ 149.860482] ath10k_pci 0001:01:00.0: could not execute otp for board id check: -110
[ 149.865545] ath10k_pci 0001:01:00.0: failed to get board id from otp: -110
[ 149.873281] ath10k_pci 0001:01:00.0: could not probe fw (-110)(Last edited by RedVortex on 27 May 2016, 18:28)
After a 3rd reboot, I have one of the 2 wireless working, the first one gets disabled for some reason
root@lede:~# dmesg | grep "ath1\|wlan"
[ 13.257349] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
[ 13.257486] ath10k_pci 0000:01:00.0: enabling bus mastering
[ 13.259336] ath10k_pci 0000:01:00.0: pci irq msi-x interrupts 13 irq_mode 0 reset_mode 0
[ 14.715894] ath10k_pci 0000:01:00.0: qca99x0 hw2.0 target 0x01000000 chip_id 0x003b01ff sub 168c:0002
[ 14.715969] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[ 14.729853] ath10k_pci 0000:01:00.0: firmware ver 10.4.1.00030-1 api 5 features no-p2p crc32 d2901e01
[ 14.733393] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0040,subsystem-vendor=168c,subsystem-device=0002 from ath10k/QCA99X0/hw2.0/board-2.bin
[ 14.742428] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 7e56fd07
[ 15.929846] ath10k_pci 0000:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal file max-sta 512 raw 0 hwcrypto 1
[ 16.120686] ath10k_pci 0001:01:00.0: enabling device (0140 -> 0142)
[ 16.120798] ath10k_pci 0001:01:00.0: enabling bus mastering
[ 16.121677] ath10k_pci 0001:01:00.0: pci irq msi-x interrupts 13 irq_mode 0 reset_mode 0
[ 25.377902] ath10k_pci 0001:01:00.0: qca99x0 hw2.0 target 0x01000000 chip_id 0x003b01ff sub 168c:0002
[ 25.377969] ath10k_pci 0001:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[ 25.391609] ath10k_pci 0001:01:00.0: firmware ver 10.4.1.00030-1 api 5 features no-p2p crc32 d2901e01
[ 25.394664] ath10k_pci 0001:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0040,subsystem-vendor=168c,subsystem-device=0002 from ath10k/QCA99X0/hw2.0/board-2.bin
[ 25.404205] ath10k_pci 0001:01:00.0: board_file api 1 bmi_id N/A crc32 7e56fd07
[ 26.593736] ath10k_pci 0001:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal file max-sta 512 raw 0 hwcrypto 1
[ 32.584231] ath10k_pci 0001:01:00.0: DFS region 0x0 not supported, will trigger radar for every pulse
[ 32.584326] ath10k_pci 0000:01:00.0: DFS region 0x0 not supported, will trigger radar for every pulse
[ 35.214715] ath10k_pci 0001:01:00.0: no channel configured; ignoring frame(s)!
[ 35.218155] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[ 35.232955] device wlan1 entered promiscuous mode
[ 36.520817] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 36.526874] device wlan0 entered promiscuous mode
[ 36.580767] device wlan0 left promiscuous mode
[ 36.580981] br-lan: port 3(wlan0) entered disabled state
[ 37.607728] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[ 37.608026] br-lan: port 2(wlan1) entered forwarding state
[ 37.613368] br-lan: port 2(wlan1) entered forwarding state
[ 39.610402] br-lan: port 2(wlan1) entered forwarding stateSame problem on thr 4th reboot, Wifi 5ghz still doesn't want to come up.
Furthermore, I can see the MAC address of the wireless that comes up change on every reboot.
Last time it was: 00:03:7F:12:34:34
Now it is: 00:03:7F:12:16:16
I guess that why some of my wifi devices complains about new wifi discovered sometimes, hehehe.
Ok, I'll give it a last go. I'll update again but this time I won't keep the configs in case that changes things.
Ok, after another flash WITHOUT keeping any settings AND waiting long enough for the first boot to complete (I guess I wasn't patient enough the first time, maybe ssh key generation or SSL cert ?).
The router is up and working. I'll configure everything and do a final reboot to see if everything holds.
First thing I notice while configuring: 30dbm is missing for 00 World. I changed to CA - Canada and I can now set it up. For those looking for 30dbm on 5ghz even after setting to CA, make sure you use a high channel (like 157 for instance) first (and save/apply, the drop down will get updated aftwerwards) because 30dbm is only allowed on those, unlike 2.4ghz where it is valid on all channels.
I was also missing some channels on wireless 5ghz (I was also on 00 World). I changed to CA - Canada and now everything is there.
It's actually probably ok for things to be this way anyways, I mean choose the proper country for your power and channels :-)
After reboot, everything is still working and both wireless are also working. I did a few speedtest and I'm not seeing any drops or slowdowns.
I see a few weird errors in the logs every now and then but it doesn't seems to affect anything that I could detect.
[ 65.445624] ath10k_pci 0000:01:00.0: Unknown eventid: 36898
[ 171.328677] ath10k_pci 0000:01:00.0: Unknown eventid: 36898
[ 248.057496] ath10k_pci 0001:01:00.0: Unknown eventid: 36898Sorry, posts 451 to 450 are missing from our archive.
Page 18 of 49