IBM OEM drive (E15) as boot device

Thread View: comp.sys.next.sysadmin

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by paul buster Sun, 01 Nov 1992 21:07

#66

Author: paul buster
Date: Sun, 01 Nov 1992 21:07

39 lines
1703 bytes

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
SCSI unexpected msg: 1
sc: Unexpected msg
SCSI unexpected msg: 1
sc: Unexpected msg
booting SCSI target 2, lun 0
blk0 boot: sd()sdmach
SCSI unexpected msg: 1
sc: Unexpected msg
sd: target 1 lun 0 opcode 18
sd: addr 0x43bbf10 bcount 66 rdflag 1
sd: sdstatus 0 sdstate 0 resid 66
sc: s5c state 7 status 0x87
sc: intrstatus 0x8 seqstep 0x4
sc: fifo level = 0 transfer count 0
sc: command 0x10 config 0x57 

on one 25Mhz machine, it goes ahead and boots, but on another 25MHz
system it just hangs.  It _acts_ like it's not getting a boot block
from the IBM drive, finds one on the NeXT drive, then returns to find
mach on the IBM drive.  I've tried playing with disk -i and disk -b
but with no progress.

can anyone in netland tell me what's going on and if there's a fix ?

thanks
-paul buster
buster@mongrel.Colorado.EDU

Re: IBM OEM drive (E15) as boot device

#73

Author: Dave Olson
Date: Mon, 02 Nov 1992 04:18

27 lines
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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads