From: Takashi Iwai <tiwai@suse.de>
To: Laura Abbott <labbott@redhat.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org,
"linux-kernel@vger.kernel.org >> Linux Kernel Mailing List"
<linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] Headphones no longer working on MacPro6,1 with 4.4
Date: Sat, 21 May 2016 08:41:28 +0200 [thread overview]
Message-ID: <s5hwpmn3obr.wl-tiwai@suse.de> (raw)
In-Reply-To: <f64ce31c-4465-0f4a-b7f4-4546fe3bc66a@redhat.com>
On Sat, 21 May 2016 00:27:22 +0200,
Laura Abbott wrote:
>
> On 03/15/2016 12:49 PM, Takashi Iwai wrote:
> > On Tue, 15 Mar 2016 20:38:41 +0100,
> > Takashi Iwai wrote:
> >>
> >> On Tue, 15 Mar 2016 20:23:09 +0100,
> >> Laura Abbott wrote:
> >>>
> >>> Hi,
> >>>
> >>> We received a bug report https://bugzilla.redhat.com/show_bug.cgi?id=1316119
> >>> that the headphone jack on a MacPro6,1 stopped working on an upgrade from 4.3
> >>> to 4.4.
> >>>
> >>> The bugzilla has the alsainfo, diffing shows that the Amp-Out vals are
> >>> different. I tried a revert of 9f660a1c4 (" ALSA: hda/realtek - Fix silent
> >>> headphone output on MacPro 4,1 (v2)") but that didn't help.
> >>>
> >>> Any ideas before asking for a bisect? Does this hardware version need to have
> >>> the vref fixup as well?
> >>
> >> The obvious difference is the power state of each node. The recent
> >> kernel has the finer power saving mode, and this might be the cause --
> >> Mac has some secret that requires some node to be powered up.
> >>
> >> Try to power on each node via hda-verb. For example, to power up the
> >> node 0x05, run like:
> >> hda-verb /dev/snd/hwC0D0 0x05 SET_POWER 0x01
> >
> > Oops, a typo: the last argument must be 0x00, corresponding to D0:
> > hda-verb /dev/snd/hwC0D0 0x05 SET_POWER 0x00
> >
> >
>
> Bringing this back again, the command that makes it work is
>
> hda-verb /dev/snd/hwC0D0 0x10 SET_POWER 0x00
OK, then please give alsa-info.sh output (run with --no-upload option)
at both working and non-working cases.
> And this is still needed as of 4.5.4
Of course, nothing has changed. I didn't hear from you since my
previous question...
I'll start checking this later in in the next week.
thanks,
Takashi
next prev parent reply other threads:[~2016-05-21 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 19:23 Laura Abbott
2016-03-15 19:38 ` Takashi Iwai
2016-03-15 19:49 ` Takashi Iwai
2016-05-20 22:27 ` Laura Abbott
2016-05-21 6:41 ` Takashi Iwai [this message]
2016-05-21 7:42 ` Takashi Iwai
2016-05-24 16:41 ` Laura Abbott
2016-05-24 17:54 ` Takashi Iwai
2016-06-02 21:20 ` Laura Abbott
2016-06-06 14:30 ` 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=s5hwpmn3obr.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
/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®