Subject: Re: boot blocks - (really DMA M3100/M10 problem)
To: David Brownlee <>
From: John Hayward <>
List: port-vax
Date: 10/03/2000 23:44:22
Today I set up a second M3100/M10 which has an internal scsi drive on the
A chain.  The scsi drive is working without problems.  Maybe tomorrow I
can attach the external drive and try to see if there are no problems with
drives on both chains.

I did note some messages relative to a CD drive about sensing when
booting (which was on the B chain).


On Tue, 3 Oct 2000, David Brownlee wrote:

> Date: Tue, 3 Oct 2000 15:17:55 +0100 (BST)
> From: David Brownlee <>
> To: John Hayward <>
> Cc: Chuck McManis <>,
> Subject: Re: boot blocks
> On Tue, 3 Oct 2000, John Hayward wrote:
> > I had a couple of problems - I had unpacked the i386 ALPHA2 sets on my vax
> > (-{ (big problem) and in switching between net booting and attempting to
> > boot off the disk entered netbsd for the boot file when the boot flag was
> > on to prompt for the boot file.  I have since unpacked the vax sets, a
> > kernel which has the dma offset removed and turned off the boot flag and I
> > can boot ALPHA2 on my M3100.  It seems faster than running of the network
> > (maybe because I could hear the disks doing stuff).
> > 
> 	Excellent news :)
> > I'd still like to know if any one has docs on how the DMA should work on
> > the 3100 - I'm concerned that the tkxx drive hanging off the scsiA chain
> > might have dma problems with disks doing dma on the scsiB chain.  I need
> > to clean my tkxx drives to see if I can get them to work but this is a
> > lower priority item for me.
> 	Do you have a spare disk you can hang off the scsiA chain to
> 	test them both in parallel?