From: "John Bäckstrand" <sandos@home.se>
To: <linux-kernel@vger.kernel.org>
Subject: sb16 isa non-pnp problems
Date: Fri, 10 May 2002 03:26:49 +0200 [thread overview]
Message-ID: <001101c1f7c1$c233fba0$0319450a@sandos> (raw)
Ive been trying to get my sb16 isa non-pnp working on a
old 486, it has got two isa slots.
Ive checked the config of both my two NICs (tried two
different ones), and the config on my sb16, no
conflicts, and I am sure that I set the correct
parameters. I also tried a pnp isa sb16 (vibra). Ive
tried 2.2.20 and 2.4.17, both compiled in and module,
but not every possible combination though.
The problems Im seeing is for the pnp card that it isnt
detected at all, even if I do modprobe sb io=0x220
dma=1 irq=5, I guess that is because I cant seem to be
able to configure it using pnp, isapnp didnt print
anything and the conf-files seemed very long-winded.
The non-pnp card is atleast detected, and I can even
get sound from it. The sb16 DOS-util diagnose.exe from
creative plays fine on this card, but it doesnt even
detect the newer pnp card. Anyway, in linux I can cat
/dev/urandom > /dev/dsp on my non-pnp, and will get
noise. But my system will hang after about 10-20
seconds with this. Playing a mp3 using mpg123 gets me a
seg fault, or unable to handle paging request, aiiie:
killing interrupt handler or some other oops.
Any ideas? I have looked into /proc/interrupts,
/proc/ioports, /proc/dma, and there are no conflicts
afaics. Its an oldish 486, 20mb ram, running a
overdrive 80mhz right now.
---
John Bäckstrand
next reply other threads:[~2002-05-10 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 1:26 John Bäckstrand [this message]
2002-05-10 3:48 ` Albert D. Cahalan
2002-05-10 9:48 ` Zwane Mwaikambo
2002-05-10 13:12 ` John Bäckstrand
2002-05-10 11:30 ` Kurt Roeckx
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='001101c1f7c1$c233fba0$0319450a@sandos' \
--to=sandos@home.se \
--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
all inboxes | Powered by JetHome®