Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: linux-sound@vger.kernel.org
Subject: Re: /dev/audio, /dev/dsp not running for an es1371
Date: Tue, 15 Feb 2000 16:55:55 +0000	[thread overview]
Message-ID: <marc-linux-sound-95063495617197@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95060250626587@msgid-missing>

JFO>   The sndconfig detects an Ensoniq card, for which it
JFO> installs an es1371 module in /etc/conf.modules

Correct, This card uses an Ensoniq chip. Creative bought Ensoniq to get
a PCI card out quickly.

JFO>   However, a 'cat /dev/sndstat' then reports
JFO> "no device with this type", and the /dev/audio0
JFO> and /dev/dsp0 don't appear in their directory.

/dev/sndstat only works for drivers that use the OSS API. Newer cards
(esp. PCI) us a more low-level API (sound_core) and so it's normal that
sndstat doesn't know about them.

JFO>   So, a try for reading from anyone either of the 
JFO> /dev/audio or /dev/dsp with the command:
JFO>  'dd bs=8k count=5 </dev/audio > sample.au'
JFO> or the same with /dev/dsp... It doesn't read
JFO> anything, such that the sample.au file
JFO> contains always the same character, indicating
JFO> that there is only a silence.

Beware that this card may need a different type of microphone. Our
1371's down't work with the old microphones that we use with SB16.

JFO>   Although, under the Gnome Windows Manager,
JFO> the sounds appear fine for any events they
JFO> are set up for.

So it probably just works as much as it is supposed to. Read the docs
about ES137* drivers!

-- 
Meelis Roos (mroos@tartu.cyber.ee)

  parent reply	other threads:[~2000-02-15 16:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-15  8:10 /dev/audio, /dev/dsp not running for an es1371 Jean Francois Ortolo
2000-02-15 13:12 ` 
2000-02-15 13:39 ` Thomas Sailer
2000-02-15 16:55 ` Meelis Roos
2000-02-15 16:55 ` Meelis Roos [this message]
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-95063495617197@msgid-missing \
    --to=mroos@linux.ee \
    --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