[Wylug-discuss] Help USB devices under Virtualbox
Dave Fisher
wylug-discuss at davefisher.co.uk
Fri Dec 4 20:05:54 UTC 2009
Hi,
Apologies if people think this should go to wylug-help, but I've seen
so little traffic on that list over the last year that I've got the
impression that it is somewhat derelict.
I've recently broken a long-standing gadget abstinence vow and bought
myself a Tacx Bushido VR Cycle Trainer.
Obviously, the software is Windows-only, but people have reported it
working under VirtualBox.
The software installs fine, and the USB dongle which provides wireless
connection to the trainer hardware is correctly identified by name,
but 'greyed out' as 'unavailable'. I've never had any problem with
getting XP to use basic USB devices under VirtualBox, e.g. mass
storage, cameras, serial.
I suspect that the problem is trivial for someone who knows the
secrets of Linux USB, but I don't. My suspicion is that there is
either a problem in the way that Linux handles the dongle (e.g. the
driver), or in the way that it passes the details on to VirtualBox ...
although, given how little I understand of USB, it could just as well
be a problem with VirtualBox or the Windows XP guest.
The, admittedly shaky, grounds for my suspicion are the based on the
way Linux seems to be using uhci, while the VirtualBox settings make a
point of enabling ehci ... I realise this may be a complete red
herring, but I've got to start somewhere ;-)
I'd appreciate any suggestions on the above and the following output
from dmesg and udevadm info.
Any advice on how to get useful diagnostics out of VirtualBox or XP
might be very helpful.
Thanks,
Dave
=====
dmesg
=====
[ 1183.161264] usb 6-1: new full speed USB device using uhci_hcd and address 6
[ 1183.334850] usb 6-1: configuration #1 chosen from 1 choice
[ 1183.340794] cp210x 6-1:1.0: cp210x converter detected
[ 1183.460013] usb 6-1: reset full speed USB device using uhci_hcd and address 6
[ 1183.618833] usb 6-1: cp210x converter now attached to ttyUSB0
====================================
udevadm info --attribute-walk --name /dev/ttyUSB0
====================================
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device
'/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0/ttyUSB0/tty/ttyUSB0':
KERNEL=="ttyUSB0"
SUBSYSTEM=="tty"
DRIVER==""
looking at parent device
'/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0/ttyUSB0':
KERNELS=="ttyUSB0"
SUBSYSTEMS=="usb-serial"
DRIVERS=="cp210x"
ATTRS{port_number}=="0"
looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0':
KERNELS=="6-1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="cp210x"
ATTRS{bInterfaceNumber}=="00"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bNumEndpoints}=="02"
ATTRS{bInterfaceClass}=="ff"
ATTRS{bInterfaceSubClass}=="00"
ATTRS{bInterfaceProtocol}=="00"
ATTRS{modalias}=="usb:v0FCFp1004d0300dc00dsc00dp00icFFisc00ip00"
ATTRS{supports_autosuspend}=="0"
ATTRS{interface}=="Dynastream ANT2USB"
looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb6/6-1':
KERNELS=="6-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bMaxPower}=="100mA"
ATTRS{urbnum}=="17"
ATTRS{idVendor}=="0fcf"
ATTRS{idProduct}=="1004"
ATTRS{bcdDevice}=="0300"
ATTRS{bDeviceClass}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="12"
ATTRS{busnum}=="6"
ATTRS{devnum}=="6"
ATTRS{version}==" 1.10"
ATTRS{maxchild}=="0"
ATTRS{quirks}=="0x0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="Silicon Labs"
ATTRS{product}=="Dynastream ANT2USB"
ATTRS{serial}=="10143"
looking at parent device '/devices/pci0000:00/0000:00:1d.0/usb6':
KERNELS=="usb6"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bMaxPower}==" 0mA"
ATTRS{urbnum}=="149"
ATTRS{idVendor}=="1d6b"
ATTRS{idProduct}=="0001"
ATTRS{bcdDevice}=="0206"
ATTRS{bDeviceClass}=="09"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="12"
ATTRS{busnum}=="6"
ATTRS{devnum}=="1"
ATTRS{version}==" 1.10"
ATTRS{maxchild}=="2"
ATTRS{quirks}=="0x0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="Linux 2.6.31-14-generic uhci_hcd"
ATTRS{product}=="UHCI Host Controller"
ATTRS{serial}=="0000:00:1d.0"
ATTRS{authorized_default}=="1"
looking at parent device '/devices/pci0000:00/0000:00:1d.0':
KERNELS=="0000:00:1d.0"
SUBSYSTEMS=="pci"
DRIVERS=="uhci_hcd"
ATTRS{vendor}=="0x8086"
ATTRS{device}=="0x2934"
ATTRS{subsystem_vendor}=="0x1458"
ATTRS{subsystem_device}=="0x5004"
ATTRS{class}=="0x0c0300"
ATTRS{irq}=="23"
ATTRS{local_cpus}=="00000000,00000003"
ATTRS{local_cpulist}=="0-1"
ATTRS{modalias}=="pci:v00008086d00002934sv00001458sd00005004bc0Csc03i00"
ATTRS{numa_node}=="0"
ATTRS{broken_parity_status}=="0"
ATTRS{msi_bus}==""
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
More information about the Wylug-discuss
mailing list