pacman -Syu ----> usb sound device no longer works

hedron · 02-18-2022, 07:50 PM

So, I updated and my startech usb sound device (https://www.startech.com/en-us/cards...s/icusbaudio2d) doesn't work anymore. I plug it in, and the lights come on, and there's a hissing in the ear phones, and after a while they get hot. I never had hot ear phones before.

I don't see the device in pavucontrol or in the plasma system settings.

The attached image is what alsamixer looks like.

lsusb | grep Media:

Code:

Bus 002 Device 010: ID 0d8c:8810 C-Media Electronics, Inc. USB Advanced Audio Device

cat .asoundrc:

Code:

pcm.!default {
        type plug
        slave.pcm "gtkrwn"
}

pcm.gtkrwn {
        type plug
        slave.pcm "dmix:1,0"
}

ctl.!default {
        type hw
        card 2
}

I tried a similar more compact/defaultish config, but it didn't work.

lsmod | grep snd_usb:

Code:

snd_usb_audio         376832  3
snd_usbmidi_lib        45056  1 snd_usb_audio
snd_rawmidi            49152  1 snd_usbmidi_lib
mc                     65536  5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common
snd_hwdep              16384  2 snd_usb_audio,snd_hda_codec
snd_pcm               163840  5 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core
snd                   126976  28 snd_ctl_led,snd_hda_codec_generic,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,thinkpad_acpi,snd_pcm,snd_rawmidi

aplay -l: (edited for brevity)

Code:

card 2: Device [USB Advanced Audio Device], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Device [USB Advanced Audio Device], device 1: USB Audio [USB Audio #1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

cat /proc/asound/cards:

Code:

 0 [HDMI           ]: HDA-Intel - HDA Intel HDMI
                      HDA Intel HDMI at 0xe0630000 irq 50
 1 [PCH            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xe0634000 irq 49
 2 [Device         ]: USB-Audio - USB Advanced Audio Device
                      Speed Dragon USB Advanced Audio Device at usb-0000:00:14.0-3, full speed

ondoho · 02-19-2022, 05:58 AM

Assuming it really has something to do with the upgrade, have you rebooted?

hedron · 02-19-2022, 12:27 PM

Quote:

Originally Posted by ondoho

have you rebooted?

Yes.

Everytime I upgrade I regret upgrading because something always breaks.

boughtonp · 02-19-2022, 04:21 PM

Quote:

Originally Posted by hedron

Everytime I upgrade I regret upgrading because something always breaks.

Sounds like you may be using the wrong distro.

Quote:

Originally Posted by https://wiki.archlinux.org/title/Frequently_asked_questions#Why_would_I_not_want_to_use_Arch?

Why would I not want to use Arch?

You may not want to use Arch, if:
* you do not have the ability/time/desire for a 'do-it-yourself' GNU/Linux distribution.

However, hot ear phones sounds to me like a hardware issue - do you have other audio devices or another computer to verify?

hedron · 02-19-2022, 06:02 PM

Code:

[  631.833539] usb 2-3: new full-speed USB device number 11 using xhci_hcd
[  631.993354] usb 2-3: New USB device found, idVendor=0d8c, idProduct=8810, bcdDevice= 1.04
[  631.993361] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  631.993363] usb 2-3: Product: USB Advanced Audio Device
[  631.993366] usb 2-3: Manufacturer: Speed Dragon
[  632.038158] input: Speed Dragon USB Advanced Audio Device as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.3/0003:0D8C:8810.0007/input/input29
[  632.093577] hid-generic 0003:0D8C:8810.0007: input,hidraw4: USB HID v1.11 Device [Speed Dragon USB Advanced Audio Device] on usb-0000:00:14.0-3/input3

dmesg seems to imply that the updated kernel thinks it's an input device.

I tried what it said to do here: https://unix.stackexchange.com/quest...ce-realtek-nic but I'd get this:

Code:

echo 0000:00:14.0 > /sys/bus/hid/drivers/hid-generic/unbind
bash: echo: write error: No such device

It could be a hardware issue, but it's a little too much of a coincidence to have it mysterious break after a software update.

ondoho · 02-20-2022, 04:30 AM

^ Why did you think that stackexchange article has any bearing on your situation? I don't see the connection.

You're going to have to do more troubleshooting.

You could remove ~/.asoundrc and see if it has an impact on your problem.

Are the hot earphones reproducible?

Have you selected your external soundcard as the default card at boot?
Have you selected it at all before plugging the phones in? You can do that via alsamixer.

If you're sure the upgrade is at fault, you're going to have to prove it. Might want to start with pacman logs.

hedron · 02-20-2022, 09:35 PM

Quote:

Originally Posted by ondoho

^ Why did you think that stackexchange article has any bearing on your situation? I don't see the connection.

Because dmesg says it's loading the wrong driver. That article explains how to force (un)load a driver, but it's possible that it doesn't work if hid-generic is built-in.

Quote:

You're going to have to do more troubleshooting.

You could remove ~/.asoundrc and see if it has an impact on your problem.

No effect.

Quote:

Are the hot earphones reproducible?

It takes 2 or 3 minutes, but they heat up everytime.

Quote:

Have you selected your external soundcard as the default card at boot?

Code:

cat /etc/asound.conf 
defaults.pcm.card 2
defaults.ctl.card 2

I assume that's what determines what gets loaded at boot time.

Quote:

Have you selected it at all before plugging the phones in? You can do that via alsamixer.

Yes, the image in the OP shows the device in alsamixer when selected.

hedron · 02-20-2022, 10:21 PM

Ok, I installed the LTS kernel, and removed the "regular" kernel. And now it(plasma system settings) sees the device, but there's still no sound, but static and the headphones get hot. I guess it's entirely possible that it did break coincidentally at the same time I updated, I just remain doubtful that's the case.

ondoho · 02-21-2022, 02:59 AM

Quote:

Originally Posted by hedron

Yes, the image in the OP shows the device in alsamixer when selected.

Oh yes, light yellow on white.

Sorry, I'm fresh out of ideas here.

If you think it loads the wrong driver, maybe try brute-force removing it?
I believe rmmod will do that.
Anyhow, test that theory. If it turns out to be correct at least you know what solutions to search for.