Hello!

After a little more playing, learning and scanning of source, I finaly
figured out all of the errors that I had when compiling my own 1.2.1
kernel for the Classic II.  Incase anyone cares, I will go ahead and
answer my own questions:

>On Boot Errors:
>sd1: mode sense (4) returned nonsense; using fictitious geometry
>sd3: mode sense (4) returned nonsense; using fictitious geometry

Removing the ncrscsi driver and compiling in the sbc driver instead,
solved this one.  Being that sbc0 wasn't in my GENERIC configuration when
I edited it for the new kernel, I didn't even realize that it was already
in the source tree.  The only thing that confuses me is that the mode
sense only returned nonsense on sd1 and sd3 when sd2 is the EXACT same
drive as the others.

>can't find device 0/0

>Program Errors:
>dmesg: magic number incorrect

Can't find device 0/0 was from savecore:.  Once I woke up to that one, and
the link with dmesg as well, I relized that my kernel HAD to be named
netbsd.  netbsd.test didn't cut it.  :)

>The system does seem to boot up, however, in single user mode, I have had
>it lockup under fsck after the mode sense error.

This quit locking up with 1.2.1.  Seems to be fine now.  However, it
hasn't had to do anything since the partitions were already clean.  We'll
see for sure after I have some unpleasant shutdowns or force a check.

Thanks to anyone who at least thought about this one.  :)

-me

 +'^'+.,.+'^'+.,.+'^'+.,.+'^'+.,.+'^'+.,.+'^'+.,.+'^'+.,.+'^'+.,.+'^'+.,.+

    Mike Eckhoff / Network Administrator / Wayne Public School District
       KB0TPT		 http://www.wayne.esu1.k12.ne.us/~meckhoff/ 

		"Everyday I relearn something different." -me

 '`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'