Martin Michlmayr wrote:
* Jonas Häggqvist [2009-10-27 01:23]:
setenv bootcmd_mmc 'mmcinit; ext2load mmc 0:1 0x080 /boot/uInitrd; ext2load
mmc 0:1 0x40 /boot/uImage'
or
setenv bootcmd_mmc 'mmcinit; ext2load mmc 0:2 0x080 /boot/uInitrd; ext2load
mmc 0:2 0x4000
Martin Michlmayr wrote:
* Jonas Häggqvist [2009-10-27 00:38]:
Marvell>> setenv bootcmd_mmc 'mmcinit; ext2load mmc 0 0x080
/boot/uInitrd; ext2load mmc 0 0x40 /boot/uImage'
I'm not sure, but can you try
setenv bootcmd_mmc 'mmcinit; ext2load mmc 0:1 0x08000
0x00, b0 = 0
** Invalid partition type "" (expect "U-Boot")
** Invalid partition type "" (expect "U-Boot")
## Booting image at 0040 ...
Bad Magic Number
Marvell>>
U-Boot 1.1.4 (Sep 14 2009 - 15:36:37) Marvell version: 3.4.19
file system corruption, so I assume this *might* be related, but I
obviously don't know for sure.
The file system is clean now, and /lost+found doesn't seem to contain
anything interesting as far as I can tell.
Running armel, Linux kernel 2.6.25-7
Any help appreciated.
--
Jonas Häggqv
4 matches
Mail list logo