Has anyone had experience with settings like these ...
CONFIG_EXTRA_BINUTILS_CONFIG_OPTIONS="--enable-lto --enable-plugins --enable-threads "
CONFIG_EXTRA_GCC_CONFIG_OPTIONS="--with-cpu-64=cortex-a53+crc+crypto+rdma --with-isl --enable-lto "
CONFIG_EXTRA_OPTIMIZATION="-fno-caller-saves -fno-plt -mcpu=cortex-a53+crc+crypto+rdma -Wa,-mcpu=cortex-a53+crc+crypto+rdma"
CONFIG_KERNEL_CFLAGS="-O2 -pipe -mcpu=cortex-a53+crc+crypto+rdma -Wa,-mcpu=cortex-a53+crc+crypto+rdma"
CONFIG_TARGET_OPTIMIZATION="-O3 -pipe -mcpu=cortex-a53+crc+crypto+rdma -Wa,-mcpu=cortex-a53+crc+crypto+rdma -fipa-pta -fgraphite-identity -floop-nest-optimize -ftree-loop-ivcanon -fivopts -ftree-vectorize -fgcse-sm -fgcse-las -Wno-error"
781781
January 5, 2025, 11:40pm
3032
Did you ever find a solution?
otnert
January 6, 2025, 12:12am
3033
Nope, just put it down to snapshot being experimental.
I'm only using snapshots for the apk
capabilities, have scripts I need to migrate over.
I wonder if this is occurring on 24.10-rc4
?
781781
January 6, 2025, 12:48am
3034
I have the snapshot with APK installed right before the decision to keep opkg as default package manager so can't comment, unfortunately.
Try editing /etc/init.d/network
and replace reload_legacy
with reload
.
1 Like
Running SNAPSHOT:
ubus call network.interface.wg0 down
ubus call network.interface.wg0 up
The "down" option works, but the "up" option does not.
Does anybody know what is the LED behaviour on the WAN(2.5G) port in stock FW?
Meaning, what do green and yellow LED-s indicate?
I am debugging them in OpenWrt but I dont remember how stock FW configured them
Thanks, I think this will fix it:
openwrt:main
← robimarko:dynalink-led
opened 11:34AM - 18 Jan 25 UTC
Currently, 2.5G port LED-s on Dynalink are incorrectly configured and thus they … will light up all of the time.
So, lets fix this by:
1. Current green LED is actually yellow, change the color
2. Fix its polarity as its actually active-low
3. The yellow LED that was registered as being connected to LED_1 pin on the PHY is not actually connected at all, so remove it.
4. The actual green LED is connected to LED_2 on the PHY so add it.
Fixes: 75ad5c24142a ("qualcommax: switch to qca8081 upstream PHY driver")
Fixes: #14502
Please give it a go, it works for me and I would love to get it into 24.10 as well
7 Likes
ka2107
January 24, 2025, 4:43am
3040
What's the status on availability of Airtime Queue Limits (AQL) (https://www.bufferbloat.net/projects/make-wifi-fast/wiki/ ) on Dynalink DL-WRX36 (and ath11k driver / firmware in general) on OpenWrt 24.10.0-rc6?
3 Likes
I am running OpenWrt SNAPSHOT, r28739 and I believe the patch is included.
As I removed the multicast to unicast now fully on my interfaces, and having zero issues.
kzaoaai
February 3, 2025, 7:56pm
3042
are you sure? I couldn't find any commits indicating so.
1 Like
Oh yeah, I was hit by the problems later that day.
Still don't see the patch @ https://github.com/openwrt/openwrt/tree/main/package/kernel/mac80211/patches/ath11k
Will toggle multicast to unicast on again
ka2107
February 4, 2025, 8:21pm
3044
@rmandrad Do you have the latest OEM firmware v1.10.01.323 file or any other version after v1.10.01.201? I am trying to return back to OEM firmware on a friend's DL-WRX36. Thanks in advance.
no i am afraid i don't have
kzaoaai
February 5, 2025, 1:46am
3046
yes I figured out after trying it and getting the errors. Reverted to qosmio's NSS build which includes the patch.
ka2107
February 5, 2025, 4:08am
3047
How did you obtain the v1.10.01.201 firmware file? I don't see any firmware download link in either Dynalink or Askey website.
frollic
February 5, 2025, 5:04am
3048
It was intercepted mid air, read this thread or the WRX36 wiki page for more info.
1 Like
hnyman
February 6, 2025, 9:58pm
3049
Caution:
It is possible that ipq807x with DL-WRX36 is currently broken.
I have now compiled and flashed r28775-98d7f4202f twice, and the image fails to boot.
It fails to read rootfs from UBI during the boot process:
[ 1.167937] cpr4_ipq807x_apss_calculate_target_quotients: apc_corner: fused STURBO: quot[ 7]=1191, quot_offset[ 7]= 175
[ 1.179117] cpr3_regulator_init_ctrl: apc: Default CPR mode = closed-loop
[ 1.182172] cpufreq: cpufreq_online: CPU0: Running at unlisted initial frequency: 800000 KHz, changing to: 1017600 KHz
[ 1.198414] remoteproc remoteproc0: cd00000.q6v5_wcss is available
[ 1.207552] UBI error: cannot open mtd rootfs, er▒+▒r▒▒ʂ▒▒▒Waiting for root device /dev/ubiblock0_1...
This might be related to the introduction of ipq5018 subtarget to qualcommax, but there is no certainly about that yet.
My previous build r28737-084618f8db from 31.1.2025 boots ok, so there is a 6 day regression window, where the change has happened.
EDIT: r28746-63e178f067 compiled by buildbot on 5.2.2025 also boots ok, so the regression window get more narrow as r28775-98d7f4202f fails for me.
1 Like
slh
February 7, 2025, 9:17am
3051
Just as potential additional data point, r28753-f480fa60d3 (2025-02-05) works on my Xiaomi Mi AIoT Router AX3600 (ipq8071a with NAND and UBI).