On Jul 21,  5:07pm, Markus Illenseer wrote:
>  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).

  Loadbsd now tries to determine what machine it is running on and passes
that machine type to the kernel.  The kernel assumes that value is correct
and configures based on that.  If loadbsd says it's running on an A2000/A500,
then the kernel won't try to configure the A3000 scsi and it's not suprising
it doesn't find the SCSI device.

  The test for the A3000 is if there is a module named either "A3000 bonus"
or "A3000 Bonus" in the Exec Resident Module list.  It looks like something
in the startup-sequence must be modifying this in some fashion.

  You can force the machine type with the -c 3000 option on loadbsd - this
will override the attempt to automagically determine the machine type
(which certainly isn't fool proof).

Michael

-- 
Michael L. Hitch			INTERNET:  osymh@montana.edu
Computer Consultant
Office of Systems and Computing Services
Montana State University	Bozeman, MT	USA

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