[alsa-devel] Recalcitrant input pin on ALC262

Tony Vroon tony at linx.net
Sun Feb 1 21:56:40 CET 2009

Good evening,

Currently I am implementing full support for the Tyan Thunder n6650W and
have noticed a pin complex that advertises input, but can't seem to be
set to it:
Node 0x1c [Pin Complex] wcaps 0x400001: Stereo
  Pincap 0x00000020: IN
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x00:

As you can see the pin capabilities reflect input. However, even after
issuing this in the model-specific verbs:

the pin-ctls firmly remains 0x00. Even the python-based hda-analyzer
appears unable to flip the pin-ctls over to 0x20 and reports no error
messages in the GUI or in the terminal.

What am I missing please?

Slightly related, is it considered acceptable to modify pin defaults if
they are blatantly wrong? (Reported colour, N/A vs Fixed, etc)

Tony V.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20090201/1ddbee2a/attachment-0001.sig 

More information about the Alsa-devel mailing list