It did. I changed my ALSA_CARD setting from "es1371" to "ens1371" and alsa-driver successfully installed. Weird.
On Sat, 2005-02-12 at 17:12 +0100, Holly Bostick wrote:Michael Sullivan wrote:Yes, I understand that, jut just because the module is called es1371, it does not mean that the *card* is also called es1371-- in fact it probably is not, given that alsa-driver does not recognize that as a valid card, or valid card name, or something, during the compile.baby src # modprobe snd-ens1371 modprobe: Can't locate module snd-ens1371 baby src # modprobe ens1371 modprobe: Can't locate module ens1371 baby src # modprobe es1371 baby src #
So what I meant is that maybe your ALSA_CARDS setting should be for ens1371, which might compile the snd-es1371 driver. It would be odd, but it could happen.
Holly
Yes, usually the hardware is named exactly the same as the driver, but on the odd occasion (like this), there is a slight variation. Glad you got it working.
Holly
-- [email protected] mailing list
