5ghz Linksys 1900AC - command failed: Not supported

Installing and Using OpenWrt
1

Hi all,
New OpenWrt user on a Linksys 1900AC. The 5ghz radio seems to have some kind of issues. It seems to only come up after a reboot...and for any restart of the interface or config changes I get this in the logs. Doesn't seem to matter what mode n,ac, or channels/width I select.

Sun Dec 22 07:20:16 2019 user.notice mac80211: Failed command: iw phy phy1 set antenna all all
Sun Dec 22 07:20:16 2019 daemon.notice netifd: radio1 (18143): command failed: Not supported (-95)
Sun Dec 22 07:20:16 2019 user.notice mac80211: Failed command: iw phy phy1 set distance 0
Sun Dec 22 07:20:16 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf
Sun Dec 22 07:20:16 2019 kern.debug kernel: [37045.633246] ieee80211 phy1: change: 0xffffffff
Sun Dec 22 07:20:17 2019 daemon.notice hostapd: wlan1: INTERFACE-ENABLED
Sun Dec 22 07:20:17 2019 kern.info kernel: [37045.748647] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Sun Dec 22 07:20:17 2019 daemon.notice hostapd: wlan1: INTERFACE-DISABLED
Sun Dec 22 07:20:17 2019 daemon.err hostapd: nl80211: Could not configure driver mode
Sun Dec 22 07:20:17 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan1 disabled_11b_rates=0
Sun Dec 22 07:20:17 2019 daemon.err hostapd: nl80211 driver initialization failed.
Sun Dec 22 07:20:17 2019 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->DISABLED
Sun Dec 22 07:20:17 2019 daemon.notice hostapd: wlan1: AP-DISABLED
Sun Dec 22 07:20:17 2019 daemon.notice hostapd: wlan1: CTRL-EVENT-TERMINATING
Sun Dec 22 07:20:17 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan1 wasn't started
Sun Dec 22 07:20:17 2019 daemon.notice netifd: radio1 (18143): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 4898 path ()
Sun Dec 22 07:20:17 2019 daemon.notice netifd: radio1 (18143): Device setup failed: HOSTAPD_START_FAILED

2

Can you share your wireless config file here, please?

3

I have removed the SSIDs and keys only.

cat /etc/config/wireless

config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11g'
option path 'soc/soc:pcie@82000000/pci0000:00/0000:00:02.0/0000:02:00.0'
option htmode 'HT20'
option country 'NZ'
option legacy_rates '1'
option channel '13'

config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option macaddr '94:10:3e:1a:40:e7'
option encryption 'psk2'
option key
option ssid

config wifi-device 'radio1'
option type 'mac80211'
option hwmode '11a'
option path 'soc/soc:pcie@82000000/pci0000:00/0000:00:03.0/0000:03:00.0'
option country 'NZ'
option legacy_rates '1'
option htmode 'VHT80'
option channel '104'

config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option macaddr '94:10:3e:1a:40:e8'
option ssid
option key
option encryption 'psk2'

config wifi-iface
option device 'radio0'
option mode 'ap'
option ssid
option encryption 'psk2'
option key
option network 'guest'

4

If you're not using a DFS channel, does it work fine?
E.g. 36

2 Likes
5

Please run the following command:

cat /dev/mtd3 | grep cert_

If you still want to use a DFS channel (Channels 52-144), option country must match the output of the above command.

mwlwifi only supports DFS when you're running the following regdomains (extracted from core.c):

static const struct region_code_mapping regmap[] = {
	{"US", 0x10}, /* US FCC */
	{"CA", 0x20}, /* Canada */
	{"FR", 0x30}, /* EU */
	{"ES", 0x31}, /* Spain  */
	{"FR", 0x32}, /* France */
	{"JP", 0x40}, /* Japan  */
	{"TW", 0x80}, /* Taiwan */
	{"AU", 0x81}, /* Australia */
	{"CN", 0x90}, /* China (Asia) */
};

WARNING: Keep in mind that mwlwifi is very unstable on DFS as these devices were never certified to operate on these channels with the open source driver or the OEM firmware (excluding the WRT3200/WR32X).

6

Selecting channel 36 or another DFS channel and restarting the radio, results in the same log entries and failures. It seems that once there is a failure, only a reboot will restore the operation again. Without using any security at all I can seem to get it to work more reliably...making me wonder if the hostapd error has anything to do with this. (or perhaps it's just a failure as a consequence of the earlier failure to set the radio up...( radio1 (18143): command failed: Not supported (-95))

7

Thanks.

 cat /dev/mtd3 | grep cert_

cert_region=EU

I see exactly the same error regardless of what channel I set...

8

Change option country from NZ to FR or DE. Also change the channel to 36. Then run wifi down; sleep 5; wifi up.

9

Did this and thanks. However no change. Exactly the same error. wifi status on radio1 shows down....

10

Everything works following a reboot. I am on country code DE rather than NZ...and have been testing with DFS CH 52

"Mon Dec 23 12:33:48 2019 user.notice mac80211: Failed command: iw phy phy1 set antenna all all
Mon Dec 23 12:33:48 2019 daemon.notice netifd: radio1 (5746): command failed: Not supported (-95)
"
This happens if it works or doesn't work...so probably unrelated.

What I don't have when things are working is the "Device setup failed: HOSTAPD_START_FAILED"

Seems as if the country code NZ + DFS channels was causing something to get stuck that only a reboot could solve.

11

Glad to hear it's working with the regdomain change.

The following errors can be ignored. They're harmless chatty shell command outputs meant for other devices. I also see them too.

Mon Dec 23 12:33:48 2019 user.notice mac80211: Failed command: iw phy phy1 set antenna all all
Mon Dec 23 12:33:48 2019 daemon.notice netifd: radio1 (5746): command failed: Not supported (-95)

Yeah that is a severe issue when you see that in the log.

If we have solved your problem, please mark the solution so that this thread may be archived.

12

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