Jon Pennington wrote:
"Paul W. Abrahams"
said: You were right: what I thought was an es1371 was actually, according to lspci, an es1370. But I still can't get to the point where `cat /dev/sndstat' yields anything useful. It just says `device not found'.
Common. Creative did a horrible job with labeling the cards. BTW: `cat /dev/sndstat' won't do jack with an es137x anyway.
Any idea why not? That certainly contradicts the Sound Howto, which seems to be saying that `cat /dev/sndstat' is the critical test. But if that isn't the critical test, what is the test that the sound modules are installed correctly?
I've tried both compiling sound support modularly and compiling it into the kernel.
Stop. Back the train up. Reinstall a standard SuSE kernel (using YaST), and remove the modules directory that you created. Reinstall kernmod.rpm, and clear out whatever changes you made to /etc/modules.conf.
I'm reluctant to do that if there's any alternative. The problem is that I'm running SuSE 6.2. I'm concerned about trying to use a much later SuSE kernel with it. (Plus the pain of the long download and reimporting all my other config options.)
Reboot your machine with the SuSE kernel, and *comment* these three lines in /etc/modules.conf:
alias char-major-14 off alias sound off alias midi off
Then uncomment these lines in the same file:
# alias char-major-14 es1370 # options es1370 joystick=1
I had already done that.
After that, your modules will load on-demand. If you're paranoid, add a line like so to /sbin/init.d/boot.local:
modprobe es1370
I had the impression that /sbin/init.d/boot was supposed to do the load. Was I wrong? 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/