mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Takashi Iwai <tiwai@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>, alsa-devel@alsa-project.org
Subject: Re: Problems with snd-hda-intel on hp 6930p (2.6.30)
Date: Tue, 30 Jun 2009 16:15:37 +0200	[thread overview]
Message-ID: <200906301615.38244.rjw@sisk.pl> (raw)
In-Reply-To: <200906301529.56598.rjw@sisk.pl>

On Tuesday 30 June 2009, Rafael J. Wysocki wrote:
> On Tuesday 30 June 2009, Takashi Iwai wrote:
> > At Mon, 29 Jun 2009 20:37:09 +0200,
> > Rafael J. Wysocki wrote:
> > > 
> > > Hi Takashi,
> > > 
> > > I have a problem with snd-hda-intel from 2.6.30 on an hp EliteBook 6930p, which
> > > is that the sound is not audible, although everything appears to work just
> > > fine.  Except maybe that when the box is rebooted and KDE (3.5) is started,
> > > the master control is "muted" and the led indicator next to the keyboard shows
> > > "no sound".  Then, changing the "muted" status of the master control doesn't
> > > change the state of the led indicator and vice versa (the two things appear to
> > > be totally independent of each other).
> > > 
> > > Can you please tell me what I can do to debug this issue?
> > 
> > Could you run alsa-info.sh with --no-upload option on both "muted"
> > and "not muted" states, and attach the generated files?
> 
> Sure.  In the meantime it turned out that after a power off and cold boot the
> status of the master control is 'on', but the led indicator shows 'no sound', so
> there are 5 outputs:
> * alsa-info-postboot.txt - after power off and cold boot
> * alsa-info-led.txt - led indicator switched to 'on' when it was in the
>   alsa-info-postboot.txt state
> Now I switched to AC power and rebooted the box without powering off:
> * alsa-info-muted.txt - initial state with the 'muted' master control
> * alsa-info-on.txt - master control switched to 'on' when it was in the
>   alsa-info-muted.txt state
> * alsa-info.txt - led indicator switched to 'on' when it was in the
>   alsa-info-on.txt state
> 
> > If it's a regression (heh :), please give alsa-info.sh output on
> > older kernels.
> 
> No, it's not a regression.  At least not from 2.6.27.
> 
> Please let me know if you need more information.

One more thing.  The headphones output actually works regardless of the
led indicator status, so only the built-in speakers output seems to be
affected.

Thanks,
Rafael

  reply	other threads:[~2009-06-30 14:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 18:37 Rafael J. Wysocki
2009-06-30  9:31 ` Takashi Iwai
2009-06-30 13:29   ` Rafael J. Wysocki
2009-06-30 14:15     ` Rafael J. Wysocki [this message]
2009-06-30 14:34       ` Takashi Iwai
2009-06-30 22:47         ` Rafael J. Wysocki
2009-07-01 16:00         ` Rafael J. Wysocki
2009-07-01 16:10           ` Takashi Iwai
2009-07-01 22:46             ` Rafael J. Wysocki

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=200906301615.38244.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@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 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®