[lkml]   [2006]   [Aug]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ALSA problems with 2.6.18-rc3
On Wednesday 09 August 2006 21:57, Lee Revell wrote:
> On Wed, 2006-08-09 at 16:51 -0400, Gene Heskett wrote:
> > I already have the 'alsactl restore' in my rc.local. Would there be any
> > harm in just adding the -F to that invocation, or will that just restore
> > it to a 'default' condition always. Seems like it would, canceling
> > anything you have done & then did an 'alsactl store' to save..
> That's what I was suggesting - just add -F to the alsactl restore in
> your init script. It won't restore it to a default state - the only
> difference is that it will do a better job restoring your mixer state if
> new controls are added by a driver update.
> alsactl --help:
> -F,--force try to restore the matching controls as much as
> possible

I assume there are drawbacks to such an option, since whatever method is used
to "force" the control may make a mistake if similarly named controls are

Personally, I think the correct approach would be to have more sensible
default values. Having the External Amplifier default off when it cripples
analogue output on emu10k1, and has no effect on digital output, seems rather
weird. Also, I never really understood the rationale for the "all zeros"
mixer default. Why not 50%?


Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-08-09 23:25    [W:0.061 / U:11.116 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site