Re: Can't get sound to work
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. 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. Sorry, my bad. I thought you referenced headphones earlier. 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54c16b28.5010...@gmail.com
Re: Can't get sound to work
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 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54c16dc0.1050...@gmail.com
Re: Can't get sound to work
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,
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
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-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150120200730.7c3ca994@dotcom.mfs32
Re: Can't get sound to work
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. Frederic -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201501191146.49918.frederic.marc...@wowtechnology.com
Re: Can't get sound to work
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. 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54bac902.6040...@gmail.com
Re: Can't get sound to work
On 1/16/15, Mike McGinn mikemcg...@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 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAO1P-kA52XAWDdSgED1o7ftCc1iPOtY+mWsF=ayugfiqk0e...@mail.gmail.com
Re: Can't get sound to work
On Friday 16 January 2015 21:49:37, Ric Moore wrote : 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 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201501171329.31063.frederic.marc...@wowtechnology.com
Re: Can't get sound to work
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?
-- August
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/m9agfi$bnc$1...@dont-email.me
Re: Can't get sound to work
On Thursday 15 January 2015 21:28:30, Robert Latest 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
}
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:~$
Sound has been missing on my wheezy for some time until your mail prompted me
to investigate it.
Running aplay test.wav produces no sound.
The output of aplay -l is:
List of PLAYBACK Hardware Devices
card 0: HDMI_1 [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI_1 [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI_1 [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: 92HD91BXX Analog [92HD91BXX Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Running aplay -D hw:1,0 test.wav reports an error and produces no sound:
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-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/201501160941.29640.frederic.marc...@wowtechnology.com
Re: Can't get sound to work
On Friday 16 January 2015 08:41:29 Frédéric Marchal wrote:
On Thursday 15 January 2015 21:28:30, Robert Latest 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
}
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:~$
Sound has been missing on my wheezy for some time until your mail prompted
me to investigate it.
Running aplay test.wav produces no sound.
The output of aplay -l is:
List of PLAYBACK Hardware Devices
card 0: HDMI_1 [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI_1 [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: HDMI_1 [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: 92HD91BXX Analog [92HD91BXX Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Running aplay -D hw:1,0 test.wav reports an error and produces no sound:
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.
So the advice is to have alsa and pulseaudio?
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201501160933.23468.lisi.re...@gmail.com
Re: Can't get sound to work
On Friday 16 January 2015 10:33:23, Lisi Reisz wrote :
On Friday 16 January 2015 08:41:29 Frédéric Marchal wrote:
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.
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.
Frederic
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/201501161153.37226.frederic.marc...@wowtechnology.com
Re: Can't get sound to work
On Thu, 15 Jan 2015 19:43:23 -0500 Ric Moore wayward4...@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? 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? F6 lets me select different cards in alsamixer, but it doesn't change 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. I put it there hoping to make the -D hw:0,0 thingy the default for 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. 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 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150116192420.25211d69@dotcom.mfs32
Re: Can't get sound to work
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. 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b96529.3060...@optonline.net
Re: Can't get sound to work
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. -- 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201501161433.29846.mikemcg...@mcginnweb.net
Re: Can't get sound to work
On Thu, 15 Jan 2015 19:43:23 -0500 Ric Moore wayward4...@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. Thanks robert -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150116205622.3f0fc1af@dotcom.mfs32
Re: Can't get sound to work
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 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b975ab.4060...@gmail.com
Fwd: Re: Can't get sound to work
I hit the wrong send to: button. Forwarded Message Subject: Re: Can't get sound to work Date: Fri, 16 Jan 2015 15:29:50 -0500 From: Ric Moore wayward4...@gmail.com To: Robert Latest boblat...@gmail.com On 01/16/2015 01:24 PM, Robert Latest wrote: On Thu, 15 Jan 2015 19:43:23 -0500 Ric Moore wayward4...@gmail.com wrote: 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. In a nut shell, alsa is the basement for sound. Pulse sits on top and directs input/output to multiple sound decices. It seems you have several. I've got a sound card plugged in, so I disabled the onboard sound card, that won't work at all, in the bios. Now alsa has one less headache to deal with. Then install pauvucontrol. That is the graphical interface to pulse. Running that I can define my outputs, like USB headphonne + mono-mike, 6.1 sound card. Now I can select playback and direct the sound between my suround speakers and stereo headphones, ON THE FLY!! Again, if alsa is not happy, pulse will not work at all either. If you have a sound card in your junk box, install that to the motherboard and disable the onboard intel setup in the bios. My onboard audio refused to work, and that fixed it nicely. Or, just get a cheap usb audio device, with all the bells and whistles, like 7.1 sound. I love blasting the neighborhood with my setup. When I need quiet, I just use pavucontrol to direct the output to the usb headphones. That beats the dickens out of messing with ancient alsa scripts and edits. Works For Me!tm 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 -- 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b975ed.50...@gmail.com
Re: Can't get sound to work
On 01/16/2015 04:33 AM, Lisi Reisz wrote: 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 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b97700.2020...@gmail.com
Re: Can't get sound to work
Le 16.01.2015 19:24, Robert Latest a écrit : On Thu, 15 Jan 2015 19:43:23 -0500 Ric Moore wayward4...@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, 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? If you purge alsa-related stuff, you will end with no sound at all. 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/7336596ddab655b8d37400e9c49a9...@neutralite.org
Re: Can't get sound to work
On 01/16/2015 02:56 PM, Robert Latest wrote: On Thu, 15 Jan 2015 19:43:23 -0500 Ric Moore wayward4...@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 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b97d8f.2030...@gmail.com
Re: Can't get sound to work
On 01/16/2015 03:51 PM, berenger.mo...@neutralite.org wrote: Le 16.01.2015 19:24, Robert Latest a écrit : On Thu, 15 Jan 2015 19:43:23 -0500 Ric Moore wayward4...@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, 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? If you purge alsa-related stuff, you will end with no sound at all. 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. Jack confuses the heck out of me, and I think it relies on a realtime 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b97e68.8040...@gmail.com
Re: Can't get sound to work
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 OK, now trying to remove all pulse-related stuff. Thanks robert -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150116205622.3f0fc1af@dotcom.mfs32 -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150117011124.GB7790@sprite
Re: Can't get sound to work
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 - -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150117132731.4e4e4d61@taogypsy
Re: Can't get sound to work
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. 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] The ALSA project has a Linux kernel driver for your 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150117132731.4e4e4d61@taogypsy -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150117055631.GA26400@sprite
Re: Can't get sound to work
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, 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150117171626.75cf67bd@taogypsy
Re: Can't get sound to work
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
--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.
Man pages and mailing lists are helpful. There is no way to
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.
I did a Windows 7 system restore for a friend's notebook
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?
No, you will always have issues configuring your system to
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-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150117171626.75cf67bd@taogypsy
--
Joel Roth
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150117065129.GB26400@sprite
Re: Can't get sound to work
On Thu, 15 Jan 2015 21:21:55 +0100 Daniel Haude sent:
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:~$
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
No such file or directory
~$ aplay -l
List of PLAYBACK Hardware Devices
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 0: ALC269VB Analog
[ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
$ lsmod | grep snd
snd_hda_codec_realtek63031 1
snd_hda_codec_hdmi 45118 1
snd_hda_codec_generic63107 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_pcm88662 4
snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
snd_timer 26614 1 snd_pcm
snd65244 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 0xf044 irq 47
$ udevadm trigger --verbose --subsystem-match=sound
/sys/devices/pci:00/:00:01.1/sound/card0
/sys/devices/pci:00/:00:01.1/sound/card0/hdaudioC0D0
/sys/devices/pci:00/:00:01.1/sound/card0/hdaudioC0D0/hwC0D0
/sys/devices/pci:00/:00:01.1/sound/card0/hdaudioC0D0/pcmC0D3p
/sys/devices/pci:00/:00:01.1/sound/card0/controlC0
/sys/devices/pci:00/:00:14.2/sound/card1
/sys/devices/pci:00/:00:14.2/sound/card1/hdaudioC1D0
/sys/devices/pci:00/:00:14.2/sound/card1/hdaudioC1D0/hwC1D0
/sys/devices/pci:00/:00:14.2/sound/card1/hdaudioC1D0/pcmC1D0c
/sys/devices/pci:00/:00:14.2/sound/card1/hdaudioC1D0/pcmC1D0p
/sys/devices/pci:00/: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
Can't get sound to work
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-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150115212830.16a3294a@dotcom.mfs32
Re: Can't get sound to work
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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3539974.jClRHfbk25@protheus2
Re: Can't get sound to work
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. 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-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b85eab.3030...@gmail.com
Can't get sound to work
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-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150115212155.01420526@dotcom.mfs32
Re: can't get sound to work with webcam Logitech C910
On Sun, 25 Mar 2012 20:04:39 +0200, Bernard wrote: Camaleón wrote: What's the output of arecord -l? I ask becasue it can be that you have now two microphones (one coming from the sound card and other from the webcam) and need to define what's the default or which to use. (...) I have just tested a bit more with alsamixer, this time using my webcam and GUVCwiewer. If I boost the alsamixer settings to maximum (red level), then I get SOME sound in my videos, which plays back using, not vlc, but 'Totem'... But then the played back sound si very week and even cracky (distorded with kinds of cracks)... and absolutely no sound at all if the alsamixer parameters are not to the maximum. As for Cheese, I just tested something else as just mentioned. It is GUVCwiewer. It looks a lot better... but still no sound or very bad and weak one as stated above. Okay, so basically what we have here is that the sound is very, very low unless you put it to the top level and still the image capturing has some hicups... let me Google a bit. I found this bug report for Ubuntu: Logitech camera microphone does not work / makes chipmunk sound https://bugs.launchpad.net/ubuntu/+source/linux/+bug/843431 At comment #37 there seems to be a pacth for some cameras and C910 is listed there. Also note that as per the other user's comments, the camera looks like it worked fine in kernel 2.6.38, not sure if it's an option (or even worth for it) for you to test with that kernel or with a newer one :-? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jkq29v$4vf$7...@dough.gmane.org
Re: can't get sound to work with webcam Logitech C910
On Sat, 24 Mar 2012 22:37:45 +0100, Bernard wrote: I just bought the above mentioned web camera, and, if I record a video using Cheese, the sound is not there when I try displaying the record using 'vlc'. I get this: main subpicture error : blending YUVA to I444 failed ^^ Mmm, the above error looks more close to be related with image than sound :-? this line repeated a number of times. The image is there though, but no sound Have you tried your microphone from Gnome sound recorder or another application (arecord)? How about running alsamixer (or your DE sound applet) to be sure the capture/input/mic source control is at a high level and not muted/lowered? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jkn0s4$q88$1...@dough.gmane.org
Re: can't get sound to work with webcam Logitech C910
On 24/03/2012 22:37, Bernard wrote: Hi to Everyone ! I just bought the above mentioned web camera, and, if I record a video using Cheese, the sound is not there when I try displaying the record using 'vlc'. I get this: main subpicture error : blending YUVA to I444 failed this line repeated a number of times. The image is there though, but no sound Thanks in advance for your input P.S. : Debian Squeeze on that system. This webcam (046d:0821) works in vlc in Wheezy/Sid, sound device is hw0,1 here but this might be different on your system. I use alsa+phonon (KDE), so pulse isn't getting in the way for me, maybe it is for you ? Squeeze could be somehow too old for this camera (alsa's snd_usb_audio module), but I doubt it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f6f1c05.2040...@googlemail.com
Re: can't get sound to work with webcam Logitech C910
Camaleón wrote: On Sat, 24 Mar 2012 22:37:45 +0100, Bernard wrote: I just bought the above mentioned web camera, and, if I record a video using Cheese, the sound is not there when I try displaying the record using 'vlc'. I get this: main subpicture error : blending YUVA to I444 failed ^^ Mmm, the above error looks more close to be related with image than sound :-? It may be the case, since the image is not good either. It appears the same as I could see it while recording, that is, in chunks... I mean, as if the camera had been working on and off this line repeated a number of times. The image is there though, but no sound Have you tried your microphone from Gnome sound recorder or another application (arecord)? How about running alsamixer (or your DE sound applet) to be sure the capture/input/mic source control is at a high level and not muted/lowered? I tried both, recording is not muted, and I can play wav files by $ play myfile.wav But, maybe Cheese is not a good choice for video recording with a webcam such as this ? What else would you recommend ? My purpose with this webcam is, for now, to use is as a video recorder, not for video chat as yet. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f6f1178.8020...@teaser.fr
Re: can't get sound to work with webcam Logitech C910
On Sun, 25 Mar 2012 14:37:12 +0200, Bernard wrote: Camaleón wrote: main subpicture error : blending YUVA to I444 failed ^^ Mmm, the above error looks more close to be related with image than sound :-? It may be the case, since the image is not good either. It appears the same as I could see it while recording, that is, in chunks... I mean, as if the camera had been working on and off Mmm, maybe is that Cheese is not well suited to get the best of HD cams, I mean, you may need more control over the video settings. Have you tried your microphone from Gnome sound recorder or another application (arecord)? How about running alsamixer (or your DE sound applet) to be sure the capture/input/mic source control is at a high level and not muted/lowered? I tried both, recording is not muted, and I can play wav files by $ play myfile.wav What's the output of arecord -l? I ask becasue it can be that you have now two microphones (one coming from the sound card and other from the webcam) and need to define what's the default or which to use. But, maybe Cheese is not a good choice for video recording with a webcam such as this ? What else would you recommend ? My purpose with this webcam is, for now, to use is as a video recorder, not for video chat as yet. Well, yup, I'd say Cheese is not aimed for video recording but online chatting. You can try with video recording/capturing programs, for instance VLC, GUVCviewer, ffmpeg, mplayer or mencoder although there are more advanced/specialized tools for the matter but maybe they're too big for your purposes. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jkn9fk$q88$1...@dough.gmane.org
Re: can't get sound to work with webcam Logitech C910
Camaleón wrote: On Sun, 25 Mar 2012 14:37:12 +0200, Bernard wrote: Camaleón wrote: main subpicture error : blending YUVA to I444 failed ^^ Mmm, the above error looks more close to be related with image than sound :-? It may be the case, since the image is not good either. It appears the same as I could see it while recording, that is, in chunks... I mean, as if the camera had been working on and off Mmm, maybe is that Cheese is not well suited to get the best of HD cams, I mean, you may need more control over the video settings. Have you tried your microphone from Gnome sound recorder or another application (arecord)? How about running alsamixer (or your DE sound applet) to be sure the capture/input/mic source control is at a high level and not muted/lowered? I tried both, recording is not muted, and I can play wav files by $ play myfile.wav What's the output of arecord -l? I ask becasue it can be that you have now two microphones (one coming from the sound card and other from the webcam) and need to define what's the default or which to use. arecord -l says: List of Capture Hardware devices Card0: Intel [HDA Intel] device 0: ALC662 rev1 Analog [ALC662 rev1 Analog] Subdevices: 1/1 Subdevices #0: subdevice #0 Card1 : U0x46d:0x821 [USB Device 0x46d:0x821], device 0: USB audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 I have tried to see with alsamixer if something looked weird: recording levels as well as play levels on both cards seem OK (Green + while in the columns, just before the red zones). Now, what happens if I try just recording voice, with and without the webcam connected ? In both cases, it records ... next to nothing, but not quite nothing though. I just type: $ rec testfile.wav and I speak a few words... then CTRL C to quit, and: $ play testfile.wav I can hear next to nothing... but if I boost alsamixer cursors to the maximum (either with alsamixer in an xterm or using the icons on the gnome desk), then if it really is on the maximum (cursor columns gone full into the red), then I can record and play a sound that I can hear ; it is weak but still I can easily reckognize my voice. In the other hand, $ play any_other_wavfile_recorded_somewhere_else.wav I get normal level good sound with alsamixer set to normal values for play I have just tested a bit more with alsamixer, this time using my webcam and GUVCwiewer. If I boost the alsamixer settings to maximum (red level), then I get SOME sound in my videos, which plays back using, not vlc, but 'Totem'... But then the played back sound si very week and even cracky (distorded with kinds of cracks)... and absolutely no sound at all if the alsamixer parameters are not to the maximum. As for Cheese, I just tested something else as just mentioned. It is GUVCwiewer. It looks a lot better... but still no sound or very bad and weak one as stated above. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f6f5e37.5020...@teaser.fr
Re: can't get sound to work with webcam Logitech C910
I have tried to see with alsamixer if something looked weird: recording levels as well as play levels on both cards seem OK (Green + while in the columns, just before the red zones). Not sure if you've tried these:- Alsamixer has 'mic-boost', 'capture', 'capture1', 'internal mic boost'. (Press F4) Also F6 might give another soundcard. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f6f741a.4050...@gmail.com
Re: can't get sound to work with webcam Logitech C910
Keith McKenzie wrote: I have tried to see with alsamixer if something looked weird: recording levels as well as play levels on both cards seem OK (Green + while in the columns, just before the red zones). Not sure if you've tried these:- Alsamixer has 'mic-boost', 'capture', 'capture1', 'internal mic boost'. (Press F4) Also F6 might give another soundcard. I sort of tried these... What I mean is that I suppose not all sound cards support all these options. Mine does have 'Capture', 'Playback' and various SPDIF options, but no 'intertnal mic boost' or 'mic boost'. As for F6, it lists the two sound cards that are available in that system, that is : HDA Intel G45 DEVCTG and the webcam sound card, that states that it does not have any playback function. For more details, please see the screen shots that I have done with alsamixer : http://bdebreil.free.fr/alsamixer1.jpg http://bdebreil.free.fr/Alsamixer2.jpg http://bdebreil.free.fr/alsamixer3.jpg http://bdebreil.free.fr/alsamixer4.jpg http://bdebreil.free.fr/alsamixer5.jpg http://bdebreil.free.fr/alsamixer6.jpg http://bdebreil.free.fr/alsamixer7.jpg http://bdebreil.free.fr/alsamixer8.jpg You will surely notice on these screen shots that most sound settings are so high that they are 'in the red'. Those settings were the only ones that allowed me to record a very weak and distorted - but still existing - sound in videos. Normal settings (green zones and green + white zones) gave no sound at all -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f6f9cbb.70...@teaser.fr
can't get sound to work with webcam Logitech C910
Hi to Everyone ! I just bought the above mentioned web camera, and, if I record a video using Cheese, the sound is not there when I try displaying the record using 'vlc'. I get this: main subpicture error : blending YUVA to I444 failed this line repeated a number of times. The image is there though, but no sound Thanks in advance for your input P.S. : Debian Squeeze on that system. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f6e3ea9.1030...@teaser.fr
RE: Can't get sound to work (CMIxxxx)
Thanks Bob, I'll try that... ~-Original Message- ~From: Bob Nielsen [mailto:[EMAIL PROTECTED]]On Behalf Of Bob Nielsen ~Sent: Tuesday, January 21, 2003 8:56 PM ~To: [EMAIL PROTECTED] ~Subject: Re: Can't get sound to work (CMI) ~ ~ ~At least some of the Debian kernel-image packages (I run ~kernel-image-2.4.20-686) already contain many of the CMI drivers, so ~compiling your own shouldn't be necessary: SNIP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Can't get sound to work (CMIxxxx)
Hello everyone! I know that this topic may have been typed to the death already, but I need help getting my soundchips (CMI8xxx, the ones that are already built in to the motherboard). I read the old SuSe Linux manual, it had some instructions for sound which I tried to follow and so far I tried sndconfig, and dselect(ed) isapnp (and it recognizes the soundchips at bootup), but it nags that I need a 2.xomething kernel in order to run, or that it needs soundcard.o files, I think I do have the correct kernel version, but I cannot get any sound out of it. Am I missing something or is there something else that I need to read (something I'm overlooking from the Woody CD dist)? Thanks In Advanced! May the Force of the Dragon's Spirit be with you...In Accordance With The Prophecy. Happy Hacking, Bright Blessings and Gentle Breezes! -*/ -= )O( Jay CoolDragon Arias-Chavez )O( =- /*- En el horizonte vertical yace el espejo de nuestra Alma. In the vertical horizon lies the mirror of our Soul. - J. Arias-Chavez -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Can't get sound to work (CMIxxxx)
Hello everyone! I know that this topic may have been typed to the death already, but I need help getting my soundchips (CMI8xxx, the ones that are already built in to the motherboard). I read the old SuSe Linux manual, it had some instructions for sound which I tried to follow and so far I tried sndconfig, and dselect(ed) isapnp (and it recognizes the soundchips at bootup), but it nags that I need a 2.xomething kernel in order to run, or that it needs soundcard.o files, I think I do have the correct kernel version, but I cannot get any sound out of it. Am I missing something or is there something else that I need to read (something I'm overlooking from the Woody CD dist)? Thanks In Advanced! May the Force of the Dragon's Spirit be with you...In Accordance With The Prophecy. Happy Hacking, Bright Blessings and Gentle Breezes! Did you actually compile the kernel yourself or are you using something that is pre-compiled? Your problem sounds like you are missing sound support in the kernel. I think you are missing soundcore.o which is core sound support. Hope this helps. Davor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Can't get sound to work (CMIxxxx)
I installed debian from the CD as the normal install, I do think that I'm missing something but I don't know what package contains it (dselect what?) Thanks again! - Jay. ~-Original Message- ~From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] ~Sent: Tuesday, January 21, 2003 3:00 PM ~To: [EMAIL PROTECTED] ~Subject: RE: Can't get sound to work (CMI) ~ ~SNIP ~ ~Did you actually compile the kernel yourself or are you using ~something that is pre-compiled? ~Your problem sounds like you are missing sound support in the ~kernel. I think you are missing soundcore.o which is core ~sound support. ~ ~ ~Hope this helps. ~ ~ ~Davor ~ ~ ~ ~-- ~To UNSUBSCRIBE, email to [EMAIL PROTECTED] ~with a subject of unsubscribe. Trouble? Contact ~[EMAIL PROTECTED] ~ ~ ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Can't get sound to work (CMIxxxx)
The driver should be provided with the kernel as a module. Try this: modprobe cmpci On Tue, Jan 21, 2003 at 04:21:14PM -0800, Jay wrote: I installed debian from the CD as the normal install, I do think that I'm missing something but I don't know what package contains it (dselect what?) Thanks again! - Jay. ~-Original Message- ~From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] ~Sent: Tuesday, January 21, 2003 3:00 PM ~To: [EMAIL PROTECTED] ~Subject: RE: Can't get sound to work (CMI) ~ ~SNIP ~ ~Did you actually compile the kernel yourself or are you using ~something that is pre-compiled? ~Your problem sounds like you are missing sound support in the ~kernel. I think you are missing soundcore.o which is core ~sound support. ~ ~ ~Hope this helps. ~ ~ ~Davor ~ ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Can't get sound to work (CMIxxxx)
I installed debian from the CD as the normal install, I do think that I'm missing something but I don't know what package contains it (dselect what?) Thanks again! - Jay. OK, now I get it. You will need to install kernel-source-2.4.18 or something like that and compile your own kernel with CMI drivers/modules either compiled in or with those modules installed. This should fix it. Davor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Can't get sound to work (CMIxxxx)
At least some of the Debian kernel-image packages (I run kernel-image-2.4.20-686) already contain many of the CMI drivers, so compiling your own shouldn't be necessary: # grep CMPCI /boot/config-2.4.20-686 CONFIG_SOUND_CMPCI=m # CONFIG_SOUND_CMPCI_FM is not set # CONFIG_SOUND_CMPCI_MIDI is not set CONFIG_SOUND_CMPCI_JOYSTICK=y CONFIG_SOUND_CMPCI_CM8738=y # CONFIG_SOUND_CMPCI_SPDIFINVERSE is not set # CONFIG_SOUND_CMPCI_SPDIFLOOP is not set CONFIG_SOUND_CMPCI_SPEAKERS=2 On Wed, Jan 22, 2003 at 01:26:07PM +1000, [EMAIL PROTECTED] wrote: I installed debian from the CD as the normal install, I do think that I'm missing something but I don't know what package contains it (dselect what?) Thanks again! - Jay. OK, now I get it. You will need to install kernel-source-2.4.18 or something like that and compile your own kernel with CMI drivers/modules either compiled in or with those modules installed. This should fix it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Can't get sound to work!
Ok, I got sound working. On my windows boot the sound was on IRQ 5, it kept trying to put it on IRQ 7 in linux. I added a /etc/modutils/sound file and put options sb irq=5 io=0x220 dma=1 in it, but when I rebooted it seemed to ignore that file. So instead I edited /etc/modules. It had a single line in it that said: sb So I change it to read: sb irq=5 io=0x220 dma=1 That worked. What is confusing me now, is that when I shut down, during my shutdown messages I get a message that the alsa driver isn't running. This is correct, it shouldn't be. But I can't figure out why my machine is trying to shut it down. I checked in rcS.d and my rc5.d directories (I'm running in mode 5) but I can't figure out where my machine is trying start/shutdown the alsa drivers. Also, during my boot sequence my machine scans for SCSI interfaces. I don't have any scsi interfaces so how can I stop it from doing this scan everytime I boot? BTW, apt-get rocks. Now I know why people who use debian never go to anything else. I'm addicted :) Kent West wrote: Rev. Ferret wrote: Ok, I added myself to user audio and I now get sound from things. There is just one problem. The sound skips. It sounds like a broken record player, where it plays the same bit over and over again. I tried chmod'ing the audio things to world usable, but it didn't help. Any ideas on how to get it to stop skipping? At least I'm getting some sound now :) Probably one of two things: (1) wrong sound driver or problems with the driver (2) IRQ or IOPort conflict If this is an ISA card, it's probably the second. Do you have a dual-boot with Win9x? If so, what IRQ/io does it report the card being on? Does this match what Linux thinks? Or maybe it's a jumper-configured card, in which case, make sure Linux sees the same settings that the card is actually on. If Linux doesn't match the actual settings, you can feed the settings to the module when it installs. For example, I have a file /etc/modutils/sound which has the two lines: options uart401 irq=9 io=0x330 options sb irq=5 io=0x220 dma=1 hth, Kent
Re: Can't get sound to work!
Rev. Ferret wrote: Ok, I got sound working. On my windows boot the sound was on IRQ 5, it kept trying to put it on IRQ 7 in linux. I added a /etc/modutils/sound file and put options sb irq=5 io=0x220 dma=1 in it, but when I rebooted it seemed to ignore that file. You also have to run update-modules; that reads the files in /etc/modules and propogates any necessary config information into /etc/modules.conf. So instead I edited /etc/modules. It had a single line in it that said: sb So I change it to read: sb irq=5 io=0x220 dma=1 That worked. What is confusing me now, is that when I shut down, during my shutdown messages I get a message that the alsa driver isn't running. This is correct, it shouldn't be. But I can't figure out why my machine is trying to shut it down. I checked in rcS.d and my rc5.d directories (I'm running in mode 5) but I can't figure out where my machine is trying start/shutdown the alsa drivers. Not being a user of ALSA, I can't speak to this; you might want to start a new thread so people don't tune out this question based on the old, now non-applicable, subject line. Also, during my boot sequence my machine scans for SCSI interfaces. I don't have any scsi interfaces so how can I stop it from doing this scan everytime I boot? You might need to recompile your kernel; the stock kernel contains code for SCSI devices; it doesn't hurt to leave it there (except getting rid of it woudl make your kernel smaller). BTW, apt-get rocks. Now I know why people who use debian never go to anything else. I'm addicted : Yeppers.
Can't get sound to work!
Hi, I'm having problems getting my sound blaster 16 working. I used modconf to select the sb module, which in turn selected a bunch of the oss modules. After doing this, I can play audio cd's, but whenever I try to run gmix it tells me that I do not have a mixer installed or my kernel doesn't support sound. When I run XMMS, it tells me my kernel either doesn't support sound or my card is not configured correctly. I figured my kernel supports sound because I can load sound modules and play audio cd's, so something else must be wrong. What else do I have to do to get sound to work under debian? Thanks, Steve
Re: Can't get sound to work!
Rev. Ferret wrote: Hi, I'm having problems getting my sound blaster 16 working. I used modconf to select the sb module, which in turn selected a bunch of the oss modules. After doing this, I can play audio cd's, but whenever I try to run gmix it tells me that I do not have a mixer installed or my kernel doesn't support sound. When I run XMMS, it tells me my kernel either doesn't support sound or my card is not configured correctly. I figured my kernel supports sound because I can load sound modules and play audio cd's, so something else must be wrong. What else do I have to do to get sound to work under debian? Thanks, Steve I'm no expert, so if you have any further questions, reply to all, not just to me, so that the list members can throw in their two cents. (1) You need to have support in your kernel for your sound card. There are two methods of doing this; one is to compile it in; the other is to plug it in as a module. Your description indicates that you're using the module method. (2) Playing an audio CD doesn't really depend on the software sound support; most CD drives will start spinning as soon as you put in a CD, and the sound from an audio CD is piped through the audio cable directly to the sound card. What a broken software setup will do is prevent you from using apps to control tracks, volume, etc. About the only thing playing an audio CD proves is that the hardware is functional (which is a good thing to know); it also points strongly to a lack of IRQ conflict (although not necessarily). (3) When you boot up, you should see some info scroll by concerning your sound card. But generally it goes by too fast to see, and you can see it after the fact by running dmesg|more. (4) You should be able to see if you card is recognized, and on which IRQ, by running cat /proc/interrupts (my card is on IRQ 5 and 9). (5) Ditto for IO by running cat /proc/ioports (my card's on 220-2FF and 330-3FF). (6) You can see what modules are loaded by running lsmod (I've got soundcore, sound, uart401, and sb). (7) I'm not sure what cat /proc/devices indicates, but it lists my sound card, so it might be relevant. (8) Perhaps the most informative command is cat /dev/sndstat, which on my machine reports: OSS/Free:3.8s2++-971130 Load type: Driver loaded as a module Kernel: Linux westk03 2.2.18 #2 Thu Jan 18 22:52:14 CST 2001 i586 Config options: 0 Installed drivers: Card config: Audio devices: 0: Sound Blaster Pro (8 BIT ONLY) (3.02) Synth devices: Midi devices: 0: MPU-401 (UART) MIDI 1: Sound Blaster Timers: 0: System clock Mixers: 0: Sound Blaster Perhaps this info will get you a bit further on your quest to get your card working. Good luck! Kent
[ferret@optonline.net: Can't get sound to work!]
- Forwarded message from Rev. Ferret [EMAIL PROTECTED] - Hi, I'm having problems getting my sound blaster 16 working. I used modconf to select the sb module, which in turn selected a bunch of the oss modules. After doing this, I can play audio cd's, but whenever I try to run gmix it tells me that I do not have a mixer installed or my kernel doesn't support sound. When I run XMMS, it tells me my kernel either doesn't support sound or my card is not configured correctly. I figured my kernel supports sound because I can load sound modules and play audio cd's, so something else must be wrong. What else do I have to do to get sound to work under debian? - End forwarded message - I had the same problem, and you can do one of 2 things.. you can add yourself as a user to the audio group, or just chmod all the /dev/mixer devices to where they are world usable.. man chmod =)
Re: Can't get sound to work!
It seems that my card is recognized. Everything looks normal except for the output of my /dev/sndstat. I can use apps to control tracks of audio cd's and things like that. I just can't use any mixer apps or play any audio except for cd audio. I can't figure out what's wrong. Using redhat and mandrake I was able to just do sndconfig and pick soundblaster and everything worked. I only seem to be having this problem with debian. The results of cat /proc/interrupts has the following entry: 7:4soundblaster The output of /proc/ioports has this entry: 0220-022f : soundblaster lsmod contains these entries: sb,uart401,sound,soundlow,soundcore cat /dev/sndstat lists the following: OSS/Free:3.8s2++-971130 Load type: Driver loaded as a module Kernel: Linux neuro 2.2.18pre21 #1 Sat Nov 18 18:47:15 EST 2000 i686 Config options: 0 Installed Drivers: Card config: Audio devices: 0: ESS ES1879 AudioDrive (rev 11) (3.01) Synth devices: Midi devices: 0: ESS ES1688 Timers: 0: System clock Mixers: 0: Sound Blaster Kent West wrote: Rev. Ferret wrote: Hi, I'm having problems getting my sound blaster 16 working. I used modconf to select the sb module, which in turn selected a bunch of the oss modules. After doing this, I can play audio cd's, but whenever I try to run gmix it tells me that I do not have a mixer installed or my kernel doesn't support sound. When I run XMMS, it tells me my kernel either doesn't support sound or my card is not configured correctly. I figured my kernel supports sound because I can load sound modules and play audio cd's, so something else must be wrong. What else do I have to do to get sound to work under debian? Thanks, Steve I'm no expert, so if you have any further questions, reply to all, not just to me, so that the list members can throw in their two cents. (1) You need to have support in your kernel for your sound card. There are two methods of doing this; one is to compile it in; the other is to plug it in as a module. Your description indicates that you're using the module method. (2) Playing an audio CD doesn't really depend on the software sound support; most CD drives will start spinning as soon as you put in a CD, and the sound from an audio CD is piped through the audio cable directly to the sound card. What a broken software setup will do is prevent you from using apps to control tracks, volume, etc. About the only thing playing an audio CD proves is that the hardware is functional (which is a good thing to know); it also points strongly to a lack of IRQ conflict (although not necessarily). (3) When you boot up, you should see some info scroll by concerning your sound card. But generally it goes by too fast to see, and you can see it after the fact by running dmesg|more. (4) You should be able to see if you card is recognized, and on which IRQ, by running cat /proc/interrupts (my card is on IRQ 5 and 9). (5) Ditto for IO by running cat /proc/ioports (my card's on 220-2FF and 330-3FF). (6) You can see what modules are loaded by running lsmod (I've got soundcore, sound, uart401, and sb). (7) I'm not sure what cat /proc/devices indicates, but it lists my sound card, so it might be relevant. (8) Perhaps the most informative command is cat /dev/sndstat, which on my machine reports: OSS/Free:3.8s2++-971130 Load type: Driver loaded as a module Kernel: Linux westk03 2.2.18 #2 Thu Jan 18 22:52:14 CST 2001 i586 Config options: 0 Installed drivers: Card config: Audio devices: 0: Sound Blaster Pro (8 BIT ONLY) (3.02) Synth devices: Midi devices: 0: MPU-401 (UART) MIDI 1: Sound Blaster Timers: 0: System clock Mixers: 0: Sound Blaster Perhaps this info will get you a bit further on your quest to get your card working. Good luck! Kent
Re: Can't get sound to work!
Rev. Ferret wrote: It seems that my card is recognized. Everything looks normal except for the output of my /dev/sndstat. I can use apps to control tracks of audio cd's and things like that. I just can't use any mixer apps or play any audio except for cd audio. I can't figure out what's wrong. Using redhat and mandrake I was able to just do sndconfig and pick soundblaster and everything worked. I only seem to be having this problem with debian. The results of cat /proc/interrupts has the following entry: 7:4soundblaster The output of /proc/ioports has this entry: 0220-022f : soundblaster lsmod contains these entries: sb,uart401,sound,soundlow,soundcore cat /dev/sndstat lists the following: OSS/Free:3.8s2++-971130 Load type: Driver loaded as a module Kernel: Linux neuro 2.2.18pre21 #1 Sat Nov 18 18:47:15 EST 2000 i686 Config options: 0 Installed Drivers: Card config: Audio devices: 0: ESS ES1879 AudioDrive (rev 11) (3.01) Synth devices: Midi devices: 0: ESS ES1688 Timers: 0: System clock Mixers: 0: Sound Blaster Looks good from what I can tell. The difference with your /dev/sndstat file are just because you have a different card than mine. Someone else replied (I've already deleted the message, so can't give proper credit; sorry) and suggested it was a permissions problem. Make sure you're in the audio group (as the user, type groups); if not, add yourself (as root, type adduser [yourUserName] audio). Then logout and log back in and test. You might also try a simpler testing scheme for now; from a terminal, run something like play [someWAVfile]; you can do this as root and as a normal user to test permissions issues. I think you're probably getting close. And yes, other distros such as Redhat and Mandrake tend to help you get a system up easier in many cases, but Debian makes maintaining a system much easier than those other distros do. There are also many other advantages to Debian (see the recent Why choose Debian thread for more info), so don't get too disappointed with Debian yet; in the long run you'll really be glad you went Debian.
Re: Can't get sound to work!
Ok, I added myself to user audio and I now get sound from things. There is just one problem. The sound skips. It sounds like a broken record player, where it plays the same bit over and over again. I tried chmod'ing the audio things to world usable, but it didn't help. Any ideas on how to get it to stop skipping? At least I'm getting some sound now :) Marcial Zamora III wrote: - Forwarded message from Rev. Ferret [EMAIL PROTECTED] - Hi, I'm having problems getting my sound blaster 16 working. I used modconf to select the sb module, which in turn selected a bunch of the oss modules. After doing this, I can play audio cd's, but whenever I try to run gmix it tells me that I do not have a mixer installed or my kernel doesn't support sound. When I run XMMS, it tells me my kernel either doesn't support sound or my card is not configured correctly. I figured my kernel supports sound because I can load sound modules and play audio cd's, so something else must be wrong. What else do I have to do to get sound to work under debian? - End forwarded message - I had the same problem, and you can do one of 2 things.. you can add yourself as a user to the audio group, or just chmod all the /dev/mixer devices to where they are world usable.. man chmod =) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Can't get sound to work!
Rev. Ferret wrote: Ok, I added myself to user audio and I now get sound from things. There is just one problem. The sound skips. It sounds like a broken record player, where it plays the same bit over and over again. I tried chmod'ing the audio things to world usable, but it didn't help. Any ideas on how to get it to stop skipping? At least I'm getting some sound now :) Probably one of two things: (1) wrong sound driver or problems with the driver (2) IRQ or IOPort conflict If this is an ISA card, it's probably the second. Do you have a dual-boot with Win9x? If so, what IRQ/io does it report the card being on? Does this match what Linux thinks? Or maybe it's a jumper-configured card, in which case, make sure Linux sees the same settings that the card is actually on. If Linux doesn't match the actual settings, you can feed the settings to the module when it installs. For example, I have a file /etc/modutils/sound which has the two lines: options uart401 irq=9 io=0x330 options sb irq=5 io=0x220 dma=1 hth, Kent
[westk@acu.edu: Re: Can't get sound to work!]
- Forwarded message from Kent West [EMAIL PROTECTED] - Rev. Ferret wrote: Ok, I added myself to user audio and I now get sound from things. There is just one problem. The sound skips. It sounds like a broken record player, where it plays the same bit over and over again. I tried chmod'ing the audio things to world usable, but it didn't help. Any ideas on how to get it to stop skipping? At least I'm getting some sound now :) Probably one of two things: (1) wrong sound driver or problems with the driver (2) IRQ or IOPort conflict If this is an ISA card, it's probably the second. Do you have a dual-boot with Win9x? If so, what IRQ/io does it report the card being on? Does this match what Linux thinks? Or maybe it's a jumper-configured card, in which case, make sure Linux sees the same settings that the card is actually on. If Linux doesn't match the actual settings, you can feed the settings to the module when it installs. For example, I have a file /etc/modutils/sound which has the two lines: options uart401 irq=9 io=0x330 options sb irq=5 io=0x220 dma=1 hth, Kent - End forwarded message - nah, if it wuz a conflict, he would get an error message telling him the device or resource wuz busy.. im thinkin the former, and I forgot wut card it wuz you stated.. repeat it, and I or someone else should be able to tell yaz which is the proper module to load =)
