unknown HID "Adomax" found in sys-usb while all USB-ports empty

[edal...@riseup.net]

Hi,

On a machine with sys-usb configured and mouse/keyboard connected
through "old" PS2-connections, I've noticed this when running lsusb -v

Michal Lee has pointed this out earlier
(https://groups.google.com/d/msg/qubes-users/EANuL9rj_6w/-tjgYcThBAAJ),
but I still lack an explanation of what is going on here.


Best regards
Ed Alvarez



[code]

[someuser@sys-usb]$ sudo lsusb -v

(...)

Bus 005 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0627 Adomax Technology Co., Ltd
idProduct 0x0001
bcdDevice 0.00
iManufacturer 1 QEMU
iProduct 3 QEMU USB Tablet
iSerial 5 42
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 7 HID Tablet
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 0.01
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 74
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)

(...)

[/code]

[Ivan Mitev]

On 05/22/2018 05:42 PM, edal...@riseup.net wrote:
> Hi,
>
> On a machine with sys-usb configured and mouse/keyboard connected
> through "old" PS2-connections, I've noticed this when running lsusb -v
>
> Michal Lee has pointed this out earlier
> (https://groups.google.com/d/msg/qubes-users/EANuL9rj_6w/-tjgYcThBAAJ),
> but I still lack an explanation of what is going on here.

The adomax device is a virtual qemu "tablet" used to provide absolute
mouse coordinates. In other words it helps with mouse pointer
synchronization between the host and vms.

You may have noticed that the device is picked up by sys-usb's
input-proxy sender as a HID device, which is why you may get a popup
dialog (if qubes.InputKeyboard policy is set to 'ask') - even if you
don't have a usb keyboard.

[Ivan Mitev]

> You may have noticed that the device is picked up by sys-usb's
> input-proxy sender as a HID device, which is why you may get a popup
> dialog (if qubes.InputKeyboard policy is set to 'ask') - even if you
> don't have a usb keyboard.

sorry - scrap that bit, it's not true.

(I thought the qemu tablet was actually the reason I had a recurring usb
keyboard popup dialog [1] but the device is properly blacklisted in
sys-usb).

[1] https://github.com/QubesOS/qubes-issues/issues/3604