Return-Path: owner-linux-activists@Niksula.hut.fi
Return-Path: <owner-linux-activists@Niksula.hut.fi>
Received: from joker.cs.hut.fi by hydra.Helsinki.FI (4.1/SMI-4.1/39)
	id AA06042; Fri, 16 Apr 93 02:09:16 +0300
Received: from joker.cs.hut.fi by niksula.hut.fi id <61531-11>; Fri, 16 Apr 1993 02:08:38 +0300
From: "Linux Activists" <linux-activists@Niksula.hut.fi>
To: "Linux-Activists" <linux-activists@Niksula.hut.fi>
Reply-To: "Linux-Activists" <linux-activists@Niksula.hut.fi>
X-Note1: Remember to put 'X-Mn-Key: DOC' to your mail body or header
Subject: Linux-Activists - DOC Channel digest. 93-3-15-19:46
X-Mn-Key: DOC
Sender: owner-linux-activists@Niksula.hut.fi
Message-Id: <93Apr16.020838eet_dst.61531-11@niksula.hut.fi>
Date: Fri, 16 Apr 1993 02:08:30 +0300
Status: RO
X-Status: 


Topics:
	 Re: Linux-Activists - DOC Channel digest. 93-3-15-13:5 


----------------------------------------------------------------------

From: Drew Eckhardt <drew@frisbee.cs.Colorado.EDU>
Subject: Re: Linux-Activists - DOC Channel digest. 93-3-15-13:5 
Date: Thu, 15 Apr 1993 21:33:28 +0300


--------

    
    Topics:
    	 splitting man(2) pages
    	 DTC scsi adaptors
    
    
    ------------------------------
    
    From: johnsonm@stolaf.edu (Michael K Johnson)
    Subject: DTC scsi adaptors
    Date: Thu, 15 Apr 1993 17:03:26 +0300
    
    
       When you boot the a1 disk, check to see if the kernel detects any
       SCSI hosts. You should get a message like "1 scsi hosts detected"
       and "host 1 is an Adaptec 1542".
    
       If you get a "0 SCSI hosts found" and the parition table check
       fails, then I fear that the 3292 isn't compatible with the 1542.
    
    Or that the BIOS signature is slightly different.  If it doesn't work,
    contact the author of the Adaptec 1542 driver and give him your bios
    identification string.  If you don't know how, he should be able to
    help you out...  You just use debug and look around, and many adaptors
    actually print out their ID string (or part of it) on bootup (bios
    check, actually), so it isn't hard to find.

No, the Adaptec driver simply pokes at ports trying to discover a 
host adapter.  The 1542C, an allegedly 100% Adaptec Compatable 
board didn't respond favorably to this routine (Eric 
fixed this problem) perhaps other Adaptec Compatables have similar 
problems.
    



------------------------------

End of DOC Digest
*****************
-------
