Jesse McDonnell wrote:

On Sun, 28 Feb 1999, Juergen Braukmann wrote:

Juergen and zentara,

I'm haven't made the transition yet to 2.2.*, I'm still with 2.0.36 but my experience was that the alsa driver was easier to set up and produced much better sound than the sound I compiled into the kernel. My card is a Creative Ensoniq with ES1371 chipset.

I've read on the alsa-users list accounts of people installing the alsa driver because of the poor quality of the sound with the new 2.2._ kernels. I don't remember if there were postings for all 2.2.* kernels. The alsa driver is fully oss-compatible for all the sound cards it supports and is Open Source. If you haven't done so already, check out the home page at alsa.jcu.cz to see if your cards are supported.

The alsa-users mailing list archive at the same address is also a great resource for troubleshooting purposes.

Good Luck,

Hi, I went a bit further using a good collection of hints (Zentara, your last two mails were quite helpful in the end) I was on the brink to get it working. Zentara, I tried to follow your remarks about these different modules to load. found out: 1. soundon/soundoff won't work 2. a "modprobe sound" would load all modules. I had missed to run isapnp (because I thought I wouldn't need it, s.o. hinted that earlier, but I forgot about that halfway), Zentaras remark and quoted files rang that bell. Ran all this, logged into X and heared the famous last words that ironicly were as false as the "original" speaker HAL9000. Had a quick think about, all files OK, well "reboot" time, to see everything work from bootup. Next thing: KERNEL PANIC!. suspicion. Did I do my work accidently with the working 2.0.26, all for peanuts? a few reboot attemts with 2.0.36 KERNEL PANIC, including the Messages saing that there's a problem with the hard drive. After that, JUERGEN PANIC. Emergency system ..... well *all* my (and this is serious) partitions that had been mounted looked like a duck that had been hunted with an anti tank grenade. thousends of errors, duplicate blocks, everything you might think of. I have to add, that I changed some setup options (once in there to look for the printer port... I could not resist changeing some), in this case probably something concerning HD access and DMA. The disc was not broken (wish it was!), since I could reformat it. So it'll be a brand new 6.0 install that. Luckyly, I still had my ols 5.3 on the other disc. I hope all this was caused by my foolishness and not by a severe bug in kernel 2.2.2. Just for the sake of others. Juergen -- ========================================== __ _ Juergen Braukmann mail: brauki@cityweb.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu| /\\ /__/ / _ \/ // /\ \/ / ==========================================_\_v __/_/_//_/\_,_/ /_/\_\ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>