🚀 go-pugleaf

wolff@mhwsys.han.de (Markus Wolff) writes:

>I have an ASUS PCI/I P5MP3 (Rev. 3.1) Mainboard with the optional
>NCR 53c810 based ASUS PCI-SC200 SCSI Controller.
>The board has Mercury Revision 3.

>When I boot Linux 1.1.64 (earlier versions don't work either...)
>it prints the following:

>bios32_init : BIOS32 Service Directory Structure at 0xfb0a0
>bios32_init : BIOS32 Service Directory entry at 0xfb320
>pcibios_init : PCI BIOS revision 2.00 entry at 0xfb350
>..
>...
>...
>scsi1: at PCI BUS 0, device 6, function 0
>scsi1: NCR53c810 at memory 0xfc000000, io 0xd000, irq 15

>and then it just hangs ....

This is the typical reaction if you have wrong configured interrupts.
Your CPU doesn't get informed if the NCR sends an interrupt, so it waits
and waits and waits ...

In this case, the MINICAM.SYS and DOSCAM.SYS drivers you get with your
board for DOS will also hang at the same point of initialisation. Do they?
DOS BIOS doesn't use the interrupt for accessing the NCR (single-tasking
operating systems can afford to poll), so if DOS without DOSCAM.SYS
works, this indicates nothing about the interrupts.

Correct configuration of the NCR is (as it should also be described
in detail in your manual and as it is the default configuration):

level triggered interrupts for the slot in which the NCR is, route the
INTA of this slot to IRQ 9, jumper the NCR card, so that it uses 
INTA. This is what the PCI standard wants and this is what works for me.

If you have rare crashes if two SCSI devices (e.g. harddisk and cdrom) are
used simultaneously and if your disk hangs if the tape rewinds: this are
known Linux driver problems, I hope that Drew will release the fixes soon
(when, Drew? ;-).

>Adaptec: 1.4MB/s
>NCR: 3.4 MB/s

I get 4.0 MB/s with the NCR on DOS :-)

Markus

---
Markus Kuhn, Computer Science student -- University of Erlangen,
Internet Mail: <mskuhn@cip.informatik.uni-erlangen.de> - Germany
WWW Home: <http://wwwcip.informatik.uni-erlangen.de/user/mskuhn>