Netgert R6100 can not find 802.11ac in Wireless Setting with 18.06,but 17.01.4 have,Please help
@jow Why didn't you bump kernel before the release?
sit is broken now in the 4.9 kernel. But upstream fix it long ago enough. Just the next kernel 4.9.112.
Lack of time. WIll happen with .1
Sorry，I don`t konw what dmesg is.But I find this in my Kernel Log.
[ 13.542380] PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
[ 13.548353] ath10k_pci 0000:00:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[ 13.820612] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:00:00.0.bin failed with error -2
[ 13.831507] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 13.994166] firmware ath10k!pre-cal-pci-0000:00:00.0.bin: firmware_loading_store: map pages failed
[ 14.003637] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/cal-pci-0000:00:00.0.bin failed with error -2
[ 14.014180] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 14.219926] firmware ath10k!cal-pci-0000:00:00.0.bin: firmware_loading_store: map pages failed
[ 14.229054] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2
[ 14.239953] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 14.442011] firmware ath10k!QCA988X!hw2.0!firmware-6.bin: firmware_loading_store: map pages failed
[ 14.467268] ath10k_pci 0000:00:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub 0000:0000
[ 14.476637] ath10k_pci 0000:00:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[ 14.491121] ath10k_pci 0000:00:00.0: firmware ver 10.2.4-1.0-00033 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 c41417d0
[ 14.577145] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[ 14.587785] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 14.694507] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[ 14.731020] ath10k_pci 0000:00:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[ 14.885766] ath10k_pci 0000:00:00.0: otp calibration failed: 2
[ 14.891724] ath10k_pci 0000:00:00.0: failed to run otp: -22
[ 14.897399] ath10k_pci 0000:00:00.0: could not init core (-22)
[ 14.903428] ath10k_pci 0000:00:00.0: could not probe fw (-22)
@Willen Thanks. I've ordered an R6100 now and will investigate once it arrived. Consider downgrading to LEDE 17.01.5 and wait until 18.06.1 for the issue to be fixed.
I found the same errors in my Archer C5, but everything is working as far as I could test.
[ 11.665601] PCI: Enabling device 0000:01:00.0 (0000 -> 0002)
[ 11.671536] ath10k_pci 0000:01:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[ 11.950693] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
[ 11.961577] ath10k_pci 0000:01:00.0: Falling back to user helper
[ 12.030559] firmware ath10k!pre-cal-pci-0000:01:00.0.bin: firmware_loading_store: map pages failed
[ 12.041724] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2
[ 12.052613] ath10k_pci 0000:01:00.0: Falling back to user helper
[ 12.198141] firmware ath10k!QCA988X!hw2.0!firmware-6.bin: firmware_loading_store: map pages failed
[ 12.211534] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[ 12.220927] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[ 12.233943] ath10k_pci 0000:01:00.0: firmware ver 10.2.4-1.0-00033 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 c41417d0
[ 12.330779] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[ 12.341413] ath10k_pci 0000:01:00.0: Falling back to user helper
[ 12.413818] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[ 12.423058] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[ 13.522272] ath10k_pci 0000:01:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
I upgraded from 17.01.5 in my wrt1900acs :
- install packages, everything ok, backup the config.
- reboot and the device was not accessible
- reset the device, it was 17.01.5.
- re flash 18.06, re install the packages, restore the backup config and same thing.
- device is not accessible.
i reset again, and now its 18.06.
i re installed the packages and manually i re config the network.
What's going on with the reboot ?
Thank you
wrt1900xxx series has dual firmware partitions. You always flash to the "other" partition, so that the current one (that you run when flashing) stays as the fallback option. If the new firmware fails, the router reverts to the old firmware.
I guess that something in your 17.01 config was not compatible with 18.06, so the boot failed. I can't remember if there are such things for wrt1900xxx series, but I do not remember seeing problems with my own wrt3200acm (but I haven't used the ancient 17.01 much for ages).
3 Likes
ok, thank you.
1 Like
I guess that something in your 17.01 config was not compatible with 18.06
After hours of reset, boot, reconfig from scratch, the only thing different i found is the upgrade added .1 and .2 to the interface name. Now its ok . Thanks.
So, then the network VLAN config for switch is different, and possibly some package misbehaved.
Apparently some settings got modified by the native upgrade, but then your backuped settings only partially contained the respective settings.
1 Like
I found that with 18.06.0, 5 GHz does work on my R6100, at least for a simple test of one AP with PSK2 encryption.
Lots of errors will normally appear in the kernel log during the loading of ath10k. But I get normal results of identifying the chip version and setting the country at the end which @Willen did not.
[ 13.121165] PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
[ 13.127131] ath10k_pci 0000:00:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
[ 13.400600] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:00:00.0.bin failed with error -2
[ 13.411499] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 13.573237] firmware ath10k!pre-cal-pci-0000:00:00.0.bin: firmware_loading_store: map pages failed
[ 13.582709] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/cal-pci-0000:00:00.0.bin failed with error -2
[ 13.593258] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 13.864807] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2
[ 13.875721] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 13.998146] firmware ath10k!QCA988X!hw2.0!firmware-6.bin: firmware_loading_store: map pages failed
[ 14.013421] ath10k_pci 0000:00:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub 0000:0000
[ 14.022844] ath10k_pci 0000:00:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[ 14.037295] ath10k_pci 0000:00:00.0: firmware ver 10.2.4-1.0-00033 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 c41417d0
[ 14.137157] ath10k_pci 0000:00:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
[ 14.147793] ath10k_pci 0000:00:00.0: Falling back to user helper
[ 14.256839] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
[ 14.293380] ath10k_pci 0000:00:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[ 15.409944] ath10k_pci 0000:00:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
[ 15.548527] ath: EEPROM regdomain: 0x0
[ 15.548536] ath: EEPROM indicates default country code should be used
[ 15.548540] ath: doing EEPROM country->regdmn map search
[ 15.548554] ath: country maps to regdmn code: 0x3a
[ 15.548560] ath: Country alpha2 being used: US
[ 15.548564] ath: Regpair used: 0x3a
Will there be a generic release for tl-wr841 or is tiny all it will be getting from now on?
Is it ok to do a sysupgrade to tiny from an older generic? Does the tiny build lack anything that was in the old generic?
You can sysupgrade to tiny. I didn't notice any change regarding limitations. 18.06 firmware is small enough, because some packages are built with LTO.
@Willen - may R6100 arrived today. I flashed it with the 18.06.0 release right away and unfortunately cannot reproduce the 5GHz radio issue 
Hey, which firmware did you use to do this? How has performance been since upgrading?
@lleachii you should change topic title:
according to countless issues i've read about during past few days 18.06 is everything just not stable release.....
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.