zentara wrote:

Hi,

Way back when I started with Linux, I thought setting up awe32 sound on a 2.0.* was a real hard task. I finally master how to do it, and it ran fine. Easy...insmod sound...rmmod sound.

my experiments in the old days never ended up with modules, I got it only working direct in the kernel

Now all of a sudden, in the new 2.2.* kernels, the "easy" OSSFREE drivers are forced on us.

I just went thru the sound docs and to get the damn thing to work I need these commands

insmod soundcore insmod soundlow insmod sound insmod uart401 insmod sb

oss is started with the "soundon" and "stopped" with soundoff command. Is it possible that you are doing it "by hand"? Of course, it wont work with my setup. A cuple of devices is recognised on my card (cat /dev/sndstat) but not *THE* audio thing. No matter what I do or device drivers I select.

and I have to specify module parameters in conf.modules. And there are just as many to remove them.

What's even worse...it sounds like CRAP.

IŽd be happy to get sofar. ;-))

How do you get rid of the OSS SOUND being forced upon you in make menuconfig?

Is this some clever ploy by OSS to force everyone to buy their drivers?

Yes. I miss the old drivers as well. Jürgen -- ========================================== __ _ 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/ 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