Karen wrote:
Either way modprobe'd modules are lost on reboot even though I thought I had compensated for that by coding the relevant lines in the boot file, as per Jon's recommendation. This bothers me because I am unfamiliar with the SuSE system and suspect I am misunderstanding or simply missing something about the way in which SuSE is handling the boot sequence/system.
I suspect that's the heart of your problem. I recommend doing what I did: edit the file /sbin/init.d/boot.local to include: /sbin/modprobe es1371 [es1370 in my case] /sbin/modprobe sound A good way to check what commands you need there is to issue them as root from the command line and see if sound gets turned on. And if you ever do get your sound working again, do an lsmod to see what modules are around. Paul Abrahams -- 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/