[Bug 17393] New: USB 2.0 VT6212 PCI Card and CPCR-402 Card Reader not working

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Sun Oct 9 16:37:59 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=17393
Ubuntu | linux

           Summary: USB 2.0 VT6212 PCI Card and CPCR-402 Card Reader not
                    working
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: linux
        AssignedTo: ben.collins at ubuntu.com
        ReportedBy: mayo at clara.co.uk
         QAContact: kernel-bugs at lists.ubuntu.com


Using Breezy (linux-image-k7  2.6.12.16), tried (and failed) to upgrade an Asus
A7V266-E motherboard to USB2 to read xD cards by adding a
USB 2.0 PCI card based on VT6212:
(SD-U2VIA6212-4I 
http://www.area-powers.jp/product/pci/usb2.0/u26212-4i.html)

0000:00:0d.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) (prog-if 20
[EHCI])
        Subsystem: VIA Technologies, Inc. USB 2.0
        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: 32, Cache Line Size: 0x10 (64 bytes)
        Interrupt: pin C routed to IRQ 12
        Region 0: Memory at ed800000 (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-

and a External TUL CPCR-402 card reader
(http://www.tul.com.tw/global/productlistCP.aspx?folderid=3&cat1=41&cat2=117&cat3=287)

dmesg from start up with card reader plugged in to USB2:

[4294682.375000] ehci_hcd 0000:00:0d.2: VIA Technologies, Inc. USB 2.0
[4294682.377000] ehci_hcd 0000:00:0d.2: new USB bus registered, assigned bus
number 6
[4294682.377000] ehci_hcd 0000:00:0d.2: irq 12, io mem 0xed800000
[4294682.377000] ehci_hcd 0000:00:0d.2: USB 2.0 initialized, EHCI 1.00, driver
10 Dec 2004
[4294682.379000] hub 6-0:1.0: USB hub found
[4294682.379000] hub 6-0:1.0: 4 ports detected
[4294682.379000] usb 1-1: can't set config #1, error -84

[4294683.780000] usb 6-1: new high speed USB device using ehci_hcd and address 2

[4294694.630000] Initializing USB Mass Storage driver...
[4294694.631000] scsi1 : SCSI emulation for USB Mass Storage devices
[4294694.631000] usb-storage: device found at 2
[4294694.631000] usb-storage: waiting for device to settle before scanning
[4294694.631000] usbcore: registered new driver usb-storage
[4294694.631000] USB Mass Storage support registered.

[4294699.632000]   Vendor: ICSI      Model: IC1210        CF  Rev: 1.6B
[4294699.632000]   Type:   Direct-Access                      ANSI SCSI revision: 00
[4294699.670000]   Vendor: ICSI      Model: IC1210        MS  Rev: 1.6B
[4294699.670000]   Type:   Direct-Access                      ANSI SCSI revision: 00
[4294699.673000]   Vendor: ICSI      Model: IC1210    MMC/SD  Rev: 1.6B
[4294699.673000]   Type:   Direct-Access                      ANSI SCSI revision: 00
[4294699.676000]   Vendor: ICSI      Model: IC1210        SM  Rev: 1.6B
[4294699.676000]   Type:   Direct-Access                      ANSI SCSI revision: 00
[4294699.679000] usb-storage: device scan complete

[4294731.811000] ehci_hcd 0000:00:0d.2: fatal error
[4294731.812000] ehci_hcd 0000:00:0d.2: HC died; cleaning up
[4294731.812000] usb 6-1: USB disconnect, address 2
[4294732.141000] usb 1-1: new full speed USB device using uhci_hcd and address 4
[4294732.221000] uhci_hcd 0000:00:0d.0: host system error, PCI problems?
[4294732.221000] uhci_hcd 0000:00:0d.0: host controller halted, very bad!


Plug the card reader into a motherboard USB 1 port and it works fine.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the kernel-bugs mailing list