From: Alessandro Zummo <azummo@ita.flashnet.it>
To: linux-sound@vger.kernel.org
Subject: Re: SB, PNP, kernel, etc.
Date: Tue, 15 Feb 2000 22:07:02 +0000 [thread overview]
Message-ID: <marc-linux-sound-95066320710986@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95071956214609@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 292 bytes --]
Amiga............: YAM http://www.yam.ch/
Unix.............: Metamail ftp://ftp.bellcore.com/nsb/
Windows/Macintosh: Eudora http://www.qualcomm.com/
General info about MIME can be found at:
http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/mime-faq/top.html
[-- Attachment #2: Type: text/plain, Size: 958 bytes --]
On 15-Feb-00 at 23:22:14,
Peter Leif Rasmussen <plr@cedara.com> wrote:
> I have also tried to compile the SB driver as a module, run isapnp with
> the isapnp.conf file that came out of using "pnpdump -c", but edited to
> use the same values as when compiling the driver into the kernel. And then
> attempting to load the driver with depmod (and I also attempted insmod).
> Here I usually get a message that there isn't any PNP device, and that
> puzzles me because executing "isapnp isapnp.conf" went all right?
Well, that's a fault of mine. Kernel 2.3.45 has a new pnp
driver for the soundblaster.
Unluckly is still bugged, so here is a patch for you.
You could simply apply it over your 2.3.45 kernel tree,
but remember to remove it before upgrading to 2.3.46.
If it doesn't still work, please send me the output
of cat /proc/isapnp and check for relevant parts
in the kernel log file(s).
--
- *Alex* -
http://freepage.logicom.it/azummo/
[-- Attachment #3: sb_patch.2.3.45.gz --]
[-- Type: application/octet-stream, Size: 4781 bytes --]
next prev parent reply other threads:[~2000-02-15 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-13 4:48 SB, PNP, kernel, etc
2000-02-15 21:22 ` Peter Leif Rasmussen
2000-02-15 22:07 ` Alessandro Zummo [this message]
2000-02-16 9:18 ` Alessandro Zummo
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-95066320710986@msgid-missing \
--to=azummo@ita.flashnet.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox