From: Kurt Roeckx <Q@ping.be>
To: Jim Bonnet <jimbo@sco.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sb.o support in 2.4-broken?
Date: Wed, 8 Nov 2000 21:19:09 +0100 [thread overview]
Message-ID: <20001108211909.A7107@ping.be> (raw)
In-Reply-To: <3A09BD3E.9F2FAF04@sco.com>
In-Reply-To: <3A09BD3E.9F2FAF04@sco.com>
On Wed, Nov 08, 2000 at 12:53:18PM -0800, Jim Bonnet wrote:
> I am using the 2.4.0-test10 kernel. I have a sound blaster 16 which
> works fine under 2.2.17.
>
> I see that a while back someone posted on this problem previously but
> there were no answers I can find..
>
> Is support for soundblaster16 ISA broken in the 2.4 kernel? Compiled in
> or used as a module I can not get it to work. I have passed sb=220,5,1,5
> during boot when compiled in and also sent those during insmod.
Use sb=0x220,5,1,5
Kurt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-08 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 20:53 sb.o support in 2.4-broken? Jim Bonnet
2000-11-08 20:19 ` Kurt Roeckx [this message]
2000-11-08 20:49 ` Richard Torkar
2000-11-08 20:57 ` Richard Torkar
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=20001108211909.A7107@ping.be \
--to=q@ping.be \
--cc=jimbo@sco.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox