Re: Iomega ix2-200
"Lars M. Johansson" <lars.m.johansson@gmail.com> writes:
> Hi all,
Hi,
>
> I've been experimenting a bit with installing Debian on my ix2-200.
> I've managed to install a full system using the OpenRD installer and
> arcNumber 1682 (the ix2-200 identifies itself as such during it's
> factory boot sequence).
> The installation runs fine, except for the "make system bootable" step
> (flash is not at the same adress, or something, i guess), but when I
it would not be surprising to have differences like different flash
partition or even different flash chip. There may be even more HW
differences than that.
> try to boot the kernel and initrd instaled on my boot partition I get
> Bad Magic Number (see below)!?
> The installation kernel obviously boots fine, any pointers to what
> could be the problem?
> (I'm happy to supply the installed kernel and initrd images on request...)
>
> Kind regards,
> Lars
>
> Marvell>> ide reset
>
> Reset IDE:
> Marvell Serial ATA Adapter
> Integrated Sata device found
> [0 0 0]: Enable DMA mode
> Device 0 @ 0 0:
> Model: ST31000520AS Firm: CC37 Ser#:
> 5VX0ZAH5
> Type: Hard Disk
> Supports 48-bit addressing
> Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
> [0 1 0]: Enable DMA mode
> Device 1 @ 0 1:
> Model: ST31000520AS Firm: CC37 Ser#:
> 5VX0Y76L
> Type: Hard Disk
> Supports 48-bit addressing
> Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
>
> Marvell>> ext2ls ide 0:1
> <DIR> 1024 .
> <DIR> 1024 ..
> <DIR> 12288 lost+found
> 1435120 vmlinuz-2.6.32-5-kirkwood
> 84134 config-2.6.32-5-kirkwood
> <SYM> 28 initrd.img
> <SYM> 25 vmlinuz
> 1004912 System.map-2.6.32-5-kirkwood
> 5480642 initrd.img-2.6.32-5-kirkwood
> Marvell>> setenv bootargs 'console=ttyS0,115200 root=/dev/sdb3'
> Marvell>> ext2load ide 0:1 0x01100000 /initrd.img
>
> 5480642 bytes read
> Marvell>>
> Marvell>> ext2load ide 0:1 0x00800000 /vmlinuz
uboot needs a uImage file (made with mkimage from uboot-envtools) :
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n "2.6.32.5-kirkwood" -d vmlinuz uImage
and then load the uImage instead of vmlinuz file.
Arnaud
Reply to: