uKev wrote:Then with the new version of the script during the installation my usb drive got mounted by the system (I guess iomega services) and as a result the formatting/partitioning failed.
But there is another issue with the installation: If I "cold-start" the iconnect (power off->on) it will boot into the debian/iconnect system even though my archlinux usb drive is plugged in. I have to ssh into the box and type "reboot" again. Then it boots into my archlinux drive.
igorert wrote:Hmm, the script is explicitly unmounting the drive during the installation. If you can reproduce it, I'd like to see /var/log/iconnect-install.log - copy it over after running the script, it's not preserved after reboot.
igorert wrote:In general, if you have a Linux box you can format the USB stick as ext2 there and unpack http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz to it manually; you can then skip the arch installation portion of the script.
igorert wrote:Try this with another USB stick - occasionally uboot is not able to properly initialize one during cold boot, it happens to me with one of 5 or 6 usb sticks I've tried. As far as I know, it hasn't been fully fixed in newer uboots either. You could try bumping up rootdelay parameter but I doubt it'll help.
uKev wrote:But I can say already that I unmounted the usb drive after the failed installation manually and the system remounted it five seconds later automatically...
You really could have mentioned that earlier . I didn't read through your script and guessed it would do some more magic .
# iomega iconnect
# MTD device name Device offset Env. size Flash sector size
/dev/mtd0 0xa0000 0x20000 0x20000
bknight wrote:can't figure how to slow down eth0
Users browsing this forum: No registered users and 4 guests