From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001765]: Issue 001595 does not fix Audigy 4
Date: Sun, 9 Apr 2006 21:57:15 +0200 [thread overview]
Message-ID: <75d2f03c6de2a018fb49d97d4fbb98a1@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1765>
======================================================================
Reported By: alexholkner
Assigned To: jcdutton
======================================================================
Project: ALSA - driver
Issue ID: 1765
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Distribution:
Kernel Version:
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 01-21-2006 01:49 CET
Last Modified: 04-09-2006 21:57 CEST
======================================================================
Summary: Issue 001595 does not fix Audigy 4
Description:
I have an Audigy 4 with the same device/subsystem as khampf from issue
1595. I applied his patch, but it does NOT work unless I change
.ca0102_chip = 1 to .ca0108_chip = 1.
I did experience the same confusion where loading one driver with ca0108
will make any subsequent driver work (e.g., ca0102) until the next reboot.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0001595 Audigy 4 (bulk, non-Pro) unsupported (p...
======================================================================
----------------------------------------------------------------------
jprk - 02-05-06 13:25
----------------------------------------------------------------------
As 0001595 has been closed, I would just like to confirm, that Audigy 4
_partially_ works with entry
{.vendor = 0x1102, .device = 0x0008,
.driver = "Audigy2", .name = "Audigy 2 Value [Unknown]",
.id = "Audigy2",
.emu10k2_chip = 1,
.ca0108_chip = 1,
.ac97_chip = 1}
I have a 5.1 speaker set and I do not get sound from front left and front
right speakers. I tried to set up reasonable levels on every output with
alsamixer, but without success. I tried patching the Audigy 2 entry in
emu10k1_main.c to specify .spk71 = 1 - it did not have any influence.
Replugging front left/right minijack from its corresponding socket (L1)
into the center/subwoofer socket (L3) as reported by 'kjes' in discussion
for 0001595 is not a solution as then I loose subwoover and central
speaker.
I am now running unpathced 2.6.15.2 on AMD-64 (64-bit kernel) with Audigy
4 being the first of two soundcards (the second one is an integrated AC97
clone on the motherboard).
-----
cat /proc/asound/version:
Advanced Linux Sound Architecture Driver Version 1.0.10rc3 (Mon Nov 07
13:30:21 2005 UTC).
(I had exactly the same experience with 1.0.11rc2 and kernel 2.6.12)
-----
cat /proc/asound/cards:
0 [Audigy2 ]: Audigy2 - Audigy 2 Value [Unknown]
Audigy 2 Value [Unknown] (rev.0, serial:0x10211102)
at 0xdf00, irq 217
1 [CK804 ]: NFORCE - NVidia CK804
NVidia CK804 with ALC850 at 0xfebfd000, irq 233
----------------------------------------------------------------------
jcdutton - 04-09-06 21:57
----------------------------------------------------------------------
Fixed in alsa cvs on 9-4-2006
Fixed in alsa cvs version 1.0.11rc5 or above.
Issue History
Date Modified Username Field Change
======================================================================
01-21-06 01:49 alexholkner New Issue
01-22-06 00:06 jcdutton Status new => assigned
01-22-06 00:06 jcdutton Assigned To => jcdutton
01-22-06 00:06 jcdutton Relationship added related to 0001595
01-22-06 00:19 jcdutton Note Added: 0007741
01-22-06 00:19 jcdutton Status assigned => feedback
02-05-06 13:25 jprk Note Added: 0007933
04-09-06 21:57 jcdutton Status feedback => closed
04-09-06 21:57 jcdutton Note Added: 0009186
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-04-09 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 19:57 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-05 12:25 [ALSA - driver 0001765]: Issue 001595 does not fix Audigy 4 bugtrack
2006-01-21 23:19 bugtrack
2006-01-21 23:06 bugtrack
2006-01-21 23:06 bugtrack
2006-01-21 0:49 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=75d2f03c6de2a018fb49d97d4fbb98a1@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 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.