Subject: Re: snapshot kernel / disklabel problems
To: None <>
From: Michael Kukat <>
List: port-vax
Date: 02/27/1999 18:13:14
Hi !

> VAXstation 3100/m{30,40}
> cpu0 at mainbus0: KA41/42

BTW: Does this match ? KA41 and VAXstation ? So what's the difference to the
MicroVAX 3100 M10/M20.

> ncr0 at vsbus0

Ok, firing up the first on...

> scsibus0 at ncr0: 8 targets, 8 luns per target
> sd0 at scsibus0 targ 5 lun 0: <DEC, RZ23     (C) DEC, 0A18> SCSI1 0/direct fixed
> sd0: 100MB, 776 cyl, 8 head, 33 sec, 512 bytes/sect x 204864 sectors
> boot device: ln0

Hmm... second one is not initialized.
Maybe this kernel doesn't have ncr1 enabled in the configuration. But as i
know, the SCSI support for VAXstation 3100 series is not yet really usable.
Network might be faster than the hard disk, maybe that's the reason why in some
kernels the SCSI modules just aren't compiled in.

If you got your box running so far booting from the net, install the source
package of a recent kernel, and cd to /usr/src/sys/arch/vax/conf. Copy
"GENERIC" to "KA41" or so, edit the file "KA41", do "config KA41" (think, you
should compile "config" before... Or i send you the binary.), then cd to
/usr/src/sys/arch/vax/compile/KA41, do "make depend" and "make", if everything
runs without errors, your homemade kernel should be somewhere in the actual
directory. In your config file "KA41" you should have a sharp look into lines
starting with "ncr0" or "ncr1".
No guarantee, i didn't try out newer kernels for a longer time.

Cu.. Michael