Fritzbox 4040 - 5GHz Network cannot be switched on

Cableghost · June 4, 2020, 12:58pm

For my part I have here an AVM Frtizbox4040 with OpenWRT 19.07.2 r10947-65030d81f3 / LuCI openwrt-19.07 branch git-20.057.55219-13dd17f.

The problem is, that one of the WLAN transmitters can not be switched on.
While the 2.4GHZ WLAN works, the 5GHZ one doesn't, it can't be switched on.

Under Network/Wireless the radio1 (Generic 802.11nac is set to "Device is not active".
The SSID shows "Wireless is not associated".

If I press the button "Restart", it says "Device is restarting" for a short time, but finally it shows "Device is not active" again.

The log shows the following:

Thu Jun  4 14:49:57 2020 daemon.notice netifd: radio1 (26211): command failed: Not supported (-95)
Thu Jun  4 14:49:57 2020 user.notice mac80211: Failed command: iw phy phy1 set distance 0
Thu Jun  4 14:49:57 2020 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf
Thu Jun  4 14:49:59 2020 kern.warn kernel: [31044.063998] ath10k_ahb a800000.wifi: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
Thu Jun  4 14:49:59 2020 kern.warn kernel: [31044.064050] ath10k_ahb a800000.wifi: msdu-desc: 2500  skid: 32
Thu Jun  4 14:49:59 2020 kern.info kernel: [31044.099575] ath10k_ahb a800000.wifi: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
Thu Jun  4 14:49:59 2020 kern.info kernel: [31044.100564] ath10k_ahb a800000.wifi: wmi print 'free: 56528 iram: 23400 sram: 32520'
Thu Jun  4 14:49:59 2020 kern.warn kernel: [31044.363123] ath10k_ahb a800000.wifi: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Thu Jun  4 14:49:59 2020 kern.info kernel: [31044.365065] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Thu Jun  4 14:49:59 2020 daemon.notice hostapd: wlan1: INTERFACE-ENABLED
Thu Jun  4 14:49:59 2020 kern.warn kernel: [31044.375988] ath10k_ahb a800000.wifi: peer-unmap-event: unknown peer id 0
Thu Jun  4 14:49:59 2020 daemon.notice hostapd: wlan1: INTERFACE-DISABLED
Thu Jun  4 14:49:59 2020 daemon.err hostapd: nl80211: Could not configure driver mode
Thu Jun  4 14:49:59 2020 daemon.notice hostapd: nl80211: deinit ifname=wlan1 disabled_11b_rates=0
Thu Jun  4 14:49:59 2020 daemon.err hostapd: nl80211 driver initialization failed.
Thu Jun  4 14:49:59 2020 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->DISABLED
Thu Jun  4 14:49:59 2020 daemon.notice hostapd: wlan1: AP-DISABLED
Thu Jun  4 14:49:59 2020 daemon.notice hostapd: wlan1: CTRL-EVENT-TERMINATING
Thu Jun  4 14:49:59 2020 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan1 wasn't started
Thu Jun  4 14:49:59 2020 daemon.notice netifd: radio1 (26211): cat: can't open '/var/run/wifi-phy1.pid': No such file or directory
Thu Jun  4 14:49:59 2020 daemon.notice netifd: radio1 (26211): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process  path (/proc/exe)
Thu Jun  4 14:49:59 2020 daemon.notice netifd: radio1 (26211): Command failed: Invalid argument
Thu Jun  4 14:49:59 2020 daemon.notice netifd: radio1 (26211): Device setup failed: HOSTAPD_START_FAILED

Does anyone have any idea how I can fix this?

Thank you already now for your help!

mk24 · June 4, 2020, 1:05pm

This is probably an incompatible radio setting. Set to defaults, except:

Change the country from blank to your 2-letter country code.
Set the channel to a specific channel that is allowed in your country, instead of "auto"
For initial testing, set bandwidth to VHT20 and use a non-DFS channel. Try wider bandwidth and/or DFS only after confirming proper basic operation.

Cableghost · June 4, 2020, 2:06pm

Thank you very much for your feedback.

Unfortunately I could not fix the error.

However, the extract from the log also points to another source of error.

mk24 · June 4, 2020, 2:09pm

The problem is that many such errors occur "normally" and the radio still works. So finding the one that is actually fatal can be difficult.

It looks like something happened with radio1 before the first line you posted as well. Maybe reboot and check the log all the way through on the first "clean" attempt to start up rather than stopping and restarting the radio.

aboaboit · June 4, 2020, 6:36pm

I am using the 4040 now with 19.07.3 but also with the previous version it was running just fine.

The suggestion from @mk24 to try a basic configuration is correct, if you feel like trying a "known working" configuration here is mine:

config wifi-device 'radio1'
        option type 'mac80211'
        option hwmode '11a'
        option path 'platform/soc/a800000.wifi'
        option htmode 'VHT80'
        option channel '124'
        option country 'IT'
        option txpower '13'
        option disabled '0'
        option legacy_rates '0'
        option beacon_int '1000'

Adjust the countrycode as required and keep in mind this is a DFS channel, so it will take one minute of radar scanning before the channel is cleared for use.

Cableghost · January 15, 2021, 1:05pm

In the meantime we have arrived at OpenWrt 19.07.5 r11257-5090152ae3 / LuCI openwrt-19.07and I still have the problem that I can't get the 5GHZ to run.

I can still turn on the wireless device and get "Wireless is not associated".

This is so disturbing, is there nothing you can do?

frollic · January 15, 2021, 1:16pm

I'm pretty sure that only means there are no devices connected to the WiFi.

Cableghost · January 15, 2021, 1:30pm

Unfortunately, it is not that simple after all.
The 5 GHZ network is not visible in any device. In fact, it is not activated.

Cableghost · March 28, 2021, 10:07am

The described problem has solved itself in an unknown way!

system · April 7, 2021, 10:07am

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.