Subject: Re: Dilog Disk Controller in Vaxstation II
To: Chuck McManis <cmcmanis@mcmanis.com>
From: Douglas Meade <inforum@umd5.umd.edu>
List: port-vax
Date: 08/03/1999 10:36:50
Hi Chuck,
I still haven't negotiated the price of the system yet. Let's say
I'm "borrowing" it for now, as the owner is not making much use of
it ;).
Actually, the boot messages below are just what I would love to see,
but that's the problem, I only see mscpbus0 (TQK50) and mscpbus1 (RDQX3).
Since the drives are booting VMS without a problem, what could be
some reasons why NetBSD doesn't see them?
Doug
On Mon, 2 Aug 1999, Chuck McManis wrote:
> The controller is an MSCP to ESDI controller (the disks are ESDI). In the
> boot sequence for 1.4 you should see some notes like:
>
> mscpbus2 at uda1: version 3 model 5
> mscpbus2: DMA burst size set to 4
> ra1 at mscpbus2 drive 0: XXXX (some drive id)
> ra2 at mscpbus2 drive 1: XXXX (another drive id)
>
> Those are your two ESDI drives. If you type disklabel -r ra1 it should tell
> you how many sectors the drive has and from that you can create a disk
> label. Nice catch BTW, how much did it cost you?
>
>
> --Chuck
>
>
> At 10:45 PM 8/2/99 -0400, you wrote:
> >I found myself a Vaxstation II a couple of weeks ago, and I've been
> >able to get it to boot NetBSD 1.41, but now I'd like to try putting
> >something on the disks. In addition to the RDQX3 with one RD54 disk,
> >it has a controller made by Dilog, with the number "90710" on the
> >plastic handle. It's attached by MFM/RLL cables to two Maxtor
> >XT8380E's, which say they're 390 Mb each on the faceplace. The
> >first time I plugged the system into a serial console, it booted
> >up VMS 4.6 from one of these drives, which VMS sees as DUB0 and
> >DUB1. I've got a working installation of VMS, so I know I should be
> >happy, but I think I would like to replace it with NetBSD. The trouble
> >is, the kernal messages about installed devices don't reveal a clue
> >about their whereabouts, nor indicate the existence of the controller.
> >Is it that this controller and its disks are not supported by NetBSD,
> >or do I need to compile a different kernel?
> >
> >Doug
> >
> >
>
>