Hello Bodhi, Thank you for your answer. I will indeed look in to the working thread to see what I can find. I also stumbled on the web on this site with scripts to automate a (Lenovo)iomega-ix2 install for either usb / ide or disk install so was also reading trough the scripts what it does. It seems to have been made for using your Kirkwood builds. https://minaret.biz/tips/ix2/index.html#by cable - Debian
Hello Bodhi, I was searching if I stored somewhere my original boot log when it was still running the latest firmware from iomega. there I saw this line. Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0xa0000@0x0(uboot),0x10000@0xa0000(env),0x224000@0xb0000(zImage),0x224000@0x2d4000(initrd),32m@0x0(flash) also this NAND device: Manufacturer ID: 0xec, Chip ID: 0xby cable - Debian
Hello Bodhi, It now seems to give no more errors. Runs with your downloaded tool set and the build tool set. Now I am still trying to see how to change the envs so it will boot directly from disk. Debian GNU/Linux 11 debian ttyS0 debian login: root Password: Linux debian 5.13.6-kirkwood-tld-1 #1.0 PREEMPT Sat Jul 31 22:10:39 PDT 2021 armv5tel The programs included with the Deby cable - Debian
Hello Bodhi, Well I managed to now let it start with the rootfs from disk. Using most of the wiki boot from raid1 info. Except now it still boots from usb disk kernel and then loads the disk rootfs if I see it correct. Marvell>> setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial' Marvell>> seby cable - Debian
Hello Bodhi, Thank you for the answer. From where you pointed at I found this line added under what you wrote. Not sure if that is correct for the iomega-ix4-200d. setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial' setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage' setenv load_uinitrdby cable - Debian