[alsa-devel] Dell N5110 HDA External Speaker is mute

Cefn Hoile alsa-project.org at cefn.com
Thu Jan 12 11:56:24 CET 2012

In case anything has changed in my config since the original info run,
here is the same script run right now...


On 12 January 2012 10:52, Cefn Hoile <alsa-project.org at cefn.com> wrote:
> Thanks for your interest, Takashi.
> The alsa disgnostic script output was already linked (but a bit hidden
> in all the noise) in the downstream bug report...
> http://www.alsa-project.org/db/?f=039be3036a03f707edc130bbc63b5063619e5755
> Cefn
> http://cefn.com
> On 12 January 2012 10:32, Takashi Iwai <tiwai at suse.de> wrote:
>> At Wed, 11 Jan 2012 00:56:18 +0000,
>> Cefn Hoile wrote:
>>> I'd like to report an issue experienced with the latest Oneiric, Dell
>>> N5110, and IDT STAC92HD87 which has been explored through quite a few
>>> steps already, and seems to have bottomed out to a set of
>>> pins/controls/flags which are not being properly managed in order to
>>> toggle speaker activation when a headphone is inserted.
>>> So far, I haven't heard sound from my speakers at all, although within
>>> Alsamixer, the Speaker volume is visibly toggled from 100% to MM
>>> (mute) on headphone insertion.
>>> I've tried every model against snd-hda-intel, many different other
>>> options, and started to explore the HDA Analyzer, which includes
>>> controls named like this...
>>> Node 0x13 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L
>>>   Device: name="STAC92xx Analog", type="Audio", device=0
>>>   Control: name="Speaker Playback Volume", index=0, device=0
>>>     ControlAmp: chs=3, dir=1, idx=0, ofs=63
>>>   Control: name="Speaker Playback Switch", index=0, device=0
>>>     ControlAmp: chs=3, dir=1, idx=0, ofs=0
>>>   Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x02, mute=1
>>>   Amp-Out vals: [0x7f 0x7f]
>>>   Converter: stream=5, channel=0
>>>   Power: setting=D0, actual=D0
>>>   Delay: 13 samples
>>> ...but toggling these checkboxes within the HDA Analyzer gui doesn't
>>> trigger any sound from the speakers either. It could be a rich
>>> combination of the very many checkboxes and sliders which are revealed
>>> by the Analyzer, but I don't really know where to start. The bug
>>> information downstream is here...
>>> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/914290
>>> I'd really welcome suggestions for what else to try and happy to
>>> invest time exploring options to try and make ALSA better still.
>> Could you give alsa-info.sh output for checking the mixer and register
>> states?
>> Takashi

More information about the Alsa-devel mailing list