On Fri, Oct 16, 2009 at 6:40 PM, Brandon Sandrowicz <email address hidden> wrote:
> Through searching I have found this: https://lists.ubuntu.com/archives
> /kernel-team/2006-March/000699.html
>
> There is no mention of *why* it needs to be blacklisted. Is it possible
> that due to changes in the past 3+ years this blacklisting is no longer
> necessary? At one point I pulled down the alsa source and trying to
> grok it for some sort of obvious error, but I couldn't make heads or
> tails of it.
Well, I'll explain here (that's my patch):
Many of those AD19xxB codecs erroneously expose X Jack Sense mixer
elements via the driver. You have to disable them (or mute them using
alsamixer if they're exposed) to get ANY audible analog output. As far
as I know, that remains the case and is completely orthogonal to your
issue, BUT I can't tell without seeing the contents of your
/proc/asound/card*/*codec*/* before and after the second suspend.
On Fri, Oct 16, 2009 at 6:40 PM, Brandon Sandrowicz <email address hidden> wrote: /lists. ubuntu. com/archives team/2006- March/000699. html
> Through searching I have found this: https:/
> /kernel-
>
> There is no mention of *why* it needs to be blacklisted. Is it possible
> that due to changes in the past 3+ years this blacklisting is no longer
> necessary? At one point I pulled down the alsa source and trying to
> grok it for some sort of obvious error, but I couldn't make heads or
> tails of it.
Well, I'll explain here (that's my patch):
Many of those AD19xxB codecs erroneously expose X Jack Sense mixer card*/* codec*/ * before and after the second suspend.
elements via the driver. You have to disable them (or mute them using
alsamixer if they're exposed) to get ANY audible analog output. As far
as I know, that remains the case and is completely orthogonal to your
issue, BUT I can't tell without seeing the contents of your
/proc/asound/