Re: SD problems (on h5450)

On Wednesday 02 November 2005 09:48 am, Radek Podgorny wrote:
> Hi,
>
> I've tried the new driver and it seems to be working only half-way:
>
> I create a monolithic 2.6 kernel image and move it /boot on the internal
> flash. When I boot it normally (root=/dev/mtdblock1) it seems to be working
> ok and I can mount my SD card without a problem. BUT! When I try to boot
> the kernel with root=/dev/mmcblk0p2 it fails with:
>
> ...
> samcop_sdi_card_power: MMC subsystem requesting bogus clock rate 0.
> Hardcoding prescaler to 255
> samcop sdi: initialisation done.
> NET: Registered protocol family 2
> samcop_sdi_card_power: samcop gpio clock rate 50000000
> samcop_sdi_card_power: MMC subsystem requesting bogus clock rate 0.
> Hardcoding prescaler to 255
> samcop_sdi_card_power: samcop gpio clock rate 50000000
> samcop_sdi_card_power: samcop gpio clock rate 50000000
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> TCP established hash table entries: 4096 (order: 3, 32768 bytes)
> TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
> TCP: Hash tables configured (established 4096 bind 4096)
> TCP reno registered
> TCP bic registered
> NET: Registered protocol family 1
> mmc0: host does not support reading read-only switch. assuming
> write-enable. samcop_sdi_card_power: samcop gpio clock rate 50000000
> samcop_sdi_card_power: samcop gpio clock rate 50000000
> samcop_sdi_card_power: samcop gpio clock rate 50000000
> samcop_sdi_card_power: samcop gpio clock rate 50000000
> mmcblk0: mmc0:0d9e SD512 500224KiB
> /dev/mmc/blk0:<7>MMC: starting cmd 12 arg 00000000 flags 00000009
> p1 p2
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(254,2)
>
> This is strange since I use no modules so it should work for both
> boot-from-sd and mount-later or none of these two configs. You can see the
> card is detected correctly (even the partitions on it).
>
> Can anyone point me where the problem may be? Thanks...
>
> Radek Podgorny

My first guess would be that you don't have the right filesystem code built-in
to mount the rootfs. What kind of rootfs is it: vfat, ext2, ...? You'll need
to make sure all its dependencies are built-in.

Matt
Received on Wed Nov 02 2005 - 13:00:53 EST