From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0002280]: nforce 570 with AD1988A no sound
Date: Sun, 6 Aug 2006 14:20:58 +0200 [thread overview]
Message-ID: <a7fe4454f37b8dbf03bb8d4c53547c19@bugtrack.alsa-project.org> (raw)
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2280>
======================================================================
Reported By: Tobias Diedrich
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 2280
Category: PCI - hda-intel
Reproducibility: always
Severity: major
Priority: normal
Status: resolved
Distribution: Debian/GNU Linux testing
Kernel Version: 2.6.18-rc1
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 07-14-2006 14:40 CEST
Last Modified: 08-06-2006 14:20 CEST
======================================================================
Summary: nforce 570 with AD1988A no sound
Description:
I just bought a new mainboard, an Asus M2N with nforce 570 chipset (mcp55)
and snd-hda-intel loads fine, but complains about an unknown chip version
and tries to get some configuration values from the BIOS. Apparently this
does not work, since while it loads fine I have so far been unable to get
any sound from it.
======================================================================
----------------------------------------------------------------------
tiwai - 07-19-06 20:33
----------------------------------------------------------------------
Try the latest HG version. The codec might be AD1988B, not AD1988A.
----------------------------------------------------------------------
Tobias Diedrich - 08-06-06 11:15
----------------------------------------------------------------------
Ok, I got around to testing it again and it is working now since 2.6.18-rc2
AFAICS.
Issue History
Date Modified Username Field Change
======================================================================
07-14-06 14:40 Tobias DiedrichNew Issue
07-14-06 14:40 Tobias DiedrichDistribution => Debian/GNU Linux
testing
07-14-06 14:40 Tobias DiedrichKernel Version => 2.6.18-rc1
07-19-06 20:33 tiwai Note Added: 0011098
08-06-06 11:15 Tobias DiedrichNote Added: 0011465
08-06-06 14:20 Adrian Bunk Status assigned => resolved
08-06-06 14:20 Adrian Bunk Resolution open => fixed
======================================================================
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2006-08-06 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 12:20 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-06 9:15 [ALSA - driver 0002280]: nforce 570 with AD1988A no sound bugtrack
2006-07-19 18:33 bugtrack
2006-07-14 12:40 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=a7fe4454f37b8dbf03bb8d4c53547c19@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