9 Dec
2017
9 Dec
'17
9:37 p.m.
David Kastrup wrote:
Clemens Ladisch writes:
The host hardware is not capable of causing the "disconnect" message.
David Kastrup wrote:
You sure that it's the Bamster taking the initiative here? I just got some older Bamster soundbar model
(probably not a keeper)
that takes USB either for power (in which case it uses AUX in analog) or
also as USB soundcard. In the latter case, however, it just switches
itself off after a few seconds.
[ 1201.960192] usb 5-2: new full-speed USB device number 5 using uhci_hcd
[ 1203.344305] usbhid 5-2:1.3: can't add hid device: -71
[ 1203.456336] usb 5-2: USB disconnect, device number 5
I'd guess that the firmware tries to detect if it is connect to an actaual
PC (as opposed to some charger), and that Linux doesn't look right. it sounds more like Linux does something bad here.
Should it respond
differently to any request?
I guess the Bamster expects it to behave identical with the Windows driver.
Regards,
Clemens