Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #221242 > unrolled thread
| Started by | riveravaldez <riveravaldezmail@gmail.com> |
|---|---|
| First post | 2020-04-12 02:10 +0200 |
| Last post | 2020-04-13 15:10 +0200 |
| Articles | 11 — 4 participants |
Back to article view | Back to linux.debian.user
Sound issues on ThinkPad X220T (Lenovo) riveravaldez <riveravaldezmail@gmail.com> - 2020-04-12 02:10 +0200
Re: Sound issues on ThinkPad X220T (Lenovo) riveravaldez <riveravaldezmail@gmail.com> - 2020-04-12 04:30 +0200
Re: Sound issues on ThinkPad X220T (Lenovo) riveravaldez <riveravaldezmail@gmail.com> - 2020-04-12 04:50 +0200
Re: Sound issues on ThinkPad X220T (Lenovo) deloptes <deloptes@gmail.com> - 2020-04-12 10:50 +0200
Re: Sound issues on ThinkPad X220T (Lenovo) riveravaldez <riveravaldezmail@gmail.com> - 2020-04-12 16:50 +0200
Re: Sound issues on ThinkPad X220T (Lenovo) Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-12 10:20 +0200
Re: Sound issues on ThinkPad X220T (Lenovo) riveravaldez <riveravaldezmail@gmail.com> - 2020-04-12 16:50 +0200
Re: Sound issues on ThinkPad X220T (Lenovo) Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-12 17:30 +0200
Re: Sound issues on ThinkPad X220T (Lenovo) riveravaldez <riveravaldezmail@gmail.com> - 2020-04-12 18:00 +0200
Re: Sound issues on ThinkPad X220T (Lenovo) deloptes <deloptes@gmail.com> - 2020-04-12 21:40 +0200
Re: Sound issues on ThinkPad X220T (Lenovo) Florent Rougon <f.rougon@free.fr> - 2020-04-13 15:10 +0200
| From | riveravaldez <riveravaldezmail@gmail.com> |
|---|---|
| Date | 2020-04-12 02:10 +0200 |
| Subject | Sound issues on ThinkPad X220T (Lenovo) |
| Message-ID | <zUymd-2DH-1@gated-at.bofh.it> |
Hi,
I would like to know what's the proper way to solve this. I'm on an
updated debian-testing installation (with pulseaudio installed and
working, but the problem seems to be previous, i.e., in ALSA, because
pavucontrol doesn't show the soundcard in its correspondent tab).
I can get audio from audacity and audacious as long as I choose
manually the proper soundcard in its options, but not from other
programs (e.g., firefox, mplayer, etc.), which I suppose use the
default soundcard.
Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo
speaker-test -c2' works flawlessly. (The idea to check that came from
[1].)
I already tested (following [2]):
$ sudo alsactl init
Found hardware: "HDA-Intel" "Conexant CX20590"
"HDA:14f1506e,17aa21db,00100003 HDA:80862805,80860101,00100000"
"0x17aa" "0x21db"
Hardware is initialized using a generic method
But nothing changed after reboot. (Though, the CX20590 is the working
choice for audacious/audacity.)
I have this info:
$ cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf2520000 irq 35
$ lspci -v
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
Family High Definition Audio Controller (rev 04)
Subsystem: Lenovo 6 Series/C200 Series Chipset Family High Definition
Audio Controller
Flags: bus master, fast devsel, latency 0, IRQ 35
Memory at f2520000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
Any other info I could provide?
What should I do?
BTW, JACK also fails to work, with these messages:
20:59:14.349 Reiniciar estadísticas.
20:59:14.356 Cambios en las conexiones ALSA.
Cannot connect to server socket err = No existe el fichero o el directorio
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
skipping unlock
20:59:31.365 JACK está iniciándose...
20:59:31.366 /usr/bin/jackd -v -dalsa -r48000 -p512 -n2 -Xseq -D
-Chw:PCH,0 -Phw:PCH,0
Cannot connect to server socket err = No existe el fichero o el directorio
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
skipping unlock
20:59:31.382 JACK se inició con PID=3144.
no message buffer overruns
no message buffer overruns
no message buffer overruns
jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackPosixThread::ThreadHandler : start
Jack: capture device hw:PCH,0
Jack: playback device hw:PCH,0
Jack: apparent rate = 48000
Jack: frames per period = 512
Jack: JackDriver::Open capture_driver_name = hw:PCH,0
Jack: JackDriver::Open playback_driver_name = hw:PCH,0
Jack: Check protocol client = 8 server = 8
Jack: JackEngine::ClientInternalOpen: name = system
Jack: JackEngine::AllocateRefNum ref = 0
Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = 0
Jack: JackEngine::NotifyAddClient: name = system
Jack: JackGraphManager::SetBufferSize size = 512
Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0
Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Jack: JackDriver::SetupDriverSync driver sem in flush mode
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:PCH,0|hw:PCH,0|512|2|48000|0|0|nomon|swmeter|-|32bit
ATTENTION: The playback device "hw:PCH,0" is already in use. Please
stop the application using it and run JACK again
Jack: JackDriver::Close
Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0
Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Jack: JackEngine::ClientInternalClose ref = 0
Jack: JackEngine::ClientCloseAux ref = 0
Jack: JackGraphManager::RemoveAllPorts ref = 0
Released audio card Audio0
audio_reservation_finish
Jack: ~JackDriver
Cannot initialize driver
Jack: no message buffer overruns
Jack: JackPosixThread::Stop
Jack: JackPosixThread::ThreadHandler : exit
JackServer::Open failed with -1
Jack: Succeeded in unlocking 82280346 byte memory area
Jack: JackShmMem::delete size = 0 index = 0
Jack: ~JackDriver
Jack: Succeeded in unlocking 1187 byte memory area
Jack: JackShmMem::delete size = 0 index = 1
Jack: Cleaning up shared memory
Jack: Cleaning up files
Jack: Unregistering server `default'
Failed to open server
20:59:31.602 JACK ha sido detenido
20:59:33.455 No puede conectarse al servidor JACK como cliente. - La
operación global falló. - No puede conectarse al servidor. Por favor
revise la ventana de mensajes para mas información.
Cannot connect to server socket err = No existe el fichero o el directorio
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
skipping unlock
Thanks a lot!
[1] http://forums.debian.net/viewtopic.php?f=6&t=39116#p246951
[2] https://wiki.debian.org/ALSA#Loading_modules
[toc] | [next] | [standalone]
| From | riveravaldez <riveravaldezmail@gmail.com> |
|---|---|
| Date | 2020-04-12 04:30 +0200 |
| Message-ID | <zUAxH-3X8-1@gated-at.bofh.it> |
| In reply to | #221242 |
On 4/11/20, riveravaldez <riveravaldezmail@gmail.com> wrote: > Hi, > > I would like to know what's the proper way to solve this. I'm on an > updated debian-testing installation (with pulseaudio installed and > working, but the problem seems to be previous, i.e., in ALSA, because > pavucontrol doesn't show the soundcard in its correspondent tab). > > I can get audio from audacity and audacious as long as I choose > manually the proper soundcard in its options, but not from other > programs (e.g., firefox, mplayer, etc.), which I suppose use the > default soundcard. > > Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo > speaker-test -c2' works flawlessly. (The idea to check that came from > [1].) > > I already tested (following [2]): > > $ sudo alsactl init > Found hardware: "HDA-Intel" "Conexant CX20590" > "HDA:14f1506e,17aa21db,00100003 HDA:80862805,80860101,00100000" > "0x17aa" "0x21db" > Hardware is initialized using a generic method > > But nothing changed after reboot. (Though, the CX20590 is the working > choice for audacious/audacity.) > > I have this info: > > $ cat /proc/asound/cards > 0 [PCH ]: HDA-Intel - HDA Intel PCH > HDA Intel PCH at 0xf2520000 irq 35 > > $ lspci -v > 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset > Family High Definition Audio Controller (rev 04) > Subsystem: Lenovo 6 Series/C200 Series Chipset Family High Definition > Audio Controller > Flags: bus master, fast devsel, latency 0, IRQ 35 > Memory at f2520000 (64-bit, non-prefetchable) [size=16K] > Capabilities: <access denied> > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > > Any other info I could provide? > What should I do? > > BTW, JACK also fails to work, with these messages: > > 20:59:14.349 Reiniciar estadísticas. > 20:59:14.356 Cambios en las conexiones ALSA. > Cannot connect to server socket err = No existe el fichero o el directorio > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > 20:59:31.365 JACK está iniciándose... > 20:59:31.366 /usr/bin/jackd -v -dalsa -r48000 -p512 -n2 -Xseq -D > -Chw:PCH,0 -Phw:PCH,0 > Cannot connect to server socket err = No existe el fichero o el directorio > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > 20:59:31.382 JACK se inició con PID=3144. > no message buffer overruns > no message buffer overruns > no message buffer overruns > jackdmp 1.9.12 > Copyright 2001-2005 Paul Davis and others. > Copyright 2004-2016 Grame. > Copyright 2016-2017 Filipe Coelho. > jackdmp comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute it > under certain conditions; see the file COPYING for details > JACK server starting in realtime mode with priority 10 > self-connect-mode is "Don't restrict self connect requests" > Jack: JackPosixThread::StartImp : create non RT thread > Jack: JackPosixThread::ThreadHandler : start > Jack: capture device hw:PCH,0 > Jack: playback device hw:PCH,0 > Jack: apparent rate = 48000 > Jack: frames per period = 512 > Jack: JackDriver::Open capture_driver_name = hw:PCH,0 > Jack: JackDriver::Open playback_driver_name = hw:PCH,0 > Jack: Check protocol client = 8 server = 8 > Jack: JackEngine::ClientInternalOpen: name = system > Jack: JackEngine::AllocateRefNum ref = 0 > Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = 0 > Jack: JackEngine::NotifyAddClient: name = system > Jack: JackGraphManager::SetBufferSize size = 512 > Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 > Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 > Jack: JackDriver::SetupDriverSync driver sem in flush mode > audio_reservation_init > Acquire audio card Audio0 > creating alsa driver ... > hw:PCH,0|hw:PCH,0|512|2|48000|0|0|nomon|swmeter|-|32bit > ATTENTION: The playback device "hw:PCH,0" is already in use. Please > stop the application using it and run JACK again > Jack: JackDriver::Close > Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0 > Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 > Jack: JackEngine::ClientInternalClose ref = 0 > Jack: JackEngine::ClientCloseAux ref = 0 > Jack: JackGraphManager::RemoveAllPorts ref = 0 > Released audio card Audio0 > audio_reservation_finish > Jack: ~JackDriver > Cannot initialize driver > Jack: no message buffer overruns > Jack: JackPosixThread::Stop > Jack: JackPosixThread::ThreadHandler : exit > JackServer::Open failed with -1 > Jack: Succeeded in unlocking 82280346 byte memory area > Jack: JackShmMem::delete size = 0 index = 0 > Jack: ~JackDriver > Jack: Succeeded in unlocking 1187 byte memory area > Jack: JackShmMem::delete size = 0 index = 1 > Jack: Cleaning up shared memory > Jack: Cleaning up files > Jack: Unregistering server `default' > Failed to open server > 20:59:31.602 JACK ha sido detenido > 20:59:33.455 No puede conectarse al servidor JACK como cliente. - La > operación global falló. - No puede conectarse al servidor. Por favor > revise la ventana de mensajes para mas información. > Cannot connect to server socket err = No existe el fichero o el directorio > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > > Thanks a lot! > > [1] http://forums.debian.net/viewtopic.php?f=6&t=39116#p246951 > [2] https://wiki.debian.org/ALSA#Loading_modules > I guess I should have added: $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 Thanks a lot in advance.
[toc] | [prev] | [next] | [standalone]
| From | riveravaldez <riveravaldezmail@gmail.com> |
|---|---|
| Date | 2020-04-12 04:50 +0200 |
| Message-ID | <zUAR3-448-1@gated-at.bofh.it> |
| In reply to | #221247 |
On 4/11/20, riveravaldez <riveravaldezmail@gmail.com> wrote:
> On 4/11/20, riveravaldez <riveravaldezmail@gmail.com> wrote:
>> Hi,
>>
>> I would like to know what's the proper way to solve this. I'm on an
>> updated debian-testing installation (with pulseaudio installed and
>> working, but the problem seems to be previous, i.e., in ALSA, because
>> pavucontrol doesn't show the soundcard in its correspondent tab).
>>
>> I can get audio from audacity and audacious as long as I choose
>> manually the proper soundcard in its options, but not from other
>> programs (e.g., firefox, mplayer, etc.), which I suppose use the
>> default soundcard.
>>
>> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo
>> speaker-test -c2' works flawlessly. (The idea to check that came from
>> [1].)
>>
>> I already tested (following [2]):
>>
>> $ sudo alsactl init
>> Found hardware: "HDA-Intel" "Conexant CX20590"
>> "HDA:14f1506e,17aa21db,00100003 HDA:80862805,80860101,00100000"
>> "0x17aa" "0x21db"
>> Hardware is initialized using a generic method
>>
>> But nothing changed after reboot. (Though, the CX20590 is the working
>> choice for audacious/audacity.)
>>
>> I have this info:
>>
>> $ cat /proc/asound/cards
>> 0 [PCH ]: HDA-Intel - HDA Intel PCH
>> HDA Intel PCH at 0xf2520000 irq 35
>>
>> $ lspci -v
>> 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
>> Family High Definition Audio Controller (rev 04)
>> Subsystem: Lenovo 6 Series/C200 Series Chipset Family High Definition
>> Audio Controller
>> Flags: bus master, fast devsel, latency 0, IRQ 35
>> Memory at f2520000 (64-bit, non-prefetchable) [size=16K]
>> Capabilities: <access denied>
>> Kernel driver in use: snd_hda_intel
>> Kernel modules: snd_hda_intel
>>
>> Any other info I could provide?
>> What should I do?
>>
>> BTW, JACK also fails to work, with these messages:
>>
>> 20:59:14.349 Reiniciar estadísticas.
>> 20:59:14.356 Cambios en las conexiones ALSA.
>> Cannot connect to server socket err = No existe el fichero o el
>> directorio
>> Cannot connect to server request channel
>> jack server is not running or cannot be started
>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
>> skipping unlock
>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
>> skipping unlock
>> 20:59:31.365 JACK está iniciándose...
>> 20:59:31.366 /usr/bin/jackd -v -dalsa -r48000 -p512 -n2 -Xseq -D
>> -Chw:PCH,0 -Phw:PCH,0
>> Cannot connect to server socket err = No existe el fichero o el
>> directorio
>> Cannot connect to server request channel
>> jack server is not running or cannot be started
>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
>> skipping unlock
>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
>> skipping unlock
>> 20:59:31.382 JACK se inició con PID=3144.
>> no message buffer overruns
>> no message buffer overruns
>> no message buffer overruns
>> jackdmp 1.9.12
>> Copyright 2001-2005 Paul Davis and others.
>> Copyright 2004-2016 Grame.
>> Copyright 2016-2017 Filipe Coelho.
>> jackdmp comes with ABSOLUTELY NO WARRANTY
>> This is free software, and you are welcome to redistribute it
>> under certain conditions; see the file COPYING for details
>> JACK server starting in realtime mode with priority 10
>> self-connect-mode is "Don't restrict self connect requests"
>> Jack: JackPosixThread::StartImp : create non RT thread
>> Jack: JackPosixThread::ThreadHandler : start
>> Jack: capture device hw:PCH,0
>> Jack: playback device hw:PCH,0
>> Jack: apparent rate = 48000
>> Jack: frames per period = 512
>> Jack: JackDriver::Open capture_driver_name = hw:PCH,0
>> Jack: JackDriver::Open playback_driver_name = hw:PCH,0
>> Jack: Check protocol client = 8 server = 8
>> Jack: JackEngine::ClientInternalOpen: name = system
>> Jack: JackEngine::AllocateRefNum ref = 0
>> Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val =
>> 0
>> Jack: JackEngine::NotifyAddClient: name = system
>> Jack: JackGraphManager::SetBufferSize size = 512
>> Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0
>> Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
>> Jack: JackDriver::SetupDriverSync driver sem in flush mode
>> audio_reservation_init
>> Acquire audio card Audio0
>> creating alsa driver ...
>> hw:PCH,0|hw:PCH,0|512|2|48000|0|0|nomon|swmeter|-|32bit
>> ATTENTION: The playback device "hw:PCH,0" is already in use. Please
>> stop the application using it and run JACK again
>> Jack: JackDriver::Close
>> Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 =
0
>> Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
>> Jack: JackEngine::ClientInternalClose ref = 0
>> Jack: JackEngine::ClientCloseAux ref = 0
>> Jack: JackGraphManager::RemoveAllPorts ref = 0
>> Released audio card Audio0
>> audio_reservation_finish
>> Jack: ~JackDriver
>> Cannot initialize driver
>> Jack: no message buffer overruns
>> Jack: JackPosixThread::Stop
>> Jack: JackPosixThread::ThreadHandler : exit
>> JackServer::Open failed with -1
>> Jack: Succeeded in unlocking 82280346 byte memory area
>> Jack: JackShmMem::delete size = 0 index = 0
>> Jack: ~JackDriver
>> Jack: Succeeded in unlocking 1187 byte memory area
>> Jack: JackShmMem::delete size = 0 index = 1
>> Jack: Cleaning up shared memory
>> Jack: Cleaning up files
>> Jack: Unregistering server `default'
>> Failed to open server
>> 20:59:31.602 JACK ha sido detenido
>> 20:59:33.455 No puede conectarse al servidor JACK como cliente. - La
>> operación global falló. - No puede conectarse al servidor. Por favor
>> revise la ventana de mensajes para mas información.
>> Cannot connect to server socket err = No existe el fichero o el
>> directorio
>> Cannot connect to server request channel
>> jack server is not running or cannot be started
>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
>> skipping unlock
>> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
>> skipping unlock
>>
>> Thanks a lot!
>>
>> [1] http://forums.debian.net/viewtopic.php?f=6&t=39116#p246951
>> [2] https://wiki.debian.org/ALSA#Loading_modules
>>
>
> I guess I should have added:
>
> $ aplay -l
> **** List of PLAYBACK Hardware Devices ****
> card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
> Subdevices: 0/1
> Subdevice #0: subdevice #0
> card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
>
> Thanks a lot in advance.
>
Maybe relevant:
This produces sound correctly:
$ aplay -vv -D sysdefault:CARD=PCH /usr/share/sounds/alsa/Noise.wav
But this not, even as sudo (and the error is similar to JACK one):
$ aplay -vv -D front:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav
aplay: main:830: audio open error: Device or resource bussy
This is the complete list:
$ aplay -L
default
Playback/recording through the PulseAudio sound server
surround21
2.1 Surround output to Front and Subwoofer speakers
surround40
4.0 Surround output to Front and Rear speakers
surround41
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50
5.0 Surround output to Front, Center and Rear speakers
surround51
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
null
Discard all samples (playback) or generate zero samples (capture)
lavrate
Rate Converter Plugin Using Libav/FFmpeg Library
samplerate
Rate Converter Plugin Using Samplerate Library
speexrate
Rate Converter Plugin Using Speex Resampler
jack
JACK Audio Connection Kit
oss
Open Sound System
pulse
PulseAudio Sound Server
upmix
Plugin for channel upmix (4,6,8)
vdownmix
Plugin for channel downmix (stereo) with a simple spacialization
sysdefault:CARD=PCH
HDA Intel PCH, CX20590 Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, CX20590 Analog
Front speakers
surround21:CARD=PCH,DEV=0
HDA Intel PCH, CX20590 Analog
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, CX20590 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, CX20590 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, CX20590 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, CX20590 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, CX20590 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
hdmi:CARD=PCH,DEV=0
HDA Intel PCH, HDMI 0
HDMI Audio Output
hdmi:CARD=PCH,DEV=1
HDA Intel PCH, HDMI 1
HDMI Audio Output
hdmi:CARD=PCH,DEV=2
HDA Intel PCH, HDMI 2
HDMI Audio Output
dmix:CARD=PCH,DEV=0
HDA Intel PCH, CX20590 Analog
Direct sample mixing device
dmix:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct sample mixing device
dmix:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct sample mixing device
dmix:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct sample mixing device
dsnoop:CARD=PCH,DEV=0
HDA Intel PCH, CX20590 Analog
Direct sample snooping device
dsnoop:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct sample snooping device
dsnoop:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct sample snooping device
dsnoop:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct sample snooping device
hw:CARD=PCH,DEV=0
HDA Intel PCH, CX20590 Analog
Direct hardware device without any conversions
hw:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct hardware device without any conversions
hw:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct hardware device without any conversions
hw:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct hardware device without any conversions
plughw:CARD=PCH,DEV=0
HDA Intel PCH, CX20590 Analog
Hardware device with all software conversions
plughw:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Hardware device with all software conversions
plughw:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Hardware device with all software conversions
plughw:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Hardware device with all software conversions
usbstream:CARD=PCH
HDA Intel PCH
USB Stream Output
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2020-04-12 10:50 +0200 |
| Message-ID | <zUGts-7wd-7@gated-at.bofh.it> |
| In reply to | #221248 |
riveravaldez wrote: > But this not, even as sudo (and the error is similar to JACK one): > $ aplay -vv -D front:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav > aplay: main:830: audio open error: Device or resource bussy aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav read this https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture you should know what you are doing
[toc] | [prev] | [next] | [standalone]
| From | riveravaldez <riveravaldezmail@gmail.com> |
|---|---|
| Date | 2020-04-12 16:50 +0200 |
| Message-ID | <zUM5P-2vR-9@gated-at.bofh.it> |
| In reply to | #221264 |
On 4/12/20, deloptes <deloptes@gmail.com> wrote: > riveravaldez wrote: > >> But this not, even as sudo (and the error is similar to JACK one): >> $ aplay -vv -D front:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav >> aplay: main:830: audio open error: Device or resource bussy > > aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav Problem persists, no sound: $ aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav aplay: main:830: audio open error: Device or resource busy > read this > https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture I'll check it again. > > you should know what you are doing Yes, that's the idea. Any help? Thanks!
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-04-12 10:20 +0200 |
| Message-ID | <zUG0q-7mm-9@gated-at.bofh.it> |
| In reply to | #221242 |
[Multipart message — attachments visible in raw view] — view raw
On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: > > Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo > speaker-test -c2' works flawlessly. (The idea to check that came from > [1].) Any error message? Is your user a member of group 'audio'? Some program might be blocking the sound card, check also the output of 'lsof | grep /dev/snd' (as root). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | riveravaldez <riveravaldezmail@gmail.com> |
|---|---|
| Date | 2020-04-12 16:50 +0200 |
| Message-ID | <zUM5Q-2vR-21@gated-at.bofh.it> |
| In reply to | #221259 |
On 4/12/20, Andrei POPESCU <andreimpopescu@gmail.com> wrote:
> On Sb, 11 apr 20, 21:02:39, riveravaldez wrote:
>>
>> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo
>> speaker-test -c2' works flawlessly. (The idea to check that came from
>> [1].)
>
> Any error message? Is your user a member of group 'audio'?
>
> Some program might be blocking the sound card, check also the output of
> 'lsof | grep /dev/snd' (as root).
>
> Kind regards,
> Andrei
Thanks a lot for your answer and help, Andrei.
I've got these:
$ groups
thinkpad cdrom floppy sudo audio dip video plugdev netdev
$ speaker-test -c2 [Still not sound.]
speaker-test 1.2.2
Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 96 to 1048576
Period size range from 32 to 349526
Using max buffer size 1048576
Periods = 4
was set period_size = 262144
was set buffer_size = 1048576
0 - Front Left
1 - Front Right
Time per period = 12,314270
0 - Front Left
1 - Front Right
^CTime per period = 12,317682
$ sudo speaker-test -c2 [Sounds OK.]
speaker-test 1.2.2
Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 2048 to 16384
Period size range from 1024 to 1024
Using max buffer size 16384
Periods = 4
was set period_size = 1024
was set buffer_size = 16384
0 - Front Left
1 - Front Right
Time per period = 5,644667
0 - Front Left
^CWrite error: -4,Llamada al sistema interrumpida
xrun_recovery failed: -4,Llamada al sistema interrumpida
Transfer failed: Llamada al sistema interrumpida
[System is in Spanish, last lines mean, 'Interrupted system-call'.]
$ sudo lsof | grep /dev/snd/
timidity 644 timidity mem CHR
116,2 13463 /dev/snd/pcmC0D0p
timidity 644 timidity 3r CHR
116,33 0t0 12547 /dev/snd/timer
timidity 644 timidity 4u CHR
116,2 0t0 13463 /dev/snd/pcmC0D0p
timidity 644 timidity 5u CHR
116,9 0t0 13479 /dev/snd/controlC0
timidity 644 timidity 6u CHR
116,1 0t0 12548 /dev/snd/seq
alsamixer 2150 thinkpad 3u CHR
116,9 0t0 13479 /dev/snd/controlC0
Maybe a timidity configuration issue?
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-04-12 17:30 +0200 |
| Message-ID | <zUMIy-2YD-1@gated-at.bofh.it> |
| In reply to | #221314 |
[Multipart message — attachments visible in raw view] — view raw
On Du, 12 apr 20, 11:39:52, riveravaldez wrote: > > $ groups > thinkpad cdrom floppy sudo audio dip video plugdev netdev Ok. > $ speaker-test -c2 [Still not sound.] And no error... > $ sudo speaker-test -c2 [Sounds OK.] That would indicate that sound is handled differently for the regular user (e.g. via pulseaudio) vs. the root user. This could be either pulseaudio or an .asoundrc (do you have one in your home directory?). Try this as user: pasuspender -- speaker-test -c2 > $ sudo lsof | grep /dev/snd/ > timidity 644 timidity mem CHR > 116,2 13463 /dev/snd/pcmC0D0p > timidity 644 timidity 3r CHR > 116,33 0t0 12547 /dev/snd/timer > timidity 644 timidity 4u CHR > 116,2 0t0 13463 /dev/snd/pcmC0D0p > timidity 644 timidity 5u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > timidity 644 timidity 6u CHR > 116,1 0t0 12548 /dev/snd/seq > alsamixer 2150 thinkpad 3u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > > Maybe a timidity configuration issue? Try stopping / disabling it and see if that helps. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | riveravaldez <riveravaldezmail@gmail.com> |
|---|---|
| Date | 2020-04-12 18:00 +0200 |
| Message-ID | <zUNbz-390-3@gated-at.bofh.it> |
| In reply to | #221314 |
On 4/12/20, riveravaldez <riveravaldezmail@gmail.com> wrote: > On 4/12/20, Andrei POPESCU <andreimpopescu@gmail.com> wrote: >> On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: >>> >>> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo >>> speaker-test -c2' works flawlessly. (The idea to check that came from >>> [1].) >> >> Some program might be blocking the sound card, check also the output of >> 'lsof | grep /dev/snd' (as root). >> >> Kind regards, >> Andrei > > Thanks a lot for your answer and help, Andrei. > I've got these: > > $ sudo lsof | grep /dev/snd/ > timidity 644 timidity mem CHR > 116,2 13463 /dev/snd/pcmC0D0p > timidity 644 timidity 3r CHR > 116,33 0t0 12547 /dev/snd/timer > timidity 644 timidity 4u CHR > 116,2 0t0 13463 /dev/snd/pcmC0D0p > timidity 644 timidity 5u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > timidity 644 timidity 6u CHR > 116,1 0t0 12548 /dev/snd/seq > alsamixer 2150 thinkpad 3u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > > Maybe a timidity configuration issue? Oh, mother-bugger... Problem - practically - solved. I did: $ sudo apt-get purge timidity Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Los siguientes paquetes se ELIMINARÁN: timidity* timidity-daemon* 0 actualizados, 0 nuevos se instalarán, 2 para eliminar y 9 no actualizados. Se liberarán 1.655 kB después de esta operación. ¿Desea continuar? [S/n] (Leyendo la base de datos ... 123466 ficheros o directorios instalados actualmente.) Desinstalando timidity-daemon (2.14.0-8) ... Desinstalando timidity (2.14.0-8) ... Procesando disparadores para mime-support (3.64) ... Procesando disparadores para man-db (2.9.1-1) ... Procesando disparadores para desktop-file-utils (0.24-1) ... (Leyendo la base de datos ... 123413 ficheros o directorios instalados actualmente.) Purgando ficheros de configuración de timidity-daemon (2.14.0-8) ... Purgando ficheros de configuración de timidity (2.14.0-8) ... Procesando disparadores para systemd (244.3-1) ... And everything came to work. Pavucontrol shows the devices, streams and configurations. All media-players (audacious, mplayer, firefox, audacity, etc.) work with default audio configuration, and even JACK is working flawlessly. In fact, tested JACK (qjackctl) with qsynt and vmpk and everything worked fine (maybe I don't even need timidity at all?). And then - testing if could reinstall - found the cause of the problem: $ sudo apt-get install timidity Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Paquetes sugeridos: fluid-soundfont-gs pmidi timidity-daemon Se instalarán los siguientes paquetes NUEVOS: timidity 0 actualizados, 1 nuevos se instalarán, 0 para eliminar y 9 no actualizados. Se necesita descargar 0 B/627 kB de archivos. Se utilizarán 1.582 kB de espacio de disco adicional después de esta operación. Obteniendo informes de fallo... Finalizado Analizando información Encontrada/Corregida... Finalizado Fallos critical del paquete timidity (→ 2.14.0-8) <Pendientes> b1 - #901148 - timidity: upgrading to 2.14.0-2 broke sound via pulseaudio Fusionado con: 902330 904652 918522 Resumen: timidity(1 fallo) ¿Está seguro de que desea instalar/actualizar los paquetes mostrados anteriormente? [Y/n/?/...] n ************************************************************* ****** Saliendo con error para detener la instalación. ****** ************************************************************* E: El subproceso /usr/bin/apt-listbugs apt devolvió un código de error (10) E: Failure running script /usr/bin/apt-listbugs apt Don't know how that passed without me noticing it... Last messages from: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901148#147 > After many tests I have found the solution about the > bugs around timidity-daemon and pulseaudio. > > timidity-daemon installs an system-wide daemon. But > pulseaudio is a user-wide "daemon". I guess that explains the 'sudo works, non-sudo non-works'? > With my appended patch the system-wide daemon will be > removed and a xdg/autostart script will be installed. > > After that timidity together with pulseaudio runs > perfectly. > Now I have made new Debian packages for buster and testing > including my patch: That last's from 20 Feb 2020, maybe still not uploaded? Should I mark this as 'SOLVED' in some manner? Thanks a lot for everything. Andrei, you saved me. ^_^ (!)
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2020-04-12 21:40 +0200 |
| Message-ID | <zUQCt-5kr-9@gated-at.bofh.it> |
| In reply to | #221332 |
riveravaldez wrote: > On 4/12/20, riveravaldez <riveravaldezmail@gmail.com> wrote: >> On 4/12/20, Andrei POPESCU <andreimpopescu@gmail.com> wrote: >>> On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: >>>> >>>> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo >>>> speaker-test -c2' works flawlessly. (The idea to check that came from >>>> [1].) >>> >>> Some program might be blocking the sound card, check also the output of >>> 'lsof | grep /dev/snd' (as root). >>> >>> Kind regards, >>> Andrei >> >> Thanks a lot for your answer and help, Andrei. >> I've got these: >> >> $ sudo lsof | grep /dev/snd/ >> timidity 644 timidity mem CHR >> 116,2 13463 /dev/snd/pcmC0D0p >> timidity 644 timidity 3r CHR >> 116,33 0t0 12547 /dev/snd/timer >> timidity 644 timidity 4u CHR >> 116,2 0t0 13463 /dev/snd/pcmC0D0p >> timidity 644 timidity 5u CHR >> 116,9 0t0 13479 /dev/snd/controlC0 >> timidity 644 timidity 6u CHR >> 116,1 0t0 12548 /dev/snd/seq >> alsamixer 2150 thinkpad 3u CHR >> 116,9 0t0 13479 /dev/snd/controlC0 >> >> Maybe a timidity configuration issue? > > Oh, mother-bugger... Problem - practically - solved. > IT is known issue with timidity. I did not know that sound can be played via root account though. We learned a bit more.
[toc] | [prev] | [next] | [standalone]
| From | Florent Rougon <f.rougon@free.fr> |
|---|---|
| Date | 2020-04-13 15:10 +0200 |
| Message-ID | <zV70C-77O-7@gated-at.bofh.it> |
| In reply to | #221350 |
Hi, For the record, I had the exact same problem on a computer running buster that I don't use very often. For sure, it was working fine even with timidity installed a few months ago. Many thanks to Andrei for the 'lsof | grep /dev/snd' command that pointed us in the right direction! Debugging these sound issues that appear spontaneously on a previously-working setup is not easy, especially now that PulseAudio is required everywhere. Regards -- Florent
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web