There were a few things that differed from the expected results in the flashing instructions. Only one real error. That was in the command to dump mtd0. The rest are inconsiquential but since they differed from the instructions I thought I'd list them and let you decide how/if to handle it. section 2.1 command is incorrect; missing '-f' before output filename section 2.2 prby sparks - uBoot
Looks good. root@balder:/home/michael/Downloads/u-boot-dns325/test new uboot# ../kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2024.10-tld-1.dns325.kwb -p Sending boot message. Please reboot the target...| Sending boot image... 0 % [......................................................................] 1 % [......................................................................] 3 % [by sparks - uBoot
Much joy! Things look very good from my perspective. I had to do some cleanup to get it this way. Plus I moved the boot disk to one of the SATA disks. I figured I'd need that usb port someday to expand my jbod. Thank you. root@balder:/home/michael/Downloads/u-boot-dns325/test new uboot# ../kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2024.10-tld-1.dns325.kwb -p Sending boot message. Plby sparks - uBoot
The good news is that the system boots. The bad news is that it seems to be really confused about the network and leaves it in a non-working state. I booted with uboot.2021.04-tld-1.dns325.mtd0.kwb just to check that it still worked. It booted just fine. I use uEnv.txt for the older u-boot. There was no mention of this file in your post so I didn't use it for the test. I used only uboot.2024by sparks - uBoot
Thank you for your last suggestion. It got my boxes booted into Debian. I hadn't mentioned that I have 2 of these boxes. The reason for the delay in reply is that one of the boxes boots but doesn't recognize the hard drives. I've been spending a lot of time trying to figure this out. I approached it as a software problem and burned a lot of time getting nowhere. I went down this paby sparks - uBoot
bodhi Wrote: ------------------------------------------------------- > > 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 tby sparks - uBoot
I forgot to include the boot messages. Quoteroot@balder:/home/michael/Downloads/u-boot-dns325# ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2021.04-tld-1.dns325.mtd0.kwb -p Sending boot message. Please reboot the target.../ Sending boot image... 0 % [......................................................................] 1 % [.............................................................by sparks - uBoot
@bodhi, In the topic u-boot for d-link dns35, you provide u-boot for the device but with the warning not to flash to nand. I have DLed the u-boot and have been able to boot via UART and there was much joy. Could I get a version of this that is flashable? What makes the version in the linked topic unflashable? I have tried to cross-compile u-boot myself but never had success. To shamelesslyby sparks - uBoot
> Did you chroot into it to install kernel? Yes, I did. > Did you use Ext3 or Ext4 for the format? I used ext3 for the bad USB stick. I am also surprised that it didn't recover but I don't know how else to explain it. Everything is running well enough so no use spending any more time on 'what happened?'. I've been a lurker for several years and would likby sparks - uBoot
I did as you suggested. I even added the 'c' option for fsck. The check did modify the filesystem. I reinstalled the kernel to create a new initrd.img... and then recreated uInitrd. No joy. I went and made a new usb boot drive from the Debian image and copied non-boot files from the bad drive. It works but apt-get and dpkg are a little wonky. They don't recognize some packages as iby sparks - uBoot
While I was away on holidays, my home suffered a power outage. When I came home and tried to access my GoFlexHome (that I usually turn off when going away), I couldn't. The NC Console showed me this: Found bootable drive on usb 0 Bootargs = console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) init=/bin/systemd loading uImageby sparks - uBoot
I had a similar problem on my Seagate FreeAgent. I came across this thread looking for an answer. Taking Bodhi's lead I looked for shell solution. What I ended up doing is stopping /etc/network/if-up.d/nptdate from running and added ntpdate to the ntp start script. To /etc/network/if-up.d/nptdate I added an exit statement thus: Quote #!/bin/sh exit 0 blah blah blah... It effectivelyby sparks - Debian