I suspect the problem is somewhere in the alsa setup, so I went and d/l'd the new alsa 0.5.8 off of the SuSE 6.4 updates page. No better. Actually, it griped about not having a libasound.so.1 dependency after install. I linked it to /usr/lib/libasound.so, which made it quit griping, but it didn't necessarily work any better. The updates page said to run alsaconf as root after installing alsa 0.5.8, but that seems to do weird things to konsole, plus it didn't seem to work. WTF? Any ideas?
Update: On a whim, I decided to try and run alsaconf from a plain root console login, instead of konsole su'd to root. Much different results: alsaconf actually seems to run, instead of fubaring the console. Now it runs, 'Detecting Soundcards' or something like that , then 'Found Card: -->CS4236<--' 'Driver: snd-card-cs4236', then 'Do you want to modify /etc/modules.conf' --> Yes, then 'Ok, 1 card(s) configured', and it says it will prepare the card for playing now, yada yada. --> Ok. Now for the spoiler: Loading driver: Starting sound driver: snd-card-cs4236 Starting sound driver: snd-card-cs4236 Setting the PCM volume to 100%, and the Master output volume to 80% amixer: Unable to read group 'Master',0: sucess Could not initialize the mixer, the card was probably not detected correctly # amixer was the program that was griping about libasound.so.1 earlier, so apparenly, it didn't get 'fixed' like I'd thought. Any ideas. Monte -- The Law of Unintended Consequences: Whether or not what you do has the effect you want, it will have three at least you never expected, and one of those usually unpleasant. -- 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