From: Paul Mackerras <paulus@cs.anu.edu.au>
To: jquinn@nortelnetworks.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Broken sound?
Date: Fri, 16 Jul 1999 10:49:36 +1000 [thread overview]
Message-ID: <199907160049.KAA23985@tango.anu.edu.au> (raw)
In-Reply-To: <14222.9603.505701.976724@gargle.gargle.HOWL> (jquinn@nortelnetworks.com)
Jerry Quinn <jquinn@nortelnetworks.com> wrote:
> I have a Powercenter 120 with 200Mhz 604e card running vanilla 2.2.10. Sound
> seems to be broken. I do 'cat junk.au > /dev/audio' and get very interesting
> sounding static. Is there a patch in vger I should be using that hasn't made
What is the nature of junk.au? Is it 16-bit or 8-bit, stereo or mono,
linear, mu-law or A-law encoded, and if it's 16-bit, is it big-endian
or little-endian?
When you open /dev/audio, the driver sets it to 8kHz, mono, mu-law
encoded. It's possible that the mu-law decoding is stuffed, I've
never used it myself. I just tried catting a .au file to /dev/audio
and it worked fine, though.
> Also, if I send a sound to /dev/audio, it plays through both internal and
> external speakers. If I try to send the sound to /dev/audio1, bash claims it
> doesn't exist even though it shows up on 'ls'.
You can use one of the many mixer programs to set the volume levels
for the internal speaker and the headphone output.
Paul.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-07-16 0:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-15 18:16 Broken sound? Jerry Quinn
1999-07-15 18:44 ` Joseph Palani Garcia
1999-07-16 0:57 ` Paul Mackerras
1999-07-15 21:34 ` Peter Handel
1999-07-16 0:49 ` Paul Mackerras [this message]
1999-07-19 15:30 ` Jerry Quinn
1999-07-20 6:10 ` Paul Mackerras
1999-07-20 14:23 ` Jerry Quinn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199907160049.KAA23985@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=jquinn@nortelnetworks.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).