Hi Srikant,
In my system, i have something like this,
# ls -l /sys/class/mmc_host/mmc1/
lrwxrwxrwx 1 0 0 0 Jan 1 00:00 device ->
../../../MMC
drwxr-xr-x 4 0 0 0 Jan 1 00:00 mmc1:bf0a
drwxr-xr-x 2 0 0 0 Jan 1 00:00 power
lrwxrwxrwx 1 0 0 0 Jan 1 00:00 subsystem ->
../../../../class/mmc_host
-rw-r--r-- 1 0 0 4096 Jan 1 00:00 uevent
# ls -l /sys/class/mmc_host/mmc0
lrwxrwxrwx 1 0 0 0 Jan 1 00:00
/sys/class/mmc_host/mmc0 -> ../../devices/EMMC/mmc_host/mmc0
#
#ls /sys/devices/platform
it shows uevent and some other components specific to my platform and no MMC
components.
But i have something like this,
# ls /sys/devices/MMC
driver irq0 power subsystem
id mmc_host resource uevent
# ls /sys/devices/MMC/mmc_host
mmc1
# ls /sys/devices/MMC/mmc_host/mmc1
device mmc1:bf0a power subsystem uevent
That is why i have choosen the media path in vold.conf as below:
## vold configuration file for the emulator/SDK
volume_sdcard {
## This is the direct uevent device path to the SD slot on the device
media_path /devices/MMC/mmc_host/mmc1
media_type mmc
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun0
}
Please let me know if this is not fine.
Regards,
Sreedhar
On Wed, Nov 11, 2009 at 3:08 PM, Srikant <w.sreeka...@gmail.com> wrote:
> Change your development/data/etc/vold.conf file "media_path" to the
> correct path as per your device file system from the adb shell and
> find /class/mmc/mmc0 or similar exists.
>
> Then build it and see.
>
> On Nov 10, 11:24 am, sreedhar b <sreedhar...@gmail.com> wrote:
> > I have seen this problem in cupcake versions also where vold is involved.
> > Sdcard was not an issue with mountd earlier.
> >
> >
> >
> > On Mon, Nov 9, 2009 at 10:30 AM, Hayden Huang <h.huang1...@gmail.com>
> wrote:
> > > I am having exactly same problem here.
> > > is it caused by the donut release or it can work before?
> >
> > > On Nov 4, 10:41 pm, sreedhar b <sreedhar...@gmail.com> wrote:
> > > > Hi All,
> >
> > > > Iam seeing the SDcard mount issue with the donut release 1.6_r1.
> >
> > > > This uses vold.
> >
> > > > Please see the below log portion for details:
> >
> > > > # I/vold ( 620): Android Volume Daemon version 2.0
> > > > I/vold ( 620): New MMC card 'MMC08G' (serial 520946106) added @
> > > > /devices/EMMC/mmc_host/mmc0/mmc0:0001
> > > > I/vold ( 620): Disk (blkdev 179:0), 15638528 secs (7636 MB) 4
> > > partitions
> > > > I/vold ( 620): New blkdev 179.0 on media MMC08G, media path
> > > > /devices/EMMC/mmc_host/mmc0/mmc0:0001, Dpp 4
> > > > I/vold ( 620): Partition (blkdev 179:1), 16384 secs (8 MB) type
> 0x83
> > > > I/vold ( 620): New blkdev 179.1 on media MMC08G, media path
> > > > /devices/EMMC/mmc_host/mmc0/mmc0:0001, Dpp 3
> > > > I/vold ( 620): Partition (blkdev 179:2), 524288 secs (256 MB)
> type
> > > 0x83
> > > > I/vold ( 620): New blkdev 179.2 on media MMC08G, media path
> > > > /devices/EMMC/mmc_host/mmc0/mmc0:0001, Dpp 2
> > > > I/vold ( 620): Partition (blkdev 179:3), 2277376 secs (1112 MB)
> type
> > > > 0x83
> > > > I/vold ( 620): New blkdev 179.3 on media MMC08G, media path
> > > > /devices/EMMC/mmc_host/mmc0/mmc0:0001, Dpp 1
> > > > I/vold ( 620): New MMC card 'SU02G
> > > > I/vold ( 620): ' (serial 821168021) added @
> > > > /devices/MMC/mmc_host/mmc1/mmc1:bf0a
> > > > I/vold ( 620): Disk (blkdev 179:8), 3862528 secs (1886 MB) 4
> > > partitions
> > > > I/vold ( 620): New blkdev 179.8 on media SU02G
> > > > I/vold ( 620): , media path /devices/MMC/mmc_host/mmc1/mmc1:bf0a,
> Dpp
> > > 1
> > > > W/vold ( 620): Skipping partition 8
> > > > I/vold ( 620): Partition (blkdev 179:9), 3858489 secs (1884 MB)
> type
> > > 0x0
> > > > I/vold ( 620): New blkdev 179.9 on media SU02G
> > > > I/vold ( 620): , media path /devices/MMC/mmc_host/mmc1/mmc1:bf0a,
> Dpp
> > > 0
> > > > E/vold ( 620): Unable to open '/sys/class/switch' (No such file
> or
> > > > directory)
> > > > D/vold ( 620): Bootstrapping complete
> >
> > > > -------------------------------------------------------------------
> >
> > > > D/vold ( 620): Accepted connection from framework
> > > > D/vold ( 620): dispatch_cmd(send_ums_status):
> > > > D/dalvikvm( 636): GC freed 4588 objects / 209768 bytes in 105ms
> > > > D/MountListener( 636): handleEvent volume_nomedia:/sdcard
> > > > D/vold ( 620): dispatch_cmd(mount_volume:/sdcard):
> > > > E/vold ( 620): Cannot start volume '/sdcard' (volume is not
> bound)
> >
> > > > The log gives some error like this
> > > > E/vold ( 620): Unable to open '/sys/class/switch' (No such file
> or
> > > > directory)
> > > > E/vold ( 620): Cannot start volume '/sdcard' (volume is not
> bound)
> >
> > > > Please let me know if someone already has seen this issue and how to
> > > > overcome the same.
> >
> > > > If i manually run the following command,
> > > > $mount -t vfat /dev/block/mmcblk1p1 /sdcard
> >
> > > > then i am able to see inside the /sdcard my SDCard contents.
> >
> > > > Regards,
> > > > Sreedhar
> >
> > > --
> > > unsubscribe:
> > > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com>
> <android-porting%2bunsubscr...@googlegroups.com>
> > > website:http://groups.google.com/group/android-porting- Hide quoted
> text -
> >
> > - Show quoted text -
>
> --
> unsubscribe:
> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com>
> website: http://groups.google.com/group/android-porting
>
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
