I can't get to the error.  The boot process occurs normally, and the error manifests
itself only in userland.  I get a healthy dmesg, some of which I've quoted below.
Upon running a newfs, either from sysinst or from a shell, the system slams a
millisecond worth of debug (how do I get to this?) to the screen and hard resets.

fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
mcclock0 at isa0 port 0x70-0x71: mc146818 or compatible
mcbus0 mid 2: CPU 4MB BCache
scsibus0: waiting 2 seconds for devices to settle...
cd0 at scsibus0 targ 5 lun 0: <DEC, RRD46   (C) DEC,  1337> SCSI2 5/cdrom removable
probe(ncr0:5:1): 10.0 MB/s (100 ns, offset 8)
scsibus1: waiting 2 seconds for devices to settle...
de0: enabling 10baseT port
scsibus2: waiting 2 seconds for devices to settle...
isp1: SCSI bus 0 reset detected
sd0 at scsibus2 targ 0 lun 0: <DEC, RZ1CB-CA (C) DEC, LYJ0> SCSI2 0/direct fixed
sd0: 4091 MB, 3708 cyl, 20 head, 113 sec, 512 bytes/sect x 8380080 sectors
isp1: SCSI bus 2 reset detected
sd1 at scsibus2 targ 2 lun 0: <DEC, RZ1CB-CA (C) DEC, LYJ0> SCSI2 0/direct fixed
sd1: 4091 MB, 3708 cyl, 20 head, 113 sec, 512 bytes/sect x 8380080 sectors
isp1: SCSI bus 4 reset detected
sd2 at scsibus2 targ 4 lun 0: <DEC, RZ1CB-CA (C) DEC, LYJ0> SCSI2 0/direct fixed
sd2: 4091 MB, 3708 cyl, 20 head, 113 sec, 512 bytes/sect x 8380080 sectors
md0: internal 4650K image area
WARNING: can't figure what device matches "DVA 0 1000 0 0 0 8086 0002"
root on md0a dumps on md0b
root file system type:ffs
Terminal type? [vt100]

The warning above refers to the floppy drive, which is probed as fd0 earlier in the
dmesg just fine.

Thanks,
dhop


Matthew Jacob wrote:

> On Thu, 9 Dec 1999, David Hopper wrote:
>
> > Thanks, Matthew.  It's a Digital-supplied card, part of the default
> > setup for the 1200.  I have a null serial link, but I'm not able to
> > get past the Terminal type request.  What settings will I need for the
> > SRM and/or kernel, to capture the boot sequence, and still have
> > control of sysinst or /bin/sh?  (I can control the SRM properly
> > through serial, but lose it on NetBSD)
>
> Can you cut and paste or say what the boot messags are?
>
> >
> > Hell, this is weird.  I've used NetBSD since 0.8, and I've _never_ had to do
> > this.  I feel so...  ...special...  :)
> >
> > Thanks again,
> > dhop
> >
> > Matthew Jacob wrote:
> >
> > > I'm sorry if I missed any previous mail on this. There's some uncertainty
> > > as to whether a big checkin of ISP code on 12/4 made the 12/4 snapshot.
> > > It's certainly true that an important fix to isp_netbsd.c on 12/5 didn't.
> > >
> > > Also- is the Qlogic 1040B you used a Digital supplied card?
> > >
> > > -matt
> > >
> > > On Thu, 9 Dec 1999, Matthew Jacob wrote:
> > >
> > > >
> > > > How about some details as to why it doesn't work for the isp?
> > > >
> > > > On Thu, 9 Dec 1999, David Hopper wrote:
> > > >
> > > > > Hot damn.  It works, but not with the QLogic ISP1040B that comes with
> > > > > the box.  I replaced this with an Adaptec 2940, and I'm up and running.
> > > > > >From what I can see so far (I'm still hammering at it...), it looks like
> > > > > NetBSD has chalked up another model number.
> > > > >
> > > > > Thanks, guys!!
> > > > > dhop
> > > > >
> > > > >
> > > >
> >