Oliver Sampson wrote: > > The sound card matrix for my AudioPCI card says to use the ens1371 > driver. Now would that be the snd-ens1371 driver or the > snd-card-ens1371 driver?
snd-ens1371 is the correct name. The snd-card-foo naming convention went away around the time alsa was accepted into the kernel. I think because Linus preferred it without the "-card". > The output from the modprobe is at the bottom. The output makes me > think that I should be loading something else. Should I be doing > something other than just a modprobe? When I see other modules.conf > files it seems that there's a lot more going on than a simple modprobe > for just one card. If so what else should I consider modprobing? > Right now, I have no modules.conf file at all. The minimum for your modules.conf should look like this: # sound specific modules alias char-major-116 snd alias snd-card-0 snd-ens1371 this loads soundcore.o (the only piece needed from the kernel itself in version earlier than 2.5.5) and registers it as major device number 116. snd-card-0 is then aliased to the name of the module for your soundcard. This is the bare minimum needed in modules.conf, as far as I know. There are other lines that need to be added for OSS emulation if you intend to use its add on modules. But, with only these two lines (with ymfpci replacing ens1371, in my case) I am able to record and playback sounds. And I believe the modules needed for midi are also automatically loaded, though I have yet to test any midi apps on my system. This is explained in the INSTALL file included with the alsa-driver source in the section labeled "modprobe/kmod support". You do need a modules.conf file. It might be a good idea to read the INSTALL file and the following man pages if you haven't already: man modprobe man insmod man modules.conf man depmod hope this helps, Eric Rz. _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
