Opened 12 years ago
Closed 8 years ago
#10486 closed defect (obsolete)
CCID USB card reader within an XP guest fails to start
| Reported by: | Rafael | Owned by: | |
|---|---|---|---|
| Component: | USB | Version: | VirtualBox 4.1.12 |
| Keywords: | usb card reader | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description
I have a USB card reader as specified on the picture and it doesn't work on Windows XP as guest. I'm running Ubuntu 11.04 as host.
When I plug in into my Win XP guest, it fails to start the device.
Some comments:
1) I'm already member of the vboxusers and plugdev groups;
2) My WinXP is totally updated with Service Pack 3 and some hotfixes are already installed (particulary this one KB968730, as recommended from the manufacturer's website);
3) The device drivers on WinXP are installed and updated;
4) I've created a USB filter for the device and indeed it doesn't work either;
There are some pictures attached that show the problem. It fails with an error code 10 saying that the device driver cannot start.
Attachments (4)
Change History (10)
by , 12 years ago
| Attachment: | error-1.jpeg added |
|---|
by , 12 years ago
| Attachment: | error-2.jpeg added |
|---|
by , 12 years ago
| Attachment: | error-3.jpeg added |
|---|
by , 12 years ago
| Attachment: | ccid_usb_smart_reader.jpg added |
|---|
comment:1 by , 12 years ago
Could you please attach the log to the defect? Is pcscd running on your host? note, it automatically grab all readers attached to host.
follow-up: 3 comment:2 by , 12 years ago
Yes, pcscd is running on my Ubuntu host. Here is the output of pcsc_scan:
PC/SC device scanner
V 1.4.17 (c) 2001-2009, Ludovic Rousseau <ludovic.rousseau@free.fr>
Compiled with PC/SC lite version: 1.5.5
Scanning present readers...
0: ACS ACR 38U-CCID 00 00
Tue May 1 15:57:45 2012
Reader 0: ACS ACR 38U-CCID 00 00
Card state: Card inserted,
ATR: 3B FD 18 00 FF 80 B1 FE 45 1F 07 80 73 00 21 13 57 4A 54 48 61 31 4A 00 52
ATR: 3B FD 18 00 FF 80 B1 FE 45 1F 07 80 73 00 21 13 57 4A 54 48 61 31 4A 00 52
+ TS = 3B --> Direct Convention
+ T0 = FD, Y(1): 1111, K: 13 (historical bytes)
TA(1) = 18 --> Fi=372, Di=12, 31 cycles/ETU
129032 bits/s at 4 MHz, fMax for Fi = 5 MHz => 161290 bits/s
TB(1) = 00 --> VPP is not electrically connected
TC(1) = FF --> Extra guard time: 255 (special value)
TD(1) = 80 --> Y(i+1) = 1000, Protocol T = 0
-----
TD(2) = B1 --> Y(i+1) = 1011, Protocol T = 1
-----
TA(3) = FE --> IFSC: 254
TB(3) = 45 --> Block Waiting Integer: 4 - Character Waiting Integer: 5
TD(3) = 1F --> Y(i+1) = 0001, Protocol T = 15 - Global interface bytes following
-----
TA(4) = 07 --> Clock stop: not supported - Class accepted by the card: (3G) A 5V B 3V C 1.8V
+ Historical bytes: 80 73 00 21 13 57 4A 54 48 61 31 4A 00
Category indicator byte: 80 (compact TLV data object)
Tag: 7, len: 3 (card capabilities)
Selection methods: 00
Data coding byte: 21
- Behaviour of write functions: proprietary
- Value 'FF' for the first byte of BER-TLV tag fields: invalid
- Data unit in quartets: 2
Command chaining, length fields and logical channels: 13
- Logical channel number assignment: by the card
- Maximum number of logical channels: 4
Tag: 5, len: 7 (card issuer's data)
Card issuer data: 4A 54 48 61 31 4A 00
+ TCK = 52 (correct checksum)
Possibly identified card (using /usr/share/pcsc/smartcard_list.txt):
3B FD 18 00 FF 80 B1 FE 45 1F 07 80 73 00 21 13 57 4A 54 48 61 31 4A 00 52
e-CPF issued by AASP (Lawyers Association of São Paulo, Brazil)
I've searched for Win logs at Event Viewer > System and Application logs and nothing is logged when I attach the device. I thought it was because the .NET runtime framework was not installed on the guest but after installing it the problem still remains.
comment:3 by , 12 years ago
so please stop pcscd
# sudo service pcscd stop
and retry to grab card reader with your VM.
comment:4 by , 12 years ago
I've already stopped pcscd with your command and nothing happened, the problem still continues with the same cause (error code 10: the device driver cannot start). Last Friday I've tested it on Windows XP not virtualized and it worked perfectly. Have you checked the screenshots I added on the defect?
comment:5 by , 11 years ago
I solved a similar issue just by disabling ehci support to guest machine.
comment:6 by , 8 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.


The USB reader device