From: Scott Doty <scott@ponzo.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Creative ca0132 on Gigabyte Z170X Gaming 7 motherboard: no sound
Date: Thu, 3 Mar 2016 15:13:14 -0800 [thread overview]
Message-ID: <56D8C50A.2030904@ponzo.net> (raw)
In-Reply-To: <s5h4mcnsxte.wl-tiwai@suse.de>
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
prev parent reply other threads:[~2016-03-03 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 2:47 Creative ca0132 on Gigabyte Z170X Gaming 7 motherboard: no sound Scott Doty
2016-03-03 9:41 ` Takashi Iwai
2016-03-03 23:13 ` Scott Doty [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56D8C50A.2030904@ponzo.net \
--to=scott@ponzo.net \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.