0

Running Pop_OS 20.10, I'm occasionally having problems with my headset not working after waking from sleep. The device is plugged in, and the issue persists even after switching from one USB to another (though I don't discount problems with the bus). Running pulseaudio -k && sudo alsa force-reload sometimes gets it back, but as it didn't this time I dug a bit deeper.

Checking the output of sudo lsusb -v, I'm able to see the following:

$ sudo lsusb -v

...
Bus 001 Device 010: ID 0951:16da Kingston Technology HyperX Cloud Stinger Wireless
Device Descriptor:
...
Device Status:     0x0000
  (Bus Powered)
...

Comparing against other devices like my USB mouse, that Device Status field is set to 0x0001 rather than 0x0000 so it seems like as a troubleshooting step we may want to try flipping the status of the headset. I've been trying to figure how to go about this however, and I'm not able to figure out how to do so. For now, I'll try relogging/booting to get back in order.

Edit: As recommended by Eduardo in the comments I checked dmesg and found messages in there indicating the headset was detected as input but nothing on output.

[    1.927460] usb 3-1.1: Product: HyperX Cloud Stinger Wireless
[    1.927461] usb 3-1.1: Manufacturer: Kingston
...
[    1.988615] input: Kingston HyperX Cloud Stinger Wireless Consumer Control as
 /devices/pci0000:00/0000:00:07.1/0000:0a:00.3/usb3/3-1/3-1.1/3-1.1:1.3/0003:095
1:16DA.0005/input/input11
[    2.048324] input: Kingston HyperX Cloud Stinger Wireless as /devices/pci0000
:00/0000:00:07.1/0000:0a:00.3/usb3/3-1/3-1.1/3-1.1:1.3/0003:0951:16DA.0005/input
/input12
[    2.048388] input: Kingston HyperX Cloud Stinger Wireless as /devices/pci0000:00/0000:00:07.1/0000:0a:00.3/usb3/3-1/3-1.1/3-1.1:1.3/0003:0951:16DA.0005/input/input13
[    2.048443] input: Kingston HyperX Cloud Stinger Wireless as /devices/pci0000:00/0000:00:07.1/0000:0a:00.3/usb3/3-1/3-1.1/3-1.1:1.3/0003:0951:16DA.0005/input/input14
[    2.048555] hid-generic 0003:0951:16DA.0005: input,hiddev2,hidraw4: USB HID v1.11 Device [Kingston HyperX Cloud Stinger Wireless] on usb-0000:0a:00.3-1.1/input3

Similar output after switching to a different USB bus:

[  328.966274] usb 1-8: Product: HyperX Cloud Stinger Wireless
[  328.966275] usb 1-8: Manufacturer: Kingston
[  329.475135] input: Kingston HyperX Cloud Stinger Wireless Consumer Control as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-8/1-8:1.3/0003:0951:16DA.000A/input/input36
[  329.532475] input: Kingston HyperX Cloud Stinger Wireless as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-8/1-8:1.3/0003:0951:16DA.000A/input/input37
[  329.532570] input: Kingston HyperX Cloud Stinger Wireless as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-8/1-8:1.3/0003:0951:16DA.000A/input/input38
[  329.532632] input: Kingston HyperX Cloud Stinger Wireless as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-8/1-8:1.3/0003:0951:16DA.000A/input/input39
[  329.532744] hid-generic 0003:0951:16DA.000A: input,hiddev2,hidraw4: USB HID v1.11 Device [Kingston HyperX Cloud Stinger Wireless] on usb-0000:02:00.0-8/input3

Despite this, after killing pulse, restarting alsa, and using pactl to refresh the device list there are two output entries (digital and analog) in Gnome for the headset.

Edit 2: Also, now it's persisting across reboots and the best I can get is just the right ear working for some reason.

Edit 3: Alright, I'm not sure what happened here but the audio came back after I actually adjusted the volume on the headset itself. lsusb still shows the device as being status 0, so I guess that was a red herring. Maybe it had something to do with Gnome rather than some kind of device issue.

4
  • Also check sudo dmesg. – Eduardo Trápani Apr 2 at 18:53
  • Good thinking, checked in there and found messages in there indicating that it was detected as input but nothing on output. Despite this, after killing pulse, restarting alsa, and using pactl to refresh the device list there are two output entries (digital and analog) in Gnome for the headset. – Lucas Tobin Apr 2 at 20:08
  • I don't see the new information. Usually it is a good idea to add it to the question, so that it is readily available to new readers. – Eduardo Trápani Apr 2 at 20:09
  • Sorry, new to this site and hit enter without realizing that would send a comment. I've edited that comment and will add it to the question as well. – Lucas Tobin Apr 2 at 20:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.