From: Andreas Reis <andreas.reis@gmail.com>
To: alsa-devel@alsa-project.org
Subject: [Report] ALSO: hda - CA0132: Bugs and missing features
Date: Tue, 19 Nov 2013 17:04:46 +0100 [thread overview]
Message-ID: <CAM_hTGFcrt2voAOOGfJG8=XaaFRuJCPdeyj3CCituhFthLLr4Q@mail.gmail.com> (raw)
Posting here by Takashi's advice after my alsa-user post remained unanswered.
There are a number of grave issues with the CA0132 codec on my
Gigabyte G1.Sniper M5 (rev. 1.0) (Intel Z87, Recon3Di onboard, latest
bios F8c). I've tried kernels (x64) from 3.9 to 3.13-preRC1 (as
currently in Torvald's git), both with pulse on Ubuntu 13.10 and
without on Arch Linux.
First a description, then the issues; contacting Creative's support
only led to one of those "we don't do Linux" replies.
This motherboard has 2/5.1 channel support with a total of eight jacks
(the last two below are stated as duplicated for a front panel, with
only one of each pair to be used at a time):
* Line/Mic In
* Line/Front Speaker Out
* Optical S/PDIF Out
* Center/Subwoofer Speaker Out
* Rear Speaker Out
* Headphone/Speaker Out
On Windows everything works (optical not tested), although the In jack
must be set to "Mic" to work, not to "Line" (no corresponding setting
exists in alsamixer).
The manual recommends using the headphone jacks for stereo (as it
"supports amplifying function"), but from the moment of pressing the
power button both also output very audible static noise along with the
actual sound, so I only use the Line Out.
Now, the actual issues on Linux:
* No way to change to 5.1, at least not with alsamixer (the "Surround"
switch there refers to some stereo effect). C/S and Rear Out jacks are
just dead.
* The front panel Headphone/Speaker Out works, but the rear panel one
only provides the static.
* Often after restarting from a system crash, the sound will not work
until I change the Master volume and restart all programs which tried
to play something.
* One needs these lines in /etc/asound.conf to fix the sound card
ordering, as card 0 only has three S/PDIF outs (presumably the HDMI/DP
outs of the Intel chipset):
defaults.pcm {
card 1
device 0
}
defaults.ctl {
card 1
device 0
}
And what irks the most:
* No microphone input whatsoever, on neither jack.
The only noise on Linux is a faint click on disabling either
"AMic1/DMic" or "AMic1/DMic Auto Detect", and the attached garbage
when Mic1-Boost is enabled along with the latter two (regardless of
weather the mic is actually plugged in).
Passing model=generic to snd-hda-intel, as suggested by Takashi in an
email, had no effect.
Some observations:
* alsamixer seems to always show "Analog-Mic2" or "What U Hear"
(sometimes both) enabled after boot, even if they had been manually
disabled previously.
* As written above, there is no way to cycle between the three input
settings (rear panel line-in, rear panel mic, front panel mic) as on
Windows.
* One can switch on both "Analog-Mic2" and "AMic1/DMic"/"AMic1/DMic
Auto Detect" at the same time, although they should probably be
mutually exclusive.
* It only works on Windows 8.1 if I hard boot into it. If I reboot
from Linux it will fail as well: The Mic is still detected (ie, not
reported as unplugged), but instead of actually recording, it take any
output as its input, while corrupting it into a what sounds to me like
a soft, fading feedback loop. Unfortunately I have been unable to
record this. Cycling the settings there doesn't help, only shutting
down and removing the power for a brief while does.
Attachments:
* alsa-info (split due to size):
part1: http://pastie.org/pastes/8492817/text?key=p2wnvkcvn0h7o3t2pdgg
part2: http://pastie.org/pastes/8492822/text?key=yjurqav8tzrpvbfar4o87a
* lspci -vvnn: http://pastie.org/pastes/8492798/text
* alsamixer, capture: http://i.imgur.com/ByA20f0.png
* alsamixer, playback: http://i.imgur.com/7dkvo66.png
* recorded garbage (arecord -f S16_LE -r 44100 -d 10 hw:1,0
test-mic.wav): http://www.mediafire.com/?yy1fno6vw9dbdo8
next reply other threads:[~2013-11-19 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 16:04 Andreas Reis [this message]
2013-11-19 16:08 ` [Report] ALSO: hda - CA0132: Bugs and missing features Andreas Reis
-- strict thread matches above, loose matches on Subject: below --
2013-11-20 18:10 Dylan Reid
2013-11-22 12:28 ` Andreas Reis
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='CAM_hTGFcrt2voAOOGfJG8=XaaFRuJCPdeyj3CCituhFthLLr4Q@mail.gmail.com' \
--to=andreas.reis@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).