Hello!

The ELF bootblocks are giving me some headache. The system is:
NetBSD 1.5R (MUULI) #0: Thu Jan  4 08:43:49 PST 2001
    root@newmuuli:/usr/src/sys/arch/hp300/compile/MUULI
    HP 9000/385 (33MHz MC68040 CPU+MMU+FPU, 4k on-chip physical I/D caches)

<snip>

oscsi0 at dio0 scode 14 ipl 3: 32 bit dma, async, no parity, scsi id 7
sd0 at oscsi0 targ 0 lun 0: <HP, D2076A, 8870> (SCSI-2)
sd0: 1872 cylinders, 15 heads, 2059140 blocks, 512 bytes/block
sd1 at oscsi0 targ 1 lun 0: <HP, C2247-300, 0BA4> (SCSI-2)
sd1: 2051 cylinders, 13 heads, 2054864 blocks, 512 bytes/block
sd2 at oscsi0 targ 2 lun 0: <MICROP, 4421-07   0329SJ, 0329> (SCSI-2)
sd2: 4049 cylinders, 7 heads, 4193360 blocks, 512 bytes/block
st0 at oscsi0 targ 3 lun 0: <ARCHIVE, Python 25501-XXX, 4.BN> (SCSI-2)
sd3 at oscsi0 targ 4 lun 0: <MATSHITA, CD-ROM CR-8008, 8.0e> (SCSI-2)
sd3: CD-ROM, 91402 blocks, 2048 bytes/block
st1 at oscsi0 targ 5 lun 0: <EXABYTE, EXB-8200, 251K>
dcm0 at dio0 scode 17 ipl 5
fhpib0 at dio0 scode 19 ipl 3: 98625A/98625B HP-IB
hpibbus1 at fhpib0
internal parallel at dio0 scode 24 not configured
le0 at dio0 scode 25 ipl 4: address 08:00:09:07:9b:98
le0: 8 receive buffers, 2 transmit buffers
fhpib1 at dio0 scode 29 ipl 3: 98625A/98625B HP-IB
hpibbus2 at fhpib1
oscsi1 at dio0 scode 30 ipl 3:async, scsi id 7
interrupt levels: bio = 3, net = 4, tty = 5
boot device: sd2
root on sd2a dumps on sd2b

(It's a 380 actually, the wait state jumper makes it lie)
I have root on sd2a and the HP is set to select sd2 (1Z in this case) 
automatically. However the bootblocks suggest booting from
sd131a:netbsd, followed by a failed attempt with "bad adaptor number".

This *only* happens after power-on, not after shutdown -r. It's not
a big deal but it is pretty annoying as it's supposed to run pretty
much headless. This did not happen with 1.5.

I got a "panic: bad dir" which ate away a sizable hunk of my fs. I'll
downgrade this to 1.5 and continue experimenting with nfs-rooted machines.

TIA,
-- 
jht