On Fri, Mar 03, 2000 at 09:22:51AM -0600, Jon Pennington wrote:
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?
AWE64, ISA, PnP is what I'm using. Works fine with OSS. Just wanted to try ALSA and have been so far deeply disappointed.
...........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.
Same here, except that I haven't had the courage with this last kernel to compile since I haven't had the time to figure out the back-out strategies with my reiser file system. So, I've opted to stay stock, for now.
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 :].
Maybe I should give the tar ball a try, since the RPM contains modules that just don't work on my system. What the heck.... -- Brad Shelton On Line Exchange http://online-isp.com -- 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/