Comment 2 for bug 493328

This bug appears to be caused by an incomplete driver.

According to this page:
http://openfacts.berlios.de/index-en.phtml?title=TI_FlashMedia_xx12/xx21_driver
the driver is implemented as a set of modules, tifm_xd being one of them. However, the page states that tifm_xd was in the early stages of development in September 2007 and it hasn't been updated since so I'm not sure of the current status.

This is consistent with the problem I see, I have a Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) as follows:
           *-storage
                description: Mass storage controller
                product: 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)
                vendor: Texas Instruments
                physical id: 9.2
                bus info: pci@0000:0a:09.2
                version: 00
                width: 32 bits
                clock: 33MHz
                capabilities: storage pm bus_master cap_list
                configuration: driver=tifm_7xx1 latency=57 maxlatency=4 mingnt=7
                resources: irq:20 memory:c8302000-c8302fff

When I insert an SD card /var/log/messages says this:
Feb 19 20:32:17 turk kernel: [11887.220081] tifm_core: MMC/SD card detected in socket 0:1
Feb 19 20:32:17 turk kernel: [11887.370285] mmc1: new MMC card at address 0001
Feb 19 20:32:17 turk kernel: [11887.373017] mmcblk0: mmc1:0001 16M 15.3 MiB
Feb 19 20:32:17 turk kernel: [11887.373112] mmcblk0: p1
and the card is mounted at "/media/Memory Card", when removing the SD card:
Feb 19 20:32:27 turk kernel: [11896.592155] tifm0 : demand removing card from socket 0:1
Feb 19 20:32:27 turk kernel: [11896.592226] mmc1: card 0001 removed
and it is unmounted.

When I insert an xD card /var/log/messages says only this:
Feb 19 20:33:06 turk kernel: [11936.192105] tifm_core: SmartMedia/xD card detected in socket 0:0
but the card is not mounted, removing the xD card:
Feb 19 20:33:11 turk kernel: [11941.005370] tifm0 : demand removing card from socket 0:0

There appear to be quite a few duplicates of this bug with the same and other hardware, I'm new to launchpad and fairly new to ubuntu so I'm not sure how to go about marking these duplicates or judging which are considered duplicates, so it's difficult to tell how many people this affects at the moment. I'd be happy to assist if anyone can point me in the right direction.