mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [Alsa-user] another in kernel alsa update that breaks backward compatibilty?
Date: Wed, 09 Aug 2006 12:33:16 -0400	[thread overview]
Message-ID: <200608091233.16264.gene.heskett@verizon.net> (raw)
In-Reply-To: <s5h3bc5zy3q.wl%tiwai@suse.de>

On Wednesday 09 August 2006 12:13, Takashi Iwai wrote:
>At Wed, 09 Aug 2006 12:07:26 -0400,
>
>Gene Heskett wrote:
>> On Wednesday 09 August 2006 11:46, Sergei Steshenko wrote:
>> >On Wed, 09 Aug 2006 11:40:02 -0400
>> >
>> >Gene Heskett <gene.heskett@verizon.net> wrote:
>> >> Greetings;
>> >>
>> >> The old fart is back again. :)
>> >>
>> >> I've just done a divide and conquer on kernel versions, and have
>> >> found that while I DO have a kde audio signon for kernels
>> >> 2.6.18-rc1-rc3-rc4, I do not have any other functioning audio,
>> >> including the kde sound effects I normally get.  xmms and tvtime are
>> >> mute, as are the firefox plugins to play videos from the network.
>> >> 2.6.17.8 and below works great yet.
>> >>
>> >> So whats the fix?
>> >
>> >Demand stable ABI.
>>
>> It does not appear to be so.  And ATM booted to 18-rc1, I didn't see an
>> error message when rc.local made a call of "[root@coyote gene]# alsactl
>> restore
>> alsactl: set_control:894: warning: name mismatch (Mic Boost (+20dB)/Mic
>> Boost (+20dB) Switch) for control #45
>> alsactl: set_control:896: warning: index mismatch (0/0) for control #45
>> alsactl: set_control:898: failed to obtain info for control #45
>> (Operation not permitted)
>> [root@coyote gene]#
>
>This kind of problems can be fixed by calling "alsactl restore" with
>-F option.  The warnings may be still there but the values are handled
>better.
>
>The behavior with -F could be default, but it's kept so just for the
>compatibility reason.
>
>
Humm, and that fixed it for 2.6.18-rc4.  Gawd, I'd sure like to get some of 
that stuff, it must be great stuff.  Goes off scratching head & letting 
imagination work overtime.

>Takashi

Many thanks Takashi.
-- 
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.

  reply	other threads:[~2006-08-09 16:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09 15:40 Gene Heskett
2006-08-09 15:46 ` [Alsa-user] " Sergei Steshenko
2006-08-09 15:53   ` Lee Revell
2006-08-09 15:56   ` Benoit Fouet
2006-08-09 16:00     ` Sam Ravnborg
2006-08-09 16:17       ` Sergei Steshenko
2006-08-09 16:33         ` Sam Ravnborg
2006-08-09 16:36         ` Dmitry Torokhov
2006-08-09 16:44           ` Sergei Steshenko
2006-08-09 17:54             ` Dmitry Torokhov
2006-08-09 19:53               ` Sergei Steshenko
2006-08-09 16:07   ` Gene Heskett
2006-08-09 16:13     ` Takashi Iwai
2006-08-09 16:33       ` Gene Heskett [this message]
2006-08-09 16:13     ` Lee Revell
2006-08-09 16:29     ` Gene Heskett

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=200608091233.16264.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    /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®