In article <393662D6.A068FDA5@neuronet.pitt.edu>, Rafael E. Herrera
I use the same kind of card. I think you copied the wrong entries in your email, from your lspci output you should be using the es1371 driver. In any case, I have modules.conf look like this:
#alias char-major-14 off #alias sound off #alias midi off
alias char-major-14 es1371 options es1371 joystick=0x200
these entries match my /etc/modules.conf - I think I confused the issue by quoting Jon who was referring to the (similar) treatment of es1370.
run depmod afterwards and everything is ready to go. After the next boot if you run 'modprobe es1371' it should load all the necessary drivers (soundcore, sound, etc.), that is what depmod should setup. If they don't load then something is not working right, although I never had problems with that setup.
'modprobe es1371' loads 'soundcore' but not 'sound' and 'soundlow', even after I added them to /sbin/init.d/boot.local which makes me think I should track back through the boot sequence more carefully. This install was the standard SuSE install inasmuch as nothing 'extra' was compiled in and the soundcard configuration was done using the installer (although as I said I am new to SuSE and yast, and a bit too limited keyboard wise to try anything 'non standard' at the first run of a new distribution <g>). However the sound configuration did seem to add in extra drivers which I wouldn't have normally expected but assumed they were a part of the standard SuSE build (in fact the whole kernel seems big to me). I haven't taken them out - maybe I should - although I have edited /etc/modules.conf in the recommended way? If I do an lsmod immediately after boot I get this lot:
Module Size Used by snd-pcm-oss 16680 0 (autoclean) snd-pcm-plugin 12840 0 (autoclean) [snd-pcm-oss] snd-mixer-oss 4244 0 (autoclean) [snd-pcm-oss] snd-card-ens1371 2016 0 snd-ens1371 9404 0 [snd-card-ens1371] snd-pcm 28504 0 [snd-pcm-oss snd-pcm-plugin snd- ens1371] snd-timer 8032 0 [snd-pcm] snd-rawmidi 9432 0 [snd-ens1371] snd-seq-device 3360 0 [snd-rawmidi] snd-ac97-codec 23904 0 [snd-ens1371] snd-mixer 22576 0 [snd-mixer-oss snd-ens1371 snd- ac97-codec] snd 31852 1 [snd-pcm-oss snd-pcm-plugin snd-mixer- oss snd-card-ens1371 snd-ens1371 snd-pcm snd-timer snd-rawmidi snd-seq- device snd-ac97-codec snd-mixer] soundcore 2564 5 [snd] usb-uhci 17000 0 (unused) serial 42612 0 (autoclean) memstat 1476 0 (unused) usbcore 42344 1 [usb-uhci] which seems like rather a lot to me... And I still have to add the others manually.
This driver does not support .au files. That may be why your attempts to record using the /dev/audio device failed. /dev/audio is for .au files only, you should use /dev/dsp instead. I mostly play sounds, don't record much and I'm not familiar with your voice recognition software. You may need first to load the right drivers, set your software with the right devices and try again.
I definitely can create sound files using /dev/audio, and poor quality files using /dev/dsp by using the following method from console (using console to eliminate wm/desktop factors): dd bs=8k count=4 /tmp/test.au (or .wav) cat /tmp/test.au (or .wav) > /dev/audio (or dsp). but the volume is poor. If the es1371 drivers do not support .au maybe other drivers loaded are conflicting/impacting? Like you sound was just for music for me until I hit the world of VR software - now I realise how little I know about it <wry grin> I definitely need to find out more about the underlying files within ViaVoice for Linux.
You may want to try the ALSA drivers, a replacement to the above. Install the alsa package, comment all the above, remove the modules if loaded and run 'alsaconf'. It should detect your sound card and add the necessary entries to modules.conf. The package has a mixer controller, so you will have more control of the input/output levels, etc.
By the way, the ALSA drivers from the SuSE CDs are for version 2.2.14 of the kernel. If you upgrade to 2.2.15 or 2.2.16 you will have to recompile the package from sources.
Thanks for that - I was intending to upgrade the kernel once sound was under control. It may well be worth trying the ALSA drivers but it is just frustrating to me that I did have it working briefly with the currently loaded drivers plus a modprobe to get 'sound' and 'soundlow' and now cannot get it back. I must have change something without realising it. I just can't get away from that nagging feeling that I have missed/overlooked/done something obvious here and that maybe I just am not seeing the wood for the trees. Many thanks for your feedback, regards, -- Karen Hunter-Jones karen@lspace.org -- 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/