/dev/audio, /dev/dsp not running for an es1371

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

that's exactly my setup as far as that goes.

didn't work for me. I compiled the driver into the kernel instead.

you should not worry about that. /dev/sndstat is as far as I can collect, considered deprecated, and most new drivers don't support it.

i cite the documentation for the driver (i keep it in /usr/src/linux-2.2.14/Documentation/sound/es1371):

# In short, playing a Sun .au file as follows:
#

# cat my_file.au > /dev/dsp
# 
# does not work. Instead, you may use the play script from
# Chris Bagwell's sox-12.14 package (available from the URL
# below) to play many different audio file formats.

you should read the whole fine manual, actually.

���

now if someone could tell me how to use the joystick port for midi on this card, everything would be perfect :-)
____________________________________________________________________________
home page @ -=> http://www.mnf.nu/magog
listening to 02-Gary_Numan-The_Aircrash_Bureau.mp3
{pung ghap HoS.} - Mercy or power.

rev7 chip (lspci)? If so you need to use 2.2.15pre

Tom

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 ([email protected])

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 ([email protected])

You are right
I just didn't set the Mic input to "R" with aumix... All right now, all works well.
Thank you very very much.

Jean Francois

---------- Forwarded message ----------
Date: Tue, 15 Feb 2000 18:55:55 +0200
From: Meelis Roos <[email protected]>
To: [email protected]
Subject: Re: /dev/audio, /dev/dsp not running for an es1371

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 ([email protected])