Hello,
I should've indicated what it is I want to do.  I want to put probably root +
swap on the RD32 and boot from
that.  I figured I could put everything else on a SCSI disk.

Anyway, here's what is probed when booting into 'sysinst':

629980+1268856+159424 total=0x1f6818
Copyright (c) 1996, 1997, 1998
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 1.3I (INSTALL) #31: Mon Nov 30 20:39:58 CET 1998
    ragge@subzero:/multi/src/sys/arch/vax/compile/INSTALL

MicroVAX 2000
realmem = 14659584
avail mem = 10899456
Using 22 buffers containing 90112 bytes of memory.
mainbus0 (root)
cpu0 at mainbus0: KA410
vsbus0 at mainbus0
ln0 at vsbus0
ln0: address 08:00:2b:0c:4b:4a
dz0 at vsbus0: DC367
ncr0 at vsbus0
scsibus0 at ncr0: 8 targets
sd0 at scsibus0 targ 3 lun 0: <IBM, KZ-P, R144> SCSI2 0/direct fixed
sd0: 153MB, 1021 cyl, 8 head, 38 sec, 512 bytes/sect x 314368 sectors
md0: internal 1200K image area
boot device: ln0
root on md0a dumps on md0b
mountroot: trying nfs...
mountroot: trying ffs...
Clock has lost 10569 day(s) - CHECK AND RESET THE DATE.
root file system type: ffs
init: copying out flags `-s' 3
init: copying out path `/sbin/init' 11
erase ^?, werase ^W, kill ^U, intr ^C


BTW, I know it says MicroVAX 2000... I have it jumpered to disable the onboard
frame buffer.

What is missing from this probe?  What would the internal MSCP/MFM disk
controller's device be?
Any other clues that can be gleaned from this?

thanks,
Jonathan
:-)









Brian D Chase <bdc@world.std.com> on 04/09/99 05:53:27 PM
                                                                                
                                                                                
                                                                                


                                                              
                                                              
                                                              
 To:      Chuck McManis <cmcmanis@mcmanis.com>                
                                                              
 cc:      Jonathan Sturges/ESD/GMR@GMR, port-vax@netbsd.org   
                                                              
                                                              
                                                              
 Subject: Re: VS2k install woes: disk problems!               
                                                              








Are MSCP drives supported currently on the VAXstation 2000?  I know
support for them left for a period of time, I wasn't aware of it having
been brought back into the fold.  Ragge?

As for the SCSI support, you won't be able to boot directly from the SCSI
disk as the VS2000 doesn't directly support SCSI devices as boot devices.
It should be feasible to boot into the NetBSD/vax kernel from either the
RD32, a floppy drive (RX33), or tape drive and then still use the SCSI
drive as your system disk.  I've not tried this yet, but it is on my list
of things to eventually attempt to do.

-brian.

On Fri, 9 Apr 1999, Chuck McManis wrote:

> A bit more information is needed. When the system is booting it probes for
> devices, can you tell us what it found? Some devices are not as they
> appear, for example I have a Viking QTO scsi tape controller in my UVax but
> it reports itself as an MSCP TK50. Similarly with my RQD11 ESDI controller
> which claims it is like a UDA50 MSCP disk controller.
>
> As for recognizing the disk, it won't see it until you label it. So if saw
> the disk in the probe sequence you can use disklabel to write a label to
> it, then the device will configure the next time you boot.
>
> --Chuck
>
> At 04:30 PM 4/9/99 -0400, jsturges@gmri.com wrote:
> >Hi,
> >I've successfully netbooted my VS2k into 'sysinst' from the 12/98 snapshot.
> >However, I'm having major disk problems.
> >
> >The machine has an internal RD32, as well as an external SCSI disk.  The
> >SCSI is
> >an IBM WDS-3160, which is a 3.5" 160Mb. SCSI-2 drive.  It does *not* do Fast
> >SCSI-2, however, and is limited to 5MB/sec.
> >
> >When the kernel/sysinst initializes, it does not even see the RD32.  However,
> >the RD32 spins up, and can be formatted successfully by the ROM formatter.
> >Aren't the VS2k internal disks supported??  Or is mine broken?
> >
> >Secondly, the SCSI disk *is* recognized at boot time but cannot be accessed.
> >Any attempt to write the disklabel or anything results in the drive resetting
> >itself (so my ears tell me) and the operation fails with an error.
> >
> >Can someone provide guidance on this?  I'd really like to get the OS
installed
> >locally, as opposed to running it diskless/dataless.
> >
> >TIA,
> >Jonathan
> >
> >
>

---
Brian "JARAI" Chase | http://world.std.com/~bdc/ | VAXZilla LIVES!!!