Mailing List Archive

>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 ;-)

Well, I have Alsa working fine with RH9 - it might be a sound card issue
though (I have a VIA 8235)

>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

I think this is actually 'ARTS' complaining - I'm not sure what ARTS is -
but you don't seem to need it. I always kill off 'artsd' if I remember.

If you find out how to stop it loading at startup, please let me know.

>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?

Hmm, I haven't noticed that here - but then I've only recently got it
working, so I haven't had chance to play much with it.


Paul VPOP3 - Internet Email Server/Gateway
support@pscs.co.uk http://www.pscs.co.uk/

>>>>> On Wed, 23 Apr 2003 16:52:04 -0600, "Alex Davidson" <alexd@synergycsi.com> said:

a> Anyone know how to stop the need for the modprobe and how to force
a> the mixer to save?

Assuming your /etc/modules.conf is correct (the one you posted
before looked okay) /etc/rc.d/init.d/alsasound should do the modprobe
as well as run "alsactl restore" to restore mixer settings. Did you
run "chkconfig --add" on that script so that it is executed during
boot? This should create a link like /etc/rc.d/rc3.d/S87alsasound
that points to that script.
--
Gregorio Gervasio, Jr.
gtgj@pacbell.net

Alex Davidson wrote:
> 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:

All three of these are variations on the ALSA driver not
being loaded yet.

> Anyone know how to stop the need for the modprobe and how to force the mixer
> to save?

Yes. "modprobe" causes the driver modules to be loaded.
This should happen at boot time by a script in your init.d
directory called "alsasound" which should also save and
restore your mixer settings when you shutdown and boot up.

My guess is that your system is not running the "alsasound"
script. See the RedHat docs for how to get this script to
run when you boot or change run levels.

-- bjm

Gregorio Gervasio Jr. wrote:
... Did you
> run "chkconfig --add" on that script so that it is executed during
> boot? This should create a link like /etc/rc.d/rc3.d/S87alsasound
> that points to that script.

Thanks, Gregorio. I remembered that RedHat had a tool to
do this but couldn't remember the name =).

-- bjm

From what I gathered in my searchings:
> I think this is actually 'ARTS' complaining - I'm not sure what ARTS is -
> but you don't seem to need it. I always kill off 'artsd' if I remember.

Artsd is the KDE 2 system sound server.

> If you find out how to stop it loading at startup, please let me know.

I disabled it from starting by getting into the CONTROL CENTER (for me, it's
clicking on the "red" hat [start button] then clicking CONTROL CENTER).
Should bring up the KDE Control System. Go into SOUND AND MULTIMEDIA. Go
into SOUND SYSTEM and uncheck "Start aRts soundserver on KDA Startup."

Hey Gang,

Artsd is the kde sound server, which is redundant if you're using alsa for
everything. I think there's a check box in kcontrol under "sound server"
for canceling startup.

The modprobe can be fixed by adding a line to your /etc/modules.conf:

alias sound-slot-0 snd-sb16


As for the volume settings, I've never had luck there either. I tend to
stay as far away from alsa as possible.. It's still kludgey, despite some
improvements over oss/artsd/esd.

Cheers,
Aaron



On Thu, 24 Apr 2003, Paul Smith wrote:

>
> >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 ;-)
>
> Well, I have Alsa working fine with RH9 - it might be a sound card issue
> though (I have a VIA 8235)
>
> >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
>
> I think this is actually 'ARTS' complaining - I'm not sure what ARTS is -
> but you don't seem to need it. I always kill off 'artsd' if I remember.
>
> If you find out how to stop it loading at startup, please let me know.
>
> >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?
>
> Hmm, I haven't noticed that here - but then I've only recently got it
> working, so I haven't had chance to play much with it.
>
>
> Paul VPOP3 - Internet Email Server/Gateway
> support@pscs.co.uk http://www.pscs.co.uk/
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@snowman.net
> http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users
>

Yeah I had a similar problem even though I have alsa starting with the
init scripts, it would not restore my settings. I just added "alsactl
restore" to my rc.local and everything was happy again.

Ben

-----Original Message-----
From: mythtv-users-bounces@snowman.net
[mailto:mythtv-users-bounces@snowman.net] On Behalf Of Alex Davidson
Sent: Wednesday, April 23, 2003 6:52 PM
To: Discussion about mythtv
Subject: [mythtv-users] ALSA Working But Not Remembering Settings


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

_______________________________________________
mythtv-users mailing list
mythtv-users@snowman.net
http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users