🚀 go-pugleaf

Hello,

I recently put a NCR53c810 PCI SCSI card in my ACER montherboard with 
the NCR bios.  After finally getting the SCSI card correctly 
configured, as far as I can tell, I am having troubles getting it to
talk to my SCSI IBM 0663-E15 1.0 gig hard disk.  During the booting of
Linux everything seems ok until the SCSI config phase gets to that disk.
I also have an Archive Viper 150 QIC tape in the SCSI chain and it 
configures that ok.   Then it hangs on the SCSI disk (next target).  When
I unplug the power to the disk and reboot all is well.  I successfully
loaded a cpio file off of the tape drive and it works great.  Here is
an output of the kernel during the SCSI config phase at boot time with both
the hard disk and the tape drive connected and powered up:

scsi-ncr53c7,8xx : at PCI bus 0, device 3,  function 0
scsi-ncr53c7,8xx : warning : revision of 2 is greater than 1.
scsi-ncr53c7,8xx : NCR53c810 at memory 0x2000000, io 0xd000, irq 15
scsi0 : using io mapped access
scsi0 : using initiator ID 0
scsi0 : using edge triggered interrupts.
scsi0 ; burst length 2
scsi0 : using 40MHz SCSI clock
scsi0 : m_to_n = 0x10, n_to_m = 0x20, n_to_n = 0x30
scsi0 : NCR code relocated to 0x20d74c
scsi0 : testing
scsi0 : test 1 started
scsi0 : tests complete.
scsi0 : NCR53c{7,8}xx (rel 3)
scsi : 1 host.
  Vendor: ARCHIVE   Model: VIPER 150  21247  Rev: -005
  Type:   Sequential-Access                  ANSI SCSI revision: 01
Detected scsi tape st0 at scsi0, id 1, lun 0
scsi0: target 2 requesting synchronous transfer transfer period 100ns, offset 12
scsi0: setting target 2 to asynchronous SCSI
 
The boot process just hangs after the "scsi0: setting target 2 to 
asynchronous SCSI" line.  I have to power cycle the system.  I did notice the
mismatch between synchronous and asynchronous transfers in the last two lines
but I don't know enough about what was going on at the low level to 
understand what it means.  I had the drive working in a Sun workstation just
fine prior to attempting to put it in my PC. 

In the literature (2 pages...) that came with the hard disk there is the
following paragraph which may be relevant:

Comments:
The 0663-E15 drive listed above has modified microcode which does not return
the 'Unit Attention' condition in response to the first SCSI command sent
following a power up or SCSI bus reset.  Additionally the microcode on the 
drive supports the 'Blind Write' feature commonly used by Apple Platforms.
Both of these features are needed to allow attachment to the Apple environment.

Any ideas to what is going on are appreciated....

Thanks
	- Dan