Return to the OEM firmware and check how it behaves there.
If you observe the same problems with the OEM firmware, you have a case - if not (or if you can't restore it to OEM), you don't.
It might be easier just to 'fw_setenv' and change your USB boot file name to be something simpler like "Dynalink.itb" - or whatever.
Then regardless of new version name, you can always simply rename the new .itb file that is copied to the USB.
3 Likes
Came here wondering if someone had found a way to do this. Now wondering if there is a way to discover/expose those...
Please let me ask this question before creating a separate thread:
What could be causing all proxy clients running on this router to drastically reduce speeds and increase pings of UDP connections, but not TCP?
Got this behavior “out of the box” in my case, despite never experiencing anything like this on my another Mediatek-based router. Hardware flow offloading is already enabled.
Edit: Oh nope. Just updated my other router to the latest versions of everything: similar issue has now popped up here as well. Seems to be a problem with OpenWRT 24.10 or some package.
This would sound silly.. but here is next.. I gave up with it.. and decided to replace a device and try return to OEM. Do check and RMA it.
But before I left device runnnig (with my config but with just single ssid on 2.4G) for few days until replacement came. (single ssid worked)
Its replacement just came.. replaced.
Meanwhile I decided to return stock config and decided check one more time to record video.. ( added 2nd 2.4G) and it worked?!! .. strange
I reflashed again with same sysupgrade file as before without leaving config, to be sure.. and did same check again on vanilla state. (Did same as above a 3 simple steps ).. it works!!!?!.
Then same usb stick with same initramfs.. 3 clicks. it works!!!?!.
How it is possible? looks weird
What kind of issue can cause this?.. and it wasn't as single time bug.. and wasn't my dream: error stack was captured above. I reproduced this issue before about tens times in a row to capture logs that are above.. now with same steps nothing.. no reboots
Now left it with 3 dummy ssid 2.4G and 2 ssid on 5G. Left it unconnected to anywhere..it is not a real test.. but at least to see if it will fail in few days
i want to upgrade my dumb ap's (also wrx36's) but getting the following error. i also had that when i upgraded my main router, but it was around 2 years ago.
So what can be done to solve this? (attended upgrade not working)
extract the package names manually, use firmware-selector to create a sysupgrade image.
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=f02f6aaa8d4e1025ab4aa9f569123e57f689f4e5
Download the normal downloadable sysupgrade image from qualcommax/ipq807x target instead of the old ipx807x/generic that was deprecated/renamed in June 2023.
Like mentioned in the wiki:
Note the filename changes. For 23.05: ipq807x-generic. For Snapshots/24.10 onward: qualcommax-ipq807x.
Or use the firmware selector to build a tailored qualcommax/ipq807x image for DL-WRX36.
weird. i just tried to upgrade both of them with a image 23.05 and one of them is no longer reachable through luci and ssh. they are cabled, so i guess the only option is now a factory reset by holding down a button? The weird thing is, that it still has working wifi, and camera's connected to it by lan are also still working.
The other one seems to have not upgraded anything, it says its still on OpenWrt SNAPSHOT r21968-acd8e94d20. I used sysupgrade with the firmware selector, retaining settings. But it's still reachable with luci and ssh.
EDIT: Managed to break the other router as well. working with it's wifi, but no longer got luci access or ssh access.
I tried booting in failsafe mode but cant seem to connect with putty to 192.168.1.1 in any case. Tried making the IP of the pc static as well on 192.168.1.10 with subnet 255.255.255.0 but it doesnt want to connect. the led on the wrc36 is flashing fast red then usual, which should confirm failsafe is running.
Any tips to getting these devices back to being reachable and how to completely flash newest firmware without keeping any settings?
https://openwrt.org/toh/dynalink/dl-wrx36#part_1_-_copy_and_boot_initramfs will help you recover as long as you have the USB2TTL cable.
Had a weird moment with one of my WRX36 units yesterday - created a new sysupgrade image with the image builder, copied it over, tested it with sysupgrade and then flashed it with sysupgrade.
Something must have gone wrong with it because the device got into a boot loop, magenta LED lighting up for a few seconds then off, then lighting up again.
Thankfully I left the serial interface wiring in place, popped out through the gaps in the housing - and that told me it couldn't find init, so kept going round in circles.
I had to boot an initramfs image from USB, write a 24.10.0 factory image onto it and then restore the config backup. A few packages installs later and it was fully back in business.
I've never had a router fail like that before!
1 Like
Hello,
Ended up with the same problem after upgrading from the latest 23.05 to 24.10, one of the units (the first one I flashed) did not reboot after the flash, but after a couple of power off/power on, it finally started - had that issue 2-3 time since 24.10 and then 24.10.1.
I don't know why but today the power off/on was not sufficient to pass purple and I ended up launching a console:
[ 1.194488] cpufreq: cpufreq_online: CPU0: Running at unlisted initial frequency: 800000 KHz, changing to: 1017600 KHz
[ 1.210878] remoteproc remoteproc0: cd00000.q6v5_wcss is available
[ 1.219933] UBI error: cannot open mtd rootfs, er▒[ 1.231301] Waiting for root device /dev/ubiblock0_1...
Trying a recovery from USB:
- Using an initramfs 24.10 I was able a single time to access UBI (most of the time /proc/mtd was empty with 24.10.1). I had to use an initramfs 23.05 to properly do a recovery.
- I did a ubidetach -p /dev/mtd18 and a new ubiformat with a factory file.
- If I use a 24.10.1 factory file, I'm back with "cannot open mtd rootfs" / purple LED
- If I use a 23.05, it works but if I sysupgrade to 24.10.1, I'm back with "cannot open mtd rootfs" / purple LED
24.10.1 = OpenWrt 24.10.1 r28597-0425664679
Obviously "printenv" is as it should and was never changed and all, and the 24.10.1 images were downloaded from OpenWRT today.
I have 3 DL-WRX36 units, that's the only one with this behavior so far, and it shows the same NAND errors listed here: IPQ5018 addition commit 34d917265 breaks ipq807x/DL-WRX36 boot (due to NAND driver changes?) · Issue #17897 · openwrt/openwrt. I thought it was already fixed.
[ 0.885693] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xaa
[ 0.886145] nand: Micron NAND 256MiB 1,8V 8-bit
[ 0.892737] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 0.897028] nand: ECC (step, strength) = (512, 8) does not fit in OOB
[ 0.897039] qcom-nandc 79b0000.nand-controller: No valid ECC settings possible
[ 0.911210] qcom-nandc: probe of 79b0000.nand-controller failed with error -28
Thanks in advance for whatever help you could provide!
1 Like
Looks like we have same problem
I just keep that running with version 23. No solution so far to run ver24.
I think I had to upgrade using sysupgrade and without backing up /etc, so I had to restore the backup afterwards.
I'm running 24.10.0, but when I try to upgrade to 24.10.1 reboots and fallback to 24.10.0 after red led blinking after the magenta led.
In 24.10.0 my /prod/mtd works fine:
root@openwrt:~# dmesg | grep nand
[ 0.886763] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xaa
[ 0.887293] nand: Micron MT29F2G08ABBGAH4
[ 0.894162] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
[ 1.174902] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xaa
[ 1.189626] nand: Micron MT29F2G08ABBGAH4
[ 1.196034] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
[ 1.200318] 25 qcomsmem partitions found on MTD device qcom_nand.0
[ 1.207458] Creating 25 MTD partitions on "qcom_nand.0":
Does not seem related and yes I have the same 'dmesg | grep nand' whenever the unit works.
What I experienced with this unit is - as far as I can tell - is a race condition (or a progressive corruption of whatever can be corrupted at boot?) that prevents NAND proper detection.
As stated I was able to have the system booting with 24.10 and 24.10.1 several times by simply powering on/off - maybe in 2-3 attempts, after the initial 24.10 flash it was just 1 so I thought it was just a glitch and applied 24.10.1 as soon as I got it hoping it was ironing the kinks - but it got progressively worse with 24.10.1 and now I can barely access mtd/boot the system by powering on/off this unit.
Last time I did it I think more than 40 times before it suddenly worked for no reason that comes to mind (I'm guessing the NAND was simply detected properly during the boot sequence).
23.05 works with no issue.
Recent SNAPSHOT sporting Kernel 6.12.32... interesting!
I am already using k6.12 works without an apparent problem but the router is lightly used