From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001083]: NVIDIA CK8 ALC655 SPDIF passthrough
Date: Sun, 26 Jun 2005 13:18:16 +0200 [thread overview]
Message-ID: <fc4e64e2409a808ade23b3e76063cd3e@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1083>
======================================================================
Reported By: vedran
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1083
Category: PCI - intel8x0
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Debian sid
Kernel Version: 2.6.10-ac12
======================================================================
Date Submitted: 04-29-2005 15:33 CEST
Last Modified: 06-26-2005 13:18 CEST
======================================================================
Summary: NVIDIA CK8 ALC655 SPDIF passthrough
Description:
We're using a motherboard with nVidia nforce2IGP chipset, and the sound
device on this board is NVidia CK8, Realtek ALC655 rev 0. The motherboard
is MSI K7N2GM2, and SPDIF passthrough works fine on Windows XP with stock
realtek drivers.
On Linux, I'm using the latest ALSA CVS (29.04.2005.) on a 2.6.10-ac12
kernel.
I've been able to make a 2 channel pre-decoded SPDIF output work by using
the hw:0,2 device. If I use the default device, there is no sound on
SPDIF, regardless of the SPDIF related controls in mixer. The controls in
the mixer are:
However, I'm having trouble with AC3 passthrough, I'm using ac3dec -C from
alsa-tools CVS, and I get no sound.
I'm attaching the archive with the output of iecset and
/proc/asound/card0/codec97#0/* files during the ac3dec run, and when
idle.
Maybe the fact that decoded SPDIF output is not working until I pass it
through the hw:0,2 has something to do with this, how can I make ac3dec -C
use hw:0,2?
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
has duplicate 0001094 nforce4 - optical spdif out not working
======================================================================
----------------------------------------------------------------------
tiwai - 06-21-05 11:19
----------------------------------------------------------------------
Yes, only 48kHz works on nForce SPDIF, indeed. That is, the non-audio
stream in other rates won't work.
As mentioned, the driver works partially. It may work with the receiver
which accepts AC3 stream even without SPDIF non-audio status bit by
checking the preamble. But, the receivers strictly checking the non-audio
bit don't work.
It seems that the nForce doesn't use AC97 chip for transmitting SPDIF
signals but directly drives from the nforce core. Thus, checking the
datasheet of the ac97 codec chip won't help...
----------------------------------------------------------------------
gilesjuk - 06-26-05 13:18
----------------------------------------------------------------------
But in my case the Realtek chip is on a seperate card with the SPDIF and
audio ports. Surely the audio data gets written to this chip and then
routed to the outputs depending on how the registers are set?
This is my board:
http://www.abit-usa.com/products/mb/products.php?categories=1&model=262
Excuse my ignorance, but how is the Nforce chipset responsible for the
audio when it's an external codec being used?
Issue History
Date Modified Username Field Change
======================================================================
04-29-05 15:33 vedran New Issue
04-29-05 15:33 vedran File Added: spdif_passthrough.tar.gz
04-29-05 15:33 vedran Distribution => Debian sid
04-29-05 15:33 vedran Kernel Version => 2.6.10-ac12
05-30-05 13:21 vedran Note Added: 0004809
06-01-05 16:53 tiwai Note Added: 0004862
06-01-05 16:54 tiwai Relationship added has duplicate 0001094
06-01-05 19:19 eklarson Issue Monitored: eklarson
06-03-05 00:31 Human Note Added: 0004880
06-03-05 00:32 Human Issue Monitored: Human
06-06-05 23:30 Human Note Added: 0004910
06-08-05 15:01 tiwai Note Added: 0004928
06-10-05 18:07 Human Note Added: 0004984
06-19-05 16:07 gilesjuk Note Added: 0005090
06-21-05 00:50 gilesjuk Note Added: 0005099
06-21-05 00:57 gilesjuk Note Edited: 0005099
06-21-05 11:19 tiwai Note Added: 0005102
06-26-05 13:18 gilesjuk Note Added: 0005263
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-06-26 11:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 11:18 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 17:46 [ALSA - driver 0001083]: NVIDIA CK8 ALC655 SPDIF passthrough bugtrack
2006-01-05 13:25 bugtrack
2005-12-31 2:23 bugtrack
2005-07-19 23:37 bugtrack
2005-06-27 14:56 bugtrack
2005-06-21 9:19 bugtrack
2005-06-20 22:50 bugtrack
2005-06-19 14:07 bugtrack
2005-06-10 16:07 bugtrack
2005-06-08 13:01 bugtrack
2005-06-06 21:30 bugtrack
2005-06-02 22:31 bugtrack
2005-06-01 14:53 bugtrack
2005-05-30 11:21 bugtrack
2005-04-29 13:33 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=fc4e64e2409a808ade23b3e76063cd3e@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