Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751035AbWBSUcA (ORCPT ); Sun, 19 Feb 2006 15:32:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751036AbWBSUcA (ORCPT ); Sun, 19 Feb 2006 15:32:00 -0500 Received: from viper.oldcity.dca.net ([216.158.38.4]:29879 "HELO viper.oldcity.dca.net") by vger.kernel.org with SMTP id S1751034AbWBSUb7 (ORCPT ); Sun, 19 Feb 2006 15:31:59 -0500 Subject: Re: No sound from SB live! From: Lee Revell To: Nick Warne Cc: Jesper Juhl , Pavel Machek , tiwai@suse.de, ghrt@dial.kappa.ro, perex@suse.cz, kernel list In-Reply-To: <200602192020.36343.nick@linicks.net> References: <20060218231419.GA3219@elf.ucw.cz> <7c3341450602190318o1c60e9b5w@mail.gmail.com> <1140377394.2733.341.camel@mindpipe> <200602192020.36343.nick@linicks.net> Content-Type: text/plain Date: Sun, 19 Feb 2006 15:31:57 -0500 Message-Id: <1140381117.2733.374.camel@mindpipe> Mime-Version: 1.0 X-Mailer: Evolution 2.5.91 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1490 Lines: 40 On Sun, 2006-02-19 at 20:20 +0000, Nick Warne wrote: > On Sunday 19 February 2006 19:29, Lee Revell wrote: > > > > And now the confusing bit. If I run alsamixer but DO NOT DO ANYTHING, > > > exit, then issue 'alsactl store', then 'alsactl restore' works again > > > OK - until next reboot... > > > > Sounds like you have 2 different alsactls installed. The ALSA default > > one saves the mixer state in /etc/asound.state but lots of distros hack > > it up to save the state somewhere under /var. > > > > Use "alsactl -f" to force a restore of mixer state even if the mixer > > controls have changed (distros should do this by default but don't). > > Lee, > > Everybody here keeps saying that to me - I _don't_ have two alsactl's, I > _don't_ have 2 asound.states (or more/any other alsactl files). > > My base is Slackware 10 - a pretty clean distro. > > Tonight my MIC is not working again from a reboot, and I can't get it going > like I did before (??)... > > Every reboot 'alsactl restore' breaks on one control or another now. > > You mean -F too? I don't understand why I should have to use --force. > > It's a mystery? Sorry, no idea. You'll have to do a binary search with ALSA CVS to find out exactly when it broke. Lee - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/