On Mon, 8 Mar 1999, Andre Grosse Bley wrote:

> I played a bit with the box today (sorry, had no chance to capture the dump, 
> someone 'borred' my cableset, and the cable for my console terminal is a 
> special one...), but it occurs while scsi scan.

Hm, that's not the same place as the crash I saw during testing.

> After disconnecting both disc drives
>   Vendor: IBM       Model: MXT-540SL         Rev: J1.5 (id 0)
>   Vendor: SEAGATE   Model: ST32430N          Rev: 0510 (id 1)
> the boot up works without panic, but i dont have anything to install on. The 
> tape drive (Vendor: ARCHIVE   Model: Python 25501-XXX  Rev: 2.26 (id 6)) is 
> still connected.

What about trying each drive seperately?

> Perhaps the delay after scsi bus reset to begin of inquiry is too short? [I 
> only know FreeBSD on i386, and there's an kernel option for this delay)

There's no option. The delay is fixed at around 250mS.

> BTW, i tried another board (MVME 167B , 16 MB non ecc ram, 68040/25, but not 
> configured [pressed abort while poweron:)]), and after booting kernel from 
> tape i got the bug prompt again. no error, just "Entry point is 0x0x0800" and 
> "bug167>". Strange!

When you say 'not configured' I assume you mean that the NVRAM
contents are not valid? You could try pressing reset and abort at
the same time, then releasing reset while still holding abort.
If you release abort after a few seconds, the ROM code will copy
defaults into NVRAM. You'll still have to manually set up the
ethernet address, time and memory configuration though.

Cheers, Steve