[alsa-devel] Sound issues with ALC269VB-based hardware
tiwai at suse.de
Tue Jul 17 17:05:36 CEST 2012
At Tue, 17 Jul 2012 15:11:09 +0200,
Anisse Astier wrote:
> So I have this hardware that has a few issues (all tested with tiwai/sound for-next)
> Audio out/speakers:
> - Audio does not work by default. It needs plugging a jack in either headphone or mic.
> - disabling "Enable Automute" does make it work. But then it doesn't mute when jack is plugged (obviously).
> - needs model=laptop-dmic so that working "Internal Mic 1" appears
> - "Internal Mic" is useless.
> - no jack sense, need to select manually "Internal Mic 1" or "Mic" (external) as Input Source
> Please find alsa-info.sh with and without model=laptop-dmic in attachement.
All sounds like that your BIOS setup is broken.
You have two internal mics on 0x12 and 0x19. Judging from your
comment, the pin 0x12 seems bogus.
The problem of the auto-mute is likely because either the jack
detection on pin 0x21 doesn't work, or the pin 0x21 is bogus.
You need to figure it out.
Usually the device has a jack detection mechanism, and you can check
it via hda-verb or whatever. Plug your headphone to the headphone
jack, and check any of the pin reacts to GET_PIN_SENSE verb (call it
after setting SET_PIN_SENSE verb). For example,
% hda-verb /dev/snd/hwC0D0 0x21 SET_PIN_SENSE 1
% hda-verb /dev/snd/hwC0D0 0x21 GET_PIN_SENSE 0
Check the value returned from GET_PIN_SENSE. If bit 31 (0x80000000)
is set, this is likely the pin of the interest.
Check this for all pins, i.e. between 0x12 and 0x21. Some nodes are
no pins, but it doesn't matter much.
Ditto for other external jacks (if any). Figure out which pin
corresponds to what I/O. Then you can write your own "patch" file and
load it via option.
For details, read Documentation/sound/alsa/HD-Audio.txt.
More information about the Alsa-devel