From: dbm <db.mo@bigpond.com>
To: alsa-devel@alsa-project.org
Subject: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG (SB0820)
Date: Sun, 21 Feb 2010 11:41:32 +1000 [thread overview]
Message-ID: <4B808F4C.1020904@bigpond.com> (raw)
Greetings,
Just bought one of these to get around the fact the mobo involved
wouldn't recognize
any soundcard plugged into either PCI slots (onboard sound disabled in
BIOS) -- it will
however see a soundcard plugged into the pcie 1x slot.....
03:00.0 PCI bridge: Creative Labs Device 7006 (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=03, secondary=04, subordinate=04, sec-latency=32
Memory behind bridge: ee000000-ee0fffff
Capabilities: [50] Power Management version 3
Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+
Queue=0/4 Enable-
Capabilities: [80] Subsystem: Creative Labs Device 0010
Capabilities: [90] Express PCI/PCI-X Bridge, MSI 00
Capabilities: [100] Advanced Error Reporting <?>
Kernel modules: shpchp
04:00.0 Audio device: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG
Subsystem: Creative Labs Device 0018
Flags: bus master, medium devsel, latency 32, IRQ 16
Memory at ee000000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [dc] Power Management version 3
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
Does seemed to be claimed by snd-hda-intel (vid/pid 1102/0009), but
subsystem descriptor
of 1102/0018 is seemingly unknown by the drivers. Wild guess here is
this should be claimed
by ctxfi.ko? I can provide a list of hardware IC's fitted to the card --
most of them are *not*
codec chips afaict.....that said, 2 oncard chips I cannot readily
identify. My suspicion is it's
like other cards covered by ctxfi.ko in that the card has no
ac97-codec fitted and is just a
plain ole' sblive type card....but this is only speculation...
Anyone seens one of these, or have any idea where to start poking for
clues (if any) to get it
working?
Cheers!
reply other threads:[~2010-02-21 1:41 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=4B808F4C.1020904@bigpond.com \
--to=db.mo@bigpond.com \
--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.