From: Takashi Iwai <tiwai@suse.de>
To: Andreas Schwab <schwab@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.6: ALSA sound/ppc/keywest.c:84: tumbler: cannot initialize the MCS
Date: Sun, 16 May 2004 17:07:28 +0200 [thread overview]
Message-ID: <s5h7jvcl8b3.wl@alsa2.suse.de> (raw)
In-Reply-To: <jesme1y7e4.fsf@sykes.suse.de>
At Sat, 15 May 2004 18:36:35 +0200,
Andreas Schwab wrote:
>
> Andreas Schwab <schwab@suse.de> writes:
>
> > Takashi Iwai <tiwai@suse.de> writes:
> >
> >> At Tue, 11 May 2004 00:28:47 +0200,
> >> Andreas Schwab wrote:
> >>>
> >>> I've never been able to get a working sound with ALSA after booting my
> >>> iBook G3 (dmasound is working fine). Any idea what's wrong with
> >>> snd-powermac?
> >>
> >> does the attached patch work? it's a partial patch from the latest
> >> ALSA cvs tree.
> >> the problem seems like the initialization of i2c-keywest.
> >
> > I have now imported the alsa patch from 2.6.6-mm1 and the problem seems
> > to be fixed.
>
> Actually there are still similar problems when waking up:
>
> kernel: tumbler_init_client error
> kernel: ALSA sound/ppc/tumbler.c:589: failed to set mono volume 7
> last message repeated 2 times
> kernel: ALSA sound/ppc/tumbler.c:460: failed to set mono volume 1
> kernel: ALSA sound/ppc/tumbler.c:460: failed to set mono volume 2
> kernel: ALSA sound/ppc/tumbler.c:356: failed to set DRC
> kernel: ALSA sound/ppc/tumbler.c:221: failed to set volume
do you mean after suspend/resume?
then a similiar hack might be needed.
Takashi
next prev parent reply other threads:[~2004-05-16 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 22:28 2.6.6: ALSA sound/ppc/keywest.c:84: tumbler: cannot initialize the MCS Andreas Schwab
2004-05-11 14:25 ` Takashi Iwai
2004-05-12 19:54 ` Andreas Schwab
2004-05-15 16:36 ` Andreas Schwab
2004-05-16 15:07 ` Takashi Iwai [this message]
2004-05-16 15:50 ` Andreas Schwab
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=s5h7jvcl8b3.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schwab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.