Problems with snd-hda-intel on hp 6930p (2.6.30)

Problems with snd-hda-intel on hp 6930p (2.6.30)

[Rafael J. Wysocki]

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?

Best,
Rafael

Re: Problems with snd-hda-intel on hp 6930p (2.6.30)

[Takashi Iwai]

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?

If it's a regression (heh :), please give alsa-info.sh output on
older kernels.


thanks,

Takashi

Re: Problems with snd-hda-intel on hp 6930p (2.6.30)

[Rafael J. Wysocki]

[-- Attachment #1: Type: text/plain, Size: 1746 bytes --]

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.

Thanks,
Rafael

[-- Attachment #2: alsa-info-led.txt.gz --]
[-- Type: application/x-gzip, Size: 4906 bytes --]

[-- Attachment #3: alsa-info-muted.txt.gz --]
[-- Type: application/x-gzip, Size: 4898 bytes --]

[-- Attachment #4: alsa-info.txt.gz --]
[-- Type: application/x-gzip, Size: 4885 bytes --]

[-- Attachment #5: alsa-info-on.txt.gz --]
[-- Type: application/x-gzip, Size: 4888 bytes --]

[-- Attachment #6: alsa-info-postboot.txt.gz --]
[-- Type: application/x-gzip, Size: 4911 bytes --]

Re: Problems with snd-hda-intel on hp 6930p (2.6.30)

[Rafael J. Wysocki]

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

Re: Problems with snd-hda-intel on hp 6930p (2.6.30)

[Takashi Iwai]

At Tue, 30 Jun 2009 16:15:37 +0200,
Rafael J. Wysocki wrote:
> 
> 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.

How can you turn on/off LED?  From your explanation, it seems not
directly bound with the audio mute.

Anyway, try model=mobile or model=laptop for snd-hda-intel module
option.  Does the speaker work?


Takashi

Re: Problems with snd-hda-intel on hp 6930p (2.6.30)

[Rafael J. Wysocki]

On Tuesday 30 June 2009, Takashi Iwai wrote:
> At Tue, 30 Jun 2009 16:15:37 +0200,
> Rafael J. Wysocki wrote:
> > 
> > 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.
> 
> How can you turn on/off LED?

There's a button switch attached to it (basically, you press the led and the
status changes :-)).

> From your explanation, it seems not directly bound with the audio mute.

That's correct, it seems independent.

> Anyway, try model=mobile or model=laptop for snd-hda-intel module
> option.  Does the speaker work?

I'll check tomorrow, the box is at my university office.

Thanks,
Rafael

Re: Problems with snd-hda-intel on hp 6930p (2.6.30)

[Rafael J. Wysocki]

On Tuesday 30 June 2009, Takashi Iwai wrote:
> At Tue, 30 Jun 2009 16:15:37 +0200,
> Rafael J. Wysocki wrote:
> > 
> > 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.
> 
> How can you turn on/off LED?  From your explanation, it seems not
> directly bound with the audio mute.
> 
> Anyway, try model=mobile or model=laptop for snd-hda-intel module
> option.  Does the speaker work?

Yes, it works with both model=laptop and model=mobile.

Thanks,
Rafael

Re: Problems with snd-hda-intel on hp 6930p (2.6.30)

[Takashi Iwai]

At Wed, 1 Jul 2009 18:00:28 +0200,
Rafael J. Wysocki wrote:
> 
> On Tuesday 30 June 2009, Takashi Iwai wrote:
> > At Tue, 30 Jun 2009 16:15:37 +0200,
> > Rafael J. Wysocki wrote:
> > > 
> > > 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.
> > 
> > How can you turn on/off LED?  From your explanation, it seems not
> > directly bound with the audio mute.
> > 
> > Anyway, try model=mobile or model=laptop for snd-hda-intel module
> > option.  Does the speaker work?
> 
> Yes, it works with both model=laptop and model=mobile.

OK, I added the following patch to sound git tree.


Takashi

===
>From ff84847171508a3c76eb7e483204d1be7738729b Mon Sep 17 00:00:00 2001
From: Takashi Iwai <tiwai@suse.de>
Date: Wed, 1 Jul 2009 18:08:01 +0200
Subject: [PATCH] ALSA: hda - Add quirk for HP 6930p

Added a quirk model=laptop for HP 6930p (103c:30dc) with AD1984A codec.

Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
 sound/pci/hda/patch_analog.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/sound/pci/hda/patch_analog.c b/sound/pci/hda/patch_analog.c
index 84cc49c..85e8618 100644
--- a/sound/pci/hda/patch_analog.c
+++ b/sound/pci/hda/patch_analog.c
@@ -3966,6 +3966,7 @@ static struct snd_pci_quirk ad1884a_cfg_tbl[] = {
 	SND_PCI_QUIRK(0x103c, 0x3037, "HP 2230s", AD1884A_LAPTOP),
 	SND_PCI_QUIRK(0x103c, 0x3056, "HP", AD1884A_MOBILE),
 	SND_PCI_QUIRK_MASK(0x103c, 0xfff0, 0x3070, "HP", AD1884A_MOBILE),
+	SND_PCI_QUIRK_MASK(0x103c, 0xfff0, 0x30d0, "HP laptop", AD1884A_LAPTOP),
 	SND_PCI_QUIRK_MASK(0x103c, 0xfff0, 0x30e0, "HP laptop", AD1884A_LAPTOP),
 	SND_PCI_QUIRK_MASK(0x103c, 0xff00, 0x3600, "HP laptop", AD1884A_LAPTOP),
 	SND_PCI_QUIRK(0x17aa, 0x20ac, "Thinkpad X300", AD1884A_THINKPAD),
-- 
1.6.3.2

Re: Problems with snd-hda-intel on hp 6930p (2.6.30)

[Rafael J. Wysocki]

On Wednesday 01 July 2009, Takashi Iwai wrote:
> At Wed, 1 Jul 2009 18:00:28 +0200,
> Rafael J. Wysocki wrote:
> > 
> > On Tuesday 30 June 2009, Takashi Iwai wrote:
> > > At Tue, 30 Jun 2009 16:15:37 +0200,
> > > Rafael J. Wysocki wrote:
> > > > 
> > > > 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.
> > > 
> > > How can you turn on/off LED?  From your explanation, it seems not
> > > directly bound with the audio mute.
> > > 
> > > Anyway, try model=mobile or model=laptop for snd-hda-intel module
> > > option.  Does the speaker work?
> > 
> > Yes, it works with both model=laptop and model=mobile.
> 
> OK, I added the following patch to sound git tree.

Thanks!

I had to give the box back to the owner.  I'll verify the patch if I can get
access to it once again. :-)

Best,
Rafael


> ===
> From ff84847171508a3c76eb7e483204d1be7738729b Mon Sep 17 00:00:00 2001
> From: Takashi Iwai <tiwai@suse.de>
> Date: Wed, 1 Jul 2009 18:08:01 +0200
> Subject: [PATCH] ALSA: hda - Add quirk for HP 6930p
> 
> Added a quirk model=laptop for HP 6930p (103c:30dc) with AD1984A codec.
> 
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> ---
>  sound/pci/hda/patch_analog.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/sound/pci/hda/patch_analog.c b/sound/pci/hda/patch_analog.c
> index 84cc49c..85e8618 100644
> --- a/sound/pci/hda/patch_analog.c
> +++ b/sound/pci/hda/patch_analog.c
> @@ -3966,6 +3966,7 @@ static struct snd_pci_quirk ad1884a_cfg_tbl[] = {
>  	SND_PCI_QUIRK(0x103c, 0x3037, "HP 2230s", AD1884A_LAPTOP),
>  	SND_PCI_QUIRK(0x103c, 0x3056, "HP", AD1884A_MOBILE),
>  	SND_PCI_QUIRK_MASK(0x103c, 0xfff0, 0x3070, "HP", AD1884A_MOBILE),
> +	SND_PCI_QUIRK_MASK(0x103c, 0xfff0, 0x30d0, "HP laptop", AD1884A_LAPTOP),
>  	SND_PCI_QUIRK_MASK(0x103c, 0xfff0, 0x30e0, "HP laptop", AD1884A_LAPTOP),
>  	SND_PCI_QUIRK_MASK(0x103c, 0xff00, 0x3600, "HP laptop", AD1884A_LAPTOP),
>  	SND_PCI_QUIRK(0x17aa, 0x20ac, "Thinkpad X300", AD1884A_THINKPAD),