Problems with snd-hda-intel on hp 6930p (2.6.30)
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
At Mon, 29 Jun 2009 20:37:09 +0200,
Quoted 11 lines · 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).
Quoted 1 line
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
Quoted 13 lines · Takashi Iwai
At Mon, 29 Jun 2009 20:37:09 +0200,
Quoted 11 lines · 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).
Quoted 4 lines
Quoted 1 line
Can you please tell me what I can do to debug this issue?
Could you run
alsa-info.shwith --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
Quoted 2 lines
If it's a regression (heh :), please give
alsa-info.shoutput 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
Quoted 32 lines · Rafael J. Wysocki
Quoted 13 lines · Takashi Iwai
At Mon, 29 Jun 2009 20:37:09 +0200,
Quoted 11 lines · 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).
Quoted 4 lines
Quoted 1 line
Can you please tell me what I can do to debug this issue?
Could you run
alsa-info.shwith --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
Quoted 6 lines
Quoted 2 lines
If it's a regression (heh :), please give
alsa-info.shoutput 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
At Tue, 30 Jun 2009 16:15:37 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 35 lines · Rafael J. Wysocki
Quoted 13 lines · Takashi Iwai
At Mon, 29 Jun 2009 20:37:09 +0200,
Quoted 11 lines · 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).
Quoted 4 lines
Quoted 1 line
Can you please tell me what I can do to debug this issue?
Could you run
alsa-info.shwith --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 stateQuoted 2 lines
If it's a regression (heh :), please give
alsa-info.shoutput on older kernels.
Quoted 7 lines
Quoted 3 lines
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
Quoted 41 lines · Takashi Iwai
At Tue, 30 Jun 2009 16:15:37 +0200,
Quoted 39 lines · Rafael J. Wysocki
Quoted 37 lines · Rafael J. Wysocki
Quoted 13 lines · Takashi Iwai
At Mon, 29 Jun 2009 20:37:09 +0200,
Quoted 11 lines · 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).
Quoted 4 lines
Quoted 1 line
Can you please tell me what I can do to debug this issue?
Could you run
alsa-info.shwith --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 stateQuoted 2 lines
If it's a regression (heh :), please give
alsa-info.shoutput on older kernels.No, it's not a regression. At least not from 2.6.27.
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
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 :-)).
Quoted 1 line
From your explanation, it seems not directly bound with the audio mute.
That's correct, it seems independent.
Quoted 2 lines
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
Quoted 47 lines · Takashi Iwai
At Tue, 30 Jun 2009 16:15:37 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 35 lines · Rafael J. Wysocki
Quoted 13 lines · Takashi Iwai
At Mon, 29 Jun 2009 20:37:09 +0200,
Quoted 11 lines · 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).
Quoted 4 lines
Quoted 1 line
Can you please tell me what I can do to debug this issue?
Could you run
alsa-info.shwith --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 stateQuoted 2 lines
If it's a regression (heh :), please give
alsa-info.shoutput on older kernels.Quoted 7 lines
Quoted 3 lines
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.
Quoted 5 lines
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
At Wed, 1 Jul 2009 18:00:28 +0200,
Quoted 49 lines · Rafael J. Wysocki
Quoted 47 lines · Takashi Iwai
At Tue, 30 Jun 2009 16:15:37 +0200,
Quoted 44 lines · Rafael J. Wysocki
Quoted 32 lines · Rafael J. Wysocki
Quoted 13 lines · Takashi Iwai
At Mon, 29 Jun 2009 20:37:09 +0200,
Quoted 11 lines · 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).
Quoted 4 lines
Quoted 1 line
Can you please tell me what I can do to debug this issue?
Could you run
alsa-info.shwith --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 stateQuoted 6 lines
Quoted 2 lines
If it's a regression (heh :), please give
alsa-info.shoutput 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.
Quoted 7 lines
Quoted 5 lines
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
===
Quoted 1 line
From
ff84847171508a3c76eb7e483204d1be7738729bMon Sep 17 00:00:00 2001
From: Takashi Iwai <[email protected]>
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.
--- sound/pci/hda/patch_analog.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
sound/pci/hda/patch_analog.c +1 -0
@@ -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),
Signature · 1 line
1.6.3.2
Quoted 54 lines · Takashi Iwai
At Wed, 1 Jul 2009 18:00:28 +0200,
Quoted 52 lines · Rafael J. Wysocki
Quoted 50 lines · Takashi Iwai
At Tue, 30 Jun 2009 16:15:37 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 35 lines · Rafael J. Wysocki
Quoted 13 lines · Takashi Iwai
At Mon, 29 Jun 2009 20:37:09 +0200,
Quoted 11 lines · 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).
Quoted 4 lines
Quoted 1 line
Can you please tell me what I can do to debug this issue?
Could you run
alsa-info.shwith --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 stateQuoted 2 lines
If it's a regression (heh :), please give
alsa-info.shoutput on older kernels.Quoted 7 lines
Quoted 3 lines
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.
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
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
Quoted 25 lines
===
Fromff84847171508a3c76eb7e483204d1be7738729bMon Sep 17 00:00:00 2001
From: Takashi Iwai <[email protected]>
Date: Wed, 1 Jul 2009 18:08:01 +0200
Subject: [PATCH] ALSA: hda - Add quirk for HP 6930pAdded a quirk model=laptop for HP 6930p (103c:30dc) with AD1984A codec.
Signed-off-by Takashi Iwai <[email protected]>--- sound/pci/hda/patch_analog.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)sound/pci/hda/patch_analog.c +1
-0@@ -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),