I ran yast2 to configure the sound in 7.0 it detected my card right. It
in the info into conf.modules (the one where it says 'don't remove')
Well the sound worked but there was also a bunch of noise which I didn't have before. So I was out to compile my own stuff again. How do you
I had a similar problem when trying to get a 16bit soundblaster to work with Quake, each time it was configured with alsa, Quake just froze. So to play it, I had to uninstall the modules loaded by yast2. I did this by allowing yast2 to detect the card, then just clicking back and back or just shutting it down. That way it seems to overwrite the configuration it had previously set up. On Monday, October 30, 2000 8:49 PM, Purple Shirt [SMTP:purpleshirt@hotmail.com] wrote: put properly
remove what yast2 configured? Just taking out the stuff from conf.modules doesn't do it. On boot up it still gives the regular |sound card opl3-sa2 loaded "done"| message. I wouldn't have a problem with it but it also says |alsactl mixer error|.
I can't get the amixer to connect right. I think it is due to my own compiled stuff interfering with something maybe leftover from yast2 configuration. Will future Yast2 give you the choice to remove drivers??? It would be mighty useful.
mk
_________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at http://profiles.msn.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/faq
-- 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/faq