<div dir="ltr"><div>Thanks for the info, I've never worked with physical VAX hardware this old. The kernel is definitely accessing the DEQNA, here's what the debug output shows during boot:<br><br><p class="MsoNormal">
DBG(21694666)> XQ REG: xq_rd(PA=0x20001920 [MAC0], access=0)<br>DBG(21694666)> XQ REG: data=0xFF08<br>DBG(21694681)> XQ REG: xq_wr(data=0x00000002, PA=0x2000192E[CSR], access=2)<br>DBG(21694681)> XQ REG: xq_wr_csr(data=0x00000002)<br>
DBG(21694684)> XQ REG: xq_wr(data=0x000001F8, PA=0x2000192C[VAR], access=2)<br>DBG(21694684)> XQ REG: xq_wr_var(data= 0x000001F8)<br>DBG(21694766)> XQ REG: xq_rd(PA=0x20001920 [MAC0], access=0)<br>DBG(21694766)> XQ REG: data=0xFF08<br>
DBG(21694769)> XQ REG: xq_rd(PA=0x20001922 [MAC1], access=0)<br>DBG(21694769)> XQ REG: data=0xFF00<br>DBG(21694772)> XQ REG: xq_rd(PA=0x20001924 [MAC2], access=0)<br>DBG(21694772)> XQ REG: data=0xFF2B<br>
DBG(21694775)> XQ REG: xq_rd(PA=0x20001926 [MAC3], access=0)<br>DBG(21694775)> XQ REG: data=0xFFAA<br>DBG(21694778)> XQ REG: xq_rd(PA=0x20001928 [MAC4], access=0)<br>DBG(21694778)> XQ REG: data=0xFFBB<br>
DBG(21694781)> XQ REG: xq_rd(PA=0x2000192A [MAC5], access=0)<br>DBG(21694781)> XQ REG: data=0xFFCC<br>DBG(21695029)> XQ REG: xq_wr(data=0x000080C0, PA=0x2000192E[CSR], access=2)<br>DBG(21695029)> XQ REG: xq_wr_csr(data=0x000080C0)<br>
DBG(21695031)> XQ REG: xq_wr(data=0x00001E78, PA=0x20001924[RBDL-Lo], access=2)<br>DBG(21695034)> XQ REG: xq_wr(data=0x00000004, PA=0x20001926[RBDL-Hi], access=2)<br>DBG(21695037)> XQ REG: xq_wr(data=0x00002158, PA=0x20001928[XBDL-Lo], access=2)<br>
DBG(21695041)> XQ REG: xq_wr(data=0x00000004, PA=0x2000192A[XBDL-Hi], access=2)<br><br></p>I uploaded the RD52 image and the output of "sh c" here, anyone is welcome to use it for whatever: <a href="http://cs.oberlin.edu/~hbent/vaxultrix/ultrix1.tar.bz2">http://cs.oberlin.edu/~hbent/vaxultrix/ultrix1.tar.bz2</a><br>
<br></div><div>-Henry<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 26 June 2014 21:16, Mark Pizzolato - Info Comm <span dir="ltr"><<a href="mailto:Mark@infocomm.com" target="_blank">Mark@infocomm.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Henry,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">There are only two possible addresses for a DEQNA device, and I’m very sure that the expected address is the primary address which should be the default.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">You can verify that the kernel is attempting to touch the Qbus register space for the DEQNA device with the following simh commands added to your simh configuration:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> sim> set xq debug=REG<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> sim> set debug stdout<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Boot the simulator and the debug output should show any register references which may be occurring.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">If you truly believe that the DEQNA device isn’t working properly I can dig into the details if you can provide an RD51 or RD52 disk image and the configuration file you’re working with.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Good Luck,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><span>-<span style="font:7.0pt "Times New Roman""> </span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Mark<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div><div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:simh-bounces@trailing-edge.com" target="_blank">simh-bounces@trailing-edge.com</a> [mailto:<a href="mailto:simh-bounces@trailing-edge.com" target="_blank">simh-bounces@trailing-edge.com</a>] <b>On Behalf Of </b>Henry Bent<br>
<b>Sent:</b> Thursday, June 26, 2014 6:09 PM<br><b>To:</b> <a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a><br><b>Subject:</b> [Simh] Ultrix 1.0<u></u><u></u></span></p></div></div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p><div><div><p class="MsoNormal" style="margin-bottom:12.0pt">I had success booting the Unix Archive's floppy distribution of Ultrix 1.0 on the MicroVAX 1 simulator. It appears that the distribution there was only meant for a dual-RX50 MicroVAX 1 with an RD drive, and will not boot on any other machine. RQ0 needs to be an RD51 or RD52, and RQ1 and RQ2 need to be RX50s. TTI and TTO need to be 7 bit. To boot the installer, put 32m-1.0-bin/01 on RQ1 and 32m-1.0-bin/02 on RQ2. The install goes cleanly, albeit with quite a bit of disk swapping - the installation disk set is 13 floppies.<u></u><u></u></p>
</div><div><p class="MsoNormal" style="margin-bottom:12.0pt">The QVSS is supported and will display some output on boot. I haven't yet looked into what is needed to use it as the console (if that's possible?).<br>
<br>The kernel seems to support what I assume is the DEQNA - it has references to a qe device - but I can't figure out how to get it recognized. Unfortunately there are no kernel config files in the distribution, so I have no idea if the stock kernel is expecting the controller at a non-standard address. Any help with this would be greatly appreciated, <u></u><u></u></p>
</div><p class="MsoNormal">-Henry<u></u><u></u></p></div></div></div></div></div></div></blockquote></div><br></div>