From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001595]: Audigy 4 (bulk, non-Pro) unsupported (patch included)
Date: Sun, 15 Jan 2006 21:48:22 +0100 [thread overview]
Message-ID: <2289e65aedcaab99c549893769be383f@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1595>
======================================================================
Reported By: khampf
Assigned To: jcdutton
======================================================================
Project: ALSA - driver
Issue ID: 1595
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: Debian 3 testing/unstable hybrid
Kernel Version: 2.6.14.2-c0r3 (-ckX+swsusp2+bootsplash)
======================================================================
Date Submitted: 11-24-2005 03:35 CET
Last Modified: 01-15-2006 21:48 CET
======================================================================
Summary: Audigy 4 (bulk, non-Pro) unsupported (patch
included)
Description:
I recently bought me a Creative Audigy 4 and was surprised it didn't work
at all ... I noticed it wasn't detected and made it detectable and copied
the settings from Audigy 4 Pro. I have to click the "Audigy Analog/Digital
Output switch" switch to make it work. Front/Center, Mic works, however I
have no idea about wether SPDIF is ok or not (I have no devices). It might
be that a lot of functionality is missing still but it's a start.
First, output of "$ lspci -vn | grep -1 0401"
0000:02:09.0 0401: 1102:0008
Subsystem: 1102:1021
Then, using "modprobe emu10k1 sumsystem=xxxxxx" does not work at all for
me, doesn't get the interrupt up and errors about probe failing.
So I added did this to my kernel sound/pci/emu10k1/emu10k1_main.c:
{.vendor = 0x1102, .device = 0x0008, .subsystem = 0x10211102,
.driver = "Audigy2", .name = "Audigy 4 [A400?]",
.id = "Audigy2",
.emu10k2_chip = 1,
.ca0102_chip = 1,
/*.ca0151_chip = 1, */
/*.spk71 = 1, */
/*.spdif_bug = 1,*/
.ac97_chip = 1} ,
I left those commented out as I've tried the options and noticed no
difference in operation. Also, I don't know the SB0xxx model (can't remove
the card and look at it at the moment either).
======================================================================
----------------------------------------------------------------------
khampf - 01-15-06 20:34
----------------------------------------------------------------------
Ok guys, back home from holidays, took a while longer than expected. My
card has developed problems, distortions on the front right channel
(verified on another computer with other speakers). But while the card was
pulled out I tried to take som pictures of it and read what was printed on
the chips.
First of all, I do _not_ have the same card as on the picture earlier in
this thread. That picture has a CA0103 while I have a CA0108 as "the big
one". This is the DSP, right?
This is what I could find out:
SOUND BLASTER AUDIGY 4
MODEL: SB0610
The big one (DSP?):
Creative
CA0108-IAT LF
@CREATIVE TECH '03
55AC6LW
DAC or ADC:
Cirrus Logic
CS4382-KQZ
WAEXAX0510
TAIWAN
AC97:
Sigmatel
STAC9750
(the rest hard to make out)
I was not able to find both a DAC and an ADC .. you can look at the
pictures and see for yourself (at least some parts are readable).
http://www.c0r3.org/audigy4/
Now my question is ... how does this card work with the CA102 part of the
driver and the CA0108 part disabled? Is there some init in CA0102 that is
bringing it online? And why does the card posted earlier sport a CA10300
and mine CA0108?
The PCB is exactly the same as far as I can see, all other components than
"the big one" seems to be identical too.
But I did recompile my kernel before I took the card out and this worked
perfectly (at least 5.1 sound) with my Audigy 4 an kernel 2.6.15 (in
emu10k1_main.c):
{.vendor = 0x1102, .device = 0x0004, .subsystem = 0x10211102,
.driver = "Audigy2", .name = "Audigy 4 [SB0610]",
.id = "Audigy2",
.emu10k2_chip = 1,
.ca0102_chip = 1
/* .ca0151_chip = 1, */
/* .spk71 = 1, */
/* .spdif_bug = 1, */
/* .ac97_chip = 1 */ } ,
Untested: digital out, 7.1 surround
Working: stereo sound (2.1), 5.1 surround, AC97 mixer
I can however not test the card more before I get a replacement, and I've
got an Audigy 2 with firewire now instead (works perfectly) so I'm not too
sure I'll use the Audigy 4 in my workstation even after a warranty
replacement.
----------------------------------------------------------------------
jprk - 01-15-06 21:48
----------------------------------------------------------------------
Just before Christmas I bought what seems to be a bulk version of Audigy 4
(named "SB Audigy 4 OEM" at www.czechcomputer.cz). The DSP is CA0108-IATLF
(and not CA10300-IAT as reported by BerndBuechs and as jcdutton found on
the Creative website), but the rest is the same: DAC is Phillips 1361T,
ADC is CirrusLogic CS4382-KQZ ADC and AC97 is SigmaTel STAC9750.
Photographs of the card (2-4MB files, beware) can be found at
http://euler.fd.cvut.cz/audigy4/SB_Audigy_4_OEM_cropped.jpg
http://euler.fd.cvut.cz/audigy4/SB_Audigy_4_OEM.jpg
http://euler.fd.cvut.cz/audigy4/SB_Audigy_4_OEM_detail.jpg
I am running Ubuntu 5.10 with an almost vanilla 2.6.12 kernel (V4L
subsystem taken from V4L CVS, ALSA is unpatched, version 1.0.9). I have
on-board AC97 and this Audigy, audigy being indexed as the first one and
connected to a 5.1 analog sound system. This combinaction works nice under
Win XP. Under Linux, the only thing that I can make my Audigy to do is to
click - by switching the digital/analog output. The on-board AC97 seems to
work. The Audigy is being detected as "Audigy 2 Value [Unknown]", exactly
as khampf mentions in the post from 24th November.
I am now going to get the last version of ALSA, try to replace the kernel
modules with the newer ones without crippling everything and report if the
card works or not.
Issue History
Date Modified Username Field Change
======================================================================
11-24-05 03:35 khampf New Issue
11-24-05 03:35 khampf Distribution => Debian 3
testing/unstable hybrid
11-24-05 03:35 khampf Kernel Version => 2.6.14.2-c0r3
(-ckX+swsusp2+bootsplash)
11-24-05 03:39 khampf Issue Monitored: khampf
11-24-05 03:41 khampf Note Added: 0006837
11-24-05 21:54 jcdutton Note Added: 0006845
11-26-05 22:33 khampf Note Added: 0006850
11-29-05 22:55 BerndBuechs Issue Monitored: BerndBuechs
11-29-05 22:56 BerndBuechs Note Added: 0006874
12-22-05 13:28 jcdutton Note Added: 0007124
12-22-05 13:29 jcdutton Note Added: 0007125
12-22-05 15:07 khampf Note Added: 0007126
12-22-05 20:22 jcdutton Note Added: 0007129
12-23-05 11:02 BerndBuechs Note Added: 0007132
12-28-05 13:40 vsu Issue Monitored: vsu
01-06-06 00:49 kjes Note Added: 0007485
01-09-06 22:28 jcdutton Status new => assigned
01-09-06 22:28 jcdutton Assigned To => jcdutton
01-15-06 20:34 khampf Note Added: 0007670
01-15-06 21:48 jprk Note Added: 0007672
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-15 20:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 20:48 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-21 23:06 [ALSA - driver 0001595]: Audigy 4 (bulk, non-Pro) unsupported (patch included) bugtrack
2006-01-15 22:04 bugtrack
2006-01-15 19:34 bugtrack
2006-01-09 21:28 bugtrack
2006-01-05 23:49 bugtrack
2005-12-23 10:02 bugtrack
2005-12-22 19:22 bugtrack
2005-12-22 14:07 bugtrack
2005-12-22 12:29 bugtrack
2005-12-22 12:28 bugtrack
2005-11-29 21:56 bugtrack
2005-11-26 21:33 bugtrack
2005-11-24 20:54 bugtrack
2005-11-24 2:41 bugtrack
2005-11-24 2:35 bugtrack
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=2289e65aedcaab99c549893769be383f@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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