From: Ed Wright <edo.wright@gmail.com>
To: alsa-devel@lists.sourceforge.net
Subject: intel-hda, 965 chipset, STAC9227 - problem
Date: Thu, 11 Jan 2007 23:24:15 +0900 [thread overview]
Message-ID: <45A6488F.4010808@gmail.com> (raw)
Hi,
With the following setup, sound does not seem to work:
kernel: 2.6.19
alsa (driver, lib, utils): 1.0.13
motherboard: Intel DG965
chipset: Intel® G965 Express Chipset
controller: ICH8
audio: 6-channel (5.1) audio subsystem using the SigmaTel STAC9227
audio codec
lspci output:
0000:00:1b.0 0403: 8086:284b (rev 02)
Subsystem: 8086:2113
Flags: bus master, fast devsel, latency 0, IRQ 20
Memory at 92320000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable-
Capabilities: [70] #10 [0091]
However if I boot from a Knoppix 5.0 CD, the sound does work
(kernel: 2.6.17
alsa: 1.0.11rc4
codec: SigmaTel ID 7618)
I wonder if this is related to the issue referred to in the thread on
2006-10-26 "[PATCH] hda: add sigmatel dig mic support and refactor 9227"
- specifically about refactoring 9227. (As of 1.0.14rc1 this seems to be
still outstanding...)
At any rate if there is a way to get this configuration working, I'd
greatly appreciate the information. Alternatively, it seems that it
might work with the generic driver (ala Knoppix), but I have not been
able to figure out how to force that to load.
Thanks in advance,
Ed
-------------------------------------------------------------------------
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:[~2007-01-11 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 14:24 Ed Wright [this message]
2007-01-15 10:46 ` intel-hda, 965 chipset, STAC9227 - problem - resolved Ed Wright
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=45A6488F.4010808@gmail.com \
--to=edo.wright@gmail.com \
--cc=alsa-devel@lists.sourceforge.net \
/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