I am having problems myself with this. Not sure if the latest ppa release will fix this. Upstream fix feb13, ubuntu ppa date feb16. Posting this up while the data is on my screen, before I do the reboots and such ...
VT1705 codec has two ADCs where the secondary ADC has no MUX but only
a fixed connection to the mic pin. This confused the driver and it
tries always overriding the input-source selection by assumption of
the existing MUX for the secondary ADC, resulted in resetting the
input-source at each time PM (including power-saving) occurs.
The fix is simply to check the existence of MUX for secondary ADCs in
the initialization code.
This seems to be an upstream kernel bug.
I am having problems myself with this. Not sure if the latest ppa release will fix this. Upstream fix feb13, ubuntu ppa date feb16. Posting this up while the data is on my screen, before I do the reboots and such ...
From: www.kernel. org/pub/ linux/kernel/ v3.0/ChangeLog- 3.2.7
http://
commit 852c3a36c216e35 1d07ca96e9af30b 81fff30ccc
Author: Takashi Iwai <email address hidden>
Date: Mon Feb 13 15:04:06 2012 +0100
ALSA: hda - Fix initialization of secondary capture source on VT1705
commit fc1156c0b0f7ad4 5ec03d919866349 eeca2bf18c upstream.
VT1705 codec has two ADCs where the secondary ADC has no MUX but only
a fixed connection to the mic pin. This confused the driver and it
tries always overriding the input-source selection by assumption of
the existing MUX for the secondary ADC, resulted in resetting the
input-source at each time PM (including power-saving) occurs.
The fix is simply to check the existence of MUX for secondary ADCs in
the initialization code.
Tested-by: Anisse Astier <email address hidden>
Signed-off-by: Takashi Iwai <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>