VirtualBox

Ticket #7078 (new defect)

Opened 4 years ago

Last modified 4 years ago

VBox does not list USB device name

Reported by: luizluca Owned by:
Priority: major Component: USB
Version: VirtualBox 3.2.6 Keywords:
Cc: Guest type: other
Host type: other

Description

Hello,

My mouse product name is not shown in vbox gui and neither in cmdline. This is all vbox know about it:

# VBoxManage -nologo list usbhost (...) UUID: e75a5f58-7baf-44b3-9382-1804a81b6e19 VendorId: 0x1241 (1241) ProductId: 0x1122 (1122) Revision: 1.0 (0100) Address: sysfs:/sys/devices/pci0000:00/0000:00:1d.0/usb6/6-1//device:/dev/bus/usb/006/005 Current State: Busy (..)

I think that this is related to some non usual symbol in its name. It has slash and plus:

# lsusb -v -d 1241:1122

Bus 006 Device 005: ID 1241:1122 Belkin Typhoon Stream Optical Mouse USB+PS/2 Device Descriptor:

bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1241 Belkin idProduct 0x1122 Typhoon Stream Optical Mouse USB+PS/2 bcdDevice 1.00 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1

Change History

comment:1 Changed 4 years ago by michael

I suspect that the problem is that the device doesn't provide a textual description of what it is. If I do a search in the sources of usbutils, where lsusb is located (Ubuntu 10.04 system), I get:

~/external/usbutils-0.86$ grep Typhoon\ Stream -rI .
./usb.ids:	1122  Typhoon Stream Optical Mouse USB+PS/2

You will note that that exact text is in the output, so I presume lsusb matches the numerical ID of the device against the text in its database.

You can do

$ cat <sysfs path>/product

where <sysfs path> is the path in the output of VBoxManage list usbhost, to see for sure what text the device itself provides.

comment:2 Changed 4 years ago by luizluca

You're right. The description is based on product/vendorid. There is no manufacturer or product file in sysfs for this specific device (while all others have). So, it doesn't seem to be Vbox problem.

In this case, absence of device info, VBox could help identifying the device by filling the description with something more useful than "Unknown". Maybe just the device class (if there is one) or even it could use text from usb.ids based on productid and vendorid, just like lsusb.

Maybe this bug report can become an improvement suggestion?

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use