just update your firmware to the one of the latest available then you can install it directly from robimarko's feed repository (already included in build)
consider switching to the single partition layout first btw. it'll make your life easier.
It is one of last firmware from robimarko's and it is single partition but still I can not install zerotier or openvpn of missing in repository.
I believe you have to compile the image yourself, with some things like:
echo "CONFIG_PACKAGE_kmod-tun=y\n" >> .config
echo "CONFIG_PACKAGE_libstdcpp=y\n" >> .config
It must be the last one, not one of the last ones
ok thanks I will check it today.
On Dynalink, I noticed following about 2023/1/9 snapshot as compared to one from December (don't know exactly which):
- it's faster
- uses 2W more power
- wifi radios crash daily
How can I disable hardware acceleration?
[31509.010127] ath11k_warn: 115 callbacks suppressed
[31509.010148] ath11k c000000.wifi: failed to send WMI_VDEV_INSTALL_KEY cmd
[31509.013837] ath11k c000000.wifi: ath11k_install_key failed (-108)
[31509.020629] phy1-ap1: failed to remove key (0, f4:03:ff:09:c0:3c) from hardware (-108)
[31509.809116] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
[31509.809158] ath11k c000000.wifi: failed to send pdev bss chan info request
[31509.815854] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
[31509.822460] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
[31509.828966] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
[31509.835478] ath11k c000000.wifi: failed to submit beacon template command: -108
[31509.841647] ath11k c000000.wifi: failed to update bcn template: -108
[31509.848832] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
[31509.975793] phy1-ap1: HW problem - can not stop rx aggregation for f4:03:ff:09:c0:3c tid 0
[31509.975841] phy1-ap1: HW problem - can not stop rx aggregation for f4:03:ff:09:c0:3c tid 7
After the crash, when trying to restart both radios via Luci:
Sat Jan 14 22:41:28 2023 kern.warn kernel: [31831.427246] ath11k_warn: 51 callbacks suppressed
Sat Jan 14 22:41:28 2023 kern.warn kernel: [31831.427264] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sat Jan 14 22:41:28 2023 kern.warn kernel: [31831.430950] ath11k c000000.wifi: failed to send pdev bss chan info request
Sat Jan 14 22:41:28 2023 kern.warn kernel: [31831.438586] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Sat Jan 14 22:41:28 2023 kern.warn kernel: [31831.445211] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Sat Jan 14 22:41:28 2023 kern.warn kernel: [31831.451710] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Sat Jan 14 22:41:28 2023 kern.warn kernel: [31831.458219] ath11k c000000.wifi: failed to submit beacon template command: -108
Sat Jan 14 22:41:34 2023 kern.warn kernel: [31837.497626] ath11k_warn: 51 callbacks suppressed
Sat Jan 14 22:41:34 2023 kern.warn kernel: [31837.497646] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Sat Jan 14 22:41:34 2023 kern.warn kernel: [31837.501336] ath11k c000000.wifi: failed to send pdev bss chan info request
Sat Jan 14 22:41:34 2023 kern.warn kernel: [31837.508968] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Sat Jan 14 22:41:46 2023 kern.warn kernel: [31849.634534] ath11k_warn: 51 callbacks suppressed
Sat Jan 14 22:41:46 2023 kern.warn kernel: [31849.638242] ath11k c000000.wifi: failed to send pdev bss chan info request
Sat Jan 14 22:41:52 2023 kern.warn kernel: [31855.761539] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sat Jan 14 22:41:58 2023 kern.warn kernel: [31861.826967] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Sat Jan 14 22:45:18 2023 kern.warn kernel: [32062.051692] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Sat Jan 14 22:45:18 2023 kern.warn kernel: [32062.077403] ath11k c000000.wifi: failed to update bcn template: -108
Sat Jan 14 22:45:18 2023 kern.warn kernel: [32062.091163] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 1
Sat Jan 14 22:47:02 2023 daemon.notice hostapd: Remove interface 'phy0-ap0'
Sat Jan 14 22:47:02 2023 daemon.notice hostapd: phy0-ap0: interface state ENABLED->DISABLED
Sat Jan 14 22:47:02 2023 daemon.notice hostapd: phy0-ap0: AP-DISABLED
Sat Jan 14 22:47:02 2023 daemon.notice hostapd: phy0-ap0: CTRL-EVENT-TERMINATING
Sat Jan 14 22:47:02 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat Jan 14 22:47:02 2023 daemon.notice hostapd: nl80211: deinit ifname=phy0-ap0 disabled_11b_rates=0
Sat Jan 14 22:47:02 2023 daemon.notice netifd: Network device 'phy0-ap0' link is down
Sat Jan 14 22:47:02 2023 daemon.notice netifd: Wireless device 'radio0' is now down
Sat Jan 14 22:47:02 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy0.conf (phy phy0-ap0) --> new PHY
Sat Jan 14 22:47:02 2023 daemon.err hostapd: Could not set interface phy0-ap0 flags (UP): Cannot send after socket shutdown
Sat Jan 14 22:47:02 2023 daemon.err hostapd: nl80211: Could not set interface 'phy0-ap0' UP
Sat Jan 14 22:47:02 2023 daemon.notice hostapd: nl80211: deinit ifname=phy0-ap0 disabled_11b_rates=0
Sat Jan 14 22:47:02 2023 daemon.err hostapd: nl80211 driver initialization failed.
Sat Jan 14 22:47:02 2023 daemon.notice hostapd: phy0-ap0: CTRL-EVENT-TERMINATING
Sat Jan 14 22:47:02 2023 daemon.err hostapd: hostapd_free_hapd_data: Interface phy0-ap0 wasn't started
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): Command failed: ubus call hostapd config_add {"iface":"phy0-ap0", "config":"/var/run/hostapd-phy0.conf"} (Invalid argument)
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): Usage: ubus [<options>] <command> [arguments...]
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): Options:
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): -s <socket>: Set the unix domain socket to connect to
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): -t <timeout>: Set the timeout (in seconds) for a command to complete
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): -S: Use simplified output (for scripts)
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): -v: More verbose output
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): -m <type>: (for monitor): include a specific message type
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): (can be used more than once)
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): -M <r|t> (for monitor): only capture received or transmitted traffic
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022):
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): Commands:
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): - list [<path>] List objects
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): - call <path> <method> [<message>] Call an object method
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): - subscribe <path> [<path>...] Subscribe to object(s) notifications
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): - listen [<path>...] Listen for events
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): - send <type> [<message>] Send an event
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): - wait_for <object> [<object>...] Wait for multiple objects to appear on ubus
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): - monitor Monitor ubus traffic
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022):
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): Device setup failed: HOSTAPD_START_FAILED
Sat Jan 14 22:47:02 2023 daemon.notice netifd: Wireless device 'radio0' set retry=0
Sat Jan 14 22:47:02 2023 daemon.crit netifd: Wireless device 'radio0' setup failed, retry=0
Sat Jan 14 22:47:02 2023 daemon.notice netifd: Wireless device 'radio0' is now down
Sat Jan 14 22:47:07 2023 daemon.notice hostapd: Remove interface 'phy1-ap0'
Sat Jan 14 22:47:07 2023 daemon.notice hostapd: phy1-ap0: interface state ENABLED->DISABLED
Sat Jan 14 22:47:07 2023 daemon.notice hostapd: phy1-ap1: AP-DISABLED
Sat Jan 14 22:47:07 2023 daemon.notice hostapd: phy1-ap1: CTRL-EVENT-TERMINATING
Sat Jan 14 22:47:07 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat Jan 14 22:47:07 2023 daemon.notice netifd: Network device 'phy1-ap1' link is down
Sat Jan 14 22:47:07 2023 daemon.notice hostapd: nl80211: Failed to remove interface phy1-ap1 from bridge br-lan: No such device
Sat Jan 14 22:47:07 2023 daemon.notice hostapd: phy1-ap0: AP-DISABLED
Sat Jan 14 22:47:07 2023 daemon.notice hostapd: phy1-ap0: CTRL-EVENT-TERMINATING
Sat Jan 14 22:47:07 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sat Jan 14 22:47:07 2023 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Sat Jan 14 22:47:12 2023 daemon.notice netifd: Network device 'phy1-ap0' link is down
Sat Jan 14 22:47:12 2023 daemon.notice netifd: Wireless device 'radio1' is now down
Sat Jan 14 22:47:13 2023 daemon.notice hostapd: Configuration file: /var/run/hostapd-phy1.conf (phy phy1-ap0) --> new PHY
Sat Jan 14 22:47:13 2023 daemon.err hostapd: Could not set interface phy1-ap0 flags (UP): Cannot send after socket shutdown
Sat Jan 14 22:47:13 2023 daemon.err hostapd: nl80211: Could not set interface 'phy1-ap0' UP
Sat Jan 14 22:47:13 2023 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Sat Jan 14 22:47:13 2023 daemon.err hostapd: nl80211 driver initialization failed.
Sat Jan 14 22:47:13 2023 daemon.notice hostapd: phy1-ap0: CTRL-EVENT-TERMINATING
Sat Jan 14 22:47:13 2023 daemon.err hostapd: hostapd_free_hapd_data: Interface phy1-ap0 wasn't started
Sat Jan 14 22:47:13 2023 daemon.notice hostapd: phy1-ap1: CTRL-EVENT-TERMINATING
Sat Jan 14 22:47:13 2023 daemon.err hostapd: hostapd_free_hapd_data: Interface phy1-ap1 wasn't started
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): Command failed: ubus call hostapd config_add {"iface":"phy1-ap0", "config":"/var/run/hostapd-phy1.conf"} (Invalid argument)
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): Usage: ubus [<options>] <command> [arguments...]
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): Options:
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): -s <socket>: Set the unix domain socket to connect to
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): -t <timeout>: Set the timeout (in seconds) for a command to complete
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): -S: Use simplified output (for scripts)
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): -v: More verbose output
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): -m <type>: (for monitor): include a specific message type
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): (can be used more than once)
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): -M <r|t> (for monitor): only capture received or transmitted traffic
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174):
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): Commands:
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): - list [<path>] List objects
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): - call <path> <method> [<message>] Call an object method
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): - subscribe <path> [<path>...] Subscribe to object(s) notifications
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): - listen [<path>...] Listen for events
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): - send <type> [<message>] Send an event
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): - wait_for <object> [<object>...] Wait for multiple objects to appear on ubus
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): - monitor Monitor ubus traffic
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174):
Sat Jan 14 22:47:13 2023 daemon.notice netifd: radio1 (4174): Device setup failed: HOSTAPD_START_FAILED
Sat Jan 14 22:47:13 2023 daemon.notice netifd: Wireless device 'radio1' set retry=0
Sat Jan 14 22:47:13 2023 daemon.crit netifd: Wireless device 'radio1' setup failed, retry=0
Sat Jan 14 22:47:13 2023 daemon.notice netifd: Wireless device 'radio1' is now down
There is no HW acceleration
Is there anything I can tweak to see if it helps?
Is the second log showing luci bug?
Sat Jan 14 22:47:02 2023 daemon.notice hostapd: phy0-ap0: CTRL-EVENT-TERMINATING
Sat Jan 14 22:47:02 2023 daemon.err hostapd: hostapd_free_hapd_data: Interface phy0-ap0 wasn't started
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): Command failed: ubus call hostapd config_add {"iface":"phy0-ap0", "config":"/var/run/hostapd-phy0.conf"} (Invalid argument)
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): Usage: ubus [<options>] <command> [arguments...]
Sat Jan 14 22:47:02 2023 daemon.notice netifd: radio0 (4022): Options:
Not that I am aware, ath11k firmware panicked, we are kind of stuck until we can move off to 2.7 FW
If nothing has changed then it must be my new Amazon echo device causing it to crash more often. Looking forward to 2.7... hopefully it does happen soon 
Nothing has changed regarding ath11k, only the monitor mode was fixed and thats it.
@robimarko would it be possible to enable the ondemand governor even if is not the default (i know is schedutil) . This is so people who desire to switch to any of the other governors do so without the need to build their own setup.
thank you
1 Like
Did I miss any build config changes or something? I tried going from a compat 1.0 build to the latest one and softbricked the device. Reset via tftp, tried ubiformat from the chinese firmware, softbricked again. With the github release files everything works. Afterwards I tried sysupgrade from to github release to my build and it got bricked again. Tried dirclean and rebuild, no luck. Don't have a serial connection so I can't even look at the logs. Didn't have any issues in the past.
My diffconfig:
Have you seen the new requirement to ubiformat the initramfs version when starting out like this? This is different to before.
Procedure in Wiki: https://openwrt.org/inbox/toh/xiaomi/xiaomi_ax3600
I install version : Updated prebuilt images 2023-01-12-1631 and still the same problem
- Required dependency package libstdcpp6 is not available in any repository.
- Required dependency package kmod-tun is not available in any repository.
You need the LATEST version, that is no the latest one, there is one from yesterday
https://forum.openwrt.org/t/adding-openwrt-support-for-xiaomi-ax3600/55049/9596
https://forum.openwrt.org/t/adding-openwrt-support-for-xiaomi-ax3600/55049/9664
Yes, else I wouldn't be able to install the prebuild from github. But it's kinda weird that I can't even sysupgrade from that build to my own one, so I assumed maybe the layout change means I need to modify the build config in order for it to work.
See if it's this missing, I didn't tried it:
CONFIG_TARGET_PER_DEVICE_ROOTFS=y
https://github.com/robimarko/openwrt/releases/download/ipq807x-2023-01-14-1709/config.buildinfo
I'm on a single partition already, may I safely sysupgrade or should I do something beforehand?