On Saturday 12 February 2005 20:53, Michael Sullivan wrote:Why does modprobe detect es1371 but not detect ens1371 if they're both for the same card?
On Sat, 2005-02-12 at 20:40 +0000, Peter Ruskin wrote:On Saturday 12 February 2005 16:23, Michael Sullivan wrote:It did. I changed my ALSA_CARD setting from "es1371" to "ens1371" and alsa-driver successfully installed. Weird.Not weird at all. es1371 is the module for the the OSS driver; ens1371 is the module for the ALSA driver.
Sorry, it's snd-ens1371
If it can't be found by modprobe that'll be because you haven't enabled it in your kernel config.
$ modinfo snd-ens1371
author: Jaroslav Kysela <[EMAIL PROTECTED]>, Thomas Sailer <[EMAIL PROTECTED]>
license: GPL
description: Ensoniq/Creative AudioPCI ES1371+
parm: index:Index value for Ensoniq AudioPCI soundcard.
parm: id:ID string for Ensoniq AudioPCI soundcard.
parm: enable:Enable Ensoniq AudioPCI soundcard.
parm: joystick_port:Joystick port address.
vermagic: 2.6.10-gentoo-r7 K7 REGPARM 4KSTACKS gcc-3.3
depends: snd-pcm,gameport,snd-rawmidi,snd,snd-ac97-codec
alias: pci:v00001274d00001371sv*sd*bc*sc*i*
alias: pci:v00001274d00005880sv*sd*bc*sc*i*
alias: pci:v00001102d00008938sv*sd*bc*sc*i*
[
But he's using a 2.4 series kernel, with the alsa-driver package. Isn't the whole point that the alsa module is compiled by the package during emerge? But it isn't, if the alsa module is ens1371, which refused to compile... wait a minute.
I think I see where we're going with this, let me start from the beginning and work it through (somewhat) logically.
OK. The original problem was that the alsa-driver wouldn't compile with the "wrong" card specified (because the card name was wrong in /etc/make.conf). While trying to compile alsa-driver, modprobe would load the OSS driver (from the 2.4 kernel, since that was what was available), and not the alsa driver (because that does not exist in the 2.4 kernel, and the alsa-driver package was not yet compiled).
Fine. We got all that straightened out, and yet we do not have alsa sound, or in fact any sound at all.
Is it possible that this is because 1) Michael still has the OSS drivers enabled in the kernel, and 2) the kernel drivers are loading on boot, so 3) alsasound cannot load the alsa driver for this card because there is already a driver loaded for this card, and 4) Michael has changed all his applications and sound servers to use ALSA (which is not loaded)?
I would 1) do a modprobe -r es1371 to unload the OSS driver, then 2) modprobe snd-ens1371 to see if the alsa driver loads at all. If it does, then I would disable OSS in the kernel, recompile and reboot, at which point it should all work. If it doesn't load, we need to find out where the stupid module is and what's wrong with it.
Am I on the right track here?
Holly
-- [email protected] mailing list
