From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Cc: Lee Revell <rlrevell@joe-job.com>,
Andrew Benton <b3nt@ukonline.co.uk>, Takashi Iwai <tiwai@suse.de>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: ALSA problems with 2.6.18-rc3
Date: Wed, 09 Aug 2006 21:47:11 -0400 [thread overview]
Message-ID: <200608092147.11457.gene.heskett@verizon.net> (raw)
In-Reply-To: <1155157036.26338.200.camel@mindpipe>
On Wednesday 09 August 2006 16:57, Lee Revell wrote:
>On Wed, 2006-08-09 at 16:51 -0400, Gene Heskett wrote:
>> On Wednesday 09 August 2006 16:41, Lee Revell wrote:
>> [...]
>>
>> >> >Takashi-san,
>> >> >
>> >> >Does this help at all? Many users are reporting that sound broke
>> >> > with 2.6.18-rc*.
>> >> >
>> >> >Lee
>> >>
>> >> Takashi-san's suggestion earlier today of running an "alsactl -F
>> >> restore" seems to have fixed all those diffs right up, I now have
>> >> good sound with an emu10k1 using an audigy 2 as card-0, running
>> >> kernel-2.6.18-rc4.
>> >
>> >Distros should probably be using this as a default. Otherwise, simply
>> >adding a new mixer control will cause restoring mixer settings to
>> > fail.
>> >
>> >Lee
>>
>> 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
>
>Lee
Great, Lee, thanks. That also gave me a good excuse to expand the
operating $PATH for rc.local, recent heyu changes seem to have killed my
restoration of the config that existed after cron made the last change in
config.
--
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules. I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2006-08-10 1:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 20:28 Andrew Benton
2006-08-08 21:50 ` Lee Revell
2006-08-09 16:30 ` Andrew Benton
2006-08-09 16:35 ` Lee Revell
2006-08-09 16:51 ` [Alsa-devel] " Liam Girdwood
2006-08-09 18:17 ` Gene Heskett
2006-08-09 20:41 ` Lee Revell
2006-08-09 20:51 ` Gene Heskett
2006-08-09 20:57 ` Lee Revell
2006-08-09 21:22 ` Alistair John Strachan
2006-08-09 21:34 ` Lee Revell
2006-08-09 22:07 ` Alistair John Strachan
2006-08-09 22:11 ` Lee Revell
2006-08-09 22:28 ` Alistair John Strachan
2006-08-09 22:49 ` Lee Revell
2006-08-10 8:47 ` Takashi Iwai
2006-08-10 1:47 ` Gene Heskett [this message]
2006-08-10 13:13 ` [Alsa-devel] " Takashi Iwai
2006-08-09 10:58 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200608092147.11457.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=b3nt@ukonline.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®