The sd-card reader ist still broken in feisty (Thinkpad Z61m).
--- /var/log/messages
Apr 21 16:18:41 homer kernel: [ 321.332000] tifm_7xx1: sd card detected in
socket 1
Apr 21 16:18:42 homer kernel: [ 321.664000] mmcblk0: mmc1:3975 SD02G 2011136KiB
Apr 21 16:18:42 homer kernel: [ 321.664000] mmcblk0: p1
Apr 21 16:21:53 homer kernel: [ 513.012000] end_request: I/O error, dev
mmcblk0, sector 4022208
Apr 21 16:21:53 homer kernel: [ 513.012000] printk: 1341 messages suppressed.
Apr 21 16:21:53 homer kernel: [ 513.012000] end_request: I/O error, dev
mmcblk0, sector 4022208
Apr 21 16:21:53 homer kernel: [ 513.012000] end_request: I/O error, dev
mmcblk0, sector 4022256
Apr 21 16:21:53 homer kernel: [ 513.012000] end_request: I/O error, dev
mmcblk0, sector 4022256
Apr 21 16:21:53 homer kernel: [ 513.012000] end_request: I/O error, dev
mmcblk0, sector 0
Apr 21 16:21:53 homer last message repeated 2 times
Apr 21 16:21:53 homer kernel: [ 513.016000] end_request: I/O error, dev
mmcblk0, sector 0
Apr 21 16:21:53 homer last message repeated 25 times
...
... hundreds of messages
---
---- lspci -vvv|less -p " Standard Compliant SD Host Controller"
15:00.3 Generic system peripheral [0805]: Texas Instruments PCIxx12 SDA
Standard Compliant SD Host Controller (prog-if 01)
Subsystem: Lenovo Unknown device 207d
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (1750ns min, 1000ns max)
Interrupt: pin A routed to IRQ 16
Region 0: Memory at e4302800 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Before upgrading to feisty it worked if i loaded the following modules manually
----
modprobe tifm_7xx1 sdhci tifm_sd mmc_core tifm_core tifm_sd sdhci
----
--
tifm: Texas Instruments Card reader not working
https://bugs.launchpad.net/bugs/53923
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
