I'm currently using the software installed by the Alpha-6 installer
, which includes the Uboot mentioned here
, and the 2.6.30-rc6 kernel.
I'm not sure why the kernel would be important, as the problem occurs before the kernel is loaded.
I have not tried another SDcard. (Actually, I don't have any other cards handy.) However, the card in question has been used for the past month under the original and rc6 kernels w/o exhibiting any problems.
My desire is to eventually upgrade to the 126.96.36.199 kernel, but I'd like to be able to figure out how to make it boot completely off the SDcard so that I have a fall back path if something doesn't work right.
Here is the output of some manually entered commands from Uboot:
U-Boot 1.1.4 (May 13 2009 - 13:10:52) Marvell version: 3.4.16
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CF100
Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz
DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS base 0x00000000 size 256MB
DRAM CS base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Flash: 0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
CPU : Marvell Feroceon (Rev 1)
Write allocate disabled
USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0
SDHC found. Card desciption is:
Manufacturer: 0x1d, OEM "AD"
Product name: "SD ", revision 0.0
Serial number: 3003129443
Manufacturing date: 5/2009
CRC: 0x00, b0 = 0
Marvell>> ext2ls mmc 0:1 /
<DIR> 4096 .
<DIR> 4096 ..
<DIR> 16384 lost+found
<DIR> 0 bin
<DIR> 4096 dev
<DIR> 4096 etc
<DIR> 4096 lib
<DIR> 4096 mnt
<DIR> 4096 opt
<DIR> 4096 srv
<DIR> 4096 tmp
<DIR> 4096 sys
<DIR> 4096 var
<DIR> 0 usr
<DIR> 4096 boot
<DIR> 0 home
<DIR> 0 proc
<DIR> 4096 sbin
<DIR> 4096 root
<DIR> 4096 media
<DIR> 4096 selinux
<DIR> 4096 hd
Marvell>> ext2ls mmc 0:1 /boot
<DIR> 4096 .
<DIR> 4096 ..
Marvell>> ext2ls mmc 0:2
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:2 **
Marvell>> ext2load mmc 0:1 0x800000 /uImage
0 bytes read
Note the zero lengths on some of the directories in the ext2ls
listing, and the uImage. Note that the ext2load
command doesn't fail -- it just reads in zero bytes. Also note that the "0:2" attempt fails, although once I boot Linux, I can access this partition w/o problems.
Anyway, that's where I stand. I'm hoping someone may see something I dont.
Addendum: I just satisfied myself that I was able to change the bootargs_root
parameter to "root=/dev/mmcblk0p2" and boot Linux with the root FS being the second partition. I really believe the inability to access the second partition with Uboot is entirely a Uboot issue. (And, this doesn't address the zero-length file issue at all.)