From: Takashi Iwai <tiwai@suse.de>
To: Luis Henriques <luis.henriques@canonical.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [Regression] No sound on HP Pavilion dv6, STAC92xx
Date: Tue, 26 Jun 2012 16:35:18 +0200 [thread overview]
Message-ID: <s5hr4t25eft.wl%tiwai@suse.de> (raw)
In-Reply-To: <878vfatafv.fsf@canonical.com>
At Tue, 26 Jun 2012 15:27:48 +0100,
Luis Henriques wrote:
>
> Takashi Iwai <tiwai@suse.de> writes:
>
> > At Tue, 26 Jun 2012 15:13:43 +0100,
> > Luis Henriques wrote:
> >>
> >> Hi,
> >>
> >> After commit b0791dda813c179e539b0fc1ecd3f5f30f2571e2 ("ALSA: hda/idt
> >> - Fix power-map for speaker-pins with some HP laptops") we have
> >> several bug reports about not having sound on HP Pavilion laptops.
> >>
> >> Here's a link to one of these bug reports:
> >>
> >> http://bugs.launchpad.net/bugs/1013183
> >>
> >> After reverting the referred commit, everything seems to be working
> >> fine again.
> >>
> >> Any ideas/fixes?
> >
> > Could you give alsa-info.sh output on both working and non-working
> > kernels?
>
> You should be to get the same information in the bug URL.
It's not same :) Many information are missing, e.g. sysfs pincfgs.
alsa-info.sh output contains the whole information in a single file,
and above all, it can be fed to hda-emu for analyzing the problem.
Takashi
next prev parent reply other threads:[~2012-06-26 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 14:13 [Regression] No sound on HP Pavilion dv6, STAC92xx Luis Henriques
2012-06-26 14:13 ` Luis Henriques
2012-06-26 14:16 ` Takashi Iwai
2012-06-26 14:27 ` Luis Henriques
2012-06-26 14:35 ` Takashi Iwai [this message]
2012-06-26 15:10 ` Takashi Iwai
2012-06-26 15:52 ` Takashi Iwai
2012-06-26 15:54 ` Takashi Iwai
2012-06-27 9:09 ` Luis Henriques
2012-06-27 9:44 ` Takashi Iwai
2012-06-26 16:02 ` Luis Henriques
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=s5hr4t25eft.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
/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.