The "Creative" in the company name "Creative Labs" seems to refer mostly to their way of naming products, though "Confusing" would be more accurate. Anyway, the card known to ALSA as a SoundBlaster AWE (sbawe) is an ISA card, so if, as you say, the card you have is not an ISA card, it is not a "sbawe". If you have a pci sound card that is a real soundblaster and not some other kind that claims to be compatible, it is probably an emu10k1, ens1371, or ens1370. On Sunday 23 March 2003 02:58 pm, Max Webb wrote: > I hope this isn't a stupid question, but I'm fairly inexperienced > with both linux and the ALSA driver. I believe I followed the > instructions closely for building and installing the driver, libs, > and utilities for ALSA; I have a PnP soundblaster 32 (AWE) card (not > isa), and selected the sbawe name for the card from the table at > www.alsa-project.org/alsa-doc/ . Everything seemed to be going okay, > until I got to doing the modprobe to install the module in the > kernel. > > When I issued the "modprobe snd-sbawe" command, I got a failure. > Since modprobe has a "-d" option, I have included it's output below, > in case that yields a clue. I see that the insmod portion of the > command failed, so I also issued that at top level, so you could all > see the way that fails - issued by itself, it finds unresolved > symbols - but I don't know if that is the way it failed inside > modprobe. BTW, the "modprobe snd-seq-oss" failed with "device busy" - > the other two modprobes seemed to succeed. > > Can anyone tell me what I need to do? > > Thanks in advance, > > Max > > /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: init_module: No > such device /lib/modules/2.4.18/kernel/sound/isa/sb/snd-sbawe.o: -- "Can you remember the future? Forget it!"
