[alsa-devel] USB headset cannot get freq

[Greg KH]

On Sat, May 16, 2015 at 04:25:23PM +0200, Heinz Diehl wrote:
> Hi,
> 
> this is the Jabra Evolve 40 MS headset:
> Bus 001 Device 008: ID 0b0e:0305 GN Netcom
> 
> When plugged in, dmesg says:
> 
> [  247.215998] usb 1-5: new full-speed USB device number 8 using xhci_hcd
> [  247.384000] usb 1-5: New USB device found, idVendor=0b0e, idProduct=0305
> [  247.384008] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [  247.384012] usb 1-5: Product: Jabra EVOLVE LINK MS
> [  247.384016] usb 1-5: Manufacturer: GN Netcom A/S
> [  247.384019] usb 1-5: SerialNumber: 0001A3E08CFC09
> [  247.386542] usb 1-5: 1:1: cannot get freq at ep 0x83
> [  247.388490] usb 1-5: 2:1: cannot get freq at ep 0x4
> [  247.406532] input: GN Netcom A/S Jabra EVOLVE LINK MS as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.3/0003:0B0E:0305.0009/input/input12
> [  247.457203] hid-generic 0003:0B0E:0305.0009: input,hiddev0,hidraw1: USB HID v1.00 Device [GN Netcom A/S Jabra EVOLVE LINK MS] on usb-0000:00:14.0-5/input3
> [  247.467683] usb 1-5: 1:1: cannot get freq at ep 0x83
> [  247.467912] usb 1-5: 1:1: cannot get freq at ep 0x83
> [  247.473505] usb 1-5: 2:1: cannot get freq at ep 0x4
> [  247.473718] usb 1-5: 2:1: cannot get freq at ep 0x4
> [  247.475488] usb 1-5: 1:1: cannot get freq at ep 0x83
> [  247.475721] usb 1-5: 1:1: cannot get freq at ep 0x83
> [  247.481899] usb 1-5: 2:1: cannot get freq at ep 0x4
> [  247.482097] usb 1-5: 2:1: cannot get freq at ep 0x4
> [  247.483351] usb 1-5: 1:1: cannot get freq at ep 0x83
> [  247.483566] usb 1-5: 1:1: cannot get freq at ep 0x83
> [  247.487396] usb 1-5: 2:1: cannot get freq at ep 0x4
> [  247.487586] usb 1-5: 2:1: cannot get freq at ep 0x4
> [  247.494730] usb 1-5: 1:1: cannot get freq at ep 0x83
> [  247.495018] usb 1-5: 1:1: cannot get freq at ep 0x83
> 
> The micro/playback devices show up, but there's no sound and the mic is also
> dead.
> 
> I've spent the last two days reading on the net, tried a lot of different
> options, but whithout any success. In a lot of similar bug reports, people
> point out that this is a bug in the Linux kernel USB subsystem..
> 
> What can I do to debug this further, in order to get a working headset?

The sound developers should be able to help you (added to the cc:)

greg k-h