Re: CMD controller not found on 4000/500A

   I'm not sure I'd call it a smoking gun, but my 705A boots reliably 
now from a CMD CQD-223/TM.

   In sys/arch/vax/vax/ka680.c, in struct ka680_calls, there's a 
hard-coded timing value in member cpu_vups.  Change that to 45 or so. 
That made the difference here.

              -Dave

On 2/18/24 05:15, George Harvey wrote:
> On Sun, 18 Feb 2024 02:21:51 +0100
> Johnny Billquist <[email protected]> wrote:
> 
>> How much memory do the machine have?
>>
> 
> 128 MB, which is the same as the 705A that was showing similar symptoms in the linked thread.
> 
> George
> 
> 
>> On 2024-02-17 21:48, George Harvey wrote:
>>> Hi,
>>>
>>> I have a 4000/500A with CMD CQD-223/TM SCSI controller. I did a network install of 10.0_RC3 onto a 4.3GB SCSI disk and it all proceeded normally until the reboot when the kernel failed to find the CMD controller. If I netboot the same kernel, it does find the CMD card and the system runs normally. I have since updated to the RC4 kernel and see the same behaviour. The relevant lines from kernel are:
>>>
>>> Netbooting 10.0_RC4 GENERIC
>>>
>>> [   1.0000000] uba0 at mainbus0: Q22
>>> [   1.0000000] mtc0 at uba0 csr 174500 vec 774 ipl 17
>>> [   1.0000000] mscpbus0 at mtc0: version 4 model 14
>>> [   1.0000000] mscpbus0: DMA burst size set to 4
>>> [   1.0000000] uda0 at uba0 csr 172150 vec 770 ipl 17
>>> [   1.0000000] mscpbus1 at uda0: version 6 model 13
>>> [   1.0000000] mscpbus1: DMA burst size set to 4
>>> [   1.0000000] qt0 at uba0 csr 174440 vec 764 ipl 17
>>>
>>> Booting the same kernel from the SCSI disk (DUA1):
>>>
>>> [   1.0000000] uba0 at mainbus0: Q22
>>> [   1.0000000] mtc0 at uba0 csr 174500 vec 774 ipl 17
>>> [   1.0000000] mscpbus0 at mtc0: version 4 model 14
>>> [   1.0000000] mscpbus0: DMA burst size set to 4
>>> [   1.0000000] qt0 at uba0 csr 174440 vec 770 ipl 17
>>>
>>> The CMD card at mscpbus1 is missing when booted from disk.
>>>
>>> Looking back through the mailing list archives, I see something similar reported for 9.3 on a 705A in this thread:
>>>
>>>     http://mail-index.netbsd.org/port-vax/2023/02/01/msg004175.html
>>>
>>> However, it doesn't look like a solution was found. Did anyone find a solution?
>>>
>>> George
>>>

-- 
Dave McGuire, AK4HZ
New Kensington, PA