volume not persistent between reboots
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Found the problem. There was a script in /etc/rc.boot that was calling
aumix. Since rc.boot gets called after the rcS.d scripts (and before
rcrunlevel.d scripts) it was negating what alsactl had done for me.
This is just one of several little 2.4.x - 2.6.x kernel upgrade tweaks
I've needed
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
wouldn't just running alsamixer and setting the desired levels solve
this problem?
I tried exactly this in the past. Still didn't keep my settings.
Although I noticed that the Gnome volume control accurately reflected
the changes I made
On Tue, 11 Apr 2006 10:29:48 -0400
Rick Reynolds [EMAIL PROTECTED] wrote:
A few topics similar to this have been recently discussed, and I was
waiting for this particular question to be hit, but it never did (at
least that I saw).
My sound works great. My only problem is that the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Rick Reynolds napsal(a):
A few topics similar to this have been recently discussed, and I was
waiting for this particular question to be hit, but it never did (at
least that I saw).
My sound works great. My only problem is that the
Liam O'Toole wrote:
On Tue, 11 Apr 2006 10:29:48 -0400
Rick Reynolds [EMAIL PROTECTED] wrote:
My sound works great. My only problem is that the settings I apply
to the Gnome volume control applet don't persist across reboots
(although they do across restarts of X).
The alsa-utils
Lubos Vrbka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Rick Reynolds napsal(a):
A few topics similar to this have been recently discussed, and I was
waiting for this particular question to be hit, but it never did (at
least that I saw).
My sound works great. My only
Kim Christensen wrote:
On 4/11/06, Rick Reynolds [EMAIL PROTECTED] wrote:
A few topics similar to this have been recently discussed, and I was
waiting for this particular question to be hit, but it never did (at
least that I saw).
My sound works great. My only problem is that the settings
On Tue, 11 Apr 2006 10:50:02 -0400
Rick Reynolds [EMAIL PROTECTED] wrote:
Liam O'Toole wrote:
On Tue, 11 Apr 2006 10:29:48 -0400
Rick Reynolds [EMAIL PROTECTED] wrote:
My sound works great. My only problem is that the settings I apply
to the Gnome volume control applet don't persist
Checking...
Yes, that script is there. And it is pointed to by
/etc/init.d/rcS.d/S50alsa-utils.
I think that should be '/etc/rcS.d/S50alsa-utils'.
Oops. You're right, of course
more snip
What happens if you manually invoke '/etc/init.d/alsa-utils start'? Do
you now have the
On Tue, 11 Apr 2006 11:23:44 -0400
Rick Reynolds [EMAIL PROTECTED] wrote:
SNIP
Maybe I should remove the symlinks to /etc/init.d/alsa and see what
happens since alsa-util is already getting called earlier. Any
thoughts?
There are two links to alsa scripts in the /etc/rc2.d dir: alsa
Liam O'Toole wrote:
On Tue, 11 Apr 2006 11:23:44 -0400
Rick Reynolds [EMAIL PROTECTED] wrote:
SNIP
Maybe I should remove the symlinks to /etc/init.d/alsa and see what
happens since alsa-util is already getting called earlier. Any
thoughts?
There are two links to alsa scripts in the
Rick Reynolds wrote:
[...]
I see that in my boot log [...]
What is the boot log? I'm using Sarge, and I don't see a
/var/log/boot.log or anything similar.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
wouldn't just running alsamixer and setting the desired levels solve
this problem?
I tried exactly this in the past. Still didn't keep my settings.
Although I noticed that the Gnome volume control accurately reflected
the changes I made
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Sumo Wrestler (or just ate too much) napsal(a):
Rick Reynolds wrote:
[...]
I see that in my boot log [...]
What is the boot log? I'm using Sarge, and I don't see a
/var/log/boot.log or anything similar.
that's output of the boot process
wouldn't just running alsamixer and setting the desired levels solve
this problem?
I tried exactly this in the past. Still didn't keep my settings.
Although I noticed that the Gnome volume control accurately reflected
the changes I made via alsamixer (before reboot, that is).
one more thing
On 4/11/06, Rick Reynolds [EMAIL PROTECTED] wrote:
A few topics similar to this have been recently discussed, and I was
waiting for this particular question to be hit, but it never did (at
least that I saw).
My sound works great. My only problem is that the settings I apply to
the Gnome
17 matches
Mail list logo
