From: kswisher@iolinc.net (Swisher, Karl)
To: linux-sound@vger.kernel.org
Subject: Re: setting up sblive
Date: Fri, 23 Jul 1999 15:26:48 +0000 [thread overview]
Message-ID: <marc-linux-sound-93275908422115@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93269644400113@msgid-missing>
On Thu, 22 Jul 1999, Abe Smith wrote:
I have about the same setup except a K6-2 350mhz I have the 0.3 driver. I
havent' got everyting to work yet either. It may be a week or two before I get
a chance to try a recompile of the kernel. My problem I think is that there
are still some leftover modules still hanging around. I believe it will work,
we are just not doing something right yet.
> I apologize in advance for the foolishness of this question:
> I'm trying to use an SB Live! on a P133 with 128M running redhat 5.2
> (kernel 2.0.36-0.7)
> I was previously using a quirky sb16
>
> I'm trying to get Creative's v0.2 beta driver to work, and the install
Try the v0.3
process claims to work, and have tried the "manual" method as well (as
> per the INSTALL file). The card doesn't even seem to be recognized on
> boot, and of course, none of the audio devices work.
My card is recognized on boot and I can get CD's and MP3's to play. Haven't
been able to get the digital I/O or the MIDI working.
Thanks
Karl
> are there any thing
obvious that I'm missing? > I've neve really dealt with modular kernels before..
anything I'm > missing there?
> might the v0.3 driver work, even with my slower CPU, etc?
>
>
> thanks
>
>
> --
> Abraham D. Smith <abesmith@execpc.com> Wisconsin, USA
> --------------------------------------------------------
next prev parent reply other threads:[~1999-07-23 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-23 2:24 setting up sblive Abe Smith
1999-07-23 15:26 ` Swisher, Karl [this message]
1999-07-23 20:27 ` Abe Smith
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=marc-linux-sound-93275908422115@msgid-missing \
--to=kswisher@iolinc.net \
--cc=linux-sound@vger.kernel.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.