You are not logged in.

#1 2015-10-25 03:23:03

mypetbirdrules
Member
From: Columbus
Registered: 2015-10-04
Posts: 16

USB Headset Works on Boot But Fails When Reconnected

I have this weird problem where my Turtle Beach PLa headset works on boot but stops playing audio when I unplug it and plug it in again. When I reconnect it, dmesg outputs no errors, the headset is detected, and amixer shows it unmuted and working but it doesn't play sound.

Offline

#2 2015-10-25 11:40:14

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,167

Re: USB Headset Works on Boot But Fails When Reconnected

maybe the default audio output is set differently depending on what is detected at boot time.

Please post aplay -L  (that's a Capital Lima ) from booting with headset plugged in and booted without .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 2015-10-25 14:55:49

mypetbirdrules
Member
From: Columbus
Registered: 2015-10-04
Posts: 16

Re: USB Headset Works on Boot But Fails When Reconnected

Well, it seems that the headset will not work unless it is connected during system boot. Plugging it in causes it to be detected, but running # speaker-test gives me this:

speaker-test

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Playback open error: -2, No such file or directory

When I boot with the headset plugged in, it works. However, when I unplug it and plug it in again, speaker-test throws an error about 1074:dmix unable to open slave.

Offline

#4 2015-10-26 14:35:50

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,167

Re: USB Headset Works on Boot But Fails When Reconnected

That suggests something is not initialized correctly when the headset is plugged in after boot.

Please post aplay -L  (that's a Capital Lima ) from booting with headset plugged in and booted without .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Board footer

Powered by FluxBB