fnddr@acad3.fai.alaska.edu (Rice Don D) (10/02/90)
This shouldn't be so much work, and it seems that lots of people are using the HP drives (HP97549T, 1GB) with DECstations, so either: (a) I'm missing an obvious step, (b) the drive jumpers are set wrong, or (c) the drive is defective. Basically, the drive is set as unit 1, and cabled between an rz55 (rz0) and a tk50 (tz5), which has the terminator. The DS5000 monitor cnfg 5 shows all three, with rz1 ID=97549T100, VID=HP. When I boot 5/rz0/vmunix with the HP drive off, I get a normal boot, which includes the following: fpu0 (version 2.0, implementation 3) asc0 at ibus5 ... etc When the HP drive is powered up, the boot sequence prints instead: fpu0 (version 2.0, implementation 3) scsi bus 0: command aborted (#0), ID=1, cmd=0x48 scsi bus 0: resetting bus (#2) Exception condition ... cpu 0 panic: trap ... lots more exceptions and register dumps ... ...and I end up back at monitor level. Things I've tried: -modifying the RZ57 definition in /sys/data/scsi_data.c to match the HP's ID. Booting this kernel gave exactly the same errors as above. -changing some of the drive jumpers. They came set like so: 1 1 Power to termination: 2 0 power to on-board terminators only. * 3 1 Unit attention disabled. 4 0 Inhibit initiation of SDTR (sync data transfer) message. 5 1 Parity checking enabled. 6 1 Auto spin up when powered on. I tried changing 3 and 4 with no effect. * The on-board terminating resistors have been removed. So, what have I missed? This is the first 3rd party drive I've tried to add to Ultrix so I could be leaving out something very obvious. Effusive thanks to anyone who can offer a suggestion, Don Rice Internet: fnddr@flux.fai.alaska.edu Geophysical Institute E-mail: fnddr@acad3.fai.alaska.edu University of Alaska Phone: (907) 474-7569 Fairbanks, AK 99775 Loran: 64.86N 212.16E