From: "Igor Gueths" <igueths@yahoo.com>
To: <speakup@braille.uwo.ca>
Subject: Re: Sound card question
Date: Wed, 27 Mar 2002 14:55:10 -0500 [thread overview]
Message-ID: <007701c1d5c9$4e4b8740$01213e18@mycomputer> (raw)
In-Reply-To: <Pine.LNX.4.44.0203270747270.226-100000@maranatha.chartermi.net>
Hi Cheryl. I know the kernel 2.4.18 drivers support the sblive card natively. I don't know about the alsa drivers. They probably do, but just check the list of supported sound cards at www.alsa-project.org to make sure. What you could try doing if you want a backup is recompiling the sb16 driver into the kernel as a module, that way you can just switch modules by doing rmmod on the sb16 driver then doing modprobe or insmod on the sblive module. Hope this helps.
----- Original Message -----
From: Cheryl Homiak <chomiak@chartermi.net>
To: speakup <speakup@braille.uwo.ca>
Sent: Wednesday, March 27, 2002 8:50 AM
Subject: Sound card question
> Hi all!
> I am getting a sblive sound card today, but I am a bit nervous about it working,
> probably just because I've had the old sb16 for so long.
> 1. If I compile it into the kernel, do I also have to load other drivers or not?
> 2. would it be ok to leave my sb16 in until I know this is working? If so, do I
> have to take the sb16 out of the kernel when trying the sblive? I think I read
> something about sblive not working in a multiple card setup. I don't want a
> multiple setup; I just want a backup in case i have trouble getting the sblive
> to work.
> Thanks.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Cheryl Homiak
` Terry Cudney
` Igor Gueths [this message]
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='007701c1d5c9$4e4b8740$01213e18@mycomputer' \
--to=igueths@yahoo.com \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).