10:13 a.m.
I see that /etc/init.d/halt runs alsactl store to save the current mixer
settings.
I cannot find anywhere in initscript which restores the saved mixer settings
when booting. Looks like a bug.
10:24 a.m.
Am Sa, den 24.07.2004 schrieb Sam Varshavchik um 17:13:
I see that /etc/init.d/halt runs alsactl store to save the current
mixer
settings.
That is correct.
I cannot find anywhere in initscript which restores the saved mixer
settings
when booting. Looks like a bug.
Not a bug. Have you looked at the /etc/modprobe.conf and faced what
happens when the soundcard module(s) are loaded?
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.6-1.435.2.3.ad.umlsmp
Serendipity 17:23:07 up 2 days, 2:11, load average: 0.31, 0.33, 0.21
10:49 a.m.
Alexander Dalloz writes:
Am Sa, den 24.07.2004 schrieb Sam Varshavchik um 17:13:
> I see that /etc/init.d/halt runs alsactl store to save the current mixer
> settings.
That is correct.
> I cannot find anywhere in initscript which restores the saved mixer settings
> when booting. Looks like a bug.
Not a bug. Have you looked at the /etc/modprobe.conf and faced what
happens when the soundcard module(s) are loaded?
Yeah:
install sound-slot-0 /sbin/modprobe pcspkr && /sbin/modprobe --first-time
--ignore-install sound-slot-0 && { /bin/aumix-minimal -f /etc/.aumixrc -L
/dev/null 2>&1 || :; }
/etc/.aumixrc is _not_ where alsactl saves the mixer settings.
10:55 a.m.
Am Sa, den 24.07.2004 schrieb Sam Varshavchik um 17:49:
install sound-slot-0 /sbin/modprobe pcspkr && /sbin/modprobe
--first-time
--ignore-install sound-slot-0 && { /bin/aumix-minimal -f /etc/.aumixrc -L
>/dev/null 2>&1 || :; }
/etc/.aumixrc is _not_ where alsactl saves the mixer settings.
Can't say where your modprobe.conf settings come from, maybe old entries
from times before an upgrade?
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 &&
/usr/sbin/alsactl restore >/dev/null 2>&1 || :
remove snd-emu10k1 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-emu10k1
This is what is set for my sound module. It is proper and does not call
aumix. Still not a bug :)
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.6-1.435.2.3.ad.umlsmp
Serendipity 17:53:21 up 2 days, 2:41, load average: 0.46, 0.25, 0.22
10:58 a.m.
On Sat, 24 Jul 2004 11:49:12 -0400, Sam Varshavchik wrote:
Alexander Dalloz writes:
> Am Sa, den 24.07.2004 schrieb Sam Varshavchik um 17:13:
>
>> I see that /etc/init.d/halt runs alsactl store to save the current mixer
>> settings.
>
> That is correct.
>
>> I cannot find anywhere in initscript which restores the saved mixer settings
>> when booting. Looks like a bug.
>
> Not a bug. Have you looked at the /etc/modprobe.conf and faced what
> happens when the soundcard module(s) are loaded?
Yeah:
install sound-slot-0 /sbin/modprobe pcspkr && /sbin/modprobe --first-time
--ignore-install sound-slot-0 && { /bin/aumix-minimal -f /etc/.aumixrc -L
>/dev/null 2>&1 || :; }
/etc/.aumixrc is _not_ where alsactl saves the mixer settings.
This is not Fedora Core 2, but from Fedora Core 1. Assumably, you did an
upgrade to FC2. FC2's modprobe.conf runs alsactl, not aumix-minimal.
11:07 a.m.
Michael Schwendt writes:
On Sat, 24 Jul 2004 11:49:12 -0400, Sam Varshavchik wrote:
> Alexander Dalloz writes:
>
> > Am Sa, den 24.07.2004 schrieb Sam Varshavchik um 17:13:
> >
> >> I see that /etc/init.d/halt runs alsactl store to save the current mixer
> >> settings.
> >
> > That is correct.
> >
> >> I cannot find anywhere in initscript which restores the saved mixer settings
> >> when booting. Looks like a bug.
> >
> > Not a bug. Have you looked at the /etc/modprobe.conf and faced what
> > happens when the soundcard module(s) are loaded?
>
> Yeah:
>
> install sound-slot-0 /sbin/modprobe pcspkr && /sbin/modprobe --first-time
> --ignore-install sound-slot-0 && { /bin/aumix-minimal -f /etc/.aumixrc -L
> >/dev/null 2>&1 || :; }
>
> /etc/.aumixrc is _not_ where alsactl saves the mixer settings.
This is not Fedora Core 2, but from Fedora Core 1. Assumably, you did an
upgrade to FC2. FC2's modprobe.conf runs alsactl, not aumix-minimal.
Well then, the bug must be in anaconda not updating the module
configuration. Anaconda should've fixed this.
11:02 a.m.
On Saturday 24 July 2004 11:49, Sam Varshavchik wrote:
Alexander Dalloz writes:
> Am Sa, den 24.07.2004 schrieb Sam Varshavchik um 17:13:
>> I see that /etc/init.d/halt runs alsactl store to save the
>> current mixer settings.
>
> That is correct.
>
>> I cannot find anywhere in initscript which restores the saved
>> mixer settings when booting. Looks like a bug.
>
> Not a bug. Have you looked at the /etc/modprobe.conf and faced
> what happens when the soundcard module(s) are loaded?
Yeah:
install sound-slot-0 /sbin/modprobe pcspkr && /sbin/modprobe
--first-time --ignore-install sound-slot-0 && { /bin/aumix-minimal
-f /etc/.aumixrc -L
>/dev/null 2>&1 || :; }
/etc/.aumixrc is _not_ where alsactl saves the mixer settings.
Same problem I had, and the alsa docs are non-existant on that
subject.
If thats the case, has anyone got a *working* modprobe.conf entry and
could paste it here?
--
Cheers, Gene
There are 4 boxes to be used in defense of liberty.
Soap, ballot, jury, and ammo.
Please use in that order, starting now. -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004,
Maurice E. Heskett, all rights reserved.
9:34 p.m.
On Sat, 2004-07-24 at 11:02, Gene Heskett wrote:
On Saturday 24 July 2004 11:49, Sam Varshavchik wrote:
>Alexander Dalloz writes:
>> Am Sa, den 24.07.2004 schrieb Sam Varshavchik um 17:13:
>>> I see that /etc/init.d/halt runs alsactl store to save the
>>> current mixer settings.
>>
>> That is correct.
>>
>>> I cannot find anywhere in initscript which restores the saved
>>> mixer settings when booting. Looks like a bug.
>>
>> Not a bug. Have you looked at the /etc/modprobe.conf and faced
>> what happens when the soundcard module(s) are loaded?
>
>Yeah:
>
>install sound-slot-0 /sbin/modprobe pcspkr && /sbin/modprobe
> --first-time --ignore-install sound-slot-0 && { /bin/aumix-minimal
> -f /etc/.aumixrc -L
>
>>/dev/null 2>&1 || :; }
>
>/etc/.aumixrc is _not_ where alsactl saves the mixer settings.
Same problem I had, and the alsa docs are non-existant on that
subject.
If thats the case, has anyone got a *working* modprobe.conf entry and
could paste it here?
These are the 2 lines from modprobe.conf that work for me
---------------
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx &&
/usr/sbin/alsactl restore >/dev/null 2>&1 || :
remove snd-via82xx { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-via82xx
-------------
Hope this helps.
The only thing that should change for you would be the module being
loaded.
11:13 p.m.
On Sat, 2004-07-24 at 11:02, Gene Heskett wrote:
On Saturday 24 July 2004 11:49, Sam Varshavchik wrote:
>Alexander Dalloz writes:
>> Am Sa, den 24.07.2004 schrieb Sam Varshavchik um 17:13:
>>> I see that /etc/init.d/halt runs alsactl store to save the
>>> current mixer settings.
>>
>> That is correct.
>>
>>> I cannot find anywhere in initscript which restores the saved
>>> mixer settings when booting. Looks like a bug.
>>
>> Not a bug. Have you looked at the /etc/modprobe.conf and faced
>> what happens when the soundcard module(s) are loaded?
>
>Yeah:
>
>install sound-slot-0 /sbin/modprobe pcspkr && /sbin/modprobe
> --first-time --ignore-install sound-slot-0 && { /bin/aumix-minimal
> -f /etc/.aumixrc -L
>
>>/dev/null 2>&1 || :; }
>
>/etc/.aumixrc is _not_ where alsactl saves the mixer settings.
Same problem I had, and the alsa docs are non-existant on that
subject.
If thats the case, has anyone got a *working* modprobe.conf entry and
could paste it here?
--
Cheers, Gene
This is what is put into my modprobe.conf when kudzu configures my sound
card. I did a clean install of FC2, and it did this by itself so sound
just works for me.
Did you do an upgrade or an install?
alias snd-card-0 snd-via82xx
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx &&
/usr/sbin/alsactl restore >/dev/null 2>&1 || :
remove snd-via82xx { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-via82xx
NOTE: lines are wrapped by the mailer. 3 lines above beginning with
alias, install, and remove.
The segment of the install line that says "/usr/sbin/alsactl restore" is
probably what you are missing.
11:34 p.m.
I don't know why I sent this. :(
I was obviously in the wrong part of my list since the one I replied to
is more than 6 weeks old.
Please ignore.
On Sat, 2004-09-11 at 23:13, Jeff Vian wrote:
On Sat, 2004-07-24 at 11:02, Gene Heskett wrote:
> On Saturday 24 July 2004 11:49, Sam Varshavchik wrote:
> >Alexander Dalloz writes:
> >> Am Sa, den 24.07.2004 schrieb Sam Varshavchik um 17:13:
> >>> I see that /etc/init.d/halt runs alsactl store to save the
> >>> current mixer settings.
> >>
<snip)
11:41 p.m.
On Saturday 11 September 2004 23:34, Jeff Vian wrote:
I don't know why I sent this. :(
I was obviously in the wrong part of my list since the one I
replied to is more than 6 weeks old.
Please ignore.
Careful! You're only allowed two screw-ups in one calendar month
and we're counting!
Regards, Mike Klinke
11 a.m.
On Saturday 24 July 2004 11:13, Sam Varshavchik wrote:
I see that /etc/init.d/halt runs alsactl store to save the current
mixer settings.
I cannot find anywhere in initscript which restores the saved mixer
settings when booting. Looks like a bug.
I put that line to do that in my rc.local file quite a while back. It
seems to do the job ok, and I do see it flying by in the boot window.
But then my rc.local would probably give purists a tummy ache cause
I'm even starting setiathome with it.
--
Cheers, Gene
There are 4 boxes to be used in defense of liberty.
Soap, ballot, jury, and ammo.
Please use in that order, starting now. -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004,
Maurice E. Heskett, all rights reserved.
9:31 p.m.
On Sat, 2004-07-24 at 11:00, Gene Heskett wrote:
On Saturday 24 July 2004 11:13, Sam Varshavchik wrote:
>I see that /etc/init.d/halt runs alsactl store to save the current
> mixer settings.
>
>I cannot find anywhere in initscript which restores the saved mixer
> settings when booting. Looks like a bug.
I put that line to do that in my rc.local file quite a while back. It
As someone else noted, my /etc/modprobe.conf contains the line that does
the restore of alsa settings when loading the module. It was put there
by default during the install.
seems to do the job ok, and I do see it flying by in the boot window.
But then my rc.local would probably give purists a tummy ache cause
I'm even starting setiathome with it.
I wrote a small init script for setiathome and put it into
/etc/rc.d/init.d as a service. Never have to touch rc.local for that.
I also have a cron that looks at seti and will attempt to restart it
once every 4 hours if it has died. It does periodically die if unable to
contact the server when it tries to send results back.
--
Cheers, Gene
10:07 p.m.
On Saturday 24 July 2004 22:31, Jeff Vian wrote:
On Sat, 2004-07-24 at 11:00, Gene Heskett wrote:
> On Saturday 24 July 2004 11:13, Sam Varshavchik wrote:
> >I see that /etc/init.d/halt runs alsactl store to save the
> > current mixer settings.
> >
> >I cannot find anywhere in initscript which restores the saved
> > mixer settings when booting. Looks like a bug.
>
> I put that line to do that in my rc.local file quite a while back.
> It
As someone else noted, my /etc/modprobe.conf contains the line that
does the restore of alsa settings when loading the module. It was
put there by default during the install.
> seems to do the job ok, and I do see it flying by in the boot
> window. But then my rc.local would probably give purists a tummy
> ache cause I'm even starting setiathome with it.
I wrote a small init script for setiathome and put it into
/etc/rc.d/init.d as a service. Never have to touch rc.local for
that.
I suppose I could do the same here if I needed to. But in fact I'm
using a cleaned and slightly expanded version of a script called
"setibatch". It in turn takes care of maintaining the softlinks to
setiathome's data directory so that when seti runs out of data and
stops (its told to do just that data packet in its launching line)
then setibatch increments the link to a new data subdir and
re-launches setiatome. Back when they were having major bandwidth
problems on the berkekey campus (seti was using all they had) this
script would handle an arbitrary number of packets (I'm set for 100),
trying to keep enough data on hand to keep setiathome busy. I launch
another copy of this script via an entry in my crontab that tells the
script to run another copy of seti, uploading the finished data, and
refreshing the data packets in those subdirs that have been used up.
Basicly, other than checking the gkrellm display to note that the nice
time is all used, I don't have to fool with it, its self-maintaining.
I also have a cron that looks at seti and will attempt to restart it
once every 4 hours if it has died. It does periodically die if
unable to contact the server when it tries to send results back.
Setibatch will do that in just a few seconds anytime the client dies.
Its about 3 pages of bash script. I should post it someplace, but I'm
not the original author, I just did some needed cleanup and added
another type of a status display. I sent my changes back, but I
don't know if the posted copy was ever updated. According to google,
its still the 0.5 version I started with.
--
Cheers, Gene
There are 4 boxes to be used in defense of liberty.
Soap, ballot, jury, and ammo.
Please use in that order, starting now. -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004,
Maurice E. Heskett, all rights reserved.
7166
days inactive
7216
days old
13 comments
6 participants
participants (6)
-
Alexander Dalloz -
Gene Heskett -
Jeff Vian -
Michael Schwendt -
Mike Klinke -
Sam Varshavchik