appears to be a lot of rumours ans multiple bug reports here but this looks like the one for not auto mounting I'm not sure it is a tifm module issue as HAL responds correctly on card insertion see below
Disk /dev/sda: 60.0 GB, 60011642880 bytes
240 heads, 63 sectors/track, 7752 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 250 1889968+ 82 Linux swap / Solaris
/dev/sda2 251 7752 56715120 83 Linux
Disk /dev/mmcblk0: 521 MB, 521011200 bytes
9 heads, 24 sectors/track, 4711 cylinders
Units = cylinders of 216 * 512 = 110592 bytes
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 2 4712 508685+ 6 FAT16
so all is good manual mounting the card works a treat to but feisty will not automount on insertion
this is a retrograde for edgy as with the .6 drivers it worked.
appears to be a lot of rumours ans multiple bug reports here but this looks like the one for not auto mounting I'm not sure it is a tifm module issue as HAL responds correctly on card insertion see below
I have rebuilt the tifm modules from
http:// openfacts. berlios. de/index- en...12/ xx21_driver
to replace the hopelessly buggy stock 2.6.20 kernel
All is good and installing the card gives
[ 714.680000] tifm_core: MMC/SD card detected in socket 0:3
[ 714.972000] mmcblk0: mmc3:0001 SDMMC 508800KiB
[ 714.972000] mmcblk0: p1
fdisk -l
Disk /dev/sda: 60.0 GB, 60011642880 bytes
240 heads, 63 sectors/track, 7752 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 250 1889968+ 82 Linux swap / Solaris
/dev/sda2 251 7752 56715120 83 Linux
Disk /dev/mmcblk0: 521 MB, 521011200 bytes
9 heads, 24 sectors/track, 4711 cylinders
Units = cylinders of 216 * 512 = 110592 bytes
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 2 4712 508685+ 6 FAT16
so all is good manual mounting the card works a treat to but feisty will not automount on insertion
this is a retrograde for edgy as with the .6 drivers it worked.
I suspect this is a mmc problem as
lshal -m gives
Start monitoring devicelist: ------- ------- ------- ------- ------- ------- 8033_mmc_ host added
-------
pci_104c_
on card insertion so why doesn't fiesty react to the hal event ??