no soundcard output

klytu · 06-04-2007, 11:46 AM

Quote:

Originally Posted by milindlokde

I used the command:
I don't think alsa is controlling the mixer.
The alsamixer is showing volume up on logging in. While the gnome-volume-control is showing volume down.

If you mean that alsa is not controlling the settings in gnome-volume-control, you might be right. When you have the gnome-volume-control GUI app running does the name of your sound card appear in the top of the volume control window? For example, in my correctly functioning set-up it says ¨Volume Control: ESS ES1938 (Solo-1) (Alsa mixer)". If yours shows anything other than your sound card or Alsa Mixer, that´s what we need to change.

Quote:

I checked the help on it. It is says 'setting->preferences' where do I get this?

When gnome-volume-control is running, you can go to Edit>Preferences. But there are no settings there that affect which sound card or mixer is being used. I think you can change those settings with

Code:

gnome-sound-properties

Quote:

The aplay -l showed the device information of my sound card. I think my sound card is fine as I can play sound in Linux, but only that I have to reset the sound level in gnome-volume-control every time I log in as user.

Good, but I should have been more specific in my previous post as to what I wanted to look at for you. Would you please cut and paste the output of

Code:

aplay -l

milindlokde · 06-05-2007, 09:23 AM

Well I have got only one sound card device.

gnome-volume-control did show OSS in its setting and alsaconf and alsamixer has no effect on sound.

I tried to configure sound using debian configuration wizard. It gave this message.

Code:

 
Sound server informational message
Error while initializing the sound driver.
device: default can't be opened for playback (device or resource busy).
The sound server will continue using the null output device.

Now I have no sound at all!

klytu · 06-05-2007, 11:41 AM

Quote:

Originally Posted by milindlokde

Well I have got only one sound card device.

gnome-volume-control did show OSS in its setting and alsaconf and alsamixer has no effect on sound.

I tried to configure sound using debian configuration wizard. It gave this message.

Code:

 
Sound server informational message
Error while initializing the sound driver.
device: default can't be opened for playback (device or resource busy).
The sound server will continue using the null output device.

Now I have no sound at all!

I can understand that this is a frustrating situation for you. I'd like to help but I don't have enough information about the hardware you are using. That was why I asked you twice for the output of

Code:

aplay -l

You could just cut and paste the output into your post. Twice you responded to my request by stating you have only one sound card device. That's fine, but since I am not sitting in front of your computer I have no idea what that device is.

The reason I am asking what specific sound card you have is because for many cards to work properly or get full functionality with Alsa, you'd need to set up an appropriate asoundrc file. If you would prefer to look the information up yourself, check out this site:
http://alsa.opensrc.org/Main_Page

milindlokde · 06-16-2007, 10:34 AM

Quote:

Originally Posted by klytu

You could just cut and paste the output into your post. Twice you responded to my request by stating you have only one sound card device.

Please excuse me for my laziness. Actually I got a blank file for the command:
aplay -l > msg.txt
I put it in this thread.
http://www.linuxquestions.org/questi...d.php?t=560047

Here is the output of the command 'aplay -l'

Code:

**** List of PLAYBACK Hardware Devices ****
card 0: rev50 [VIA 82C686A/B rev50], device 0: VIA 82C686A/B rev50 [VIA 82C686A/B rev50]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Actually, I don't have any sound in gnome session which gives the message :

Code:

Sound server informational message
Error while initializing the sound driver.
device: default can't be opened for playback (device or resource busy).
The sound server will continue using the null output device.

While the sound works fine with KDE session on resetting the sound using gnome-volume-control on every login.

klytu · 06-16-2007, 12:32 PM

Quote:

Originally Posted by milindlokde

Please excuse me for my laziness. Actually I got a blank file for the command:
aplay -l > msg.txt
I put it in this thread.
http://www.linuxquestions.org/questi...d.php?t=560047

Here is the output of the command 'aplay -l'

Code:

**** List of PLAYBACK Hardware Devices ****
card 0: rev50 [VIA 82C686A/B rev50], device 0: VIA 82C686A/B rev50 [VIA 82C686A/B rev50]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Actually, I don't have any sound in gnome session which gives the message :

Code:

Sound server informational message
Error while initializing the sound driver.
device: default can't be opened for playback (device or resource busy).
The sound server will continue using the null output device.

While the sound works fine with KDE session on resetting the sound using gnome-volume-control on every login.

OK. So you have a VIA 82C686 soundcard - the correct ALSA modules that should be loaded for your card are the snd-via82xx series. While you are in a gnome session without sound, what are the outputs of

Code:

lsmod | grep snd

and

Code:

ps -ef

?
The first command is to check to see if the modules for your soundcard are loading (they probably are ...) and the second command is to check to see if there are any sound processes/daemons that are conflicting and competing to use your card at the same time.