sb16 isa non-pnp problems

sb16 isa non-pnp problems

[John Bäckstrand]

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

Re: sb16 isa non-pnp problems

[Albert D. Cahalan]

> Ive been trying to get my sb16 isa non-pnp working on a
> old 486, it has got two isa slots.
...
> 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.

Ditch isapnp and those config files. If using Red Hat,
add "nopnp" to the kernel command line. Configure your
kernel (2.4.xx or 2.5.xx) to handle ISA PnP by itself.

> 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.

Blame your motherboard. Many 486 motherboards have
trouble with DMA. I've had similar problems with a
real SoundBlaster16 and a "486". (IBM BlueLightning
486SLC2-66, Intel 486SX-25, and Intel DX4-75 OverDrive)

DOS DOOM played in DOS     --> crash
DOS DOOM in an OS/2 window --> OK
Linux with 8-bit sounds    --> OK
Linux with 16-bit sounds   --> crash

Forget about sound, junk the box, or use OS/2.

Re: sb16 isa non-pnp problems

[Zwane Mwaikambo]

I wouldn't mind seeing the dmesg+oops of a 2.4.18ish kernel with 
kernel ISAPNP. As well as /proc/isapnp before loading the module, and if 
possible /proc/dma and /proc/ioports after loading.

Thanks,
	Zwane

-- 
http://function.linuxpower.ca
		

Re: sb16 isa non-pnp problems

[Kurt Roeckx]

On Fri, May 10, 2002 at 03:26:49AM +0200, John Bäckstrand wrote:
> 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.

I still have a SB16 ISA non-PNP around here and used it until a
few months ago.  It always worked perfectly.  It worked with 2.4,
2.2, 2.0 and older.

In my lilo.conf I had: append="sb=0x220,7,1,5"

So io=0x220, irq=7, dma=1 and dma16=5


Kurt

Re: sb16 isa non-pnp problems

[John Bäckstrand]

----- Original Message -----
From: "Zwane Mwaikambo" <zwane@linux.realnet.co.sz>
To: "John Bäckstrand" <sandos@home.se>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, May 10, 2002 11:48 AM
Subject: Re: sb16 isa non-pnp problems


> I wouldn't mind seeing the dmesg+oops of a 2.4.18ish
kernel with
> kernel ISAPNP. As well as /proc/isapnp before loading
the module, and if
> possible /proc/dma and /proc/ioports after loading.

They all look normal, afaics, and its probably not a
linux-pnp problem, since we found the problem. It was
the overdrive CPU causing problems. Works fne with the
original DX33. This was also the case in windows.
Suspecting wrong voltage to the cpu, ah well. Thanks
anyway =)

---
John Bäckstrand