Article View: comp.sys.next.sysadmin
Article #73Re: IBM OEM drive (E15) as boot device
From: Dave Olson
Date: Mon, 02 Nov 1992 04:18
Date: Mon, 02 Nov 1992 04:18
27 lines
1610 bytes
1610 bytes
In <1992Nov1.210746.2846@colorado.edu> buster@mongrel.Colorado.EDU (paul buster) writes:
| I've been working with IBM 1GB OEM drives (0663 H12 and E15)
| They seem to work fine if they're not being used as boot devices.
|
| I followed the instructions about modifying the proprietary mode
| select sense page number 0, but when I try to boot from the IBM
| drive, I get the following (with the IBM as SCSI ID 1 and the NeXT
| internal drive as SCSI ID 2):
|
| Boot command: sd
| boot sd(0,0,0)
| SCSI unexpected msg: 1
| sc: Unexpected msg
It looks to me like you have the IBM drive that *always* does
target initiated synchronous negotiations, and the NeXT PROMs
can't handle that.
I know that IBM has customized the firmware for some vendors
to *not* do target initiated sync (i.e., to wait until the host
does it). Whether your drive is cabple of having that set without new
firmware, I don't know.
--
Let no one tell me that silence gives consent, | Dave Olson
because whoever is silent dissents. | Silicon Graphics, Inc.
Maria Isabel Barreno | olson@sgi.com
Technical Details
Message-ID:
<rre9sj4@zuni.esd.sgi.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!usc!sol.ctr.columbia.edu!spool.mu.edu!agate!ames!sgi!fido!zola!zuni!anchor!olsonReferences:
<1992Nov1.210746.2846@colorado.edu>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.sysadmin Path: arc1-ca.pugleaf.net!sparky!uunet!usc!sol.ctr.columbia.edu!spool.mu.edu!agate!ames!sgi!fido!zola!zuni!anchor!olson From: olson@anchor.esd.sgi.com (Dave Olson) Subject: Re: IBM OEM drive (E15) as boot device Message-ID: <rre9sj4@zuni.esd.sgi.com> Sender: news@zuni.esd.sgi.com (Net News) Organization: Silicon Graphics, Inc. Mountain View, CA References: <1992Nov1.210746.2846@colorado.edu> Date: Mon, 2 Nov 92 04:18:01 GMT Lines: 27