> You can find how to set up to boot the ix4-200d
> with stock u-boot using USB rootfs here:
> http://forum.doozan.com/read.php?3,25120
Bingo! I was able to boot stock rootfs, after fiddling a bit with correct cut&paste of setenv row into minicom...
But after that, i've upgrade the kernel to the latest 4.8.3 (and really, done a 'apt-get update && apt-get dist-upgrade') and after that seems there's no way to get the system boot back:
USB key seems ok.
I've tried to connect to my main linux box and get mounted.
But i've also done a 'e2fsck -f' by hand and now i can boot back again.
This is caused by using ext3 as FS? Better to switch to ext2?
Now, some more experimenting...
> with stock u-boot using USB rootfs here:
> http://forum.doozan.com/read.php?3,25120
Bingo! I was able to boot stock rootfs, after fiddling a bit with correct cut&paste of setenv row into minicom...
But after that, i've upgrade the kernel to the latest 4.8.3 (and really, done a 'apt-get update && apt-get dist-upgrade') and after that seems there's no way to get the system boot back:
Marvell>> boot
(Re)start USB...
USB: scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... T Device NOT ready
Request Sense returned 00 00 00
1 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 00800000 ...
Bad Magic Number
USB key seems ok.
I've tried to connect to my main linux box and get mounted.
But i've also done a 'e2fsck -f' by hand and now i can boot back again.
This is caused by using ext3 as FS? Better to switch to ext2?
root@debian:~# uname -a Linux debian 4.8.3-kirkwood-tld-1 #1 PREEMPT Thu Oct 20 23:33:18 PDT 2016 armv5tel GNU/Linux
Now, some more experimenting...