Re: [Kernel-discuss] Re: SD problems (on h5450)

Can't there be a problem in:

samcop_sdi_card_power: MMC subsystem requesting bogus clock rate 0. Hardcoding
prescaler to 255

?

How is it even possible this message is printed several times during the boot?
Shouldn't it be printed only once?

My observations show the boot process stops for several seconds after the

NET: Registered protocol family 1

and before

samcop_sdi_card_power: MMC subsystem requesting bogus clock rate 0. Hardcoding
prescaler to 255
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(254,2)

Looks like samcop code is waiting for something. Any ideas what should I do to
get more info on what's going on?

Thanks...
Radek Podgorny

> On Wed, Nov 02, 2005 at 11:07:08PM +0100, Radek Podgorny wrote:
> > Removing devfs didn't help :-( Everything seems to be the same...
> >
> > Radek Podgorny
> >
> > > On Wednesday 02 November 2005 11:28 am, you wrote:
> > > > That's exactly what I'd say, but it's weird. As I've said already, I
> > > > do have everything in kernel (even the ext2 drivers - the SD
> > > > filesystem). When I boot it and mount the SD later it works (no, no
> > > > modules loaded - they are not even there) but when I want it to mount
> > > > the SD at boot time, it fails...
> > > >
> > > > Has anyone tried the root-on-SD boot?
>
> Not on the h5400. I defer to Matt's advice on whether anything needs to
> be done to get the samcop sdi ready for a pivot.
>
> Is that the right block on the sd card that is reporting on the kernel
> panic?
>
> E
>
> > > I do it all the time on my h2200.
> > >
> > > Do you have devfs built into the kernel? If so, try removing it.
> > >
> > > Matt
> > >
> > > > > 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
> >
> > --
> > GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x98E56D84
> >
> >
> >
> > _______________________________________________
> > Kernel-discuss mailing list
> > Kernel-discuss_at_handhelds.org
> > https://handhelds.org/mailman/listinfo/kernel-discuss

-- 
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x98E56D84