So after having no success with RH9 and ALSA I went back to RH8. This time
I'm not even messing with Myth until I can get ALSA working ;-)
Things are good so far except for three quirks:
1. I get the same old RH9 message on login:
Error while initializing the sound driver
device /dev/dsp can't be opened (No such device)
The sound server will continue, using the null output device.
which I have now supressed as it seems to be unrelated
2. When I run:
aplay file.wav
it says:
aplay: main:480: audio open error: No such file or directory
But if I run:
modprobe snd-sb16
and run the exact same aplay command again it opens the wav file
successfully - though no sound comes from the speakers, which leads to...
3. It seems that alsamixer is not saving the settings between reboots even
when I run:
alsactl -f /etc/asound.state store (from the alsactl folder)
after setting the levels, and Capturing & Muting Line In
Anyone know how to stop the need for the modprobe and how to force the mixer
to save?
Thanks
Alex
I'm not even messing with Myth until I can get ALSA working ;-)
Things are good so far except for three quirks:
1. I get the same old RH9 message on login:
Error while initializing the sound driver
device /dev/dsp can't be opened (No such device)
The sound server will continue, using the null output device.
which I have now supressed as it seems to be unrelated
2. When I run:
aplay file.wav
it says:
aplay: main:480: audio open error: No such file or directory
But if I run:
modprobe snd-sb16
and run the exact same aplay command again it opens the wav file
successfully - though no sound comes from the speakers, which leads to...
3. It seems that alsamixer is not saving the settings between reboots even
when I run:
alsactl -f /etc/asound.state store (from the alsactl folder)
after setting the levels, and Capturing & Muting Line In
Anyone know how to stop the need for the modprobe and how to force the mixer
to save?
Thanks
Alex