Hello,
i have bought a faulty iomega ix4-200d which got the NAND flash erased. long story short, following this topic https://forum.doozan.com/read.php?3,25120 I have now fully working iomega ix4-200d grandpa. Problem was, that SHEEVAPLUG U-Boot could not be booted off the flash and the mtd0.bin file I have found in that thread did not recognize USB devices, so current status is:
kernel: Linux iomega 5.2.9-kirkwood-tld-1 #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019 armv5tel GNU/Linux
rootfs: Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2
dtb: kirkwood-iomega_ix4_200d.dtb (DTB file embedded in the kernel image)
the only option that worked for me was kernel + initrd are stored in 32MB NAND just after u-boot, I can post details if needed. RootFS is on the first SATA disk on first ext2 partition labeled as rootfs.
My problem (i knew it has to come but did not expect that early) is that the initrd image does not contain for example e2fsck or fuse. apt-get tries to generate new initrd image but that is being ignored because my NAS is booting kernel and ramdisk from NAND.
I have tried to replace ramdisk in NAND with the one generated by apt, but got "Bad magic number"
I'm not a master in linux, I'm happy to get this far, but is there anyone who could help me with following?
WHAT I NEED IS: I would like to get u-boot to boot Kernel and Ramdisk from either SATA disk or USB storage and not NAND, because I would like to update the kernel. . Sheevaplug u-boot loaded from UART works perfectly. But when flashed to NAND the box hangs right after power-on with no output on UART. Seems it does not find u-boot in NAND even when I used the same address to flash it.
would be anyone so kind and go through this nightmare with me?
I have the NAS attached on UART and can do kwboot and tftp, that's how I managed to get it working.
thanks
martin
i have bought a faulty iomega ix4-200d which got the NAND flash erased. long story short, following this topic https://forum.doozan.com/read.php?3,25120 I have now fully working iomega ix4-200d grandpa. Problem was, that SHEEVAPLUG U-Boot could not be booted off the flash and the mtd0.bin file I have found in that thread did not recognize USB devices, so current status is:
kernel: Linux iomega 5.2.9-kirkwood-tld-1 #1 PREEMPT Sat Aug 17 15:00:56 PDT 2019 armv5tel GNU/Linux
rootfs: Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2
dtb: kirkwood-iomega_ix4_200d.dtb (DTB file embedded in the kernel image)
the only option that worked for me was kernel + initrd are stored in 32MB NAND just after u-boot, I can post details if needed. RootFS is on the first SATA disk on first ext2 partition labeled as rootfs.
My problem (i knew it has to come but did not expect that early) is that the initrd image does not contain for example e2fsck or fuse. apt-get tries to generate new initrd image but that is being ignored because my NAS is booting kernel and ramdisk from NAND.
I have tried to replace ramdisk in NAND with the one generated by apt, but got "Bad magic number"
I'm not a master in linux, I'm happy to get this far, but is there anyone who could help me with following?
WHAT I NEED IS: I would like to get u-boot to boot Kernel and Ramdisk from either SATA disk or USB storage and not NAND, because I would like to update the kernel. . Sheevaplug u-boot loaded from UART works perfectly. But when flashed to NAND the box hangs right after power-on with no output on UART. Seems it does not find u-boot in NAND even when I used the same address to flash it.
would be anyone so kind and go through this nightmare with me?
I have the NAS attached on UART and can do kwboot and tftp, that's how I managed to get it working.
thanks
martin