Opened 6 years ago
Last modified 6 years ago
#18652 new defect
Reiner SCT CyberJack USB no longer works (reset full speed usb device ...)
| Reported by: | Jörg Skottke | Owned by: | |
|---|---|---|---|
| Component: | USB | Version: | VirtualBox 6.0.8 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Linux |
Description
Since Virtualbox 6.0.6 it appears that the Reiner SCT CyberJack Standard Chipcard reader (USB) can no longer be used from within a Windows VM.
Card reader is detected ok by Linux [ 611.544511] usb 1-7: new full-speed USB device number 5 using xhci_hcd [ 611.879182] usb 1-7: New USB device found, idVendor=0c4b, idProduct=0500, bcdDevice= 0.01 [ 611.879185] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 611.879187] usb 1-7: Product: cyberJack RFID standard [ 611.879188] usb 1-7: Manufacturer: REINER SCT [ 611.879189] usb 1-7: SerialNumber: 5287xxxxxx
After launching a Windows 10 VM (USB device connected automatically to VM) countless messages of type [ 612.661394] usb 1-7: reset full-speed USB device number 5 using xhci_hcd
and the CyberJack driver within the VM cannot access the chipcard reader.
*Additional info* Symptom: The reader does not seem to accept the card if plugged in
Attachments (1)
Change History (6)
by , 6 years ago
comment:1 by , 6 years ago
Take a look at #18593. It may talk about printers, but the latest Testbuilds might help you too with the USB issues. Give it a shot...
comment:2 by , 6 years ago
I have implemented a workaround in the meantime and am cowardly refusing to mess with my system at the time being - especially if i'm the only one with this specific problem. I am going to check with the next release provided by the update channel for my distro.
comment:3 by , 6 years ago
00:00:00.567120 VirtualBox VM 6.0.8_Debian r130347 linux.amd64 (May 15 2019 08:18:23) release log
Ah, so it looks that you're using the Debian fork version of VirtualBox after all...
You can either ask in their forums/channels for help, or completely remove/uninstall/delete/purge their version and install the official version from the Linux_Downloads section of VirtualBox.
comment:4 by , 6 years ago
Hi Socratis,
you convinced me to give it a shot and the vanilla VBox version 6.0.9 r130868 works as expected. So the issue is gone and resolved from my point of view.
Thank you for your assistance and best regards Skotti
VBox Logfile for the affected VM