From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000595]: No support for Audigy 2 rev 8 (Audigy 2 Value)
Date: Mon, 27 Dec 2004 15:49:27 +0100 [thread overview]
Message-ID: <56e08e9d3b1a1a969acaa6acbe6377df@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=595>
======================================================================
Reported By: mohammed_imran
Assigned To: pzad
======================================================================
Project: ALSA - driver
Issue ID: 595
Category: PCI - emu10k1
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Distribution:
Kernel Version: 2.6.3,2.6.5,2.6.8
Resolution: duplicate
Duplicate: 597
Fixed in Version:
======================================================================
Date Submitted: 10-22-2004 15:47 CEST
Last Modified: 12-27-2004 15:49 CET
======================================================================
Summary: No support for Audigy 2 rev 8 (Audigy 2 Value)
Description:
Hi. I have read the alsa readme and checked support but it seems that
audigy 2 cards currently working with alsa (emu10k1 driver) have revision
4. I recently bought an Audigy 2 Value card and doing lspci lists it as:
03:02.0 Multimedia audio controller: Creative Labs: Unknown device 0008
I guess this card is revision 8 and not revision 4. I have tried to make
it work with alsa 1.0.6a to no avail.
No Linux system up to Kernel 2.6.8 detects this sound card and i haven't
tried any kernel above 2.6.8.
The Audigy 2 Value card is new (its not the ZS Value)
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
duplicate of 0000597 Audigy 2 Value detected
======================================================================
----------------------------------------------------------------------
pzad - 10-22-04 16:03
----------------------------------------------------------------------
AFAIK this card has new chip. This chip is not supported. There are no
specs available from Creative for now. No specs = no driver unless someone
reverse engineering original drivers. Or you can try to add this pci id to
emu10k1 driver and try if it will work.
Issue History
Date Modified Username Field Change
======================================================================
10-22-04 15:47 mohammed_imran New Issue
10-22-04 15:47 mohammed_imran Kernel Version => 2.6.3,2.6.5,2.6.8
10-22-04 16:03 pzad Note Added: 0002243
11-01-04 22:25 wbrown338 Issue Monitored: wbrown338
11-24-04 12:40 pzad Relationship added duplicate of 0000597
11-24-04 12:41 pzad Relationship deleted duplicate of 0000597
11-24-04 12:42 pzad Relationship added duplicate of 0000597
11-24-04 12:44 pzad Duplicate ID 0 => 597
11-24-04 12:44 pzad Status assigned => resolved
11-24-04 12:44 pzad Resolution open => duplicate
12-27-04 15:49 tiwai Status resolved => closed
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next reply other threads:[~2004-12-27 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 14:49 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-24 11:44 [ALSA - driver 0000595]: No support for Audigy 2 rev 8 (Audigy 2 Value) bugtrack
2004-11-24 11:42 bugtrack
2004-11-24 11:41 bugtrack
2004-11-24 11:40 bugtrack
2004-10-22 14:03 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=56e08e9d3b1a1a969acaa6acbe6377df@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