From: Lee Revell <rlrevell@joe-job.com>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Hardware info for SBLive platinum
Date: Sat, 26 Mar 2005 17:07:07 -0500 [thread overview]
Message-ID: <1111874827.957.2.camel@mindpipe> (raw)
In-Reply-To: <4245DC54.6070206@superbug.co.uk>
On Sat, 2005-03-26 at 22:04 +0000, James Courtier-Dutton wrote:
> Lee Revell wrote:
> > James,
> >
> > My old SBLive! platinum is being detected as "SBLive! [Unknown]".
> > Here's some info:
> >
> > 0000:00:0f.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 05)
> > Subsystem: Creative Labs CT4760 SBLive!
> >
> > 0000:00:0f.0 0401: 1102:0002 (rev 05)
> > Subsystem: 1102:8040
> >
> > I feel like an idiot, but I don't see a model number of the form SB0xxx
> > anywhere. Is CT4760 the model number?
> >
> > Lee
> >
> >
>
> Yes, CT4760 is the model number.
> See http://us.creative.com/support/identifyproduct/
>
OK. I still feel stupid that I had to boot into Windows to figure that
out ;-).
> I will add that ID to the snd-emu10k1 driver
> Do you use any special extin/extout with it. I might add automatically
> setting those to the detection code.
I have heard that an extout/extin option is needed to get the MIDI port
on the Livedrive working. But to be honest I have never tried it. The
audio IO on the livedrive works great with no module options.
I'll see if I can find a MIDI cable and test it.
Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-26 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 21:53 Hardware info for SBLive platinum Lee Revell
2005-03-26 22:04 ` James Courtier-Dutton
2005-03-26 22:07 ` Lee Revell [this message]
2005-03-26 22:26 ` Lee Revell
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=1111874827.957.2.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=James@superbug.co.uk \
--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