We've encountered a magic bug of loadbsd.
 A friend of mine has an A3000 with 2MB Chip and 3MB (!) Fast.

 It depends on when he starts loadbsd (after booting ADos fully into
WB, or disabling startup-seq) whether he is able to successfully
boot into netbsd. 

 W/o startup-seq loadbsd/netbsd recognize his maschine correctly as
A3000 and successfully boots. Otherwise his machine pretends to be
an A500/A2000 and doesn't boot at all (no SCSI/rootfs found).

 This is using latest loadbsd and latest kernel from snapshot.

-- 
Markus Illenseer 

------------------------------------------------------------------------------