9 Dec
2017
9 Dec
'17
3:27 p.m.
Hi,
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.
dmesg is
[ 1201.960192] usb 5-2: new full-speed USB device number 5 using uhci_hcd
[ 1202.098273] usb 5-2: config 1 has an invalid interface number: 3 but max is 2
[ 1202.098278] usb 5-2: config 1 has no interface number 2
[ 1202.107265] usb 5-2: New USB device found, idVendor=10d6, idProduct=1100
[ 1202.107271] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1202.107276] usb 5-2: Product: USB Audio
[ 1202.107280] usb 5-2: Manufacturer: ACTIONS
[ 1203.326284] usb 5-2: 1:1: cannot get freq at ep 0x2
[ 1203.338528] usb 5-2: 3:0: cannot get min/max values for control 2 (id 3)
[ 1203.344305] usbhid 5-2:1.3: can't add hid device: -71
[ 1203.344328] usbhid: probe of 5-2:1.3 failed with error -71
[ 1203.456336] usb 5-2: USB disconnect, device number 5
and if I am fast enough (before it switches itself off again),
lsusb -v
delivers
Bus 005 Device 007: ID 10d6:1100 Actions Semiconductor Co., Ltd MPMan MP-Ki 128 MP3
Player/Recorder
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x10d6 Actions Semiconductor Co., Ltd
idProduct 0x1100 MPMan MP-Ki 128 MP3 Player/Recorder
bcdDevice 1.00
iManufacturer 1 (error)
iProduct 2 (error)
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 135
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1 Audio
bInterfaceSubClass 1 Control Device
bInterfaceProtocol 0
iInterface 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 1 (HEADER)
bcdADC 1.00
wTotalLength 40
bInCollection 1
baInterfaceNr( 0) 1
AudioControl Interface Descriptor:
bLength 12
bDescriptorType 36
bDescriptorSubtype 2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType 0x0101 USB Streaming
bAssocTerminal 0
bNrChannels 2
wChannelConfig 0x0003
Left Front (L)
Right Front (R)
iChannelNames 0
iTerminal 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (OUTPUT_TERMINAL)
bTerminalID 2
wTerminalType 0x0301 Speaker
bAssocTerminal 0
bSourceID 3
iTerminal 0
AudioControl Interface Descriptor:
bLength 10
bDescriptorType 36
bDescriptorSubtype 6 (FEATURE_UNIT)
bUnitID 3
bSourceID 1
bControlSize 1
bmaControls( 0) 0x03
Mute Control
Volume Control
bmaControls( 1) 0x00
bmaControls( 2) 0x00
iFeature 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1 Audio
bInterfaceSubClass 2 Streaming
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 1 Audio
bInterfaceSubClass 2 Streaming
bInterfaceProtocol 0
iInterface 0
AudioStreaming Interface Descriptor:
bLength 7
bDescriptorType 36
bDescriptorSubtype 1 (AS_GENERAL)
bTerminalLink 1
bDelay 0 frames
wFormatTag 1 PCM
AudioStreaming Interface Descriptor:
bLength 11
bDescriptorType 36
bDescriptorSubtype 2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 2
bSubframeSize 2
bBitResolution 16
bSamFreqType 1 Discrete
tSamFreq[ 0] 44100
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 9
Transfer Type Isochronous
Synch Type Adaptive
Usage Type Data
wMaxPacketSize 0x00c0 1x 192 bytes
bInterval 1
bRefresh 0
bSynchAddress 0
AudioControl Endpoint Descriptor:
bLength 7
bDescriptorType 37
bDescriptorSubtype 1 (EP_GENERAL)
bmAttributes 0x01
Sampling Frequency
bLockDelayUnits 2 Decoded PCM samples
wLockDelay 512 Decoded PCM samples
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 2.01
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 33
Warning: incomplete report descriptor
Report Descriptor: (length is 1)
Item(Main ): (null), data=none
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 1
Device Status: 0x78a0
(Bus Powered)
Any idea where I can go from here? It's annoying that it just powers
itself off again, and the sound quality is supposed to be better when
using sound via USB rather than AUX in.
--
David Kastrup
9 Dec
9 Dec
5:12 p.m.
David Kastrup wrote:
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.
Regards,
Clemens
5:27 p.m.
Clemens Ladisch <clemens-P6GI/4k7KOmELgA04lAiVw(a)public.gmane.org>
writes:
David Kastrup wrote:
It doesn't have batteries to charge. If I plug in the AUX cord, I can
switch it on and it stays on (without attempting to announce it on USB).
You sure that it's the Bamster taking the initiative here? If I wait
for just the right moment, I can see in cat /etc/asound/cards
dak@lola:/usr/local/tmp/lilypond$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xfe020000 irq 29
1 [Audio ]: USB-Audio - USB Audio
ACTIONS USB Audio at usb-0000:00:1d.0-2, full speed
immediately before it switches itself off again.
This behavior just does not make sense. I cannot rule out that the
chipset might be used in devices where this would be part of more useful
behavior but with as little clue as I have it sounds more like Linux
does something bad here. Should it respond differently to any request?
--
David Kastrup
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.
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
11:36 p.m.
Clemens Ladisch <clemens-P6GI/4k7KOmELgA04lAiVw(a)public.gmane.org>
writes:
I'll see what it does on some XP computer tomorrow. Can't access it
right now.
I mean, this was a used sale. Can also just be broken. Or it talks
with the host and says "I want 1A of current or 2A" and the host says
"no way". But it's delivered by default with a two-host-plug USB cable
and would not be able to know about the power available from the
power-only plug. And it doesn't complain when running from the analog
input either, so it would be somewhat strange to just shut down when in
USB mode.
Any idea what I could be testing?
--
David Kastrup
David Kastrup wrote:
Well, I'll have to trust you on that. Then perhaps one of the preceding
interactions that appear to have failed don't make the Bamster happy.
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.
10 Dec
10 Dec
8:37 a.m.
David Kastrup wrote:
Or it talks with the host and says "I want 1A of
current or 2A" and the
host says "no way".
Its descriptors claim that it wants 0 mA.
But it's delivered by default with a two-host-plug
USB cable
So it needs more power than a single plug could supply?
and would not be able to know about the power
available from the
power-only plug. And it doesn't complain when running from the analog
input either, so it would be somewhat strange to just shut down when in
USB mode.
After a short time, it just stops reacting to USB requests.
It might be possible that some capacitor does no longer work correctly,
and that its internal voltage drops too far when actually doing things.
This would imply that it doesn't work in Windows either.
Regards,
Clemens
12:49 p.m.
Clemens Ladisch <clemens-P6GI/4k7KOmELgA04lAiVw(a)public.gmane.org>
writes:
Well, the Windows PC disagrees. And the thing obviously has a whole lot
more volume reserves in USB mode: apparently the AUX in levels are badly
matched to typical sources.
I tried disabling autosuspend on USB by blacklisting in /etc/default/tlp
but it doesn't seem to help:
+++ USB
Autosuspend = enabled
Device whitelist = (not configured)
Device blacklist = 04a9:220e 10d6:1100
WWAN blacklist = enabled
Bus 002 Device 030 ID 07c4:a827 control = auto, autosuspend_delay_ms = 2000 -- Datafab
Systems, Inc. (usb-storage)
Bus 002 Device 001 ID 1d6b:0002 control = auto, autosuspend_delay_ms = 0 -- Linux
Foundation 2.0 root hub (hub)
Bus 007 Device 001 ID 1d6b:0001 control = auto, autosuspend_delay_ms = 0 -- Linux
Foundation 1.1 root hub (hub)
Bus 006 Device 001 ID 1d6b:0001 control = auto, autosuspend_delay_ms = 0 -- Linux
Foundation 1.1 root hub (hub)
Bus 005 Device 032 ID 10d6:1100 control = on, autosuspend_delay_ms = 2000 -- Actions
Semiconductor Co., Ltd MPMan MP-Ki 128 MP3 Player/Recorder (snd-usb-audio)
Bus 005 Device 001 ID 1d6b:0001 control = auto, autosuspend_delay_ms = 0 -- Linux
Foundation 1.1 root hub (hub)
Bus 001 Device 001 ID 1d6b:0002 control = auto, autosuspend_delay_ms = 0 -- Linux
Foundation 2.0 root hub (hub)
Bus 004 Device 001 ID 1d6b:0001 control = auto, autosuspend_delay_ms = 0 -- Linux
Foundation 1.1 root hub (hub)
Bus 003 Device 001 ID 1d6b:0001 control = auto, autosuspend_delay_ms = 0 -- Linux
Foundation 1.1 root hub (hub)
(tricky to time switching it on at the right moment so that tlp-stat
will see it before it turns off again). Switching autosuspend off
altogether does not help either.
Powered hub in the middle: the Boomster stays on _until_ I connect the
hub to the laptop. Then it identifies itself to the laptop and switches
off.
Really does not sound to me like it's an issue of digital power: then it
should not work under Windows I think, even granted that this is quite a
different type of laptop.
--
David Kastrup
David Kastrup wrote:
Ostensibly it's 2x5W of output. It runs without complaint on a single
plug when using Analog In, and shuts down in USB mode. I doubt that the
digital part takes up more than one plug can deliver...
Or it talks with the host and says "I want
1A of current or 2A" and the
host says "no way".
Its descriptors claim that it wants 0 mA.
But it's delivered by default with a
two-host-plug USB cable
So it needs more power than a single plug could supply? and would not
be able to know about the power available from the
power-only plug. And it doesn't complain when running from the analog
input either, so it would be somewhat strange to just shut down when in
USB mode.
After a short time, it just stops reacting to USB requests.
It might be possible that some capacitor does no longer work correctly,
and that its internal voltage drops too far when actually doing things.
This would imply that it doesn't work in Windows either. 
1:28 p.m.
On 12/10/2017 12:48 PM, David Kastrup wrote:
Really does not sound to me like it's an issue of
digital power: then it
should not work under Windows I think, even granted that this is quite a
different type of laptop.
boot that other (win) laptop from a linux usb stick and try there to be
sure.
7:06 p.m.
David Kastrup wrote:
Clemens Ladisch writes:
That points to the driver. Probably the firmware hangs when it receives
some request that is not exactly the same as one of those used by the
Windows driver.
Would you be able to recompile the driver?
Regards,
Clemens
After a short time, it just stops reacting to USB
requests.
It might be possible that some capacitor does no longer work correctly,
and that its internal voltage drops too far when actually doing things.
This would imply that it doesn't work in Windows either.
Well, the Windows PC disagrees.
7:28 p.m.
Clemens Ladisch <clemens-P6GI/4k7KOmELgA04lAiVw(a)public.gmane.org>
writes:
David Kastrup wrote:
Ugh. I guess so. I'd have to brush up on the procedure in connection
with my Ubuntu Studio kernel but in the olden times before modules
became a thing due to SLS Linux, I did it frequently.
--
David Kastrup
Clemens Ladisch writes:
That points to the driver. Probably the firmware hangs when it receives
some request that is not exactly the same as one of those used by the
Windows driver.
Would you be able to recompile the driver? After a short time, it just stops reacting to USB
requests.
It might be possible that some capacitor does no longer work correctly,
and that its internal voltage drops too far when actually doing things.
This would imply that it doesn't work in Windows either.
Well, the Windows PC disagrees.
11 Dec
11 Dec
6:55 p.m.
Clemens Ladisch <clemens-P6GI/4k7KOmELgA04lAiVw(a)public.gmane.org>
writes:
David Kastrup wrote:
Aaaaaand another data point. If I switch the Bamster on _before_
booting the laptop, it will stay around and work on USB. It just won't
stand for hotplugging. That's not the first device I had this effect
with, but the other device was an Expresscard with TI chipset (with a
built-in PCI-Express to PCI bridge, so no USB).
Relevant kernel messages for booting with Bamster on:
[ 4.776057] usb 5-1: new full-speed USB device number 2 using uhci_hcd
[ 4.911132] usb 5-1: config 1 has an invalid interface number: 3 but max is 2
[ 4.911134] usb 5-1: config 1 has no interface number 2
[ 4.920126] usb 5-1: New USB device found, idVendor=10d6, idProduct=1100
[ 4.920128] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.920129] usb 5-1: Product: USB Audio
[ 4.920131] usb 5-1: Manufacturer: ACTIONS
[ 4.926554] hidraw: raw HID events driver (C) Jiri Kosina
[ 4.931303] usbcore: registered new interface driver usbhid
[ 4.931304] usbhid: USB HID core driver
[ 4.933197] input: ACTIONS USB Audio as
/devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.3/0003:10D6:1100.0001/input/input8
[ 4.985255] hid-generic 0003:10D6:1100.0001: input,hidraw0: USB HID v2.01 Device
[ACTIONS USB Audio] on usb-0000:00:1d.0-1/input3
[ 78.306210] usb 5-1: 1:1: cannot get freq at ep 0x2
[ 83.426212] usb 5-1: 1:1: cannot get freq at ep 0x2
It works fine. Pulseaudio offers two configurations: one analog output
setting, one S/PDIF setting. However, they appear to behave identically
(there is a pause when switching) and the device does not have any
output other than the built-in speakers.
Now when hotplugging, I am pretty sure that the USB HID thingy was
refused. Is this the desktop session causing problems? At any rate,
the volume control works for the Bamster but does not seem to be routed
to the desktop volume controls: those continue to operate independently
using the volume control buttons of the Thinkpad.
--
David Kastrup
Clemens Ladisch writes:
That points to the driver. Probably the firmware hangs when it receives
some request that is not exactly the same as one of those used by the
Windows driver.
Would you be able to recompile the driver? After a short time, it just stops reacting to USB
requests.
It might be possible that some capacitor does no longer work correctly,
and that its internal voltage drops too far when actually doing things.
This would imply that it doesn't work in Windows either.
Well, the Windows PC disagrees.
8:03 p.m.
On 12/11/2017 06:55 PM, David Kastrup wrote:
Clemens Ladisch
<clemens-P6GI/4k7KOmELgA04lAiVw(a)public.gmane.org>
writes:
Aaaaaand another data point. If I switch the Bamster on _before_
booting the laptop, it will stay around and work on USB. It just won't
stand for hotplugging. That's not the first device I had this effect
with, but the other device was an Expresscard with TI chipset (with a
built-in PCI-Express to PCI bridge, so no USB).
which Kernel version is this?
8:45 p.m.
Max <abonnements-yNUSWsLiBm554TAoqtyWWQ(a)public.gmane.org> writes:
On 12/11/2017 06:55 PM, David Kastrup wrote:
Linux version 4.13.0-19-lowlatency (buildd@lcy01-amd64-021) (gcc version 7.2.0 (Ubuntu
7.2.0-8ubuntu3)) #22-Ubuntu SMP PREEMPT Mon Dec 4 12:59:42 UTC 2017
Some more data points: boot with device plugged in but turned off: will
not turn on successfully afterwards. Wait for desktop to turn on before
turning device on: will not turn on successfully.
Boot with device on: will work. Turn off and on again, refuses to
work.
Successful messages when booting:
[ 2.520052] usb 5-1: new full-speed USB device number 2 using uhci_hcd
[ 2.658075] usb 5-1: config 1 has an invalid interface number: 3 but max is 2
[ 2.658077] usb 5-1: config 1 has no interface number 2
[ 2.667086] usb 5-1: New USB device found, idVendor=10d6, idProduct=1100
[ 2.667088] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.667089] usb 5-1: Product: USB Audio
[ 2.667091] usb 5-1: Manufacturer: ACTIONS
[ 2.675698] hidraw: raw HID events driver (C) Jiri Kosina
[ 2.681185] usbcore: registered new interface driver usbhid
[ 2.681186] usbhid: USB HID core driver
[ 2.683055] input: ACTIONS USB Audio as
/devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.3/0003:10D6:1100.0001/input/input7
[ 2.735300] hid-generic 0003:10D6:1100.0001: input,hidraw0: USB HID v2.01 Device
[ACTIONS USB Audio] on usb-0000:00:1d.0-1/input3
...
[ 63.978825] usbcore: registered new interface driver snd-usb-audio
[ 69.090182] usb 5-1: 1:1: cannot get freq at ep 0x2
[ 74.210179] usb 5-1: 1:1: cannot get freq at ep 0x2
But doesn't seem to matter.
Same session, switching off:
[ 182.208259] usb 5-1: USB disconnect, device number 2
Switching on again, unsuccessfully:
[ 185.432166] usb 5-1: new full-speed USB device number 3 using uhci_hcd
[ 185.777215] usb 5-1: config 1 has an invalid interface number: 3 but max is 2
[ 185.777221] usb 5-1: config 1 has no interface number 2
[ 185.786231] usb 5-1: New USB device found, idVendor=10d6, idProduct=1100
[ 185.786237] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 185.786242] usb 5-1: Product: USB Audio
[ 185.786246] usb 5-1: Manufacturer: ACTIONS
[ 187.004176] usb 5-1: 1:1: cannot get freq at ep 0x2
[ 187.016186] usb 5-1: 3:0: cannot get min/max values for control 2 (id 3)
[ 187.021196] usbhid 5-1:1.3: can't add hid device: -71
[ 187.021212] usbhid: probe of 5-1:1.3 failed with error -71
[ 187.021349] usb 5-1: USB disconnect, device number 3
Another try:
[ 192.168084] usb 5-1: new full-speed USB device number 4 using uhci_hcd
[ 192.304267] usb 5-1: config 1 has an invalid interface number: 3 but max is 2
[ 192.304274] usb 5-1: config 1 has no interface number 2
[ 192.313204] usb 5-1: New USB device found, idVendor=10d6, idProduct=1100
[ 192.313208] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 192.313211] usb 5-1: Product: USB Audio
[ 192.313214] usb 5-1: Manufacturer: ACTIONS
[ 193.532189] usb 5-1: 1:1: cannot get freq at ep 0x2
[ 193.544205] usb 5-1: 3:0: cannot get min/max values for control 2 (id 3)
[ 193.549199] usbhid 5-1:1.3: can't add hid device: -71
[ 193.549215] usbhid: probe of 5-1:1.3 failed with error -71
[ 193.549347] usb 5-1: USB disconnect, device number 4
So this really looks like it would be connected with the "can't add hid
device" message. Immediately afterwards the device disconnects.
But when booting with the device, it works nicely and does something
with the hid.
There is also a wireless card on USB and a card reader (express slot),
but the other Thinkpad T61 I tried has neither. So I don't think they
are related.
So what's up with the usbhid here?
--
David Kastrup
Clemens Ladisch
<clemens-P6GI/4k7KOmELgA04lAiVw-XMD5yJDbdMReXY1tMh2IBg(a)public.gmane.org>
writes:
Aaaaaand another data point. If I switch the Bamster on _before_
booting the laptop, it will stay around and work on USB. It just won't
stand for hotplugging. That's not the first device I had this effect
with, but the other device was an Expresscard with TI chipset (with a
built-in PCI-Express to PCI bridge, so no USB).
which Kernel version is this?
17 Mar
17 Mar
6:47 p.m.
David Kastrup <dak-mXXj517/zsQ(a)public.gmane.org> writes:
Max
<abonnements-yNUSWsLiBm554TAoqtyWWQ-XMD5yJDbdMReXY1tMh2IBg(a)public.gmane.org>
writes:
[...]
On 12/11/2017 06:55 PM, David Kastrup wrote:
Linux version 4.13.0-19-lowlatency (buildd@lcy01-amd64-021) (gcc
version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)) #22-Ubuntu SMP PREEMPT Mon Dec
4 12:59:42 UTC 2017
Some more data points: boot with device plugged in but turned off: will
not turn on successfully afterwards. Wait for desktop to turn on before
turning device on: will not turn on successfully.
Boot with device on: will work. Turn off and on again, refuses to
work. Clemens Ladisch
<clemens-P6GI/4k7KOmELgA04lAiVw-XMD5yJDbdMReXY1tMh2IBg-XMD5yJDbdMReXY1tMh2IBg(a)public.gmane.org>
writes:
Aaaaaand another data point. If I switch the Bamster on _before_
booting the laptop, it will stay around and work on USB. It just won't
stand for hotplugging. That's not the first device I had this effect
with, but the other device was an Expresscard with TI chipset (with a
built-in PCI-Express to PCI bridge, so no USB).
which Kernel version is this? So this really looks like it would be connected with
the "can't add hid
device" message. Immediately afterwards the device disconnects.
But when booting with the device, it works nicely and does something
with the hid.
There is also a wireless card on USB and a card reader (express slot),
but the other Thinkpad T61 I tried has neither. So I don't think they
are related.
So what's up with the usbhid here?
Another data point: I can use the PC Bamster by first removing the
snd_usb_audio module, then switching on the PC Bamster (which then stays
on), then reloading the usb_snd_audio module.
So the essential thing seems to be that the snd_usb_audio module must
not be loaded when switching the PC Bamster on, or it will get turned
off again. Loading it afterwards is fine (and of course required to
actually work with the device).
--
David Kastrup
19 Mar
19 Mar
11:36 p.m.
David Kastrup <dak(a)gnu.org> writes:
Another data point: I can use the PC Bamster by first
removing the
snd_usb_audio module, then switching on the PC Bamster (which then stays
on), then reloading the usb_snd_audio module.
So the essential thing seems to be that the snd_usb_audio module must
not be loaded when switching the PC Bamster on, or it will get turned
off again. Loading it afterwards is fine (and of course required to
actually work with the device).
Here is the corresponding dmesg output:
[10909.673158] usb 5-2: new full-speed USB device number 2 using uhci_hcd
[10909.821193] usb 5-2: config 1 has an invalid interface number: 3 but max is 2
[10909.821199] usb 5-2: config 1 has no interface number 2
[10909.830151] usb 5-2: New USB device found, idVendor=10d6, idProduct=1100
[10909.830156] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[10909.830160] usb 5-2: Product: USB Audio
[10909.830164] usb 5-2: Manufacturer: ACTIONS
[10909.897725] hidraw: raw HID events driver (C) Jiri Kosina
[10911.102180] usb 5-2: 1:1: cannot get freq at ep 0x2
[10911.114146] usb 5-2: 3:0: cannot get min/max values for control 2 (id 3)
[10911.114498] usbcore: registered new interface driver snd-usb-audio
[10911.122121] usbhid 5-2:1.3: can't add hid device: -71
[10911.122138] usbhid: probe of 5-2:1.3 failed with error -71
[10911.124369] usbcore: registered new interface driver usbhid
[10911.124370] usbhid: USB HID core driver
[10911.162160] usb 5-2: 3:0: cannot get min/max values for control 2 (id 3)
[10911.172138] usb 5-2: 3:0: cannot get min/max values for control 2 (id 3)
[10911.192141] usb 5-2: 3:0: cannot get min/max values for control 2 (id 3)
[10911.202138] usb 5-2: 3:0: cannot get min/max values for control 2 (id 3)
[10911.207085] usb 5-2: USB disconnect, device number 2
And bam, the thing switched itself off again.
So:
sudo modprobe -r snd-usb-audio
[10924.329105] usbcore: deregistering interface driver snd-usb-audio
Now switching the thing on again:
[10927.969127] usb 5-2: new full-speed USB device number 3 using uhci_hcd
[10928.114284] usb 5-2: config 1 has an invalid interface number: 3 but max is 2
[10928.114290] usb 5-2: config 1 has no interface number 2
[10928.123286] usb 5-2: New USB device found, idVendor=10d6, idProduct=1100
[10928.123293] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[10928.123299] usb 5-2: Product: USB Audio
[10928.123304] usb 5-2: Manufacturer: ACTIONS
[10928.195484] input: ACTIONS USB Audio as
/devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.3/0003:10D6:1100.0001/input/input12
[10928.248278] hid-generic 0003:10D6:1100.0001: input,hidraw0: USB HID v2.01 Device
[ACTIONS USB Audio] on usb-0000:00:1d.0-2/input3
[10933.216316] usb 5-2: 1:1: cannot get freq at ep 0x2
It's still on without problem. So
sudo modprobe snd-usb-audio
[10938.345556] usbcore: registered new interface driver snd-usb-audio
and it's still on.
And
cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xfe020000 irq 31
1 [Audio ]: USB-Audio - USB Audio
ACTIONS USB Audio at usb-0000:00:1d.0-2, full speed
And I can actually use it (it's hw:Audio ).
So what can I do to get this fixed upstream in a manner where I don't
need to temporarily remove the usb-snd-audio device for plugging the PC
Bamster in?
--
David Kastrup
2236
days inactive
2336
days old
linux-audio-user@lists.linuxaudio.org
14 comments
3 participants
participants (3)
-
Clemens Ladisch -
David Kastrup -
Max