Added to the Wiki QuoteUnbricking with Serial Console & JTAG console Unbricking ReadyNAS RN104 - Tutorial 3by bodhi - uBoot
Added to the Wiki QuoteRAID Making a RAID1 rootfs - Tutorial 2by bodhi - Debian
Hereux, > Why the hell does it now boot like nothing > happened?!!!! > I didn't do anything. Just the usual "env default > -a" and "saveenv" and "boot". Absolutely nothing > different. > At least 50 times it failed... now it boots. Flaky hardware. The watchdog is a hardware watchdog. And I killed it in u-boot. > > Anywayby bodhi - uBoot
sparks , > I cannot duplicate the boot of the linux-6.5.7 > rootfs. Some how my u-boot env got hosed. I think > memory and mtd addresses are wrong. Correct. > But at least I > have got a couple of months to work it out. Not that long! I can answer questions when you have problem. > U-Boot 2021.04-tld-1 (Jun 04 2021 - 18:27:16 > -0700) > D-Link DNS-325by bodhi - uBoot
diappollo, > > Thanks but under the terminal with wget, it does > not work Check your internet connection? ping google.com ping 8.8.8.8 If no connection cat /etc/resolv.conf If it is empty cat nameserver 8.8.8.8 > /etc/resolv.confby bodhi - Debian
Bay, We did above sh-4.3# ethtool eth0 Settings for eth0: Supported ports: [ ] Supported link modes: Not reported Supported pause frame use: No Supports auto-negotiation: No Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: internal Auto-negotiation: ofby bodhi - Debian
diappollo, > Problem: I still can't get > uboot.2016.05-tld-1.environment.bodhi.tar from my > nas and I can't stop it... I tried with wget, > curl, dropbox_ulploader... nothing works, any > tips? Try this direct dropbox link https://www.dropbox.com/scl/fi/bau404owcfxysok/uboot.2016.05-tld-1.environment.bodhi.tar?rlkey=oda7yvw38624n4bb8v0hfudas&dl=0by bodhi - Debian
> > > ifup: failed to bring up eth0 > > Did you connect the Ethernet cable? you don't have > network in this boot log. I see. You're using the wrong uImage. Whhen you create the rootfs Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 you did step 4: Quote4. (Stock u-boot only) Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Sby bodhi - uBoot
sparks, Cool! this u-boot has not been tested anybody before you did. And it is an incomplete version. I need to check the source code to see if the envs are at the right location as same as other Kirkwood u-boots I released here. I will release a 2025 u-boot for this box, if you are willing to be a tester. However, it is OK if you want flash it to NAND. Because you can boot with the internby bodhi - uBoot
Hereux, The behavior is exactly as if the hardware watchdog had kicked in after 30 seconds. This box is like that originally with stock u-boot. However, the new u-boot should have killed the watchdog immediately when it started. And you have installed it. ======= Try running kwboot and load the new u-boot, interrupt u-boot count down, and let it sit there. See if the box got reset byby bodhi - uBoot
Ludacrisvp, Very nice! This is another good tutorial to add to the Wiki. I'll do that. Quotenot sure which entry in fstab is being used to mount, but I can't imagine having both hurts. You actually don't need root device in fstab any more when you already have bootcmd=dns time.apple.com 17.253.24.253; sntp; run bootcmd_usb; run boot_sata1; run boot_sata2; run bootcmd_usbby bodhi - Debian
Mikele25 & MM, As I mentioned previously https://forum.doozan.com/read.php?2,138540,138974#msg-138974 QuoteThere are 2 parts. The PCI ports and the card. First, the PCI ports should be shown in dmesg, but the card will not without the drivers. I added pcie1 in the DTS to make sure both ports are enumerated (before there was only pcie0). A general pcie0 and pcie1 like below mightby bodhi - Debian
petecom, > That's all I understood from the instructions... > You then write something about executing dpkg -i > from *.deb but where what and how on a virtual > machine, on a pendrive, exactly where? When you create the rootfs the first time, there is no dpkg involved. You need to to read the instruction. https://forum.doozan.com/read.php?2,12096 QuoteNote: If thiby bodhi - uBoot
dmitrynino, > [ 8.961990][ T18] scsi 2:0:0:0: Direct-Access > Verbatim STORE N GO 1.00 PQ: 0 ANSI: 2 > [ 8.983446][ T32] sd 2:0:0:0: 7831552 > 512-byte logical blocks: (4.01 GB/3.73 GiB) > [ 9.001680][ T32] sd 2:0:0:0: Write > Protect is off > [ 9.020944][ T32] sd 2:0:0:0: No > Caching mode page found > [ 9.027008][ T32by bodhi - uBoot
diappollo, > root@debian:~# fw_printenv ethaddr > > Cannot read environment, using default > > Cannot read default environment from file > This is expected, because there is nothing in the envs area yet. > > 2- and with this : dmesg et grep -i 'bad' > &by bodhi - Debian
diappollo, Those in red are info or warning, were expected, not errors. Yes, it is safe to flash new u-boot.by bodhi - Debian
Bay, [ 0.000000] Synology Hardware Version: DS112v10-j Just what I thought. Your box is not the orginal DS112. I'll need to create a new DTS and compile it for you to try.by bodhi - Debian
"I'm asking for help..." I've posted above: https://forum.doozan.com/read.php?3,139043,139047#msg-139047by bodhi - uBoot
poluyretan, > The device has successfully > upgraded to 6.10.10 via the web interface. Many > thanks to this forum for the recovery > instructions! Could you describe how did you recover this box? It would be very helpful for others if they run into the same problem.by bodhi - uBoot
Alex, See this: https://forum.doozan.com/read.php?2,12096,138968#msg-138968by bodhi - Rescue System
BayPanard, > Only issue I came to so far is that I don't have > network connectivity, and some strange message I > did not totally understood (added at bottom of > boot log). Quote[ 4.658175][ T1] mdio_bus f1072004.mdio-bus-mii: MDIO device at address 8 is missing. [ 4.666571][ T1] mdio_bus f1072004.mdio-bus-mii: MDIO device at address 9 is missing. It meaby bodhi - Debian
diappollo, Try the later version of kwboot here: https://forum.doozan.com/read.php?3,27280 1. When you see Quote0 % [++xmodem: Bad message Recall the kwboot command and execute again. 2. Make sure the serial wires are as far away from the power cable as you can.by bodhi - Debian
bodhi Wrote: > There is no Armada 370 u-boot support in mainline. Well it seems there is some demand. So I could take a look to see if I can mainline the Mirabox u-boot (which I own).by bodhi - uBoot
elding, Try using my kwboot build here: https://forum.doozan.com/read.php?3,27280 > I saw u-boot project on the github, but could not > understand which defconfig I needed to choose. > Maybe you can suggest? There is no Armada 370 u-boot support in mainline.by bodhi - uBoot
diappollo, > 1 - the "dual boot" problem solved with the use of > a Sandisk key Nice! > 2 - the U-Boot update: > I tried to load U-boot via UART to test but it > doesn't work, I systematically end up with lags... > it seems that I don't launch the listening at the > right time yet I tried to launch before, during... > nothing works. I seaby bodhi - Debian
twinclouds, > Even though I passed my 80 years birthday last > year, my mind seems still fine. That is one > reason I doing something technical as hobby to > keep it this way! Cool! wish I will be active and clear mind like you when I get to that milestone :) > I noticed 6.11.6 and 6.12.6's Initrd sizes are > getting much smaller. > Hope you can generate aby bodhi - Debian
Hi twinclouds, > Long time on contact. How are you doing? I'm doing great, thanks! hope you are too. > Recently, I tried to update of my Dockstars that > are still running Debian 9, Kernel 4.18 and with > 2017 uboot, (maybe because of the boredom in my > retirement :-)) I'm quite near that time when I'll stop doing consulting works completely and retby bodhi - Debian
elding, > any chances for this bins compatible with "seagate > personal cloud - 2 hdd"? Stock uboot wont see usb > storage to boot, and Im looking for it update. I'm assuming you want to boot debian on USB. Not stock FW. Even though it's the same SoC, there are differences in each board. Tthe differences will prevent you to boot the Seagate successfully uby bodhi - uBoot
petecom, > You'll need a Linux system to unbrick this box. > > In Windows 11: > 1) Connect to your computer with Windows 11 to USB > port --> AZDelivery CP2102 HW-598 USB auf Serial > Adapter CP2102 > 2) Install Drivers and check number of COM port > (devmgmt.msc) > 3) Install Software Putty on Windows 11 > 4) Run Putty on COM Terminal COM# (insby bodhi - uBoot