From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001595]: Audigy 4 (bulk, non-Pro) unsupported (patch included)
Date: Thu, 24 Nov 2005 03:35:40 +0100 [thread overview]
Message-ID: <9ed825e279fa3210bcf7e5fd1ed06e32@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1595>
======================================================================
Reported By: khampf
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1595
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: new
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: 11-24-2005 03:35 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).
======================================================================
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)
======================================================================
-------------------------------------------------------
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:[~2005-11-24 2:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 2:35 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-24 2:41 [ALSA - driver 0001595]: Audigy 4 (bulk, non-Pro) unsupported (patch included) bugtrack
2005-11-24 20:54 bugtrack
2005-11-26 21:33 bugtrack
2005-11-29 21:56 bugtrack
2005-12-22 12:28 bugtrack
2005-12-22 12:29 bugtrack
2005-12-22 14:07 bugtrack
2005-12-22 19:22 bugtrack
2005-12-23 10:02 bugtrack
2006-01-05 23:49 bugtrack
2006-01-09 21:28 bugtrack
2006-01-15 19:34 bugtrack
2006-01-15 20:48 bugtrack
2006-01-15 22:04 bugtrack
2006-01-21 23:06 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=9ed825e279fa3210bcf7e5fd1ed06e32@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