Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion

Yep... The default configuration is flawed and we will apply a more sane configuration

4 Likes

If you need someone to test I can do that also

I'll try shuffling through the discussion, but in case anyone has it... where is the newb guide?

The wiki https://openwrt.org/toh/dynalink/dl-wrx36 is almost good? It just omits some very key details. Like, how do I know if I have not gotten the initramfs to load? I can ssh right back into 192.168.216.1, and get no response doing ssh admin@192.168.1.1 so I assume that it did NOT load the initramfs as expected...

Edit 1a: After I boot to initramfs, if it's successful, I should be able to go to http://192.168.1.1 in a browser and see the luci admin panel, yes? And should the login be root (instead of admin) with password askey1234, or will it be root without a password? Once I get that far, then I should progress to step 2, but....

Then you have this...

"Use SCP to transfer OpenWrt factory image, store it in /tmp."

What is SCP? Do I just type "scp /tmp" and it's magically copying this over? The part 1 of guide was pretty nice about detailing what I needed, other than finding out how to allow ssh-rsa via ssh -oHostKeyAlgorithms=+ssh-rsa admin@192.168.216.1

Edit 1b: Oh, SCP is a secure copy command? Why not just cp? Anyway, if I have all the images on the same usb that's plugged into the router... can't I use those? And how is it differentiating from a usb mount vs the internal tmp directory?

--

Also, it looks like maybe I am on the original firmware because the output to cat /proc/mtd has mtd18 as rootfs_1 and mtd20 as rootfs, but the wiki is suggesting it should be flipped the other way round (18 as rootfs and 20 as _1).

should we list all copy commands that won't work in the wiki?

try, but the initramfs probably doesn't have the packages required for accessing USB storage.

Thanks, this is the info that is only known to the builders and veterans, not newbies. Because just two steps previously we were telling the router to use the USB, and in the immediate desired effect after using the reboot in the prior step, it is loading the image from USB. It would be expected to someone with little understanding that the USB is still accessible.

As for mention of why scp is necessary and not cp, well, just a passive mention that "The only known way to get the openwrt firmware installed persistently on the router is to write it from one device to another. The way we do that is with scp, other copy mechanisms don't work. With a terminal, no longer ssh'd into the router, preferably in the directory where your factory image is, type what Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion - #462 by ka2107 says:

" scp -O openwrt-ipq807x-generic-dynalink_dl-wrx36-squashfs-factory.ubi root@192.168.1.1:/tmp/"

Kudos to @ka2107 for sharing that.

Letting users chase around for one-off knowledge on stackexchange just isn't nice :slight_smile:

For best practice, I am totally reformatting my USB drive. I thought I could use my half full decades' old GB flash drive, but once I back up those files, I'll just flash it again and leave just the initramfs file on the drive. As only through this discussion I have learned the other files are useless on the USB, and possibly other files are conflicting with it flashing to it.

Well, they are two quite different things:

  • the USB can be used to get the initramfs running by the u-boot bootloader, which takes care of the really early stages of booting to get the proper Linux OS (OpenWrt or OEM firmware) running.
  • after Linux has been booted up, u-boot and its driver capabilities have no role. Loading image from USB in OpenWrt requires now USB storage support in OpenWrt.

In general, the OpenWrt device wiki pages do not each try to explain basic Linux file copying over network, drive usage etc. Otherwise, each wiki page would be much longer. The wiki pages assume that the user has basic knowledge Linux console tools, (and hopefully even understands the role of bootloader and the actual OS).

5 Likes

What am I doing wrong?

Every time I do this step, it recovery boots back to the dynalink firmware. I have meticulously double checked that the file in the USB drive (which for sake of me not having to unplug and plug back in over and over and over and over I have enabled via ftp sharing in the dynalink panel) and the command have the same name. Am I somehow missing something?

Should there be some kind of confirmation of "this command is acceptable" when I do the copy-paste of the fw_setenv command from the wiki?

Do I need the extra # out front? I would think not, but I seem to always make the wrong assumption with this documentation :smiley:

Should I be changing the bit about the file name to be UNTITLED/openwrt-23.05... or /UNTITLED/openwrt-23.05... because the FTP server tells me that's where the mount(?) is?

You might be using a too complex USB drive.

The USB drive support in u-boot seems to be rather picky. Too complex partitioned drives have failed also earlier. (possibly due to USB numbering being 1:1 instead of 0:1, or something similar) See example below. You should use a simple 1-4 GB MBR formatted FAT/FAT32 USB stick with just a single partition instead.

Read the discussion a month ago...

As per previous comment, I just formatted this.

On Ubuntu, I plugged in the drive. I right clicked it in Nautilus. I selected Format. I picked FAT. (I assume it's really FAT32, no reason a modern OS should use FAT16?) Literally one partition. It gave me the warning I'll lose all my data. Yep, that's what I want. The drive is "988 MB". All data is off of it except that one singular initramfs file.

My next possible USB drives to use are my Linux livedisc drives where I can format these 16/32 GB drives for this single partition. But that actually exceeds your "simplicity" recommendation.

Edit: Yep. Most of my problems were because of a faulty drive. Using my 1GB drive and attempting to format it 3 times in a row suggested it's dying. I formatted it again after this comment to no filesystem to really ensure as blank of a slate as I could. Then I tried to format it back to FAT, and it threw errors about not being able to put the label on or something. Gave up, grabbed my 32GB livedisc, formatted that and made sure it was one partition, put just the initramfs on there, plugged into router, did the ssh stuff, and it rebooted successfully into openwrt. It still took 30-40 seconds for the router to come back online, in case there is anyone out there who discovers this conversation in their troubleshooting.

as already mentioned by @hnyman, uboot is a boot loader, not an OS.

Hi everybody!

Is it possible to run OpenWrt with extroot, clear/reconfigure router flash space and revert overlay usage back to flash? Has anyone succeeded with removing all unnecessary data from 256MiB flash? Or it's not possible due to secure boot?

"all" devices with an USB port can use extroot.

Assuming it's doable, you'd probably have to create your own images, until it's picked up by openwrt, as it's been done with the AX6000.

Uboot = Ubuntu? Hmm? Since when?

All I was saying is when I used Ubuntu to format the drive - note, I mean my Linux Operating System for a Personal Computer when I Say Ubuntu - the GUI display for formatting options included something-or-other maybe "Linux" with option for "LUKS encryption", or the choice of NTFS (NFTS? I never keep it straight), or FAT. Just FAT. Not FAT16, Not FAT32, just FAT.

So in the troubleshooting steps where it's advised to make sure you use FAT32, I am saying that the GUI in Ubuntu, again, not openwrt, but a different operating system entirely my friend - though me being super extra explicit might be confusing you who has been accustomed to reading between the lines and not actually reading what you are told - it says FAT and all I make with my proclamation about a modern OS should not use FAT16 is I am making the assumption that Ubuntu is abbreviating what should be labeled accurately FAT32 as FAT. I know, I know, quite the whirlwind to wrap your mind around. Best of luck mate.


Edit to avoid a double post, I do want to give my feedback that this is a brilliant and affordable device. If you've got the right equipment (ethernet-usb adapter if not a direct ethernet port on a setup device; a well-functioning USB thumbdrive), it's an amazing thing to set up. I had a previous OpenWRT setup on a "budget" Asus router that was just a few dollars cheaper than the Dynalink. As soon as I got the Dynalink set up, my download speeds are 4-5x faster in downloading a multi-gigabit file. I went from a usual 1.5 with peaks up to 1.8 MB/s to over 7 pretty consistent with peaks almost to 10 MB/s. And that's capital B, so bytes, not bits. I was going to take ~8-9 hours to download this 50GB file via VPN on the old router, and this new one is going to whip it out before I fall asleep.

Since never.

We are really talking about u-boot, a low level bootloader used to load the actual operating system.
Like UEFI BIOS, if you want PC terms.

If offers limited troubleshooting functionality like loading an image from USB.
The size of the u-boot binary is quite small, 256kB or such, so it has really limited hardware support. But is good for embedded devices with flash size constraints.

5 Likes

We know, we know, quite the whirlwind to wrap your mind around. Best of luck @Exaskryz.

2 Likes

Yes, I know you're talking about u-boot.

Why you thought I didn't, I don't know.

Frolic quoted Exaskryz saying "no reason a modern OS should use FAT16"

Frolic responded to that out-of-context quote with: "as already mentioned by @hnyman, uboot is a boot loader, not an OS."

The FULL QUOTE is "On Ubuntu, I plugged in the drive. I right clicked it in Nautilus. I selected Format. I picked FAT. (I assume it's really FAT32, no reason a modern OS should use FAT16?)"

Somehow your talent for reading between the lines has utterly failed you. Let me rephrase the full quote in a way I hope is explicit, but it may be futile.

"On Ubuntu, I plugged in the drive. I right clicked the drive in Nautlius. (Editor's note: Nautilus is the Ubuntu version of Windows Explorer. Something magical.) I selected Format. I picked FAT. (I assume FAT's really FAT32, no reason UBUNTU should use FAT16)"

Frollic, take your embarrassment and move on. I'm here to learn. You explicitly contorting yourself to save face is not amusing in the least.

Even if hnyman missed the rhetorical nature of my questioning "Uboot = Ubuntu?", I appreciate that hnyman made an effort to teach what Uboot was. I never dismissed, downplayed, or refuted its importance or significance in the purpose of placing OpenWRT on this Dynalink router. It's just Frollic misread my post and insinuated I was retarded.

Does anyone need any particular data off the router before I wipe mine to install openwrt?

I would assume those who are working on it already have copies of the files/partitions but I thought I'd ask.

(Also, I'm thinking of looking into it myself to try to figure out dual-image - is there something I should do now before I lock myself out inadvertently? I've got a copy of /rom but I'm not sure what other things the running OS would access/use from the overwritten partition.)

1 Like

Probably it could be useful to start with this post.

Maybe there will be useful info you can take from the stock firmware that will help for resolving the issues with memory leak with NSS wifi build.
I've already provided some info from the stock QNAP firmware but it may be useful at least to compare the data from two different manufacturers.

Please be respectful. @hnyman is god-tier with openwrt and has spend more hours developing & assisting others than most of us will be able to contribute in a lifetime... and @frollic is simply a very literal communicator, but when listened to, points users directly to where they need to be. Appreciating their assistance and asking follow up questions will get you far further than typing out long winded retorts.

11 Likes

Can someone show what information the art partition for Dynalink contains regarding the country code:
for i in 1034 1458 1500 15a8; do hexdump -s 0x${i} -n 2 -e '"0x%04x "' /dev/mtd17; done