fixing sound

Hello,

I seem unable to get any audio out of my debian installation. The
relevant lines from lsmod shows me:

emu10k1 60812 0
ac97_codec 13428 0 [emu10k1]
sound 58440 0 [emu10k1]
soundcore 3972 7 [emu10k1 sound]

And, I am unable to hear audio when I try:
# cat chimes.wav > /dev/dsp

/dev/dsp does exist, though.

# uname -a
Linux gandalf 2.4.25-1-k7 #1 Tue Feb 24 14:24:28 EST 2004 i686 GNU/Linux

What must I try? Also, I am pretty sure that I have'nt detailed enough
info. here - what other things do I need to list out?

Thanks,

-K

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: fixing sound

At 11:31 PM 4/24/2004 -0400, Karthik Vishwanath wrote:
>Hello,
>
>I seem unable to get any audio out of my debian installation. The
>relevant lines from lsmod shows me:
>
>emu10k1 60812 0
>ac97_codec 13428 0 [emu10k1]
>sound 58440 0 [emu10k1]
>soundcore 3972 7 [emu10k1 sound]
>
>And, I am unable to hear audio when I try:
># cat chimes.wav > /dev/dsp
>
>/dev/dsp does exist, though.
>
># uname -a
>Linux gandalf 2.4.25-1-k7 #1 Tue Feb 24 14:24:28 EST 2004 i686 GNU/Linux
>
>What must I try? Also, I am pretty sure that I have'nt detailed enough
>info. here - what other things do I need to list out?


1. Check (and tell us, if need be) what "lspci" reports about the sound
hardware. It's hard to troubleshoot sound with no hardware information.

2. Check "ls -l /dev/dsp". Make sure it points to the right place. It
should look something like this:

crw-rw---- 1 root audio 14, 3 Mar 14 2002 /dev/dsp

3. Related to #1. please tell us what you know (independently of lspci)
about the sound hardware you are using. Are you certain (if so, how) that
the emu10k1 module is the right one?

4. Might this be an IRQ issue? Check /proc/interrupts before and after you
try to play a sound file. Make sure the access count for the audio device
has incremented. An example from one of my systems (different sound driver):

5: 134002133 XT-PIC es1371

5. Has this sound hardware ever worked previously ... for example, with an
earlier Linux kernel or a different OS?

6. Related to 5 ... are you sure your sound cabling is right and your
speakers (or headphones) work? A long shot, but I'm trying to cover all
possibilities you did not address.

7. Basic questions: Debian Woody, Sid, or Sarge? Stock or custom kernel?

8. Throughout my response, I've interpreted "unable to hear audio" as
meaning that the system fails silently ... that is, the "cat" process runs
to its conclusion without objection, but no sound actually comes out. (BTW,
this isn't a very good way to play sound files, but it should make noise
nonetheless.) If this interpretation is wrong, please correct it with
appropriate details.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: fixing sound

On Sun, 25 Apr 2004, at 8:36am, Ray Olszewski wrote:

> 1. Check (and tell us, if need be) what "lspci" reports about the sound
> hardware. It's hard to troubleshoot sound with no hardware information.

Heres the "relevant" info. from lspci -
0000:00:09.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1
(rev 04)
0000:00:09.1 Input device controller: Creative Labs SB Live! MIDI/Game
Port (rev 01)

> 2. Check "ls -l /dev/dsp". Make sure it points to the right place. It
> should look something like this:
>
> crw-rw---- 1 root audio 14, 3 Mar 14 2002 /dev/dsp

# ls -lF /dev/dsp
crw-rw---- 1 root audio 14, 3 Mar 14 2002 /dev/dsp

> 3. Related to #1. please tell us what you know (independently of lspci)
> about the sound hardware you are using. Are you certain (if so, how) that
> the emu10k1 module is the right one?
> [snip]
>
> 5. Has this sound hardware ever worked previously ... for example, with an
> earlier Linux kernel or a different OS?
>
> 6. Related to 5 ... are you sure your sound cabling is right and your
> speakers (or headphones) work? A long shot, but I'm trying to cover all
> possibilities you did not address.
>

I am certain that emu10k1 is the right driver (for SBLive) - my previous
installation of redhat used this driver and it worked fine. I think the
basic cabling and connection to speakers are fine as well, since the
soundcard works alright under windoze.

> 4. Might this be an IRQ issue? Check /proc/interrupts before and after you
> try to play a sound file. Make sure the access count for the audio device
> has incremented. An example from one of my systems (different sound driver):
>
> 5: 134002133 XT-PIC es1371

Yes, the access count did increment.

> 7. Basic questions: Debian Woody, Sid, or Sarge? Stock or custom kernel?
>

Debian sarge installation, stock kernel.

> 8. Throughout my response, I've interpreted "unable to hear audio" as
> meaning that the system fails silently ... that is, the "cat" process runs
> to its conclusion without objection, but no sound actually comes out. (BTW,
> this isn't a very good way to play sound files, but it should make noise
> nonetheless.) If this interpretation is wrong, please correct it with
> appropriate details.
>

I am sorry, I should've specified -- its not as if there is silence, I
hear some weird buzzing noises on the cat command.

Other things are that trying to play mp3 files via xmms gives a dialog box
asking me to check:
That the soundcard is configured alright
The correct output plugin is selected
No other program is accessing the soundcard

I started with the first suggestion -- the output plugin selected is the
OSS driver, and I don't think there are any other applications trying to
access the soundcard.


Thanks,

-K

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: fixing sound

At 05:20 PM 4/25/2004 -0400, Karthik Vishwanath wrote:
[...]
> > 8. Throughout my response, I've interpreted "unable to hear audio" as
> > meaning that the system fails silently ... that is, the "cat" process runs
> > to its conclusion without objection, but no sound actually comes out.
> (BTW,
> > this isn't a very good way to play sound files, but it should make noise
> > nonetheless.) If this interpretation is wrong, please correct it with
> > appropriate details.
> >
>
>I am sorry, I should've specified -- its not as if there is silence, I
>hear some weird buzzing noises on the cat command.

Oh, that's VERY different. You are getting sound, just not the sound you
want to get. The "cat" approach is not a good way to try to play music
files, not even .wav files ... the exact output you'll get is a bit
unpredictable ... but "weird buzzing noises" are a definite possibility,
even from a working system.

See the next set of comments below.

>Other things are that trying to play mp3 files via xmms gives a dialog box
>asking me to check:
>That the soundcard is configured alright
>The correct output plugin is selected
>No other program is accessing the soundcard

What userid are you using to run xmms? It needs either to be root or some
userid that is a member of group "audio", based on this part of your
response (deleted above):

># ls -lF /dev/dsp
>crw-rw---- 1 root audio 14, 3 Mar 14 2002 /dev/dsp

If it isn't, you'll get the message from xmms that you report (it's a bit
misleading, but it really is the one you get ... I had this exact problem
on a new system last week), since xmms is running under a userid that does
not have permission to write to /dev/dsp . Since (I think) your system has
you as the only real user, you can select the easy fix of

chmod 666 /dev/dsp

to avoid this problem. Or try running (say) mpg123 as root. Or add your
preferred userid to the audio group (edit /etc/group, then do a brand new
login using the userid) and try xmms again.

>I started with the first suggestion -- the output plugin selected is the
>OSS driver, and I don't think there are any other applications trying to
>access the soundcard.





-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: fixing sound

I usually run as 'karthik', and for most, I am the only one who really
works on this machine. The quick fix worked -- xmms is able to play
mp3s now. Thanks!!

-K

On Sun, 25 Apr 2004, at 2:36pm, Ray Olszewski wrote:

> At 05:20 PM 4/25/2004 -0400, Karthik Vishwanath wrote:
> [...]
> > > 8. Throughout my response, I've interpreted "unable to hear audio" as
> > > meaning that the system fails silently ... that is, the "cat" process runs
> > > to its conclusion without objection, but no sound actually comes out.
> > (BTW,
> > > this isn't a very good way to play sound files, but it should make noise
> > > nonetheless.) If this interpretation is wrong, please correct it with
> > > appropriate details.
> > >
> >
> >I am sorry, I should've specified -- its not as if there is silence, I
> >hear some weird buzzing noises on the cat command.
>
> Oh, that's VERY different. You are getting sound, just not the sound you
> want to get. The "cat" approach is not a good way to try to play music
> files, not even .wav files ... the exact output you'll get is a bit
> unpredictable ... but "weird buzzing noises" are a definite possibility,
> even from a working system.
>
> See the next set of comments below.
>
> >Other things are that trying to play mp3 files via xmms gives a dialog box
> >asking me to check:
> >That the soundcard is configured alright
> >The correct output plugin is selected
> >No other program is accessing the soundcard
>
> What userid are you using to run xmms? It needs either to be root or some
> userid that is a member of group "audio", based on this part of your
> response (deleted above):
>
> ># ls -lF /dev/dsp
> >crw-rw---- 1 root audio 14, 3 Mar 14 2002 /dev/dsp
>
> If it isn't, you'll get the message from xmms that you report (it's a bit
> misleading, but it really is the one you get ... I had this exact problem
> on a new system last week), since xmms is running under a userid that does
> not have permission to write to /dev/dsp . Since (I think) your system has
> you as the only real user, you can select the easy fix of
>
> chmod 666 /dev/dsp
>
> to avoid this problem. Or try running (say) mpg123 as root. Or add your
> preferred userid to the audio group (edit /etc/group, then do a brand new
> login using the userid) and try xmms again.
>
> >I started with the first suggestion -- the output plugin selected is the
> >OSS driver, and I don't think there are any other applications trying to
> >access the soundcard.
>
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
>

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

zero-sized /dev/dsp after forced shutdown

Hello,

Experimenting with xmms-plugins on a debian (sid) machine running 2.4.18
on an athlon 2100 chip caused the machine to hang within X while xmms was
running. I had to resort to rebooting the machine after logging in
remotely. After the machine rebooted, I am unable to hear audio. I am able
to set the mixer controls with aumix and load/play songs in xmms, but hear
no sound output (the cables are connected and fine). lsmod did not show my
sound-card module (emu10k1) loaded, so I modprob'd for it. Post modprobe
heres the output of lsmod | grep emu10k1:

emu10k1 55648 0
ac97_codec 9696 0 [emu10k1]
sound 54508 0 [emu10k1]
soundcore 3652 7 [emu10k1 sound]

ls -lF /dev/dsp* shows:
crw-rw-rw- 1 root audio 14, 0 Mar 14 2002 /dev/dsp
crw-rw-rw- 1 root audio 14, 19 Mar 14 2002 /dev/dsp1
crw-rw-rw- 1 root audio 14, 35 Mar 14 2002 /dev/dsp2
crw-rw-rw- 1 root audio 14, 51 Mar 14 2002 /dev/dsp3

ls -lF /dev/mixer* gives:
crw-rw-rw- 1 root audio 14, 0 Mar 14 2002 /dev/mixer
crw-rw-rw- 1 root audio 14, 16 Mar 14 2002 /dev/mixer1
crw-rw-rw- 1 root audio 14, 32 Mar 14 2002 /dev/mixer2
crw-rw-rw- 1 root audio 14, 48 Mar 14 2002 /dev/mixer3

I thought there was something strange about the sizes being 0 bytes. What
may be happening, and how can I fix this?

Thanks,

-K


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs