Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Can't get sound to work
85 views
Skip to first unread message
Daniel Haude
Jan 15, 2015, 3:40:04 PM1/15/15
to
Hi all,
this is my umptieth Debian installation I've done on various PCs over
the years, but this time the sound setup really has me stumped. I can't
hear anything unless I use aplay with -D hw:0,0 but setting that in the
configuration file doesn't help. No other sound-outputting program
works. Here's a shell excerpt:
bl@dotcom:~$ aplay test.wav # can't hear nothing
bl@dotcom:~$ aplay -D hw:0,0 test.wav # this plays sound
bl@dotcom:~$ cat .asoundrc
cat: .asoundrc: No such file or directory
bl@dotcom:~$ cat /etc/asound.conf
pcm.!default {
type hw
card 0
device 0
}
bl@dotcom:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD1984 Analog [AD1984 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 2: AD1984 Alt Analog [AD1984 Alt
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
bl@dotcom:~$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xfe9dc000 irq 45
bl@dotcom:~$
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20150115212...@dotcom.mfs32
this is my umptieth Debian installation I've done on various PCs over
the years, but this time the sound setup really has me stumped. I can't
hear anything unless I use aplay with -D hw:0,0 but setting that in the
configuration file doesn't help. No other sound-outputting program
works. Here's a shell excerpt:
bl@dotcom:~$ aplay test.wav # can't hear nothing
bl@dotcom:~$ aplay -D hw:0,0 test.wav # this plays sound
bl@dotcom:~$ cat .asoundrc
cat: .asoundrc: No such file or directory
bl@dotcom:~$ cat /etc/asound.conf
pcm.!default {
type hw
card 0
device 0
}
bl@dotcom:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD1984 Analog [AD1984 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 2: AD1984 Alt Analog [AD1984 Alt
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
bl@dotcom:~$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xfe9dc000 irq 45
bl@dotcom:~$
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20150115212...@dotcom.mfs32
Robert Latest
Jan 15, 2015, 3:50:05 PM1/15/15
to
Hans
Jan 15, 2015, 4:00:06 PM1/15/15
to
First questions:
Are you running pulseaudio or alsa?
Did you try alsamixer?
Often it is possible, to choose different hardware in the GUI. Did you try
other ones, too?
Best
Hans
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/3539974.jClRHfbk25@protheus2
Are you running pulseaudio or alsa?
Did you try alsamixer?
Often it is possible, to choose different hardware in the GUI. Did you try
other ones, too?
Best
Hans
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ric Moore
Jan 15, 2015, 7:50:05 PM1/15/15
to
On 01/15/2015 03:54 PM, Hans wrote:
> First questions:
>
> Are you running pulseaudio or alsa?
>
> Did you try alsamixer?
>
> Often it is possible, to choose different hardware in the GUI. Did you try
> other ones, too?
>
> Best
He's got an asoundrc file in /etc. I thought that use was deprecated
> First questions:
>
> Are you running pulseaudio or alsa?
>
> Did you try alsamixer?
>
> Often it is possible, to choose different hardware in the GUI. Did you try
> other ones, too?
>
> Best
some years ago. Maybe if the OP mv;d that file to another name, rebooted
and ran alsamixer first, then add pavucontrol along with pulse, he might
have a better experience, IMHO. I happen to love using pulse, although
years ago I was spitting mad at it. Works a charm for me now, especially
when using different sound inputs/outputs on the fly. Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Charlie
Jan 16, 2015, 12:50:04 AM1/16/15
to
On Thu, 15 Jan 2015 21:21:55 +0100 Daniel Haude sent:
Much the same here. Sound has always been a bit of a mystery in Debian
for me ever since Sarge.
This is a Jessie system.
The time I got it working, I think in Squeeze? Florian Kulzer had me
debugging things with the commands below and managed to see what the
problem was.
Interestingly I had sound working with alsa before one of the upgrades
recently. But I don't use sound all that often, so have no idea when it
was lost.Installed and tried with pulseaudio, It said that the devices
were locked, so have purged that again now.
I have not been able to see from the commands results of the commands
that Florian supplied how I can get my sound working.
Here are my results and those commands, you might compare and if you
have much the same results we will know we both have the same problem:
$ lspci
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Wrestler [Radeon HD 7310]
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler
HDMI Audio
$ cat /dev/sndstat
[ALC269VB Analog]
snd_hda_codec_realtek 63031 1
snd_hda_codec_hdmi 45118 1
snd_hda_codec_generic 63107 1 snd_hda_codec_realtek
snd_hda_intel 26327 5
snd_hda_controller 26727 1 snd_hda_intel
snd_hda_codec 104463 5
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,
snd_hda_controller
snd_hwdep 13148 1 snd_hda_codec
snd_pcm 88662 4
snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
snd_timer 26614 1 snd_pcm
snd 65244 18
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,
snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
soundcore 13026 2 snd,snd_hda_codec
$ cat /proc/asound/cards
0 [Generic ]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xf0444000 irq 46
1 [Generic_1 ]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xf0440000 irq 47
$ udevadm trigger --verbose --subsystem-match=sound
/sys/devices/pci0000:00/0000:00:01.1/sound/card0
/sys/devices/pci0000:00/0000:00:01.1/sound/card0/hdaudioC0D0
/sys/devices/pci0000:00/0000:00:01.1/sound/card0/hdaudioC0D0/hwC0D0
/sys/devices/pci0000:00/0000:00:01.1/sound/card0/hdaudioC0D0/pcmC0D3p
/sys/devices/pci0000:00/0000:00:01.1/sound/card0/controlC0
/sys/devices/pci0000:00/0000:00:14.2/sound/card1
/sys/devices/pci0000:00/0000:00:14.2/sound/card1/hdaudioC1D0
/sys/devices/pci0000:00/0000:00:14.2/sound/card1/hdaudioC1D0/hwC1D0
/sys/devices/pci0000:00/0000:00:14.2/sound/card1/hdaudioC1D0/pcmC1D0c
/sys/devices/pci0000:00/0000:00:14.2/sound/card1/hdaudioC1D0/pcmC1D0p
/sys/devices/pci0000:00/0000:00:14.2/sound/card1/controlC1
/sys/devices/virtual/sound/timer
$ speaker-test -t sine -c 2
No sound is heard.
$ amixer
Simple mixer control 'PCM',0
Capabilities: pvolume
Playback channels: Front Left - Front Right
Limits: Playback 0 - 255
Mono:
Front Left: Playback 255 [100%] [0.00dB]
Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Simple mixer control 'Digital',0
Capabilities: cvolume
Capture channels: Front Left - Front Right
Limits: Capture 0 - 120
Front Left: Capture 60 [50%] [0.00dB]
Front Right: Capture 60 [50%] [0.00dB]
Alsamixergui only shows 3 sliders:
PCM - right to the top
IEC958 - empty
Digital - half way up
All locks open.
$ lsof +c0 $(find /dev/ -group audio)
Returns no results, unless I have alsmixergui on, then it shows that:
$ lsof +c0 $(find /dev/ -group audio)
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
alsamixergui 5474 charlie 3u CHR 116,2 0t0
10941 /dev/snd/controlC0
Be well,
Charlie
--
Registered Linux User:- 329524
***********************************************
In three words I can sum up everything I've learned about life.
It goes on. ...............Robert Frost
***********************************************
Debian GNU/Linux - just the best way to create magic
-----------------------------------------------------
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20150116164405.003b298e@taogypsy
for me ever since Sarge.
This is a Jessie system.
The time I got it working, I think in Squeeze? Florian Kulzer had me
debugging things with the commands below and managed to see what the
problem was.
Interestingly I had sound working with alsa before one of the upgrades
recently. But I don't use sound all that often, so have no idea when it
was lost.Installed and tried with pulseaudio, It said that the devices
were locked, so have purged that again now.
I have not been able to see from the commands results of the commands
that Florian supplied how I can get my sound working.
Here are my results and those commands, you might compare and if you
have much the same results we will know we both have the same problem:
$ lspci
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Wrestler [Radeon HD 7310]
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler
HDMI Audio
$ cat /dev/sndstat
No such file or directory
~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
**** List of PLAYBACK Hardware Devices ****
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 0: ALC269VB Analog
Subdevice #0: subdevice #0
[ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
$ lsmod | grep snd
Subdevice #0: subdevice #0
snd_hda_codec_realtek 63031 1
snd_hda_codec_hdmi 45118 1
snd_hda_codec_generic 63107 1 snd_hda_codec_realtek
snd_hda_intel 26327 5
snd_hda_controller 26727 1 snd_hda_intel
snd_hda_codec 104463 5
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,
snd_hda_controller
snd_hwdep 13148 1 snd_hda_codec
snd_pcm 88662 4
snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
snd_timer 26614 1 snd_pcm
snd 65244 18
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,
snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
soundcore 13026 2 snd,snd_hda_codec
$ cat /proc/asound/cards
0 [Generic ]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xf0444000 irq 46
1 [Generic_1 ]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xf0440000 irq 47
$ udevadm trigger --verbose --subsystem-match=sound
/sys/devices/pci0000:00/0000:00:01.1/sound/card0
/sys/devices/pci0000:00/0000:00:01.1/sound/card0/hdaudioC0D0
/sys/devices/pci0000:00/0000:00:01.1/sound/card0/hdaudioC0D0/hwC0D0
/sys/devices/pci0000:00/0000:00:01.1/sound/card0/hdaudioC0D0/pcmC0D3p
/sys/devices/pci0000:00/0000:00:01.1/sound/card0/controlC0
/sys/devices/pci0000:00/0000:00:14.2/sound/card1
/sys/devices/pci0000:00/0000:00:14.2/sound/card1/hdaudioC1D0
/sys/devices/pci0000:00/0000:00:14.2/sound/card1/hdaudioC1D0/hwC1D0
/sys/devices/pci0000:00/0000:00:14.2/sound/card1/hdaudioC1D0/pcmC1D0c
/sys/devices/pci0000:00/0000:00:14.2/sound/card1/hdaudioC1D0/pcmC1D0p
/sys/devices/pci0000:00/0000:00:14.2/sound/card1/controlC1
/sys/devices/virtual/sound/timer
$ speaker-test -t sine -c 2
No sound is heard.
$ amixer
Simple mixer control 'PCM',0
Capabilities: pvolume
Playback channels: Front Left - Front Right
Limits: Playback 0 - 255
Mono:
Front Left: Playback 255 [100%] [0.00dB]
Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
Simple mixer control 'Digital',0
Capabilities: cvolume
Capture channels: Front Left - Front Right
Limits: Capture 0 - 120
Front Left: Capture 60 [50%] [0.00dB]
Front Right: Capture 60 [50%] [0.00dB]
Alsamixergui only shows 3 sliders:
PCM - right to the top
IEC958 - empty
Digital - half way up
All locks open.
$ lsof +c0 $(find /dev/ -group audio)
Returns no results, unless I have alsmixergui on, then it shows that:
$ lsof +c0 $(find /dev/ -group audio)
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
alsamixergui 5474 charlie 3u CHR 116,2 0t0
10941 /dev/snd/controlC0
Be well,
Charlie
--
Registered Linux User:- 329524
***********************************************
In three words I can sum up everything I've learned about life.
It goes on. ...............Robert Frost
***********************************************
Debian GNU/Linux - just the best way to create magic
-----------------------------------------------------
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
August Karlstrom
Jan 16, 2015, 3:30:05 AM1/16/15
to
On 2015-01-15 21:40, Daniel Haude wrote:
> Hi all,
>
> this is my umptieth Debian installation I've done on various PCs over
> the years, but this time the sound setup really has me stumped. I can't
> hear anything unless I use aplay with -D hw:0,0 but setting that in the
> configuration file doesn't help. No other sound-outputting program
> works. Here's a shell excerpt:
>
> bl@dotcom:~$ aplay test.wav # can't hear nothing
> bl@dotcom:~$ aplay -D hw:0,0 test.wav # this plays sound
> bl@dotcom:~$ cat .asoundrc
> cat: .asoundrc: No such file or directory
> bl@dotcom:~$ cat /etc/asound.conf
> pcm.!default {
> type hw
> card 0
> device 0
> }
What happens if you remove /etc/asound.conf?
> Hi all,
>
> this is my umptieth Debian installation I've done on various PCs over
> the years, but this time the sound setup really has me stumped. I can't
> hear anything unless I use aplay with -D hw:0,0 but setting that in the
> configuration file doesn't help. No other sound-outputting program
> works. Here's a shell excerpt:
>
> bl@dotcom:~$ aplay test.wav # can't hear nothing
> bl@dotcom:~$ aplay -D hw:0,0 test.wav # this plays sound
> bl@dotcom:~$ cat .asoundrc
> cat: .asoundrc: No such file or directory
> bl@dotcom:~$ cat /etc/asound.conf
> pcm.!default {
> type hw
> card 0
> device 0
> }
-- August
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Frédéric Marchal
Jan 16, 2015, 3:50:03 AM1/16/15
to
to investigate it.
Running aplay test.wav produces no sound.
The output of aplay -l is:
**** List of PLAYBACK Hardware Devices ****
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI_1 [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
Subdevice #0: subdevice #0
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI_1 [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
Subdevice #0: subdevice #0
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: 92HD91BXX Analog [92HD91BXX Analog]
Subdevice #0: subdevice #0
Subdevices: 1/1
Subdevice #0: subdevice #0
Running aplay -D hw:1,0 test.wav reports an error and produces no sound:
Subdevice #0: subdevice #0
Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 11025 Hz, Mono
aplay: set_params:1087: Channels count non available
But sound started to work fine after I edited $HOME/.asoundrc like this:
pcm.!default {
type plug
slave {
pcm "hw:1,0"
}
}
ctl.!default {
type hw
card 1
}
The symptoms are not the same as yours. aplay doesn't play sound when I select
the PCM device on the command line. But, with audacity, if I explicitly select
ALSA as output and device hw:1,0, sound comes out. So, I may have another
problem that prevents aplay from running when the PCM device is specified and
the above solution may still help you.
BTW, I have pulseaudio installed in case it matters.
Frederic
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Lisi Reisz
Jan 16, 2015, 4:40:05 AM1/16/15
to
Lisi
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Frédéric Marchal
Jan 16, 2015, 6:00:05 AM1/16/15
to
I don't know what's the purpose of pulseaudio nor what are the benefits of
having installed it. I don't know if it would break something to remove it.
I believe it was installed at some point as part of a routine system update
and may have been the cause of the sound failure in the first place.
Frederic
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Robert Latest
Jan 16, 2015, 1:50:04 PM1/16/15
to
On Thu, 15 Jan 2015 19:43:23 -0500
Ric Moore <waywa...@gmail.com> wrote:
> On 01/15/2015 03:54 PM, Hans wrote:
> > First questions:
> >
> > Are you running pulseaudio or alsa?
I don't know. I seem to have both on my system. I don't know what the
Ric Moore <waywa...@gmail.com> wrote:
> On 01/15/2015 03:54 PM, Hans wrote:
> > First questions:
> >
> > Are you running pulseaudio or alsa?
difference is, or if one is running on top of the other, or if they are
fighting over my soundcard. How would an application that wants to play
sound figure out which system to use?
> >
> > Did you try alsamixer?
When I just run alsamixer, I see one big vertical adjustment. When I
run alsamixer -c 0 I see a lot of controls (Master, Headphone, PCM...).
Still I can't hear anything unless running aplay -D hw:0,0.
> > Often it is possible, to choose different hardware in the GUI. Did
> > you try other ones, too?
anything if I run anything but aplay -D hw:0,0 in another window.
>
> He's got an asoundrc file in /etc. I thought that use was deprecated
> some years ago.
all sound-playing software.
> Maybe if the OP mv;d that file to another name,
> rebooted and ran alsamixer first, then add pavucontrol along with
> pulse, he might have a better experience, IMHO.
ALSA-related stuff from my system? Or could I also remove all
pulse-related stuff and keep ALSA?
> I happen to love
> using pulse, although years ago I was spitting mad at it. Works a
> charm for me now, especially when using different sound
> inputs/outputs on the fly. Ric
with video content.
Thanks,
robert
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Doug
Jan 16, 2015, 2:30:05 PM1/16/15
to
On 01/16/2015 01:24 PM, Robert Latest wrote:
>> pulse, he might have a better experience, IMHO.
>
> I'll try that (have to install first). If it works, can I then purge all
> ALSA-related stuff from my system? Or could I also remove all
> pulse-related stuff and keep ALSA?
>
>> I happen to love
>> using pulse, although years ago I was spitting mad at it. Works a
>> charm for me now, especially when using different sound
>> inputs/outputs on the fly. Ric
>
> I'm not that picky. All I want is hear sound from mplayer or webpages
> with video content.
>
> Thanks,
> robert
>
>
I won't swear to it, but I think PA runs on top of Alsa, so don't remove it.
>> pulse, he might have a better experience, IMHO.
>
> I'll try that (have to install first). If it works, can I then purge all
> ALSA-related stuff from my system? Or could I also remove all
> pulse-related stuff and keep ALSA?
>
>> I happen to love
>> using pulse, although years ago I was spitting mad at it. Works a
>> charm for me now, especially when using different sound
>> inputs/outputs on the fly. Ric
>
> I'm not that picky. All I want is hear sound from mplayer or webpages
> with video content.
>
> Thanks,
> robert
>
>
Even if that is not the case, they are compatible--i.e., Alsa will not
interfere with PA.
For years I swore at PA and always removed it, but in the last year or so,
it is working, and has some features you can't get anywhere else, like being
able to output sound from two sound cards at once, so as to send sound along
with video to your TV, while still hearing it locally at your computer.
If all else fails, you can remove pulse and keep Alsa, but I wouldn't try it
the other way round.
--doug
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Mike McGinn
Jan 16, 2015, 2:40:04 PM1/16/15
to
On Friday, January 16, 2015 14:23:21 Doug wrote:
> On 01/16/2015 01:24 PM, Robert Latest wrote:
it after an hour of troubleshooting.
--
Mike McGinn KD2CNU
Be happy that brainfarts don't smell.
No electrons were harmed in sending this message, some were inconvenienced.
** Registered Linux User 377849
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Robert Latest
Jan 16, 2015, 3:20:05 PM1/16/15
to
> On 01/15/2015 03:54 PM, Hans wrote:
> > First questions:
> >
> > Are you running pulseaudio or alsa?
> >
> > Did you try alsamixer?
> >
> > Often it is possible, to choose different hardware in the GUI. Did
> > you try other ones, too?
> >
> > Best
>
> He's got an asoundrc file in /etc. I thought that use was deprecated
> some years ago. Maybe if the OP mv;d that file to another name,
> rebooted and ran alsamixer first, then add pavucontrol along with
> pulse, he might have a better experience, IMHO.
Hi Ric,
> > First questions:
> >
> > Are you running pulseaudio or alsa?
> >
> > Did you try alsamixer?
> >
> > Often it is possible, to choose different hardware in the GUI. Did
> > you try other ones, too?
> >
> > Best
>
> He's got an asoundrc file in /etc. I thought that use was deprecated
> some years ago. Maybe if the OP mv;d that file to another name,
> rebooted and ran alsamixer first, then add pavucontrol along with
> pulse, he might have a better experience, IMHO.
it's getting weirder: I installed pavucontrol, started it, and started
mplayer in some other window. No sound on my headphones, but the
little VU bar flashing. Unplugged headphones, sound came from the built
in speaker. Plugged headphones back in, pavucontrol sees it and changes
from "unplugged" tp "plugged in", still no sound on headphones.
With aplay -D hw:0,0 it still works.
OK, now trying to remove all pulse-related stuff.
Thanks
robert
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ric Moore
Jan 16, 2015, 3:40:04 PM1/16/15
to
On 01/16/2015 03:41 AM, Frédéric Marchal wrote:
> BTW, I have pulseaudio installed in case it matters.
>
> Frederic
Once you start with the edits, pulse most likely will not work since you
> BTW, I have pulseaudio installed in case it matters.
>
> Frederic
defeated it's purpose to define things after alsa is doing it's job. I
remember the bad old days when you had to do that and even then it
didn't work half the time. Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/54B975AB...@gmail.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ric Moore
Jan 16, 2015, 3:50:04 PM1/16/15
to
On 01/16/2015 04:33 AM, Lisi Reisz wrote:
<snippage>
to direct your sound sources where you want them to be, as in multiple
sound devices, speakers and microphones. You can do this on the fly, as
in switching between 7.1 to USB head phones for quiet listening. :) Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256
<snippage>
>>
>> The symptoms are not the same as yours. aplay doesn't play sound when I
>> select the PCM device on the command line. But, with audacity, if I
>> explicitly select ALSA as output and device hw:1,0, sound comes out. So, I
>> may have another problem that prevents aplay from running when the PCM
>> device is specified and the above solution may still help you.
>>
>> BTW, I have pulseaudio installed in case it matters.
>
> So the advice is to have alsa and pulseaudio?
You have to have alsa. That is the sound system. Pulse sits on top of it
>> The symptoms are not the same as yours. aplay doesn't play sound when I
>> select the PCM device on the command line. But, with audacity, if I
>> explicitly select ALSA as output and device hw:1,0, sound comes out. So, I
>> may have another problem that prevents aplay from running when the PCM
>> device is specified and the above solution may still help you.
>>
>> BTW, I have pulseaudio installed in case it matters.
>
> So the advice is to have alsa and pulseaudio?
to direct your sound sources where you want them to be, as in multiple
sound devices, speakers and microphones. You can do this on the fly, as
in switching between 7.1 to USB head phones for quiet listening. :) Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/54B97700...@gmail.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
berenge...@neutralite.org
Jan 16, 2015, 4:00:05 PM1/16/15
to
Le 16.01.2015 19:24, Robert Latest a écrit :
> On Thu, 15 Jan 2015 19:43:23 -0500
> Ric Moore <waywa...@gmail.com> wrote:
>
>> On 01/15/2015 03:54 PM, Hans wrote:
>> > First questions:
>> >
>> > Are you running pulseaudio or alsa?
>
> I don't know. I seem to have both on my system. I don't know what the
> difference is, or if one is running on top of the other, or if they
> are
> fighting over my soundcard. How would an application that wants to
> play
> sound figure out which system to use?
There are several people more knowledgeable than me around here, but,
> On Thu, 15 Jan 2015 19:43:23 -0500
> Ric Moore <waywa...@gmail.com> wrote:
>
>> On 01/15/2015 03:54 PM, Hans wrote:
>> > First questions:
>> >
>> > Are you running pulseaudio or alsa?
>
> I don't know. I seem to have both on my system. I don't know what the
> difference is, or if one is running on top of the other, or if they
> are
> fighting over my soundcard. How would an application that wants to
> play
> sound figure out which system to use?
AFAIK, alsa is the lowest level sound manager.
If I am not wrong, pulse audio is built on it. Note that I never tried
PA: alsa always worked just fine for me, so why should I try it?
I understand the linux Audio stack like this:
Alsa ==> OSS
^
|
^
/ \
PA J
Alsa is better (why? No idea, just what people says...) than OSS, and
then you have 2 frameworks which works over Alsa. PulseAudio (PA, which
seems to be POSIX and windows compatible), and Jack (J, which seems to
be used by professional applications, for real-time stuff and other.
If you simply want sound from flash-player, iceweasel and mplayer...
well, removing PA may help you, and it will remove something you do not
necessarily need. And, in my opinion, less code running on my computer
means less surprises (on my computer), so it's the way I choose. But, I
am a minimalist lover (well, at least in computing... for beers per
example I have different tastes ;) ).
Note that I have no opinion about the quality of pulse audio and jack.
Plus, in some cases, I had problems with microphones with Alsa. Maybe in
those situations PA or jack would have helped me. Never tried, it was
not important enough for me.
>> Maybe if the OP mv;d that file to another name,
>> rebooted and ran alsamixer first, then add pavucontrol along with
>> pulse, he might have a better experience, IMHO.
>
> I'll try that (have to install first). If it works, can I then purge
> all
> ALSA-related stuff from my system? Or could I also remove all
> pulse-related stuff and keep ALSA?
Alsa means "Advanced Linux Sound Architecture". It seems to be a driver
replacement for OSS.
In short, it would be like removing your nouveau/nvidia/intel/whatever
driver and trying to run Xorg or weston... Xorg and weston would be PA
and Jack, the driver would be alsa. That's what I understand, at least.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ric Moore
Jan 16, 2015, 4:10:04 PM1/16/15
to
On 01/16/2015 02:56 PM, Robert Latest wrote:
> On Thu, 15 Jan 2015 19:43:23 -0500
> Ric Moore <waywa...@gmail.com> wrote:
>
>> On 01/15/2015 03:54 PM, Hans wrote:
>>> First questions:
>>>
>>> Are you running pulseaudio or alsa?
>>>
>>> Did you try alsamixer?
>>>
>>> Often it is possible, to choose different hardware in the GUI. Did
>>> you try other ones, too?
>>>
>>> Best
>>
>> He's got an asoundrc file in /etc. I thought that use was deprecated
>> some years ago. Maybe if the OP mv;d that file to another name,
>> rebooted and ran alsamixer first, then add pavucontrol along with
>> pulse, he might have a better experience, IMHO.
>
> Hi Ric,
>
> it's getting weirder: I installed pavucontrol, started it, and started
> mplayer in some other window. No sound on my headphones, but the
> little VU bar flashing. Unplugged headphones, sound came from the built
> in speaker. Plugged headphones back in, pavucontrol sees it and changes
> from "unplugged" tp "plugged in", still no sound on headphones.
>
> With aplay -D hw:0,0 it still works.
>
> OK, now trying to remove all pulse-related stuff.
You're shooting yourself in the foot. IF alsa won't work, pulse will not
> On Thu, 15 Jan 2015 19:43:23 -0500
> Ric Moore <waywa...@gmail.com> wrote:
>
>> On 01/15/2015 03:54 PM, Hans wrote:
>>> First questions:
>>>
>>> Are you running pulseaudio or alsa?
>>>
>>> Did you try alsamixer?
>>>
>>> Often it is possible, to choose different hardware in the GUI. Did
>>> you try other ones, too?
>>>
>>> Best
>>
>> He's got an asoundrc file in /etc. I thought that use was deprecated
>> some years ago. Maybe if the OP mv;d that file to another name,
>> rebooted and ran alsamixer first, then add pavucontrol along with
>> pulse, he might have a better experience, IMHO.
>
> Hi Ric,
>
> it's getting weirder: I installed pavucontrol, started it, and started
> mplayer in some other window. No sound on my headphones, but the
> little VU bar flashing. Unplugged headphones, sound came from the built
> in speaker. Plugged headphones back in, pavucontrol sees it and changes
> from "unplugged" tp "plugged in", still no sound on headphones.
>
> With aplay -D hw:0,0 it still works.
>
> OK, now trying to remove all pulse-related stuff.
either. IF you used pavucontrol, set up your sound sources, then
selected playback while the file was playing, you should have seen the
volume bar twitching. If it was, did you check to see if the volume was
scrolled up to 100%, unmuted, and that the headphone was selected??
Or, is this some headphone plugged into the soundcard audio-out jack?
Maybe you're plugged into audio-out (which is non-amplified) instead of
the headphone jack, which is? OR if there is just one output jack, which
relies on some sort of hardware magic to determine if it should act like
audio-out/headphone out, there in lies the problem. PLugging in the
headphone, removing it and pugging it in, multiple times might get it to
switch correctly. They don't always work right. Get a cheap set of USB
headphones and suffer no more. Leave the sound card to drive speakers,
which worked, as you mention. That must be the problem as I had that
happen trying to plug in some earbuds. The audio-out expects the plugged
in device to have it's own amplifier. Headphone out uses the sound card
amplifier to drive a non-amplified device, like old headphones. No sound
indicates you're in the wrong jack or it fails to auto-select/switch
between the two states if there is only one out jack. I bet this is the
problem. Refer to your manual if you have it. Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/54B97D8F...@gmail.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ric Moore
Jan 16, 2015, 4:20:04 PM1/16/15
to
kernel. I leave that to the true audiophiles who need that degree of
response for mostly sound only applications. You are right, alsa is a
must have installed. Pulse will only work with a working alsa setup.
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/54B97E68...@gmail.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Joel Roth
Jan 16, 2015, 8:20:04 PM1/16/15
to
Robert Latest wrote:
> With aplay -D hw:0,0 it still works.
You're 99% to the destination.
> With aplay -D hw:0,0 it still works.
IIRC, directly addressing the sound device
as hw:0,0 takes the whole device, will not
allow software mixing of audio streams from
other applications.
It may be worth trying the
aplay -D default testfile.wav &
aplay -D default testfile.wav
And you should hear two streams playing together.
At least, it works on my system without asoundrc.
Regards,
Joel
> OK, now trying to remove all pulse-related stuff.
>
> Thanks
> robert
>
>
> --
> To UNSUBSCRIBE, email to debian-us...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
> Archive: https://lists.debian.org/20150116205...@dotcom.mfs32
>
Joel Roth
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Charlie
Jan 16, 2015, 9:30:04 PM1/16/15
to
On Fri, 16 Jan 2015 15:11:24 -1000 Joel Roth sent:
> Robert Latest wrote:
> > With aplay -D hw:0,0 it still works.
>
> You're 99% to the destination.
>
> IIRC, directly addressing the sound device
> as hw:0,0 takes the whole device, will not
> allow software mixing of audio streams from
> other applications.
>
> It may be worth trying the
>
> aplay -D default testfile.wav &
> aplay -D default testfile.wav
>
> And you should hear two streams playing together.
>
> At least, it works on my system without asoundrc.
>
> Regards,
>
> Joel
Thanks Joel,
Using: aplay -D default testfile.wav &
Without pulse audio installed, I get sound.
Using: aplay -D default testfile.wav &
With pulseaudio, there is no sound but pavucontrol shows that there is
some sound being relayed to the earphones?
So sound is still a wraith in Debian. [laughing]
Be well,
Charlie
--
Registered Linux User:- 329524
***********************************************
If anything in nature strikes you as ugly, you are not
appreciating its diversity. ...anon
***********************************************
Debian GNU/Linux - just the best way to create magic
-----------------------------------------------------
> Robert Latest wrote:
> > With aplay -D hw:0,0 it still works.
>
> You're 99% to the destination.
>
> IIRC, directly addressing the sound device
> as hw:0,0 takes the whole device, will not
> allow software mixing of audio streams from
> other applications.
>
> It may be worth trying the
>
> aplay -D default testfile.wav &
> aplay -D default testfile.wav
>
> And you should hear two streams playing together.
>
> At least, it works on my system without asoundrc.
>
> Regards,
>
> Joel
Using: aplay -D default testfile.wav &
Without pulse audio installed, I get sound.
Using: aplay -D default testfile.wav &
With pulseaudio, there is no sound but pavucontrol shows that there is
some sound being relayed to the earphones?
So sound is still a wraith in Debian. [laughing]
Be well,
Charlie
--
Registered Linux User:- 329524
***********************************************
appreciating its diversity. ...anon
***********************************************
Debian GNU/Linux - just the best way to create magic
-----------------------------------------------------
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20150117132731.4e4e4d61@taogypsy
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Joel Roth
Jan 17, 2015, 1:00:03 AM1/17/15
to
On Sat, Jan 17, 2015 at 01:27:31PM +1100, Charlie wrote:
> On Fri, 16 Jan 2015 15:11:24 -1000 Joel Roth sent:
>
> > Robert Latest wrote:
> > > With aplay -D hw:0,0 it still works.
> >
> > You're 99% to the destination.
> >
> > IIRC, directly addressing the sound device
> > as hw:0,0 takes the whole device, will not
> > allow software mixing of audio streams from
> > other applications.
> >
> > It may be worth trying the
> >
> > aplay -D default testfile.wav &
> > aplay -D default testfile.wav
> >
> > And you should hear two streams playing together.
> >
> > At least, it works on my system without asoundrc.
> >
> > Regards,
> >
> > Joel
>
> Thanks Joel,
>
> Using: aplay -D default testfile.wav &
>
> Without pulse audio installed, I get sound.
Yay.
> On Fri, 16 Jan 2015 15:11:24 -1000 Joel Roth sent:
>
> > Robert Latest wrote:
> > > With aplay -D hw:0,0 it still works.
> >
> > You're 99% to the destination.
> >
> > IIRC, directly addressing the sound device
> > as hw:0,0 takes the whole device, will not
> > allow software mixing of audio streams from
> > other applications.
> >
> > It may be worth trying the
> >
> > aplay -D default testfile.wav &
> > aplay -D default testfile.wav
> >
> > And you should hear two streams playing together.
> >
> > At least, it works on my system without asoundrc.
> >
> > Regards,
> >
> > Joel
>
> Thanks Joel,
>
> Using: aplay -D default testfile.wav &
>
> Without pulse audio installed, I get sound.
> Using: aplay -D default testfile.wav &
>
> With pulseaudio, there is no sound but pavucontrol shows that there is
> some sound being relayed to the earphones?
> So sound is still a wraith in Debian. [laughing]
soundcard. Many programs, libraries, applications, plugins,
frameworks and APIs target ALSA.[1] If you're involved in
music or audio production and need to combine audio
applications, there is JACK.
So, have a coffee and doughnut, or beer and pizza!
Now maybe you want pulse audio. Why? Because maybe some app
(Skype?) or Desktop Environment demands it.
Okay, that's a lot of bloat. But you're choosing to pull
that bloat into your software stack. Or maybe it is just
your DE packager's choice.
In any case, you can probably debug it given enough
attention. Any list responsive to pulse audio issues should
be a help.
For many audio issues, you can go to the Linux Audio Users
mailing list, but even the geniuses and gurus who frequent
that list are mostly ignorant of the dark ways of PA.
A few have found and published ways to use both JACK and
PA.[2]
For now, you do have have a working audio system sitting
atop your Intel soundcard(s).
cheers,
Joel
1. http://wiki.linuxaudio.org/apps/start
2. http://jackaudio.org/faq/pulseaudio_and_jack.html
> Be well,
> Charlie
> --
> Registered Linux User:- 329524
> ***********************************************
>
> If anything in nature strikes you as ugly, you are not
> appreciating its diversity. ...anon
>
> ***********************************************
>
> Debian GNU/Linux - just the best way to create magic
>
> -----------------------------------------------------
>
>
> --
> To UNSUBSCRIBE, email to debian-us...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
> Archive: https://lists.debian.org/20150117132731.4e4e4d61@taogypsy
>
Joel Roth
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Charlie
Jan 17, 2015, 1:20:04 AM1/17/15
to
On Fri, 16 Jan 2015 19:56:31 -1000 Joel Roth sent:
> For now, you do have have a working audio system sitting
> atop your Intel soundcard(s).
Yes thank you.
I have purged pulseaudio again. Never having used it found Alsa was
always fine till recently when alsa didn't do it for me when using VLC.
But then pulseaudio didn't either.
However alsaplayer in the GUI only plays half the song and chokes.
Aplay plays the songs fine in full, no glitch when invoked on the
command line.
VLC doesn't produce any sound. But then I can live without it.
Especially since I have discovered how to add several songs to aplay on
the commandline, takes a bit more typing the way I do it, but then
that's also fine.
It's never so bad if you know how to do something, it's just a pain
when you don't and you need to scrounge through all manner of websites
to discover how it might work, often wasted because you've looked in
the wrong place and it doesn't.
I recall reading a Linux user/developer once writing that he was almost
sick of Linux because whenever you tried to do something you had to
learn how to do it. That in Windows it just worked.
It was interesting, and I know that when I want to do something and
have to troll the net to find a way to do it because it needed a tweak,
it could be frustrating. But I always blamed myself because I made the
choice to use Debian "testing" instead of stable where I assume
everything just works?
Anyway thank you,
brag for humanity rather than for myself. ....Henry David
Thoreau
***********************************************
Debian GNU/Linux - just the best way to create magic
-----------------------------------------------------
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20150117171626.75cf67bd@taogypsy
> For now, you do have have a working audio system sitting
> atop your Intel soundcard(s).
I have purged pulseaudio again. Never having used it found Alsa was
always fine till recently when alsa didn't do it for me when using VLC.
But then pulseaudio didn't either.
However alsaplayer in the GUI only plays half the song and chokes.
Aplay plays the songs fine in full, no glitch when invoked on the
command line.
VLC doesn't produce any sound. But then I can live without it.
Especially since I have discovered how to add several songs to aplay on
the commandline, takes a bit more typing the way I do it, but then
that's also fine.
It's never so bad if you know how to do something, it's just a pain
when you don't and you need to scrounge through all manner of websites
to discover how it might work, often wasted because you've looked in
the wrong place and it doesn't.
I recall reading a Linux user/developer once writing that he was almost
sick of Linux because whenever you tried to do something you had to
learn how to do it. That in Windows it just worked.
It was interesting, and I know that when I want to do something and
have to troll the net to find a way to do it because it needed a tweak,
it could be frustrating. But I always blamed myself because I made the
choice to use Debian "testing" instead of stable where I assume
everything just works?
Anyway thank you,
Charlie
--
Registered Linux User:- 329524
***********************************************
If I seem to boast more than is becoming, my excuse is that I
--
Registered Linux User:- 329524
***********************************************
brag for humanity rather than for myself. ....Henry David
Thoreau
***********************************************
Debian GNU/Linux - just the best way to create magic
-----------------------------------------------------
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Joel Roth
Jan 17, 2015, 2:00:04 AM1/17/15
to
Charlie wrote:
> On Fri, 16 Jan 2015 19:56:31 -1000 Joel Roth sent:
>
> > For now, you do have have a working audio system sitting
> > atop your Intel soundcard(s).
>
> Yes thank you.
>
> I have purged pulseaudio again. Never having used it found Alsa was
> always fine till recently when alsa didn't do it for me when using VLC.
> But then pulseaudio didn't either.
>
> However alsaplayer in the GUI only plays half the song and chokes.
>
> Aplay plays the songs fine in full, no glitch when invoked on the
> command line.
>
> VLC doesn't produce any sound. But then I can live without it.
> Especially since I have discovered how to add several songs to aplay on
> the commandline, takes a bit more typing the way I do it, but then
> that's also fine.
try vlc with the
> On Fri, 16 Jan 2015 19:56:31 -1000 Joel Roth sent:
>
> > For now, you do have have a working audio system sitting
> > atop your Intel soundcard(s).
>
> Yes thank you.
>
> I have purged pulseaudio again. Never having used it found Alsa was
> always fine till recently when alsa didn't do it for me when using VLC.
> But then pulseaudio didn't either.
>
> However alsaplayer in the GUI only plays half the song and chokes.
>
> Aplay plays the songs fine in full, no glitch when invoked on the
> command line.
>
> VLC doesn't produce any sound. But then I can live without it.
> Especially since I have discovered how to add several songs to aplay on
> the commandline, takes a bit more typing the way I do it, but then
> that's also fine.
--alsa-audio-device default
--alsa-audio-device hw:0,0
It looks like can specify the channel count
(although using '6' to get stereo seems weird.)
>From vlc --longhelp:
--alsa-audio-channels {1 (Mono), 6 (Stereo), 102
(Surround 4.0), 4198 (Surround 4.1), 103 (Surround 5.0),
4199 (Surround 5.1), 4967 (Surround 7.1)}
cheers,
> It's never so bad if you know how to do something, it's just a pain
> when you don't and you need to scrounge through all manner of websites
> to discover how it might work, often wasted because you've looked in
> the wrong place and it doesn't.
configure your system without some knowledge, or willingness
to get experience.
> I recall reading a Linux user/developer once writing that he was almost
> sick of Linux because whenever you tried to do something you had to
> learn how to do it. That in Windows it just worked.
that took forever. Many times more difficult than what
I can do with unix tools like rsync.
> It was interesting, and I know that when I want to do something and
> have to troll the net to find a way to do it because it needed a tweak,
> it could be frustrating. But I always blamed myself because I made the
> choice to use Debian "testing" instead of stable where I assume
> everything just works?
suit your hardware, networking environment and personal
needs. You cannot escape some overhead in administering
a system.
cheers,
joel
> Anyway thank you,
> Charlie
>
> --
> Registered Linux User:- 329524
> ***********************************************
>
> If I seem to boast more than is becoming, my excuse is that I
> brag for humanity rather than for myself. ....Henry David
> Thoreau
>
> ***********************************************
>
> Debian GNU/Linux - just the best way to create magic
>
> -----------------------------------------------------
>
>
> --
> To UNSUBSCRIBE, email to debian-us...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
> Archive: https://lists.debian.org/20150117171626.75cf67bd@taogypsy
>
Joel Roth
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Frédéric Marchal
Jan 17, 2015, 7:30:05 AM1/17/15
to
On Friday 16 January 2015 21:49:37, Ric Moore wrote :
> your old /etc/asoundrc is a leftover from upgrading from one release to
> the next to the next. I'm running on a fresh install of Jessie and have
> no /etc/asoundrc or ~/.asoundrc files at all. Maybe it's time or a fresh
> install?? To me, the problem of a live upgrade is that all of the old
> /home dotfile cruft hangs on forever. :) Ric
The initial problem, after installing wheezy, was that no sound was produced.
It was due to alsa using the HDMI device by default. I had to create
~/.asoundrc to make alsa use the correct PCH device.
That was a fresh install of wheezy on a new HP ProBook 650. There was no
asoundrc but I needed one to make alsa use the correct device.
I don't remember having seen pulseaudo after installing the system. I only
noticed it at some point after the sound stopped working. I didn't install it
on purpose. That's the reason I believe pulseaudio was pulled by a dependency
during an update and broke my (possibly unusual) sound configuration.
My problem is now solved. I unfortunately can't provide a full scientific
analysis of what happened. I list every clue that might help anybody else
facing the same problem.
Frederic
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/201501171329.3106...@wowtechnology.com
> On 01/16/2015 05:53 AM, Frédéric Marchal wrote:
> > On Friday 16 January 2015 10:33:23, Lisi Reisz wrote :
> >> On Friday 16 January 2015 08:41:29 Frédéric Marchal wrote:
> >>> BTW, I have pulseaudio installed in case it matters.
> >>
> >> So the advice is to have alsa and pulseaudio?
> >
> > I haven't investigated that far. I'm just stating a fact.
> >
> > I don't know what's the purpose of pulseaudio nor what are the benefits
> > of having installed it. I don't know if it would break something to
> > remove it.
> >
> > I believe it was installed at some point as part of a routine system
> > update and may have been the cause of the sound failure in the first
> > place.
>
> Nope, as you can use alsa directly at any time, as with aplay. I think
> > On Friday 16 January 2015 10:33:23, Lisi Reisz wrote :
> >> On Friday 16 January 2015 08:41:29 Frédéric Marchal wrote:
> >>> BTW, I have pulseaudio installed in case it matters.
> >>
> >> So the advice is to have alsa and pulseaudio?
> >
> > I haven't investigated that far. I'm just stating a fact.
> >
> > I don't know what's the purpose of pulseaudio nor what are the benefits
> > of having installed it. I don't know if it would break something to
> > remove it.
> >
> > I believe it was installed at some point as part of a routine system
> > update and may have been the cause of the sound failure in the first
> > place.
>
> your old /etc/asoundrc is a leftover from upgrading from one release to
> the next to the next. I'm running on a fresh install of Jessie and have
> no /etc/asoundrc or ~/.asoundrc files at all. Maybe it's time or a fresh
> install?? To me, the problem of a live upgrade is that all of the old
> /home dotfile cruft hangs on forever. :) Ric
The initial problem, after installing wheezy, was that no sound was produced.
It was due to alsa using the HDMI device by default. I had to create
~/.asoundrc to make alsa use the correct PCH device.
That was a fresh install of wheezy on a new HP ProBook 650. There was no
asoundrc but I needed one to make alsa use the correct device.
I don't remember having seen pulseaudo after installing the system. I only
noticed it at some point after the sound stopped working. I didn't install it
on purpose. That's the reason I believe pulseaudio was pulled by a dependency
during an update and broke my (possibly unusual) sound configuration.
My problem is now solved. I unfortunately can't provide a full scientific
analysis of what happened. I list every clue that might help anybody else
facing the same problem.
Frederic
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ric Moore
Jan 17, 2015, 3:50:05 PM1/17/15
to
On 01/17/2015 07:29 AM, Frédéric Marchal wrote:
> My problem is now solved. I unfortunately can't provide a full scientific
> analysis of what happened. I list every clue that might help anybody else
> facing the same problem.
All you had to do was to mute the HDMI stuff to make it easier on alsa.
> My problem is now solved. I unfortunately can't provide a full scientific
> analysis of what happened. I list every clue that might help anybody else
> facing the same problem.
More features, more choices. HDMI wasn't even an option until a few
years ago. Welcome to the new Linux! <cackles>
I betcha you have only one jack, that is supposed to autoswitch between
audio-out and headphone-out. There is a huge difference. You still
haven't replied to where your headphone is plugged in, what type, etc.
My USB 6.1 sound device has only one jack per stereo channel out. My
sound system is amplified. After I plugged them up to each other and
played a file I thought the cones were going to fly out, it was so loud.
I had to unplug and plug and unplug again several times before the
device decided I merely need audio-out.
So, to test, put your headphones on again, raise the volume level as
high as it will go and see if you don't hear some quiet tinny sound.
Your sound card didn't correctly sense that you have un-amplified
headphones and it auto-set itself to audio-out. Or, jam in some USB
sound card and forget all the pain.
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/54BAC902...@gmail.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Cindy-Sue Causey
Jan 17, 2015, 8:10:04 PM1/17/15
to
On 1/16/15, Mike McGinn <mikem...@mcginnweb.net> wrote:
>
> On Friday, January 16, 2015 14:23:21 Doug wrote:
>> On 01/16/2015 01:24 PM, Robert Latest wrote:
>
> When I had a new install I found that the mixer levels were all at zero.
> Found
> it after an hour of troubleshooting.
That was me. Raised the level up, and it still didn't work. That was
>
> On Friday, January 16, 2015 14:23:21 Doug wrote:
>> On 01/16/2015 01:24 PM, Robert Latest wrote:
>
> When I had a new install I found that the mixer levels were all at zero.
> Found
> it after an hour of troubleshooting.
on debootstrapped base Jessie with xfce4 chaser. I left it for later
and installed a few more favorite things hoping that might
accidentally fix it. Nope, still didn't work.
Then stumbled on xfce4-goodies that would have meant not having to
install a few of those earlier things. Slider was back at [zero] so I
moved it over again and...... *It works!*
What I hoped would happen actually did. Something I installed further
into the initial setup toggled something, tickled just the right file
somewhere. I've looked a couple times at everything that came with
xfce4-goodies (via /var/log/apt/history.log) but haven't seen anything
that popped off the screen yet as the (hero) fixer.....
Cindy :)
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with plastic sporks *
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Frédéric Marchal
Jan 19, 2015, 5:50:04 AM1/19/15
to
On Saturday 17 January 2015 21:41:38, Ric Moore wrote :
> On 01/17/2015 07:29 AM, Frédéric Marchal wrote:
> > My problem is now solved. I unfortunately can't provide a full scientific
> > analysis of what happened. I list every clue that might help anybody else
> > facing the same problem.
>
> All you had to do was to mute the HDMI stuff to make it easier on alsa.
How do I mute HDMI to make it easier on alsa?
> On 01/17/2015 07:29 AM, Frédéric Marchal wrote:
> > My problem is now solved. I unfortunately can't provide a full scientific
> > analysis of what happened. I list every clue that might help anybody else
> > facing the same problem.
>
> All you had to do was to mute the HDMI stuff to make it easier on alsa.
Isn't alsa reporting every sound device found at the hardware level?
> More features, more choices. HDMI wasn't even an option until a few
> years ago. Welcome to the new Linux! <cackles>
KDE complains that the audio hardware changes nearly at every boot. It reminds
me that it doesn't complain now that I take care of closing amarok before
shutting down the computer. I don't know if it is related.
The KDE Audio mixer content changes every couple of month too but I haven't
found what is the package whose update is responsible for those changes. At
this time, the "Playback devices" tab contains one slider for HDMI and one for
Analog stereo. There used to be more sliders for the various sources such as
the microphone. The mixer also used to have a menu to select the channels to
hide or show. It doesn't any more.
As I don't use sound much, a lot usually happen on this computer before I
notice a change or a failure with the sound system. And even more time pass
before I care enough to investigate thoroughly :-)
> I betcha you have only one jack, that is supposed to autoswitch between
> audio-out and headphone-out. There is a huge difference. You still
> haven't replied to where your headphone is plugged in, what type, etc.
output is the laptop internal speaker.
Frederic
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Robert Latest
Jan 20, 2015, 2:30:05 PM1/20/15
to
On Fri, 16 Jan 2015 15:11:24 -1000
Joel Roth <jo...@pobox.com> wrote:
> Robert Latest wrote:
> > With aplay -D hw:0,0 it still works.
>
> You're 99% to the destination.
>
> IIRC, directly addressing the sound device
> as hw:0,0 takes the whole device, will not
> allow software mixing of audio streams from
> other applications.
OK guys,
> Robert Latest wrote:
> > With aplay -D hw:0,0 it still works.
>
> You're 99% to the destination.
>
> IIRC, directly addressing the sound device
> as hw:0,0 takes the whole device, will not
> allow software mixing of audio streams from
> other applications.
thanks a lot for all the helpful hints. What I ended up doing is this:
- purge all pulse audio stuff
- created an .asoundrc like this:
pcm.!default {
type plug
slave {
pcm "hw:0,2"
}
}
ctl.!default {
type hw
card 1
}
I don't understand the first thing about this. I just copied this file
}
ctl.!default {
type hw
card 1
}
from somewhere. Note the "hw:0,2" part. Remember that I had to use -D
hw:0,0 with aplay to make sound work while pulseaudio was installed? Now
hw:0,2 is the way to go. Search me why.
Thanks
robert
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ric Moore
Jan 22, 2015, 4:30:05 PM1/22/15
to
On 01/19/2015 05:46 AM, Frédéric Marchal wrote:
> On Saturday 17 January 2015 21:41:38, Ric Moore wrote :
>> On 01/17/2015 07:29 AM, Frédéric Marchal wrote:
>>> My problem is now solved. I unfortunately can't provide a full scientific
>>> analysis of what happened. I list every clue that might help anybody else
>>> facing the same problem.
>>
>> All you had to do was to mute the HDMI stuff to make it easier on alsa.
>
> How do I mute HDMI to make it easier on alsa?
>
> Isn't alsa reporting every sound device found at the hardware level?
Sure! I just mute stuff I don't use.
> On Saturday 17 January 2015 21:41:38, Ric Moore wrote :
>> On 01/17/2015 07:29 AM, Frédéric Marchal wrote:
>>> My problem is now solved. I unfortunately can't provide a full scientific
>>> analysis of what happened. I list every clue that might help anybody else
>>> facing the same problem.
>>
>> All you had to do was to mute the HDMI stuff to make it easier on alsa.
>
> How do I mute HDMI to make it easier on alsa?
>
> Isn't alsa reporting every sound device found at the hardware level?
>> More features, more choices. HDMI wasn't even an option until a few
>> years ago. Welcome to the new Linux! <cackles>
>
> The audio system is still highly unstable according to my experience.
>
> KDE complains that the audio hardware changes nearly at every boot. It reminds
> me that it doesn't complain now that I take care of closing amarok before
> shutting down the computer. I don't know if it is related.
>
> The KDE Audio mixer content changes every couple of month too but I haven't
> found what is the package whose update is responsible for those changes. At
> this time, the "Playback devices" tab contains one slider for HDMI and one for
> Analog stereo. There used to be more sliders for the various sources such as
> the microphone. The mixer also used to have a menu to select the channels to
> hide or show. It doesn't any more.
>
> As I don't use sound much, a lot usually happen on this computer before I
> notice a change or a failure with the sound system. And even more time pass
> before I care enough to investigate thoroughly :-)
>
>
>
>> I betcha you have only one jack, that is supposed to autoswitch between
>> audio-out and headphone-out. There is a huge difference. You still
>> haven't replied to where your headphone is plugged in, what type, etc.
>
> I have no headphone nor external speaker so I can't test it. My only sound
> output is the laptop internal speaker.
Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/54C16B28...@gmail.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ric Moore
Jan 22, 2015, 4:40:05 PM1/22/15
to
On 01/20/2015 02:07 PM, Robert Latest wrote:
>
> I don't understand the first thing about this. I just copied this file
> from somewhere. Note the "hw:0,2" part. Remember that I had to use -D
> hw:0,0 with aplay to make sound work while pulseaudio was installed? Now
> hw:0,2 is the way to go. Search me why.
If you upgraded, then at times you get incremented in device
>
> I don't understand the first thing about this. I just copied this file
> from somewhere. Note the "hw:0,2" part. Remember that I had to use -D
> hw:0,0 with aplay to make sound work while pulseaudio was installed? Now
> hw:0,2 is the way to go. Search me why.
names/numbers, like eth0 becomes eth1, since it found eth0 already
there, so it added eth1. I guess the speckled puppy computer thought it
was "helping" you. I bet if you returned to the page you got that script
from, it will be years old. I just installed Jessie cleanly to a little
Asus mini laptop and everything worked out of the box, including it's
buil-in intel sound chip and stereo speakers. No asoundrc file anywhere.
Something is amiss, most likely up in /etc/udev in a rules file? :) Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/54C16DC0...@gmail.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
0 new messages