[SOLVED] HyperX Cloud II Headset works only in LTS kernel

bane-of-my-red-crane · 2016-11-11 03:40:51

Whenever I boot into the standard mainline kernel, the headset isn't detected by PulseAudio. If I unplug it and plug it back in it is detected and everything will work fine after that (until I reboot, etc).

When I boot to the LTS kernel, everything works fine. I don't remember when this first started, but when it did happen I ended up reinstalling Arch around my /home partition to no avail. In other words, everything was reinstalled, but my home directory stayed the same.

This is what is reported by dmesg after unplugging and plugging it the headset back in (in LTS kernel):

[  588.952337] usb 3-10: USB disconnect, device number 4
[  592.415759] usb 3-10: new full-speed USB device number 5 using xhci_hcd
[  592.802283] usb 3-10: Warning! Unlikely big volume range (=4096), cval->res is probably wrong.
[  592.802285] usb 3-10: [11] FU [Sidetone Playback Volume] ch = 1, val = 0/4096/1
[  593.030910] input: Kingston HyperX 7.1 Audio as /devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10:1.3/0003:0951:16A4.0004/input/input20
[  593.085883] hid-generic 0003:0951:16A4.0004: input,hiddev0,hidraw2: USB HID v1.11 Device [Kingston HyperX 7.1 Audio] on usb-0000:00:14.0-10/input3

This one's a stumper. I'll update soon with the dmesg output when in the mainline kernel, because it's very different from what I remember.

Thanks in advance!

Last edited by bane-of-my-red-crane (2017-03-08 23:40:11)

bane-of-my-red-crane · 2016-11-11 03:52:55

On the mainline kernel I see:

[    2.080933] input: Kingston HyperX 7.1 Audio as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.3/0003:0951:16A4.0003/input/input3

And

[    2.135373] hid-generic 0003:0951:16A4.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Kingston HyperX 7.1 Audio] on usb-0000:00:14.0-10/input3

I have a feeling these messages just mean the headset was detected as some input device, not an audio device (it shows up in `xinput`).

I also see a whole lot of:

[  126.395944] usb 1-10: 1:1: cannot get freq at ep 0x81
[  126.396054] usb 1-10: 1:1: cannot set freq 44100 to ep 0x81
[  126.397780] usb 1-10: 1:1: cannot get freq at ep 0x81
[  126.397878] usb 1-10: 1:1: cannot set freq 44100 to ep 0x81
[  126.399632] usb 1-10: 1:1: cannot get freq at ep 0x81
[  126.399729] usb 1-10: 1:1: cannot set freq 44100 to ep 0x81
[  126.401467] usb 1-10: 1:1: cannot set freq 44100 to ep 0x81
[  126.403320] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.411203] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.417876] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.424556] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.431271] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.437904] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.447916] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.457895] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.469438] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.477966] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.484595] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.491321] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.497905] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.504645] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.511298] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.517955] usb 1-10: 2:1: cannot set freq 44100 to ep 0x1
[  126.524688] usb 1-10: 1:1: cannot set freq 44100 to ep 0x81
[  126.526495] usb 1-10: 1:1: cannot set freq 44100 to ep 0x81
[  126.528251] usb 1-10: 1:1: cannot set freq 44100 to ep 0x81
[  126.530020] usb 1-10: 1:1: cannot set freq 44100 to ep 0x81
[  126.531785] usb 1-10: 1:1: cannot set freq 44100 to ep 0x81
[  126.533549] usb 1-10: 1:1: cannot set freq 44100 to ep 0x81
[  126.535289] usb 1-10: 1:1: cannot set freq 44100 to ep 0x81
[  126.537084] usb 1-10: 1:1: cannot set freq 44100 to ep 0x81

I saw a few messages like this in the LTS kernel but not nearly as much. Here's what happens if I unplug and replug the headset:

[  535.924803] usb 1-10: USB disconnect, device number 4
[  538.129479] usb 1-10: new full-speed USB device number 5 using xhci_hcd
[  538.510354] usb 1-10: Warning! Unlikely big volume range (=4096), cval->res is probably wrong.
[  538.510358] usb 1-10: [11] FU [Sidetone Playback Volume] ch = 1, val = 0/4096/1
[  538.738888] input: Kingston HyperX 7.1 Audio as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.3/0003:0951:16A4.0004/input/input20
[  538.793052] hid-generic 0003:0951:16A4.0004: input,hiddev0,hidraw2: USB HID v1.11 Device [Kingston HyperX 7.1 Audio] on usb-0000:00:14.0-10/input3

After that it's detected by pulseaudio (and alsa) just fine. I forgot to mention that before I unplug it and plug it back in, the headset isn't detected in alsa either. It's completely off the radar.

Thanks again!

Last edited by bane-of-my-red-crane (2016-11-11 04:31:40)

jasonwryan · 2016-11-11 04:29:25

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code

bane-of-my-red-crane · 2016-11-11 04:32:16

Fixed! Sorry about that.

jasonwryan · 2016-11-11 04:45:52

What difference, if any, between modules loaded before (undetected) and after (registered)?

bane-of-my-red-crane · 2016-11-11 04:49:59

Here's my alsa info in mainline: http://www.alsa-project.org/db/?f=90035 … 726af5f48f
Here it is in LTS: http://www.alsa-project.org/db/?f=6228c … 9e29f353d4

I believe it lists the loaded (sound) modules. Let me know if you want me to run something else, specifically.

bane-of-my-red-crane · 2016-11-11 04:50:57

From the looks of this, it seems the card is detected by alsa. But with some testing with aplay while in mainline there was only static being played.

rubymonk · 2016-11-29 06:56:38

I have the exact same problem.

Running 4.8.10-1-ARCH, the Kingston HyperX USB soundcard only works after been unplugged and re-plugged, despite being recognized at startup.

rubymonk · 2017-01-13 23:59:47

After the last update, today it worked without needing to unplug and replug. Can OP confirm too?

rokups · 2017-02-14 14:42:49

Using same headset, still need to unplug it after boot. Here is relevant dmesg messages on boot and after reconnecting usb sound card.

~ % dmesg|grep "1-7"
[   11.295505] usb 1-7: new full-speed USB device number 3 using xhci_hcd
[   11.734942] input: Kingston HyperX 7.1 Audio as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.3/0003:0951:16A4.0001/input/input1
[   32.631520] usb 1-7: 1:1: cannot get freq at ep 0x81
[   32.633108] usb 1-7: 2:1: cannot get freq at ep 0x1
[   46.837099] usb 1-7: 1:1: cannot get freq at ep 0x81
[   46.837186] usb 1-7: 1:1: cannot set freq 44100 to ep 0x81
[   46.838988] usb 1-7: 1:1: cannot set freq 44100 to ep 0x81
[   46.841769] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.850138] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.860109] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.866815] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.873475] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.880127] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.890168] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.896786] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.906277] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.913636] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.920118] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.926841] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.933637] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.944650] usb 1-7: 1:1: cannot set freq 44100 to ep 0x81
[   46.945418] usb 1-7: 1:1: cannot set freq 44100 to ep 0x81
[   46.947088] usb 1-7: 1:1: cannot set freq 44100 to ep 0x81
[   46.948682] usb 1-7: 1:1: cannot set freq 44100 to ep 0x81
[   46.960267] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.970215] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.976954] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[   46.983603] usb 1-7: 2:1: cannot set freq 44100 to ep 0x1
[  267.530101] usb 1-7: USB disconnect, device number 3
[  270.302320] usb 1-7: new full-speed USB device number 10 using xhci_hcd
[  270.767461] input: Kingston HyperX 7.1 Audio as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.3/0003:0951:16A4.0009/input/input21

bane-of-my-red-crane · 2017-03-07 20:03:33

I just started having the same issue on the LTS kernel. Unfortunately, the mainline kernel doesn't seem to be working either.

bane-of-my-red-crane · 2017-03-08 23:38:49

I managed to get it working by installing the pulseaudio-git package from the aur. A little investigating with git bisect showed that it was fixed in commit: 5287f09f067e81f3fd3c2d781a60e64cc0619f6c. According to the commit message (if I understand it correctly), the author's additional code shouldn't actually change anything as long as drivers are being sane. This leads me to believe that some driver was broken between kernel 4.4 and 4.9 and it triggered the bug in pulse. I'm kinda interested but I'm not sure how to go deeper. The commit itself doesn't seem to include any details of a bug that it fixes or anything of the sort.

I'm just going off on a tangent at this point, I suppose. Hopefully this helps someone who encounters a similar problem in the near future before this change gets into the next release.

rubymonk · 2017-03-10 08:29:11

bane-of-my-red-crane wrote:

I managed to get it working by installing the pulseaudio-git package from the aur. A little investigating with git bisect showed that it was fixed in commit: 5287f09f067e81f3fd3c2d781a60e64cc0619f6c. According to the commit message (if I understand it correctly), the author's additional code shouldn't actually change anything as long as drivers are being sane. This leads me to believe that some driver was broken between kernel 4.4 and 4.9 and it triggered the bug in pulse. I'm kinda interested but I'm not sure how to go deeper. The commit itself doesn't seem to include any details of a bug that it fixes or anything of the sort.
I'm just going off on a tangent at this point, I suppose. Hopefully this helps someone who encounters a similar problem in the near future before this change gets into the next release.

Hey, thanks a lot man! I'll try it out later. Finally seeing the end of the tunnel on this annoying little bugger.

rokups · 2017-03-12 09:23:07

Multiple boots after 4.10 upgrade usb card is working straight away for me. Anyone else having similar experience?

rubymonk · 2017-03-12 14:05:13

rokups wrote:

Multiple boots after 4.10 upgrade usb card is working straight away for me. Anyone else having similar experience?

Same. Seems 4.10 fixed it, I don't even need to change sink anymore. Yeah!

Arch Linux

#1 2016-11-11 03:40:51

[SOLVED] HyperX Cloud II Headset works only in LTS kernel

#2 2016-11-11 03:52:55

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#3 2016-11-11 04:29:25

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#4 2016-11-11 04:32:16

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#5 2016-11-11 04:45:52

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#6 2016-11-11 04:49:59

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#7 2016-11-11 04:50:57

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#8 2016-11-29 06:56:38

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#9 2017-01-13 23:59:47

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#10 2017-02-14 14:42:49

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#11 2017-03-07 20:03:33

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#12 2017-03-08 23:38:49

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#13 2017-03-10 08:29:11

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#14 2017-03-12 09:23:07

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

#15 2017-03-12 14:05:13

Re: [SOLVED] HyperX Cloud II Headset works only in LTS kernel

Board footer