From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001721]: Alsa 1.0.10 & 1.0.11rc2: STAC_9223 unsupported/errors, only oss-emulation works with 2 channels
Date: Fri, 6 Jan 2006 15:19:56 +0100 [thread overview]
Message-ID: <e4e80af3ee10fce5aa3c3a89ab743e49@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1721>
======================================================================
Reported By: oslo
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 1721
Category: PCI - hda-intel
Reproducibility: always
Severity: feature
Priority: normal
Status: assigned
Distribution: Gentoo Linux
Kernel Version: 2.6.14-gentoo-r5 #18 SMP PREEMPT
======================================================================
Date Submitted: 01-06-2006 15:19 CET
Last Modified: 01-06-2006 15:19 CET
======================================================================
Summary: Alsa 1.0.10 & 1.0.11rc2: STAC_9223
unsupported/errors, only oss-emulation works with 2 channels
Description:
As in summary, alsa 1.0.11rc2 works not at all, alsa-kernel 1.0.10 only
with oss-emulation and 2 channel stereo.
My Board is an
Intel Desktop Board D945PVS with 7.1 Surround Sound (Sigmatel 9223)with 5
analog jacks in the back, 2 on the board (Front Panel) and a digital jack
in the back.
The mixer shows only a "Front" (somtimes a "Headphones" on 1.0.11rc2)
device.
When starting "aplay" i get:
ALSA lib pcm_direct.c:783:(snd_pcm_direct_initialize_slave)
snd_pcm_hw_params_any failed
ALSA lib pcm_dmix.c:831:(snd_pcm_dmix_open) unable to initialize slave
aplay: main:544: audio open error: Invalid argument
also on every other alsa using software
I'v taken a look into the "[cvs/1.0.11rc2] patch_sigmatel.c" and there
probably should be something like (After Line 277):
{ .pci_subvendor = PCI_VENDOR_ID_INTEL,
.pci_subdevice = 0x0707,
.config = STAC_D945GTP5 }, /* Intel D945PVS - 5 Stack */
but for me this changed nothing...
The output of lspci is appended.
I hope this is enough information, if not tell me what you need.
PS: For me this is a major bug, butunsupported cards are generally
features?
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
01-06-06 15:19 oslo New Issue
01-06-06 15:19 oslo File Added: intel_hda_stac9223.txt
01-06-06 15:19 oslo Distribution => Gentoo Linux
01-06-06 15:19 oslo Kernel Version => 2.6.14-gentoo-r5 #18
SMP PREEMPT
======================================================================
-------------------------------------------------------
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
reply other threads:[~2006-01-06 14:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e4e80af3ee10fce5aa3c3a89ab743e49@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