> Under Windows, my sound board is identified as a "Sound Blaster AudioPCI
> 128".
I ahve the same card.. and it didn't work with 7.0 but worked fine with 7.1
and didn't had to use alsa.. what version of mandrake are u using?
>
> I notice that there is a line "alias snd es-1378" already in the
> conf.modules file, which suggests that Mandrake decided that I had an
> Ensoniq 1371 when it first booted. The sound card seems to work fine under
> both Windoze and Mandrake.
then why do u need alsa?.. Under the default mandrake system, teh driver
for u're card is es-1378 i guess (although i feel it shld be es-1371).. and
under alsa the driver name is ens1371
>
> Anyway, I did my best to follow the rather peculiar documentation in the
> ALSA driver package, but it wasn't at all clear what I should call the
> card. I decided that ens-1371 was probably the best bet. But when I issue
you don't decide what to call the driver.. the driver names are
predefined.. the README at the end tells u that.. also alsa-project.org
will has ens1371 as the driver name in front of ur'e card!
> the "modprobe snd-card-ens1371" command after editing conf.modules, I'm
> told that the device "snd" is already in use. Removing the "alias snd
first of all, the entry in conf.modules and u're doing modprobe are not
related. The conf.modules is so taht the next time u boot, the driver will
be loaded automatically. The reason its saying snd already in use is that u
have a driver already installed. the command lsmod will give u the list of
modules (drivers) loaded.. remove all drivers related to snd.. it'll mostly
be only es-1378.. then say
modprobe ens1371 then you need to load 2 more drivers for OSS compatibility
(OSS is the default sound system which comes with linux.. alsa is
relatively new and it'll be the default in development kernel 2.5 onwards)
I dont' remember the two other modules that u need to load.. but the names
are somethign like snd-oss-mixer and snd-oss-something.. its there in the
README file. once you load these 3 modules (drivers) u'll have alsa
working!.. and I guess modprobe automatically updates u're conf.modules
file..
> es1371" line from conf.modules made no difference. (Maybe I should have
> rebooted??? Or is that Windows whispering evil thoughts in my ear?)
>
no no.. u never need to reboot in linux!..
> Does anyone have a conf.modules file correctly configured to use ALSA with
> either a Sound Blaster AudioPCI 128 or an Ensoniq 1371 card??
Yup! as i said i have the exact same card.. the problem is that the company
keeps changing somehting in the h/w and dosn't tell the open-source
people.. so sometimes the default driver dosn't work!
>
> (FWIW, I notice that under Windows, the Sound Blaster AudioPCI 128 mixer is
> called "Ensoniq mixer" in the registry, so I strongly suspect that the two
> terms are synonyms.)
Sound Blaster bought Ensoniq i guess.. PCI 128 was an Ensonique product now
sold under the brand name of sound blaster.. it still uses the ensoniq
chip!
-sarang
>
> Doc Evans
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 6.0.2 -- QDPGP 2.60
> Comment: Key obtainable from servers: ID 0x362912B8
>
> iQA/AwUBObbs32nXrLw2KRK4EQJ/+ACgyfAG6YfaruM31RxEwnYm3jgZEyAAoM8X
> xLFr9Y96iL+XZF/EPGjdLTX1
> =Sm22
> -----END PGP SIGNATURE-----
>
> ----------------------------------------------------------
> D.R. Evans N7DR / G4AMJ [EMAIL PROTECTED]
>
> The last of the Chronicles of the Three Lands, "Phendric",
> has been published:
> http://www.sff.net/people/N7DR/drevans.htp
> ----------------------------------------------------------
