Can you check http://review.omapzoom.org/5228?
We need to explicitly place vold.fstab in /system/etc of file system during froyo boot. //Deva On Fri, Aug 13, 2010 at 1:56 PM, Dark Knight <[email protected]> wrote: > Hi, > > > Have u set up your battery driver properly in your kernel? > Coz i have observed that the sdcard detection has a dependency of > battery (power) drivers. > > Also the path to be specified in vold.fstab should be that of the > sdcard under /sys directory than /dev directory. > > This my vold.fstab entry: > > # Mounts the first usable partition of the specified device > dev_mount sdcard /mnt/sdcard auto > /devices/platform/pxa2xx- > mci.0/mmc_host/mmc0 > > > Regards > Vaisakh P S > > On Aug 13, 11:11 am, 邱建波 <[email protected]> wrote: > > try > > "dev_mount sdcard /mnt/sdcard auto /block/mmcblk0" > > in vold.fstab > > > > 2010/8/12 Anthony Russello <[email protected]> > > > > > > > > > > > > > Hi All, > > > > > I am currently working on bringing up Froyo on a device on which we > > > are booting to the sdcard. U-Boot, kernel, and root filesystem are all > > > there on separate partitions. > > > > > We have a partition, /dev/block/mmcblk0p1, which has a FAT32 > > > filesystem to be used as /mnt/sdcard. In Eclair, this worked fine. But > > > with the new vold, we find that it fails. > > > > > I'm using the Freescale i.MX51 platform, my vold.fstab looks like > > > this: > > > > > dev_mount sdcard /mnt/sdcard auto /devices/platform/mxsdhci.0 > > > > > I've also tried: > > > > > dev_mount sdcard /mnt/sdcard auto /devices/platform/mxsdhci.0/ > > > mmc_host/mmc0 > > > > > dev_mount sdcard /mnt/sdcard auto /devices/platform/mxsdhci.0/ > > > mmc_host/mmc0/mmc0:b368 > > > > > Niether of those worked either. > > > > > Here's the output I get while booting: > > > > > I/Netd ( 2041): Netd 1.0 starting > > > I/Vold ( 2040): Vold 2.1 (the revenge) firing up > > > D/Vold ( 2040): Volume sdcard state changing -1 (Initializing) - > > > > 0 (No-Media) > > > D/DirectVolume( 2040): Dv::diskIns - waiting for 6 partitions (mask > > > 0x7e) > > > D/Vold ( 2040): Volume sdcard state changing 0 (No-Media) -> 2 > > > (Pending) > > > D/DirectVolume( 2040): Dv:partAdd: part_num = 1, minor = 1 > > > D/DirectVolume( 2040): Dv:partAdd: pending mask now = 0x7c > > > D/DirectVolume( 2040): Dv:partAdd: part_num = 2, minor = 2 > > > D/DirectVolume( 2040): Dv:partAdd: pending mask now = 0x78 > > > D/DirectVolume( 2040): Dv:partAdd: part_num = 3, minor = 3 > > > D/DirectVolume( 2040): Dv:partAdd: pending mask now = 0x70 > > > D/DirectVolume( 2040): Dv:partAdd: part_num = 4, minor = 4 > > > D/DirectVolume( 2040): Dv:partAdd: pending mask now = 0x60 > > > D/DirectVolume( 2040): Dv:partAdd: part_num = 5, minor = 5 > > > D/DirectVolume( 2040): Dv:partAdd: pending mask now = 0x40 > > > D/DirectVolume( 2040): Dv:partAdd: part_num = 6, minor = 6 > > > D/DirectVolume( 2040): Dv:partAdd: pending mask now = 0x6 > > > > > And here is some output from the vdc command line interface: > > > > > # vdc volume list > > > 110 sdcard /mnt/sdcard 2 > > > 200 Volumes listed. > > > # vdc volume mount /mnt/sdcard > > > 405 volume operation failed (Device or resource busy) > > > > > I can manually mount the device using this command without any error: > > > > > mount -t vfat /dev/block/mmcblk0p1 /mnt/sdcard > > > > > Any help with this would be appreciated. > > > > > Thanks, > > > Anthony > > > > > -- > > > unsubscribe: > > > [email protected]<android-porting%[email protected]> > <android-porting%2Bunsubscribe@ googlegroups.com> > > > website:http://groups.google.com/group/android-porting > > > > -- > > ------ > > > > Jianbo Qiu (邱建波) > > > > Mobile: 13681184653 > > > > MSN:[email protected] <msn%[email protected]> < > msn%[email protected] <msn%[email protected]>> > > > > ------ > > -- > unsubscribe: > [email protected]<android-porting%[email protected]> > website: http://groups.google.com/group/android-porting > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
