From: Jean Francois Ortolo <ortolojf@cybercable.fr>
To: linux-sound@vger.kernel.org
Subject: /dev/audio, /dev/dsp not running for an es1371
Date: Tue, 15 Feb 2000 08:10:14 +0000 [thread overview]
Message-ID: <marc-linux-sound-95060250626587@msgid-missing> (raw)
Hello
I have Linux RedHat6.1 installed, with a Creative Lab
SoundBlaster PCI 128 in the box. It's not a clone,
the chip is a Creative Lab chip.
The sndconfig detects an Ensoniq card, for which it
installs an es1371 module in /etc/conf.modules
While doing this, the generated speech is
well heard by me, so I might believe that
all is all right.
However, a 'cat /dev/sndstat' then reports
"no device with this type", and the /dev/audio0
and /dev/dsp0 don't appear in their directory.
So, a try for reading from anyone either of the
/dev/audio or /dev/dsp with the command:
'dd bs=8k count=5 </dev/audio > sample.au'
or the same with /dev/dsp... It doesn't read
anything, such that the sample.au file
contains always the same character, indicating
that there is only a silence.
So the command 'cat sample.au > /dev/audio'
gives only a 5 seconds silence, the same
with the /dev/dsp interface.
Although, under the Gnome Windows Manager,
the sounds appear fine for any events they
are set up for.
So I can't understand which way Gnome
is successful with its sound managering,
though the /dev/audio and /dev/dsp
interfaces are not available yet.
Any help cheerfully welcome.
Jean Francois
next reply other threads:[~2000-02-15 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-15 8:10 Jean Francois Ortolo [this message]
2000-02-15 13:12 ` /dev/audio, /dev/dsp not running for an es1371
2000-02-15 13:39 ` Thomas Sailer
2000-02-15 16:55 ` Meelis Roos
2000-02-15 16:55 ` Meelis Roos
2000-02-15 20:20 ` /dev/audio, /dev/dsp not running for an es1371 (fwd) Jean Francois Ortolo
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=marc-linux-sound-95060250626587@msgid-missing \
--to=ortolojf@cybercable.fr \
--cc=linux-sound@vger.kernel.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