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),