Forums

Cannot connect to 2.4GHZ on one of my AX1800 running v2.8.6

• Author
  Posts
• January 12, 2026 at 7:43 pm #7119
  bugsby

  Participant

  I have two AX1800 and both are now updated to v2.8.6. The main router is working same as before, no issue. The AP mode router can now save updates to the Network settings page, which was getting an “Internal Server Error” before, so that was fixed.

  The new issue for the AP is no device could connect to 2.4 Ghz SSIDs on any VLAN. I tried them all – LAN, Guest, X1, etc. – and even after factory reset I cannot connect to the default unsecured pcwrt-2g network to access the initial setup. I must connect to the pcwrt-5g, which works fine. So, this must not be a config related problem.

  When trying to connect, the System Log shows the message “did not acknowledge authentication response” as if it were a client issue, but those same devices have no problem connecting to the same 2.4 Ghz SSIDs with the same settings on my main router.

  Of course not being able to have a functional 2.4 Ghz band on the AP is preventing the new mesh feature from fully working. If I enable only 5 Ghz, the mesh pairs and I can see wireless devices from the AP on the main router status page. No longer shows just “Wired” which is nice.

  Not sure where it went wrong. It was upgraded while in AP mode on v2.8.1.

  January 12, 2026 at 11:16 pm #7120
  bugsby

  Participant

  I rolled the AP back to v2.8.1 and still had the same issue. Factory reset again and still the same.

  Then I found these messages in the system log, so it appears there is a driver issue?

  “Direct firmware load for ath11k/IPQ6018/hw1.0/board-2.bin failed with error -2”
  “connect_wifi_sta: radio0(mac80211) is not supported”
  “connect_wifi_sta: radio1(mac80211) is not supported”

  11/17 16:18:12 kern.info kernel: [ 10.024024] xt_time: kernel timezone is -0000
  11/17 16:18:12 kern.err kernel: [ 15.504459] ath11k c000000.wifi: Not multipd architecture
  11/17 16:18:12 kern.info kernel: [ 15.504964] ath11k c000000.wifi: ipq6018 hw1.0
  11/17 16:18:12 kern.info kernel: [ 15.509118] ath11k c000000.wifi: qmi target mem mode 2
  11/17 16:18:12 kern.info kernel: [ 15.513273] remoteproc remoteproc0: powering up cd00000.qcom_q6v5_wcss
  11/17 16:18:12 kern.info kernel: [ 15.545665] remoteproc remoteproc0: Booting fw image IPQ6018/q6_fw.mdt, size 7340
  11/17 16:18:12 kern.info kernel: [ 16.846738] Subsystem error monitoring/handling services are up
  11/17 16:18:12 kern.info kernel: [ 16.847078] remoteproc remoteproc0: remote processor cd00000.qcom_q6v5_wcss is now up
  11/17 16:18:12 kern.info kernel: [ 16.847333] rpmsg_dev_probe: No pm domain
  11/17 16:18:12 kern.info kernel: [ 16.847610] rpmsg_dev_probe: No pm domain
  11/17 16:18:12 kern.info kernel: [ 16.847812] qcom,cpr4-apss-regulator b018000.cpr4-ctrl: CPR valid fuse count: 4
  11/17 16:18:12 kern.info kernel: [ 16.848561] qcom,cpr4-apss-regulator b018000.cpr4-ctrl: CPR valid fuse count: 4
  11/17 16:18:12 kern.err kernel: [ 16.848806] diag: In diag_send_feature_mask_update, control channel is not open, p: 2, 8187abec
  11/17 16:18:12 kern.info kernel: [ 16.849584] ath11k c000000.wifi: chip_id 0x0 chip_family 0x4 board_id 0xff soc_id 0xffffffff
  11/17 16:18:12 kern.info kernel: [ 16.849592] ath11k c000000.wifi: fw_version 0x2506844c fw_build_timestamp 2021-07-13 11:09 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HK.2.5.0.1-01100-QCAHKSWPL_SILICONZ-1

  11/17 16:18:12 kern.warn kernel: [ 16.851636] ath11k c000000.wifi: Direct firmware load for ath11k/IPQ6018/hw1.0/board-2.bin failed with error -2

  11/17 16:18:12 kern.warn kernel: [ 16.851642] ath11k c000000.wifi: Falling back to user helper
  11/17 16:18:12 kern.info kernel: [ 16.926287] qcom,cpr4-apss-regulator b018000.cpr4-ctrl: CPR valid fuse count: 4
  11/17 16:18:12 user.info kernel: [ 16.928723] kmodloader: done loading kernel modules from /etc/modules.d/*
  11/17 16:18:12 kern.err kernel: [ 16.954848] firmware ath11k!IPQ6018!hw1.0!board-2.bin: firmware_loading_store: map pages failed
  11/17 16:18:12 kern.info kernel: [ 16.962019] ath11k c000000.wifi: qmi caldata downloaded: type: 2
  11/17 16:18:12 kern.warn kernel: [ 17.093898] applying ath11k-macs
  11/17 16:18:12 daemon.notice procd: /etc/rc.d/S13openssl: Generating engines.cnf
  11/17 16:18:13 daemon.notice procd: /etc/rc.d/S16qca-ssdk:
  11/17 16:18:13 daemon.notice procd: /etc/rc.d/S16qca-ssdk: starting
  11/17 16:18:13 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
  11/17 16:18:13 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
  11/17 16:18:13 daemon.notice procd: /etc/rc.d/S19dnsmasq: uci: Entry not found
  11/17 16:18:14 daemon.info dnsmasq[1050]: Connected to system UBus
  11/17 16:18:14 daemon.info dnsmasq[1050]: started, version 2.85 DNS disabled
  11/17 16:18:14 daemon.info dnsmasq[1050]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC no-ID loop-detect inotify dumpfile
  11/17 16:18:14 daemon.info dnsmasq[1050]: UBus support enabled: connected to system bus
  11/17 16:18:14 authpriv.info dropbear[1112]: Not backgrounding
  11/17 16:18:14 daemon.notice procd: /etc/rc.d/S19firewall: tail: can’t open ‘/var/lock/fw3.lock’: No such file or directory
  11/17 16:18:14 daemon.notice procd: /etc/rc.d/S19firewall: tail: no files
  11/17 16:18:15 daemon.notice wpa_supplicant[1209]: Successfully initialized wpa_supplicant
  11/17 16:18:24 user.notice : Added device handler type: bonding
  11/17 16:18:24 user.notice : Added device handler type: 8021ad
  11/17 16:18:24 user.notice : Added device handler type: 8021q
  11/17 16:18:24 user.notice : Added device handler type: macvlan
  11/17 16:18:24 user.notice : Added device handler type: veth
  11/17 16:18:24 user.notice : Added device handler type: bridge
  11/17 16:18:24 user.notice : Added device handler type: Network device
  11/17 16:18:24 user.notice : Added device handler type: tunnel

  11/17 16:18:26 daemon.notice procd: /etc/init.d/network: connect_wifi_sta: radio0(mac80211) is not supported
  11/17 16:18:26 daemon.notice procd: /etc/init.d/network: connect_wifi_sta: radio1(mac80211) is not supported

  11/17 16:18:26 kern.info kernel: [ 36.264015] device eth3 entered promiscuous mode
  11/17 16:18:26 daemon.notice netifd: Interface ‘lan’ is enabled
  11/17 16:18:26 daemon.notice netifd: Interface ‘lan’ is setting up now
  11/17 16:18:26 daemon.notice netifd: Interface ‘lan’ is now up

  January 13, 2026 at 8:20 pm #7121
  bugsby

  Participant

  Well, I’m seeing the exact same errors in the above log on the main AX1800 router as well, which is not having any connectivity issues. So, I suppose those errors aren’t related to this specific wireless problem in the AP. Are those normal errors? Same as on the AP, there are several other kern.warn and kern.err messages as well, but the main router has been functioning fine and I’ve never bothered to review the boot log before now.

  If firmware rollback, factory reset and upgrading again have all had no effect on restoring 2.4 GHz, would this just be a hardware issue?

• Author
  Posts