** Description changed: Updated June 27th for Gutsy. - Please let me know direct if anything is wrong or misleading. Duncan + Updated January 3rd for Gutsy - 2.6.22-14-generic - Here is a run through of the status on my machine, an HP dv8000 series - laptop (dv8220ea) running Ubuntu 7.04 (Feisty Fawn) with kernel - 2.6.20-14-generic. My laptop testing page is at: - https://wiki.ubuntu.com/LaptopTestingTeam/HP_Pavilion_DV8220EA and my - (totally useless) Ubuntu Hardware Database entry is at: - http://hwdb.ubuntu.com/?xml=d7aa35a00d28d36a608b2d09bc3b27e3 + Please let me know direct if anything is wrong or confusing. Duncan + = Ubuntu 7.04 specific = + Here is a run through of the status on my machine, an HP dv8000 series laptop (dv8220ea) running Ubuntu 7.04 (Feisty Fawn) with kernel 2.6.20-14-generic. My laptop testing page is at: https://wiki.ubuntu.com/LaptopTestingTeam/HP_Pavilion_DV8220EA and my (totally useless) Ubuntu Hardware Database entry is at: http://hwdb.ubuntu.com/?xml=d7aa35a00d28d36a608b2d09bc3b27e3 + + Feisty: /var/log/messages I can see some kind of circular issue happening. I've attached an excerpt of the file which fills 1962 lines in 47/100ths of a second (20:31:59 - 20:32:06). For example the first section touched is 1000384, and it gets touched 9 times in that short time. The log starts out looking promising but then just repeats a series of the I/O errors: + Apr 13 20:31:59 ubuntu kernel: [ 3544.084000] tifm_7xx1: sd card detected in socket 1 + Apr 13 20:31:59 ubuntu kernel: [ 3544.480000] mmcblk0: mmc1:470a SD512 500224KiB + Apr 13 20:31:59 ubuntu kernel: [ 3544.480000] mmcblk0: p1 + Apr 13 20:32:00 ubuntu kernel: [ 3545.540000] end_request: I/O error, dev mmcblk0, sector 1000384 + Apr 13 20:32:00 ubuntu kernel: [ 3545.540000] printk: 317 messages suppressed. + Apr 13 20:32:00 ubuntu kernel: [ 3545.540000] end_request: I/O error, dev mmcblk0, sector 1000384 + etc... see attached file 'messages.txt' + + Running '$ mount' while the card is in shows no sign of the the card + being seen. + + Force starting the tifm_7xx1, tifm_core and tifm_sd modules makes no + difference to the output of /var/log/messages. + + = Ubuntu 7.10, updated Jan 2008 = I went to the Debian GNU/Linux device driver check page at http://kmuto.jp/debian/hcl/ which uses the PCI map of Debian kernel 2.6.18-4-686 (2.6.18.dfsg.1-9). Unlike when I first made this report, my hardware seems to be recognized. The relevant hardware is: PCI ID Working? Vendor Device - 104c8039 Yes Texas Instruments PCIxx12 Cardbus Controller yenta_socket + 104c8039 Yes Texas Instruments PCIxx12 Cardbus Controller yenta_socket [add: v2.6.23] 104c803a - Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller - 104c803b - Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) - 104c803c - Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller + 104c803b [add: Yes] Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) [add: tifm_7xx1 v2.6.23] + 104c803c - Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller + [add entry: + 80861092 Yes Intel Corporation PRO/1000 PT Server Adapter e100 v2.6.23 ] - (updated for Gutsy) So my card should be recognised. Sure enough in 'System > Preferences > Device Manager' I have an entry as follows: + So my card should be recognised. Sure enough in 'System > Preferences > Hardware Information' I have an entry as follows: - 82801 Mobile PCI Bridge - - PCIxx12 Cardbus Controller - - PCIxx12 OHCI Compliant IEEE 1394 Host Controller - (This line missing in Gutsy - - - Unknown (0x633f02)) - - 5-in-1 Multimedia Card Reader (SD/MMC/MS/ PRO/xD) - - PCIxx12 SDA Standard Compliant SD Host Controller - - - MMC/SD Host Adapter - - - PRO/100 VE Network Connection - - - - Networking Interface - (The IEEE 1394 port/system works perfectly) + If anyone wants info from the device manager just let me know. It's a + bit tedious to copy over from the Device Manager - (updated for Gutsy) Some details of 5-in-1 Multimedia Card Reader (SD/MMC/MS/ PRO/xD) are: - info.linux.driver string tifm_7xx1 - info.parent string /org/freedesktop/Hal/devices/pci_8086_2448 - info.udi string /org/freedesktop/Hal/devices/pci_104c_803b - info.sysfs_path string /sys/devices/pci0000:00/0000:00:1e.0/0000:08:06.2 - info.sysfs_path_device string /sys/devices/pci0000:00/0000:00:1e.0/0000:08:06.2 - pci.linux.sysfs_path string /sys/devices/pci0000:00/0000:00:1e.0/0000:08:06.2 - pci.product_id int 32827 (0x803b) - ( This entry missing in Gutsy: pci.subsys_product string Unknown (0x30a5) ) - pci.subsys_product_id int 12453 (0x30a5) - - Some details of PCIxx12 SDA Standard Compliant SD Host Controller are: - info.linux.driver string sdhci - info.parent string /org/freedesktop/Hal/devices/pci_8086_2448 - info.udi string /org/freedesktop/Hal/devices/pci_104c_803c - linux.sysfs_path string /sys/devices/pci0000:00/0000:00:1e.0/0000:08:06.3 - linux.sysfs_path_device string /sys/devices/pci0000:00/0000:00:1e.0/0000:08:06.3 - - ... if anyone wants more of those let me know. It's a bit tedious to - copy over from the Device Manager - - (updated for Gutsy) [EMAIL PROTECTED]:~$ lspci -n + (updated Jan 2008 for Gutsy) [EMAIL PROTECTED]:~$ lspci -n 00:00.0 0600: 8086:27a0 (rev 03) 00:01.0 0604: 8086:27a1 (rev 03) 00:1b.0 0403: 8086:27d8 (rev 01) 00:1c.0 0604: 8086:27d0 (rev 01) 00:1c.1 0604: 8086:27d2 (rev 01) 00:1c.2 0604: 8086:27d4 (rev 01) 00:1d.0 0c03: 8086:27c8 (rev 01) 00:1d.1 0c03: 8086:27c9 (rev 01) 00:1d.2 0c03: 8086:27ca (rev 01) 00:1d.3 0c03: 8086:27cb (rev 01) 00:1d.7 0c03: 8086:27cc (rev 01) 00:1e.0 0604: 8086:2448 (rev e1) 00:1f.0 0601: 8086:27b9 (rev 01) 00:1f.2 0101: 8086:27c4 (rev 01) 00:1f.3 0c05: 8086:27da (rev 01) 01:00.0 0300: 10de:01d8 (rev a1) 06:00.0 0280: 8086:4222 (rev 02) 08:06.0 0607: 104c:8039 08:06.1 0c00: 104c:803a 08:06.2 0180: 104c:803b 08:06.3 0805: 104c:803c 08:08.0 0200: 8086:1092 (rev 01) - Feisty: /var/log/messages I can see some kind of circular issue happening. I've attached an excerpt of the file which fills 1962 lines in 47/100ths of a second (20:31:59 - 20:32:06). For example the first section touched is 1000384, and it gets touched 9 times in that short time. The log starts out looking promising but then just repeats a series of the I/O errors: - Apr 13 20:31:59 ubuntu kernel: [ 3544.084000] tifm_7xx1: sd card detected in socket 1 - Apr 13 20:31:59 ubuntu kernel: [ 3544.480000] mmcblk0: mmc1:470a SD512 500224KiB - Apr 13 20:31:59 ubuntu kernel: [ 3544.480000] mmcblk0: p1 - Apr 13 20:32:00 ubuntu kernel: [ 3545.540000] end_request: I/O error, dev mmcblk0, sector 1000384 - Apr 13 20:32:00 ubuntu kernel: [ 3545.540000] printk: 317 messages suppressed. - Apr 13 20:32:00 ubuntu kernel: [ 3545.540000] end_request: I/O error, dev mmcblk0, sector 1000384 - etc... see attached file 'messages.txt' + /var/log/messages I get the changes listed below if I insert an SD card, browse the files, unmount, and remove the card. + Jan 3 15:26:37 ubuntu kernel: [11848.820000] tifm_core: SmartMedia/xD card detected in socket 0:0 + Jan 3 15:26:37 ubuntu kernel: [11849.140000] tifm0 : demand removing card from socket 0:0 + Jan 3 15:26:37 ubuntu kernel: [11849.296000] tifm_core: MMC/SD card detected in socket 0:1 + Jan 3 15:26:37 ubuntu kernel: [11849.716000] mmcblk0: mmc1:470a SD512 500224KiB + Jan 3 15:26:37 ubuntu kernel: [11849.716000] mmcblk0: p1 + Jan 3 15:27:06 ubuntu kernel: [11878.116000] tifm0 : demand removing card from socket 0:1 - Gutsy: /var/log/messages I get the changes listed below if I insert an SD card, browse the files, unmount, and remove the card. - Jun 27 19:58:31 ubuntu kernel: [ 3487.556000] tifm_core: SmartMedia/xD card detected in socket 0:0 - Jun 27 19:58:31 ubuntu kernel: [ 3487.580000] tifm0 : demand removing card from socket 0:0 - Jun 27 19:58:31 ubuntu kernel: [ 3487.792000] tifm_core: MMC/SD card detected in socket 0:1 - Jun 27 19:58:32 ubuntu kernel: [ 3488.468000] mmcblk0: mmc1:470a SD512 500224KiB - Jun 27 19:58:32 ubuntu kernel: [ 3488.468000] mmcblk0: p1 - Jun 27 19:59:00 ubuntu kernel: [ 3516.456000] tifm0 : demand removing card from socket 0:1 + running '$ mount' while the card is in produces: + June '07: + /dev/mmcblk0p1 on /media/disk type vfat (rw,nosuid,nodev,shortname=mixed,uid=1000,utf8,umask=077) + Jan '08: + /dev/mmcblk0p1 on /media/disk type vfat (ro,nosuid,nodev,shortname=mixed,uid=1000,utf8,umask=077,usefree) - Feisty: running '$ mount' while the card is in shows no sign of the the - card being seen. - - Gutsy: running '$ mount' while the card is in produces: - /dev/mmcblk0p1 on /media/disk type vfat (rw,nosuid,nodev,shortname=mixed,uid=1000,utf8,umask=077) - - Feisty: Force starting the tifm_7xx1, tifm_core and tifm_sd modules - makes no difference to the output of /var/log/messages. - - Tarek Loubani on 2007-01-12 mentions adding the modules to /etc/default - /acpi-support but after the udev bug being fixed I haven't done that - - please correct me if I'm wrong. - + = Some comments = + Tarek Loubani on 2007-01-12 mentions adding the modules to /etc/default/acpi-support but after the udev bug being fixed I haven't done that - please correct me if I'm wrong. Scott James Remnant said on 2007-03-30: udev problems fixed William Hood said on 2007-04-01: affects Averatec 2370 Laptop Mendez said on 2007-04-01: affects: HP NX9420 laptop robrichard said on 2007-04-06: affects: HP Compaq nw8240 laptop Ramesh Thiruchelvam said on 2007-04-07: Compaq NX 6120 Note Book Th3n3k said on 2007-04-11:: affects: HP pavilion ZT3115E
-- tifm: Texas Instruments Card reader not reading SD cards 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
