On Thu, 02 Mar 2000, Brad Shelton wrote:
Single processor. Basically a stock system, however the stock kernel has OSS support compiled as a module. Is this a problem?
Sound is okay (preferred) as a module. It makes things like IO, DMA, etc to be addressed (in options lines).
Here's the result of my attempts to run alsaconf:
- - 0xa SoundBlaster_AWE_64_PnP << ====== My Card - -
As per the subject line, this is a mistake. Are we talking about two different cards now? Being the paranoid type, I usually build my own kernel within 6 operating hours of getting a machine running, especially when I plan on using external modules for something like ALSA. As part of the kernel-building procedure, I `rm -rf /lib/modules/$VER/*' to get rid of depmod nastiness. After this is done, and the new kernel has been built, installed, and booted, I begin the ALSA procedures, starting with the latest release from ftp.alsa-project.org, and building it myself. NOTE: The es137x family now has limited support for a Sequencer device, as of ALSA-0.5.x :]. -- -=|JP|=- Jon Pennington | Atipa Linux Solutions -o) jpennington@atipa.com | Kansas City, MO /\\ 816-241-2641 x121 | http://www.atipa.com _\_V -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/