[alsa-devel] Fwd: Request for HW auto-recognition: HP Pavilion dv7 with STAC92xx
Hi,
At Wed, 12 Dec 2012 18:08:25 +0100, Tomas Pospisek wrote:
Hello,
I have a HP Pavilion dv7 laptop (LS066EA#UUZ), with:
# cat /proc/asound/card0/codec* | grep Codec Codec: IDT 92HD81B1X5 Codec: Intel CougarPoint HDMI
when play sound without any tweaks, I get a very weak sound output. If I want to have "beats audio", that is subwoofer and all speakers, I need to set:
# cat /etc/modprobe.d/alsa-base.conf options snd-hda-intel model=hp-dv7-4000
Could the snd_hda_intel alsa driver be updated to recognize and setup the driver accordingly?
alsa-info.sh output here:
http://www.alsa-project.org/db/?f=54ea874f43f12c1572aff3ee3113dc4b0ad0b398
I'm not quite sure that I have the exact same hardware, but I think so. I have 5 speakers (rear left and right, front left and right + subwoofer) Here is my alsa-info: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1056669/+attachme... In my case, model=hp-dv7-4000 doesn't fully solve the problem. The subwoofer works but it is not mapped as such. After some tests, it seems that the alsa's speakers rear left and rear right are mapped to the subwoofer. The front ones are alright. With the model=hp-dv5 that I'm using, the subwoofer isnt recognized at all, but the rear speakers are correctly mapped.
Also, with hp-dv7-4000, the internal microphone is still used when a micro jack is plugged in. That's not the case with hp-dv5.
If you think there's a configuration issue on my side, please let me know, but I think hp-dv5 is actually a better default choice if I have to choose between both.
Kind regards,
-- nimai
At Fri, 14 Dec 2012 22:12:18 +0100, Nicolas Maître wrote:
Hi,
At Wed, 12 Dec 2012 18:08:25 +0100, Tomas Pospisek wrote:
Hello,
I have a HP Pavilion dv7 laptop (LS066EA#UUZ), with:
# cat /proc/asound/card0/codec* | grep Codec Codec: IDT 92HD81B1X5 Codec: Intel CougarPoint HDMI
when play sound without any tweaks, I get a very weak sound output. If I want to have "beats audio", that is subwoofer and all speakers, I need to set:
# cat /etc/modprobe.d/alsa-base.conf options snd-hda-intel model=hp-dv7-4000
Could the snd_hda_intel alsa driver be updated to recognize and setup the driver accordingly?
alsa-info.sh output here:
http://www.alsa-project.org/db/?f=54ea874f43f12c1572aff3ee3113dc4b0ad0b398
I'm not quite sure that I have the exact same hardware, but I think so. I have 5 speakers (rear left and right, front left and right + subwoofer) Here is my alsa-info: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1056669/+attachme... In my case, model=hp-dv7-4000 doesn't fully solve the problem. The subwoofer works but it is not mapped as such. After some tests, it seems that the alsa's speakers rear left and rear right are mapped to the subwoofer. The front ones are alright. With the model=hp-dv5 that I'm using, the subwoofer isnt recognized at all, but the rear speakers are correctly mapped.
Also, with hp-dv7-4000, the internal microphone is still used when a micro jack is plugged in. That's not the case with hp-dv5.
If you think there's a configuration issue on my side, please let me know, but I think hp-dv5 is actually a better default choice if I have to choose between both.
So in this case you need to figure out the exact pin configurations on your machine. hda_analyzer and hdajackretask programs would be a great help for that.
Takashi
On Sat, Dec 15, 2012 at 11:21 AM, Takashi Iwai tiwai@suse.de wrote:
So in this case you need to figure out the exact pin configurations on your machine. hda_analyzer and hdajackretask programs would be a great help for that.
Well, I don't know how to do that efficiently. I have spent some time trying to play with hda analyzer and hda-jack-retask but I think it was just a waste of time. I've used "speaker-test -c 6" as test for each change. Here are my notes on my attempts to make something work by overriding the pins in hda-jack-retask, in case is could be useful anyway: http://pastebin.com/HVgURDuA I've realized it was probably not the good way to go when I've seen that the fact that pulseaudio were running actually changed the mapping.
So, do you know some guide/howto I could follow to do something useful with my issue?
Thanks.
-- nimai
Could the snd_hda_intel alsa driver be updated to recognize and setup
the > driver accordingly?
alsa-info.sh output here: > > >
http://www.alsa-project.org/db/?f=54ea874f43f12c1572aff3ee3113dc 4b0ad0b398
[ 345.964525] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x30170503 [ 346.972241] hda-intel: No response from codec, disabling MSI: last cmd=0x30170503 [ 347.979887] hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x30170503
I'm not quite sure that I have the exact same hardware, but I think > so.
I have 5 speakers (rear left and right, front left and right + > subwoofer)
Here is my alsa-info:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1056669/+attachme...
In my case, model=hp-dv7-4000 doesn't fully solve the problem. The subwoofer works but it is not mapped as such. After some tests, it seems that the alsa's speakers rear left and rear right are mapped to the subwoofer. The front ones are alright. With the model=hp-dv5 that I'm using, the subwoofer isnt recognized at all, but the rear speakers are correctly mapped.
There is no dv5 model as 92HD81 use patch_stac92hd83xxx
STAC92HD83* =========== refReference board mic-refReference board with power management for ports dell-s14Dell laptop dell-vostro-3500Dell Vostro 3500 laptop hp-dv7-4000HP dv-7 4000 hp_cNB11_intquad HP CNB models with 4 speakers hp-zephyrHP Zephyr hp-ledHP with broken BIOS for mute LED hp-inv-ledHP with broken BIOS for inverted mute LED autoBIOS setup (default)
So in this case you need to figure out the exact pin configurations on
your machine. hda_analyzer and hdajackretask programs would be a great help for that.
Well, I don't know how to do that efficiently. I have spent some time trying to play with hda analyzer and hda-jack-retask but I think it was just a waste of time. I've used "speaker-test -c 6" as test for each change.
speaker-test -c4 -D hw:0,0 -t wav
92HD81 only support up to four channels
4 Channels (2 stereo DACs and 2 stereo ADCs) with 24-bit resolution •Supports full-duplex stereo audio and simultaneous VoIP •Provides a mono output
http://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=commit;h=0c27c18...
The two internal speaker nodes have the same sequence number zero in the pin ficup
Here are my notes on my attempts to make something work by overriding the pins in hda-jack-retask, in case is could be useful anyway: http://pastebin.com/HVgURDuA I've realized it was probably not the good way to go when I've seen that the fact that pulseaudio were running actually changed the mapping.
So, do you know some guide/howto I could follow to do something useful with my issue?
Trying remove PCI quirk and use auto to find out node 0x0f is the internal speaker
- SND_PCI_QUIRK(PCI_VENDOR_ID_HP, 0x1659, - "HP", STAC_92HD83XXX_HP_cNB11_INTQUAD),
On Mon, Dec 17, 2012 at 3:55 AM, Raymond Yau superquad.vortex2@gmail.com wrote:
Trying remove PCI quirk and use auto to find out node 0x0f is the internal speaker
- SND_PCI_QUIRK(PCI_VENDOR_ID_HP, 0x1659,
- "HP", STAC_92HD83XXX_HP_cNB11_INTQUAD),
Not sure of what you expect of me, but anyway I've tried a kernel without the quirk and here's the result:
original kernel, model=dv7-4000: 0x0a 0x03a12050 0x0b 0x0321201f 0x0c 0x40f000f0 0x0d 0x90170110 0x0e 0x40f000f0 0x0f 0x40f000f0 0x10 0x90170110 0x11 0xd5a30140 0x1f 0x40f000f0 0x20 0x40f000f0 1
kernel without quirk, model=auto: 0x0a 0x40f000f0 0x0b 0x0221101f 0x0c 0x02a11020 0x0d 0x40f000f0 0x0e 0x40f000f0 0x0f 0x92170110 0x10 0x40f000f0 0x11 0xd5a30130 0x1f 0x40f000f0 0x20 0x40f000f0 1
And I can see that 0x0f is the internal speaker (at least in hda-jack-retask) The sound is only output on the 2 rear speakers (no front nor subwoofer). So what now?
-- nimai
Trying remove PCI quirk and use auto to find out node 0x0f is the
internal
speaker
- SND_PCI_QUIRK(PCI_VENDOR_ID_HP, 0x1659,
- "HP", STAC_92HD83XXX_HP_cNB11_INTQUAD),
Not sure of what you expect of me, but anyway I've tried a kernel without the quirk and here's the result:
original kernel, model=dv7-4000: 0x0a 0x03a12050 0x0b 0x0321201f 0x0c 0x40f000f0 0x0d 0x90170110 0x0e 0x40f000f0 0x0f 0x40f000f0 0x10 0x90170110 0x11 0xd5a30140 0x1f 0x40f000f0 0x20 0x40f000f0 1
kernel without quirk, model=auto: 0x0a 0x40f000f0 0x0b 0x0221101f 0x0c 0x02a11020 0x0d 0x40f000f0 0x0e 0x40f000f0 0x0f 0x92170110 0x10 0x40f000f0 0x11 0xd5a30130 0x1f 0x40f000f0 0x20 0x40f000f0 1
And I can see that 0x0f is the internal speaker (at least in
hda-jack-retask)
The sound is only output on the 2 rear speakers (no front nor subwoofer). So what now?
Can you post the output of always-info.sh (kernel without quirk, model=auto )?
Take a look at 92HD81 datasheet
2.1.Port Functionality 2.2. Mono Output 2.19.BTL Amplifier High-Pass Filter The high pass filter is enabled by default with a cut-off frequency of 300Hz 2.23.2. “Playback Path” Port Behavior
Figure 8. Functional Block Diagram
If your note book really have 5 speakers and node 0x0f is the rear speaker , the sequence number should be 1 instead of 0 by pin fixup
Do the headphone , Mic jack and internal Mic work as expected ?
subwoofer is most likely at mono pin node 0x10
use hda-analyzer to change Pin-ctls to OUT and connect node 0x19 to the audio output with speaker playback volume control
Either 0x0d or 0x0e is the front speaker
Use early patching to fix the pin default
Node 0x10 [Pin Complex] wcaps 0x400500: Mono Pincap 0x00000010: OUT Pin Default 0x40f000f0: [N/A] Other at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x00: Power states: Power: setting=D0, actual=D0 Connection: 1 0x1a
Node 0x19 [Audio Selector] wcaps 0x300501: Stereo Power states: Power: setting=D0, actual=D0 Connection: 3 0x13* 0x14 0x1c Node 0x1a [Audio Mixer] wcaps 0x200500: Mono Power states: Power: setting=D0, actual=D0 Connection: 1 0x19
Aparently Nicolas Maître wrote (for some reason I only got the followup by Takashi Iwai):
In my case, model=hp-dv7-4000 doesn't fully solve the problem. The subwoofer works but it is not mapped as such. After some tests, it seems that the alsa's speakers rear left and rear right are mapped to the subwoofer. The front ones are alright. With the model=hp-dv5 that I'm using, the subwoofer isnt recognized at all, but the rear speakers are correctly mapped.
I've also tested model=hp-dv5 and I think - I'm not sure - it doesn't use the subwoofer same as with Nicolas.
What's sure however is that it's showing the same symptoms as model=hp-dv7-4000 after wakeup as described here:
http://article.gmane.org/gmane.linux.alsa.devel/103836
Nicolas, are you able to suspend your machine while playing (or not) sound? Does your sound-system come up in order again after wakeup? *t
I have a HP Pavilion dv7 laptop (LS066EA#UUZ), with:
# cat /proc/asound/card0/codec* | grep Codec Codec: IDT 92HD81B1X5 Codec: Intel CougarPoint HDMI
http://www.alsa-project.org/db/?f=54ea874f43f12c1572aff3ee3113dc4b0ad0b398
I'm not quite sure that I have the exact same hardware, but I think so. I have 5 speakers (rear left and right, front left and right + subwoofer) Here is my alsa-info:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1056669/+attachme...
In my case, model=hp-dv7-4000 doesn't fully solve the problem. The subwoofer works but it is not mapped as such.
Do you mean node 0x0d is the subwoofer and node 0x0f is the internal speaker ?
static const unsigned int hp_dv7_4000_pin_configs[10] = { - 0x03a12050, 0x0321201f, 0x40f000f0, 0x90170110, + 0x03a12050, 0x0321201f, 0x40f000f0, 0x90170111, 0x40f000f0, 0x40f000f0, 0x90170110, 0xd5a30140, 0x40f000f0, 0x40f000f0, };
participants (4)
-
Nicolas Maître -
Raymond Yau -
Takashi Iwai -
Tomas Pospisek