neuro, > I hope the attached info helps. I am quite new to > this uboot stuff, but I am willing to test things > if possible. Very good info! Stay tune for my new u-boot upload. I've done everything else except for the registers dump you've just provided.by bodhi - Debian
Thanks! I've changed the subject of this thread to: "Debian on Western Digital My Cloud Mirror Gen1". And updated 1st post credits.by bodhi - Debian
You could try dumping the image partition and mount it in Linux. See if there are things that could prevent u-boot from loading the image. I'm guessing once you see the image layout, you could see how things need to be moved around as router B expects.by bodhi - Rescue System
sym0, Thanks! The log got cut off at the end so I did not see the rootfs mounting activities. Are you using RAID? Quote[ 0.000000][ T0] Kernel command line: root=/dev/ram console=ttyS0,115200 max_loop=32by bodhi - Debian
Quantummaster, It won't work without other changes, not just flashing the image. 1. In the log, the bootargs showed there are other differences between A and B. And the differences are: mtdparts layout (NAND vs SPI device), and the UBI device. Probably UBIFS layout is the same (only image volume). 2. The bootargs is hard coded in u-boot before it loads the kernel. 3. The u-bootby bodhi - Rescue System
> and i need a > cfg file for openocd to comunicate with my stora > ms2000 board and it is not clear where can I take > this cfg file from. IIRC. This box is basically identical to Pogo E02 in all HW aspects, i.e same SoC, except the RAM size. You can try using the Pogo E02 cfg as is, since the Pogo E02 has 256MB and the Stora has 512MB. (less is OK, not more). So follow joerby bodhi - Rescue System
> The Bootloader is different. > I can flash the complete image with cfe, but the > bootloader dont boot the openwrt i must change the > env. OK, so you have envs listing for both A and B? please post tthem here. And when you play with the envs, don't save them. You only need to save them permanently after you are satisfied that you can boot into OpenWrt.by bodhi - Rescue System
adrien, You are right! I've added the audio node in the RN102 only. Not the RN104.by bodhi - Debian
> But my Goal is the Router B with Openwrt :-) from > Router A. > If i flash the only mtd2 and it faile i can > recover with cfe? I don't have any idea about this. These routers have Broadcom SoCs. If there are enough differences between A and B SoCs then it will not boot the kernel. Does OpenWrt have installation instruction for both?by bodhi - Rescue System
adrien, > I can see in my dmesg that I don't have the error > "unsupported function audio on pin" like you. I believe you are running an older version of the DTB.by bodhi - Debian
> Flow-control is set by the pause parameters from > what I've read Correct. > Trying to turn on pause fails. > netlink error: Operation not supported So I suspected the driver is not working correctly (or we lack some set up). > Link partner advertised pause frame use: > Symmetric Receive-only It's worth noting about the switch you are connecby bodhi - Debian
Let me move this thread to the Rescue System section. It's where all OpenWrt discussions are.by bodhi - Rescue System
Mike, > Quick update, just for information really. I cured > the persistent failing to boot with the 6.17.7 > kernel and my own rootfs, it seems it was an issue > with RESUME UUID of a swap partition on the USB3 > device. Cool! > I also cured the big boot delay when > firmware-libertas is installed by patching the > kernel source to disable Bluetooth AMP devby bodhi - Debian
ZooMoo, As I mentioned above, could you set the flow control to enabled? If not, there might be an issue with this mvpp2 driver. Your log ~# mii-tool -v eth0 eth0: negotiated 1000baseT-FD flow-control, link ok product info: vendor 00:0a:c2 or 00:50:43, model 29 rev 1 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 1000baby bodhi - Debian
Thanks adrien! I'll wait for Trond to join the discussion.by bodhi - Debian
adrien, Can you confirm the time lag in Trond's test above? https://forum.doozan.com/read.php?2,92514,140494#msg-140494by bodhi - Debian
> > Thanks! good to know. Somehow we assumed there is > audio in these 2 boxes! > > I guess I need to look at the DTS again. I remember now. I've added audio in the DTS as an experiment to see if the time lag was reduced and it did show some reduction in Trond's test, IIRC. It was to test Trond's assumption about unused feature in these 2 boxes that could haby bodhi - Debian
adrien, > Neither the RN102 or RN014 have audio. > They only have USB/RJ45/eSata ports, no audio or > video. Thanks! good to know. Somehow we assumed there is audio in these 2 boxes! I guess I need to look at the DTS again.by bodhi - Debian
tiaderosa, > I started installing the basic packages, Samba, > FTP, etc., and a web-based system management > interface. I tried Ajenta, filebrowser, webadmin, > and cockpit, but the MS2100 doesn't have enough > resources to run properly. > > Even with minimal web interface configurations, > the system is very slow and stops responding after > a whileby bodhi - Rescue System
Hi Trond, Looks like we need to find the pin for audio. I forget all about this. Does this box really have audio? Quotedmesg_rn102.log [ 25.232173] armada-370-pinctrl d0018000.pin-ctrl: unsupported function audio on pin mpp51 [ 25.422902] pinctrl core: failed to register map default (0): invalid type given armada-370-netgear-rn102.dts /* TBD need to find the correct pinby bodhi - Debian
raffe, > Yes, all is on the HDD, I do not use USB. Then there is something not optimum in your rootfs. The Pogo V4 has the same specs as your LG N1T1, and I had no problem upgrading. > Is there a way to during boot change from server > mode? You don't need to run the latest kernel always. If you think one does not work well for whatever reason, then don't upgrade.by bodhi - Debian
raffe, Pogo V4 800 MHz CPU, 128 MB RAM, 1Gbs Ethernet Linux version 6.17.7-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 Mon Nov 3 16:38:22 PST 2025 USB 2.0 rootfs 2GB swapfile on HDD Took 42 minutes to upgrade from Debian 12.8 to 12.12. This is normal for a USB rootfs. It really does not matter about USB 2.0 or 3.0 rby bodhi - Debian
Mike, > My board is I think the second of the three > versions of the V5. That is, it has the internal > SD slot and the reset button. Probably. I have not opened this box for many years, and I don't remember much about it. Here is a good article by Willy Tarreau. He was the first hacker for this box, I learned a lot from his writeup. http://wtarreau.blogspot.com/2013/by bodhi - Debian
GoFlex Net 1.2GHz CPU, 128MB RAM, 1Gbs Ethernet Linux version 6.17.7-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 Mon Nov 3 16:38:22 PST 2025 USB 2.0 rootfs Took 41 minutes to upgrade from Debian 12.8 to 12.12. This is normal for a USB rootfs. Pogo V4 800 MHz CPU, 128 MB RAM, 1Gbs Ethernet Linux version 6.17.7-kirkby bodhi - Debian
BTW, the reason I configured this kernel to server mode was mentioned in the release notes. Quotehttps://forum.doozan.com/read.php?2,12096 - General kernel upgrade. - This kernel is now running with the non-preempt scheduler. This is to avoid a kernel bug that was introduced recently in mainline Linux. Also, the performance should improve a little bit for Kirkwood boxes running as serverby bodhi - Debian
Mike, This box has many problems. Booting with USB 3.0 rootfs seems to work most of the time. I recall sometime I saw intermittent problem like you did. So I run this box with the rootfs on the external SD card, and boot the kernel directly from that. The USB 3.0 slots are used for normal USB 3.0 data drive perfectly fine. root=LABEL=rootfs never fails for me. I still have an SD card in thby bodhi - Debian
raffe, > My LG N1T1 is slow, and normally apt > upgrade takes a few minutes. But with 6.17.7 > "Building dependency tree" took about 10 hours to > 100% but then never continued. It might be a coincidence, but this kernel runs differently from the 6.16.5. The 6.16.5 kernel was built with preemptive scheduler (good for response time), this 6.17.7 kernel was built witby bodhi - Debian
Mike, Post the entire serial boot log.by bodhi - Debian
ZooMoo, Here is the latest DTB and DTS. I digged a bit deeper in various places to create the pins for ethernet. This has pinctrl definition for ge0 and ge1. We are using ge1 pins in this version. Without the Datasheet, there is still some unknowns. Not sure if this will make a difference. ==== Also, I don't recall you have tried to set the NIC to use flow control? the mvpp2by bodhi - Debian
Michael Howard, > Any thoughts as to why, with the above kernel and > it's modules/initrd installed and uboot configured > appropriately, a different rootfs location would > be a problem? > The rootfs usb device has the same > partition layout as the sdcard. Did you install the kernel on that rootfs? or you just point the kernel to that rootfs (i.e. using bootby bodhi - Debian