Re: CMD MSCP SCSI problems? (again?)

[Dave McGuire <mcguire%neurotica.com@localhost>]

On 2/1/23 13:59, Anders Magnusson wrote:
> >   I've just finished installing NetBSD 9.3 on a VAX 4000-705A using a 
> > CMD CQD-220 MSCP SCSI host adapter.  I put them install disk image on 
> > a ZuluSCSI board, it booted and ran the installer just fine, but when 
> > trying to boot the newly-created system disk (also implemented via the 
> > ZuluSCSI SSD) it fails to find the controller and thus cannot mount 
> > its filesystems.
> >
> >   I remember something like this from probably twenty years ago, but I 
> > thought it was long since fixed.
> >
> >   The disk subsystem works fine; I installed VMS on it this morning 
> > via the same mechanism and it's rock solid.
> >
> >   Does anyone have any suggestions?
> Do the kernel have the correct csr address for the MSCP card?  Which 
> address do the card have?

  It's at the default first MSCP controller address of 772150.

> Can you post the dmesg output for both the install kernel and the 
> non-working kernel?

  Here's the output from the non-working kernel:

[   1.0000000] mainbus0 (root) 

[   1.0000000] cpu0 at mainbus0KA694, NVAX (ucode rev 2) 

[   1.0000000] ze0 at mainbus0 

[   1.0000000] ze0: hardware address 08:00:2b:99:8c:14 

[   1.0000000] shac at mainbus0 not configured 

[   1.0000000] uba0 at mainbus0: Q22 

[   1.0000000] mtc0 at uba0 csr 174500 vec 774 ipl 17 

[   1.0000000] mscpbus0 at mtc0: version 2 model 5 

[   1.0000000] mscpbus0: DMA burst size set to 4 

[   1.0000080] mt0 at mscpbus0 drive 0: TU81 

[   1.0996780] boot device: <unknown> 

[   1.1177780] root device: 


  I'll get the output from the installer kernel shortly.

           -Dave

--
Dave McGuire, AK4HZ
New Kensington, PA