> That link is over four years old, and other > sources say that ubldr.bin should be loaded rather > than kernel.bin. Gravelrash was correct. That link might be old, it is still relevant. As I mentioned, there are 2 different ways to boot FreeBSD, as far as I understood from my research. Quotebodhi @Gravelrash, Yes, that would be the address for the go command. There are 2by bodhi - uBoot
Peter, Power up, Interrupt serial console and execute bdinfo. Hopefully this command will be available and show it in the output. bdinfoby bodhi - Debian
@Gravelrash, Yes, that would be the address for the go command. There are 2 different ways to boot FreeBSD: 1. use go to boot the kernel.bin at 0x900000 2. use a diffrent address such as 0x800000 to boot the ubldr.bin using bootelf. @balanga, The only way I know how to help you was stated here: https://forum.doozan.com/read.php?3,34799,35928#msg-35928by bodhi - uBoot
Peter, > advance to boot your new kernel. > Right? Right! everything looks good in your post.by bodhi - Debian
braian87b, Create the USB rootfs using Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (24 Jul 2017). https://forum.doozan.com/read.php?2,12096 And use the kirkwood-lenovo-iomega-ez.dtb from this post: https://forum.doozan.com/read.php?2,15887,36138#msg-36138 If you have serial console, then try what iomega_ez did to set up booting the new USB rootfs: https://forum.doozan.com/reby bodhi - Debian
It looks good! With this exception: > *** Warning - bad CRC, using default environment This means you did not flash the defaut envs image. The internal envs in this u-boot version has been improved so that's why it booted OK. But the default envs image is what you really want. And this also, [ 0.000000] Kernel command line: console=ttyS0,115200n8 earlyprintk root=/dev/sby bodhi - uBoot
Hi Peter, That's a nice script! how an experienced Linux user would go about doing this. However, we need something more concrete here to verify the correctness of the commands (the script added a layer of abstraction). What are the MTDs? we'll find them in the following outputs. dmesg # to see the mtd definitions as the kernel detects them, and see where theby bodhi - Debian
Kernel linux-4.14.1-mvebu-tld-1 package has been uploaded. Please see 1st post for download link.by bodhi - Debian
Dwayne, > 1) What are the advantages of moving this box to > the current version of Debian? I assume security > updates are a good enough reason but any other > benefits? The benefits are countless. Hard to know where to begin! > 2) I'm going to want to back up the original hard > drive before I mess with it. I've gone through > several Disk Imagingby bodhi - Debian
Peter2017, > Before I start with installing a new uboot and or > kernel etc., I'd like to completely backup the > EEPROM (the environment is saved there, I suppose) > and the flash (uboot, kernel, initrd). > > Is there a safe and verified way to do so? > I think it was helge; I stumbled about some > scripts dd'ing the mtd-devices (called raw backup) &by bodhi - Debian
JRD, Following the instruction and flash the u-boot image and its default envs image. You will be able to set the MAC address.by bodhi - Debian
Rainer, You need to install the kernel first before you can generate uImage and uInitrd. Quote3. And install it with dpkg. Remove flash-kernel first to avoid potential problem (It is much better to generate uImage and uInitrd manually anyway):by bodhi - Debian
Quotehmartin Wrote: ------------------------------------------------------- > Quotebodhi > Other devices uses 19200n8, do you mean WD NAS > devices? > > > I guess since mcm-daemon is only for WD devices, > yes I mean other WD NAS devices use 19200 and the > EX2100 uses 115200 for MCU baud rate. Argh :) that's just thoughtless WD. Glad you've figured tby bodhi - Debian
Kernel linux-4.14.1-kirkwood-tld-1 package has been uploaded. Please 1st post for download link.by bodhi - Debian
wacke, > Thanks for your reply,I've tried to port that > patch to mainline uboot,there are too much errors > when compiling..... Like I said, it is based on a quite old u-boot, so it will be too much works to build.by bodhi - uBoot
epk Wrote: ------------------------------------------------------- > I went back to step 4 in the (oxnas) rootfs thread > just to make sure I did everything right. I > followed all the steps, edited my fstab, generated > the uInitrd, rebooted, u-boot, looks fine, it > starts the kernel, and then that's about it. It > never shows back up on the network. Not sure whereby bodhi - Debian
hughe, Glad you've resolved it! let me know how it goes with flashing new u-boot and envs images.by bodhi - uBoot
maldridge, > It is 2.5", but for that I would need a working > system right? Right! so it's too bad you don't have a Pogo V4, Goflex Net/Home, that you can just plug in this HDD. Those are the least expensive plugs that have a SATA interface. > Perhaps I need a sacrificial partition at > the start of the disk? I don't think so. I think probably yourby bodhi - uBoot
wacke, > I have a device use the armada 370 soc,but there > is no mainline uboot support.And I found someone > make some patch to support the armada 370 see: > https://sites.google.com/site/shihsung/88fxxxx-soc > > Is there anyway to port that patch to the mainline > uboot? That patch seems to be on top of a very old u-boot. So I'd rather not try to fit itby bodhi - uBoot
maldridge Wrote: ------------------------------------------------------- > The only thing I can come up with at this point is > either a bad disk (seems odd, it takes and retains > the partition table) or a bad SATA controller. > The second is plausible since I'm going USB-SATA > and I could see something getting reset or > corrupted in the transfer. I guess I coulby bodhi - uBoot
maldridge, I did not see anything wrong above. However, slightly off topic: I would suggest never use sudo while you are doing this. You must be root user to avoid any future complication while hacking.by bodhi - uBoot
OXNAS command to generate uInitrd looks like this: cd /boot mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-4.4.54-oxnas-tld-1 -d initrd.img-4.4.54-oxnas-tld-1 uInitrdby bodhi - Debian
However, be aware that Item f is different for OXNAS f. Usually a distribution upgrade like this would result in a new initramfs. So regenerate the uInitrd boot file. See section 4 in my kernel/rootfs installation for how to recreate uInitrd. It should look like this example: cd /boot mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.11.3-kirkwood-tldby bodhi - Debian
You can find the answer here: https://forum.doozan.com/read.php?2,35581 - Backup your rootfs. - Do dist-upgrade to stretch as described in the instruction above.by bodhi - Debian
Last post moved here: https://forum.doozan.com/read.php?2,43154by bodhi - Debian
maldridge, Please post your disk_create script, and the output of fdisk -l before running it.by bodhi - uBoot
huge, > OK ... likely I'm being dense ... can I just > ignore this and skip to extracting the uBoot > archive? Yes, you are in stock OS. Quote/tmp # fw_printenv Warning: Bad CRC, using default environment bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm bootdelay=5 baby bodhi - uBoot
raffe, > Only key that the LG N1T1 showed for esekeyd was > the back-up button (KEY_133), no other button did > anything. > So I use the "red power button" for starting up > and the "back-up" for shutdown, and made nice > stickers saying so :) :) well done. So are there other buttons on this box, what are they? If there are, then they could bby bodhi - Debian
hmartin, > After some further investigation I have determined > the MCU in the EX2100 communicates at 115200n8 not > 19200n8 as on other devices. Other devices uses 19200n8, do you mean WD NAS devices? > Hoping this helps someone. Absolutely will be great to be able to control the fan.by bodhi - Debian
@hmartin, Cool :) I was going to ask you to try the optware approach if the mcm-daemon is too much trouble. QuoteMaybe you can try the modified mcm-daemon on EX4100 and see if it works? I don't have this box, we need saschadd to test it. @sashadd, Please try hmartin's mcm-daemon build.by bodhi - Debian