Comment 306 for bug 1166529

Looking into it a little bit, having never messed with one with your ID, here's what is in the Windows driver inf:

[DriverSettings.AddReg]
HKR,DeviceSpecificOverwrite,SupportedMultiplexInputs, 0x00010001,0x00000005
HKR,DeviceSpecificOverwrite,SupportedMultiplexOutputs, 0x00010001,0x00000003
HKR,DeviceSpecificOverwrite,SupportDriveBay, 0x00010001,0x00000000
HKR,DeviceSpecificOverwrite,MPIO_GB_RearMicLine_FPMic, 0x00010001,0x00000001
HKR,DeviceSpecificOverwrite,MPIO_GB_FPHP_CtrLFE, 0x00010001,0x00000003
HKR,DeviceSpecificOverwrite,MPIO_GB_FPHP_CtrLFE_Mute, 0x00010001,0x00000004
HKR,DeviceSpecificOverwrite,MPIO_GB_HPAMP_Shutdown, 0x00010001,0x00000005
HKR,DeviceSpecificOverwrite,LineOutMaxVolume, 0x00010001,0x00000000

There is specific mention of "MPIO_GB_FPHP_CtrLFE" and then "MPIO_GB_FPHP_CtrLFE_Mute". Now, I don't exactly know what the numbers mean, but my guess is it may be the bitmask value for the GPIO data verb. So, 0x03 means pins 0 and 1 are on, which I'm pretty sure is what I have by default. Maybe check that 0x11 is set as output, you can do that by sending:

hda-verb /dev/snd/hwC*D* 0x11 0x707 0x44 .

That is pin 0x11, which is actually supposed to be surround, but that's the only one I've known to have problems. You could do the same to 0x10 as well, or just download hda-analyzer and see if it's set as out.