4 Mar
2016
4 Mar
'16
12:13 a.m.
On 03/03/2016 01:41 AM, Takashi Iwai wrote:
I guess this is a very long-standing known issue with CA0132 codec support. The codec driver, or more exactly, the given firmware blob, is very specific to some models (Chromebook Pixel, the old Creative CA0132 boards and some old Alienware machines), and the recent Creative models don't work with it well.
There have been some struggles, but no good solution found yet. https://bugzilla.kernel.org/show_bug.cgi?id=111021
Takashi
Thank you for the reply!
As a first step, I immediately applied the patches attached to the bug report above, which, alas, does not seem to have solved the problem.
I will post that, as well as further reports, under the bug report.
-Scott