Re: CMD MSCP SCSI problems? (again?)

[Anders Hogrelius <ahs%hogrelius.nu@localhost>]

If the installer boots and finds the disk I think it must be something missing in the configuration of the (GENERIC?) kernel. Can you boot the system with the install kernel and set the root to the installed disk using boot flags? If that works,  compile a new kernel with the same device configuration as the install kernel,  it should boot. 

Cheers 

Anders

Sent via the Samsung Galaxy S22 Ultra 5G, an AT&T 5G smartphone
Get Outlook for Android

---

From: port-vax-owner%NetBSD.org@localhost <port-vax-owner%NetBSD.org@localhost> on behalf of Dave McGuire <mcguire%neurotica.com@localhost>
Sent: Wednesday, February 1, 2023 10:33:30 AM
To: port-vax List <port-vax%netbsd.org@localhost>
Subject: CMD MSCP SCSI problems? (again?)

 

   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?

              Thanks,
              -Dave

--
Dave McGuire, AK4HZ
New Kensington, PA