Re: CMD controller not found on 4000/500A

On 2/19/24 15:27, George Harvey wrote:
>>     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.
> 
> I have built a kernel (nearly 17 hours to do a native build on the 500A) with vups increased to 45 and it still fails to find the CMD controller. There is now a noticeable pause after it detects mscpbus0, presumably due to the increased delay, but it fails to detect mscpbus1.
> 
> Since network booting always works, and disk booting doesn't, could the bootloader be doing something that is interfering with the kernel's hardware detection? My bootloader is [1.12 (Tue Jan 16 08:28:51 UTC 2024)], which version do you have on your 705A?

   That system usually runs VMS; I should have an opportunity to boot 
the NetBSD disk on it to check within the next couple of days.

              -Dave

-- 
Dave McGuire, AK4HZ
New Kensington, PA