<div dir="ltr">A little bit of update to this. The very image I created on the Microvax 2 simulator which didn't boot on the vax750 simulator booted just fine on the real thing. So there has to be some kind of bug inside the simulator as far I understand it.<div><br></div><div>
<p class="">>>>B</p>
<p class="">%%</p>
<p class="">@@</p>
<p class="">Patch Control Store is Present</p>
<p class=""><br></p>
<p class="">Done loading Patch bits and PCS</p>
<p class=""><br></p>
<p class="">Ultrixboot - V4.0 Sat Mar 31 04:11:56 EST 1990</p>
<p class=""><br></p>
<p class=""><br></p>
<p class="">Loading (a)vmunix ...</p>
<p class=""><br></p>
<p class=""><br></p>
<p class="">Sizes:</p>
<p class=""><br></p>
<p class="">text = 593304</p>
<p class=""><br></p>
<p class="">data = 100864</p>
<p class=""><br></p>
<p class="">bss = 320516</p>
<p class=""><br></p>
<p class="">Starting at 0x2d4d</p>
<p class=""><br></p>
<p class=""><br></p>
<p class="">ULTRIX V4.0 (Rev. 161) System #1: Thu May 20 23:26:51 GMT+0100 1976</p>
<p class=""><br></p>
<p class="">real mem = 8388608</p>
<p class=""><br></p>
<p class="">avail mem = 5921792</p>
<p class=""><br></p>
<p class="">using 204 buffers containing 838656 bytes of memory</p>
<p class=""><br></p>
<p class="">VAX 11/750, hardware level = 0x8c, microcode level = 99</p>
<p class=""><br></p>
<p class="">mcr0 (MS750) at address 0xf20000</p>
<p class=""><br></p>
<p class="">uba0 at address 0xf30000</p>
<p class=""><br></p>
<p class="">uda0 at uba0</p>
<p class=""><br></p>
<p class="">uq0 at uda0 csr 172150 vec 774, ipl 15</p>
<p class=""><br></p>
<p class="">ra1 at uq0 slave 1 (RA81)</p>
<p class=""><br></p>
<p class="">ra0 at uq0 slave 0 (RA81)</p>
<p class=""><br></p>
<p class="">WARNING: todr too small -- CHECK AND RESET THE DATE!</p>
<p class=""><br></p>
<p class="">Sun Jun 20 23:35:50 GMT+0100 1976</p>
<p class="">Automatic reboot in progress...</p>
<p class="">/dev/ra0a: 596 files, 5592 used, 9959 free (143 frags, 1227 blocks, 0.9% fragmentation)</p>
<p class="">/dev/rra0d: umounted cleanly</p>
<p class="">check quotas: done.</p>
<p class="">savecore: checking for dump...dump does not exist</p>
<p class="">local daemons: syslog sendmail.</p>
<p class="">Removing remnant Opser files</p>
<p class="">preserving editor files</p>
<p class="">clearing /tmp</p>
<p class="">standard daemons: update cron accounting network snmpd.</p>
<p class="">start errlog daemon - elcsd</p>
<p class="">Sun Jun 20 23:36:51 GMT+0100 1976</p>
<p class=""><br></p>
<p class=""><br></p>
<p class=""><br></p>
<p class=""><br></p>
<p class="">ULTRIX V4.0 (Rev. 161) (vax)</p>
<p class=""><br></p>
<p class=""><br></p>
<p class=""><br></p>
<p class=""><br></p>
<p class=""><br></p>
<p class="">login: root</p>
<p class="">Password:</p>
<p class="">Last login: Sun Jun 20 23:35:25 on console</p>
<p class="">ULTRIX V4.0 (Rev. 161) System #1: Thu May 20 23:26:51 GMT+0100 1976</p>
<p class=""><br></p>
<p class=""> Digital Equipment Corporation</p>
<p class=""> Nashua, New Hampshire</p>
<p class=""><br></p>
<p class=""><br></p>
<p class="">*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***</p>
<p class=""><br></p>
<p class="">The following files were created during the installation procedure:</p>
<p class=""><br></p>
<p class="">/vmunix - customized kernel</p>
<p class="">/genvmunix - generic kernel</p>
<p class="">/usr/adm/install.log - installation log file</p>
<p class="">/usr/adm/install.FS.log - file systems log file</p>
<p class="">/usr/adm/install.DEV.log - special device log file</p>
<p class=""><br></p></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-06-24 15:46 GMT+02:00 Henry Bent <span dir="ltr"><<a href="mailto:hbent@oberlin.edu" target="_blank">hbent@oberlin.edu</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>The /730 was configured with 5 MB, a UDA50, a DZ11, and a DEUNA. It suffers from the same kernel issue described above for the /750, so I really haven't done any significant testing at all other than confirming that the system comes up to multiuser and I can run basic commands.<span class="HOEnZb"><font color="#888888"><br><br></font></span></div><span class="HOEnZb"><font color="#888888">-Henry</font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 23 June 2015 at 22:21, Ethan Dicks <span dir="ltr"><<a href="mailto:ethan.dicks@gmail.com" target="_blank">ethan.dicks@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Tue, Jun 23, 2015 at 7:06 PM, Henry Bent <<a href="mailto:hbent@oberlin.edu" target="_blank">hbent@oberlin.edu</a>> wrote:<br>
> Out of curiosity I tried Ultrix 4.3 and 4.5 on the /750, both with genvmunix<br>
> and a custom kernel, and both showed the problem. Whatever the issue here<br>
> is, it appears to never have been fixed. I tried disabling just about every<br>
> device I could save for the disk, and I still got a panic every time. The<br>
> only thing I haven't yet tried is using a different disk controller (than<br>
> the UDA50).<br>
<br>
</span>Definitely try a different disk. UNIX device drivers do not use the<br>
hardware the same way that VMS drivers do. I helped debug the Simh<br>
RP03 driver long ago because it wouldn't fully boot 2.9BSD (long story<br>
short is that it was because the BSD driver wrote to a read-only<br>
register to initiate an interrupt for device probing). I've also run<br>
into issues with 4.3BSD not booting an 11/730 with RB80 (I did narrow<br>
it down to specific lines of code in the rb.c driver but haven't<br>
figured out what's not happening right. It's *very* early in the boot<br>
sequence that things go off the rails, so it wasn't too hard to trace<br>
in the code).<br>
<span><br>
> Interestingly, Ultrix 4.0 will boot on a /730 if you make a custom kernel<br>
> (genvmunix is too big). I didint' try 4.3 or 4.5.<br>
<br>
</span>Huh. I haven't tried that. Interesting. Which disk? UDA50 or the<br>
IDC + RB80? (DU driver vs DQ driver in VMS terms)<br>
<span><font color="#888888"><br>
-ethan<br>
</font></span></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com">Simh@trailing-edge.com</a><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a><br></blockquote></div><br></div>