Built-in card reader not working with tifm driver on LG W1 series laptop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Undecided
|
Rouben |
Bug Description
This bug is being filed on behalf of sasha2002, in response to our efforts to resolve his issue documented in Ubuntu question #12554 (not bug, question at this URL: https:/
The exact model of the laptop in question is described here: http://
Symptoms:
Ubuntu loads up, a properly formatted (confirmed from Windows) SD card is inserted into the proper slot on the embedded card reader. The card is never detected/mounted and the following messages appear in dmesg (my annotations appear prepended with *** below):
*** Card inserted
[ 1393.511938] tifm_core: MMC/SD card detected in socket 0:1
[ 1394.624236] tifm0 : demand removing card from socket 0:1
*** Card removed and reinserted
[ 1394.959710] tifm_core: MMC/SD card detected in socket 0:1
[ 1395.013702] mmcblk0: mmc1:0001 AF HMP 250880KiB
[ 1395.013782] mmcblk0: p1
[ 1711.514000] tifm0 : demand removing card from socket 0:1
*** Card removed
Also according to the reporter, no extra device files appear in /dev. From various forum posts, the tifm driver is supposed to create device files like /dev/mmcblk0p1 and that was not observed in this case. I am not sure if the creation of such device files is necessary in this case, since we never got this to work in the first place.
Expected behaviour:
Card is inserted, detected, automatically mounted under /media and made available through the Ubuntu GNOME desktop GUI as an icon on the desktop.
The following files will be added to this bug report once I receive it from sasha2002, as per https:/
uname -a > uname-a.log
cat /proc/version_
dmesg > dmesg.log
sudo lspci -vvnn > lspci-vvnn.log
Changed in linux-source-2.6.22: | |
assignee: | nobody → rouben |
This is a kernel issue, therefore I am adding the package association linux-source- 2.6.22.
The following information is pending, as such I am marking this bug "incomplete" until I receive this information from the bug reporter as per https:/ /wiki.ubuntu. com/KernelTeamB ugPolicies
uname -a > uname-a.log signature > version.log
cat /proc/version_
dmesg > dmesg.log
sudo lspci -vvnn > lspci-vvnn.log