[TUHS] simh vax and 4.3-quasijarus

[TUHS] simh vax and 4.3-quasijarus

[Michael Sokolov]

Rico Pajarola <rp at servium.ch> wrote:

> I installed 4.3-quasijarus on simh [...]
> I have been unable to boot it directly from it's 'own'
> filesystem.
>
> here's what I see, complete transcript at the end
> > >>>boot dua0
> > (BOOT/R5:0 DUA0)
> > 
> > 
> > 
> >   2..
> > -DUA0
> > HALT instruction, PC: 00000C1A (MOVL (R11),SP)

My ability to help you here will be limited because you are using simh rather
than a real VAX. The real KA655 console ROM does not issue halt messages like
the above, its halt message have a different form (the one prescribed by DEC
STD 032-0, VAX Architecture Standard). The last message above does not exist on
any real VAX made by DEC.

> that's obviously not what I want. I tried all combinations of
> installboot and disklabel -B I can think of, both in netbsd and
> quasijarus, and all lead to the same result.
>
> Can anybody tell me the exact incantations necessary to install
> the bootblocks for quasijarus0a [...]

This seems like a simh problem, or, more probably since you can boot That Other
OS successfully, a problem with your installation of 4.3BSD-Quasijarus0a masked
by a simh problem. You've got a halt inside VMB that happened after VMB had
successfully opened the boot device but before it accepted a valid bootblock.
What happens on a real KA655 is as follows: the console copies VMB from the
EPROM to RAM and transfers control to it, which is accompanied by the display
of 2.. on the console and on the CPU module LEDs. At that point the VAX is
unhalted, i.e., the RUN indicator on the front panel lights up. VMB thus runs
as user code and tries to perform the bootstrap. As VMB successfully opens the
boot device using its built-in drivers, it displays the device name in VMS
format on the console. Then if it finds and accepts a valid bootblock it
displays 1.. on the console and on the CPU module LEDs. Finally it transfers
control to the bootblock accompanied by 0.. display. If something goes wrong
and VMB gives up, it prints its own error message on the console and then
executes a HALT instruction to return to the console prompt. The HALT
instruction halts the VAX (the RUN indicator on the front panel goes out) and
invokes the console, which prints the halt message followed by the >>> prompt
as prescribed by DEC STD 032-0.

It looks like you are seeing VMB fail for some reason and halt, giving you the
(not compliant with DEC STD 032-0) halt message from simh. However, you are not
seeing VMB's error message which on a real KA655 will always appear before the
halt message from the console. This is a simh problem, it obviously does not
fully and properly emulate the real KA655 here. I cannot help you past this
point as I only support real VAX hardware. There is probably something wrong
with your bootblock as your emulated VAX's VMB is not accepting it while
accepting the one on DUA1 from That Other OS, but your poor emulator prevents
you from seeing what the problem is.

> So far I have not been able to boot any other VAX operating system
> from the TUHS archive, the netbsd bootloader cannot load ultrix32m,
> 32v and 3bsd.

I don't know / don't care much about That Other OS and its bootloader, but the
format of the VAX unix/vmunix kernel image and its boot interface has remained
absolutely unchanged from 32V through 4.3BSD-Quasijarus0a inclusive (but see
below about VAX model support). DEC has extended the boot interface in Ultrix,
but it's completely backward compatible: as the Ultrix bootloader starts the
kernel with a calls instruction, it passes one argument (calls $1) whereas
traditional Bell/Berkeley UNIX had zero (calls $0). A traditional kernel will
simply ignore this argument, while the Ultrix kernels checks for its presence
(thanks to the wonderful VAX architecture and its procedure call standard that
allows a procedure to determine its argument count) and lives without it if
it's absent. (That argument is a pointer to a structure with useful info,
however, and I plan to adopt this extension in 4.3BSD-Quasijarus1.)

> I have not yet had time to try any of the other 4.x
> bsds, but I assume they'd have the same problem as quasijarus0a.

4.3BSD-Quasijarus0 was the first release to support KA650/655, so don't bother
trying earlier ones. (Although you could try 4.3-Reno if that's what you like.)

> I don't
> have ultrix/vax media to do it right

You can get the complete TK50 distribution (tape images) of Ultrix V4.00 for
VAX on my FTP site ivan.Harhan.ORG in /pub/UNIX/thirdparty/Ultrix-32. I have
full sources for it there too.

> Ultrix 4.3 gives me:
> > 466788+254256+177476+[36984+34990] total=0xecfa2

OK, so the kernel has been loaded successfully.

> > machine check 82: vap 82000004 istate1 7c000c00 istate2 c070fe pc 80001c61 psl 41f0008
> > r0=8000000c, r1=8000167c, r2=0, r3=211bd0dd, r4=0, r5=dd274
> > panic: mchk

Since Ultrix V4.3 perfectly supports the KA655 CPU, this again must be a case
of simh misemulating it.

My advice to you is to get a real VAX.

MS

P.S. You may want to subscribe to the Quasijarus mailing list, send a request
to quasijarus-request at ifctfvax.Harhan.ORG.

[TUHS] simh vax and 4.3-quasijarus

[Gunther Schadow]

Hi,

I found SIMH really handy as opposed to a real VAX. Was the only
way I could bring my VAX 6460 to boot Ultrix 4.5 which I only had
on a CD and the standalone kernel that came with Ultrix 4.5 didn't
support the KA64A although the normal generic Ultrix 4.5 kernel
does. So, I made a small disk installed a generic root partition
on SIMH used an uVAX-II under NetBSD to pull the disk image via
NFS to a TK50 and then booted VAX 6460 under VMS and wrote the
disk image to RA90 and off I went. I couldn't have done it without
SIMH :-)

Anyway, to your problem:


>>here's what I see, complete transcript at the end
>>
>>>>>>boot dua0
>>>>>>
>>>(BOOT/R5:0 DUA0)
>>>
>>>
>>>
>>>  2..
>>>-DUA0
>>>HALT instruction, PC: 00000C1A (MOVL (R11),SP)


this suspiciously looks as if the HALT is from SIMH not from the
VAX it simulates. There are two halt levels in SIMH, one being
the VAX halting and going into VAX console mode, the other being
SIMH halting. Are you absolutely sure that you have a proper
VAX console with SIMH? You should get normal VAX console
behavior, try a few commands and see whether you're on the right
page.

Also, be sure you have it all configured right, that you have
the right devices defined and properly associated with files
on the hosting OS etc.


>>that's obviously not what I want. I tried all combinations of
>>installboot and disklabel -B I can think of, both in netbsd and
>>quasijarus, and all lead to the same result.
>>
>>Can anybody tell me the exact incantations necessary to install
>>the bootblocks for quasijarus0a [...]
>>
> 
> This seems like a simh problem, or, more probably since you can boot That Other
> OS successfully, a problem with your installation of 4.3BSD-Quasijarus0a masked
> by a simh problem. 


I would agree. What other system can you boot on SIMH?


>>Ultrix 4.3 gives me:
>>
>>>466788+254256+177476+[36984+34990] total=0xecfa2
>>>
> 
> OK, so the kernel has been loaded successfully.
> 
> 
>>>machine check 82: vap 82000004 istate1 7c000c00 istate2 c070fe pc 80001c61 psl 41f0008
>>>r0=8000000c, r1=8000167c, r2=0, r3=211bd0dd, r4=0, r5=dd274
>>>panic: mchk



 > Since Ultrix V4.3 perfectly supports the KA655 CPU, this again must be a case
 > of simh misemulating it.

again, your SIMH configuration may be screwed up. I definitely could
boot Ultrix 4.5.

-Gunther



-- 
Gunther Schadow, M.D., Ph.D.                    gschadow at regenstrief.org
Medical Information Scientist      Regenstrief Institute for Health Care
Adjunct Assistant Professor        Indiana University School of Medicine
tel:1(317)630-7960                         http://aurora.regenstrief.org

[TUHS] simh vax and 4.3-quasijarus

[Lord Isildur]

> I would agree. What other system can you boot on SIMH?

I know 4.3tahoe, netbsd, some ultrix version, and vms boot in it. 
(not to say other ultrix versions dont, but e.g. gunther has booted
ultrix under simh, i have heard many people booting vms, and i have run 
it with images dd'ed from the (running :) / and /usr of one of my 4.3t 
vaxen.) 

What is your configuration? 
isildur

[TUHS] simh vax and 4.3-quasijarus

[Rico Pajarola]

is there anybody who has successfully installed 4.3-quasijarus on
simh, who could tell me how to install the bootblocks (I am not
completely sure that I got the disklabel right). The exact incantation
of installboot and the output of disklabel would be very helpful.

Rico Pajarola

[TUHS] simh vax and 4.3-quasijarus

[Rico Pajarola]

I installed 4.3-quasijarus on simh, and I managed to boot indirectly
by putting the kernel as /quasijarus0a in the netbsd root filesystem,
and then booting it from the netbsd bootloader with 'boot quasijarus0a
-a'. I have been unable to boot it directly from it's 'own'
filesystem.

here's what I see, complete transcript at the end
> >>>boot dua0
> (BOOT/R5:0 DUA0)
> 
> 
> 
>   2..
> -DUA0
> HALT instruction, PC: 00000C1A (MOVL (R11),SP)

that's obviously not what I want. I tried all combinations of
installboot and disklabel -B I can think of, both in netbsd and
quasijarus, and all lead to the same result.

Can anybody tell me the exact incantations necessary to install
the bootblocks for quasijarus0a, or does anybody who has installed
quasijarus0a have a session transcript? any idea what I might be
doing wrong?

So far I have not been able to boot any other VAX operating system
from the TUHS archive, the netbsd bootloader cannot load ultrix32m,
32v and 3bsd. I have not yet had time to try any of the other 4.x
bsds, but I assume they'd have the same problem as quasijarus0a.

I have tried ultrix-4.3 (also from the netbsd bootloader, I don't
have ultrix/vax media to do it right), but it does not work either.

If anybody can help me with this, thanks in advance

Rico Pajarola

The following transcript shows how I boot it (first the way it
fails, then the way it works):

> VAX simulator V2.9-9
> sim> show c
> VAX simulator configuration
> 
> CPU, 32768KB
> TLB, 2 units
>   TLB0, 8KW
>   TLB1, 8KW
> ROM, 128KB
> NVR, 1KB
> SYSD, 2 units
>   SYSD0
>   SYSD1
> QBA
> TTI
> TTO
> CSI
> CSO, not attached
> CLK
> PTR, address=20001F68-20001F6F, not attached
> PTP, address=20001F68-20001F6F, not attached
> LPT, address=20001F4C-20001F4F, not attached
> RQ, address=20001468-2000146B, 4 units
>   RQ0, 159334KB, attached to 4.3-quasijarus0a.rd54.dsk, write enabled, RD54
>   RQ1, 622932KB, attached to ../netbsd-vax/netbsd-vax.ra82.dsk, write enabled, RA82
>   RQ2, 409KB, not attached, write enabled, RX50
>   RQ3, 409KB, not attached, write enabled, RX50
> RL, disabled
> TS, disabled
> DZ, disabled
> sim> boot cpu
> 
> 
> KA655-B V5.3, VMB 2.7
> Performing normal system tests.
> 40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
> 24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
> 08..07..06..05..04..03..
> Tests completed.
> >>>boot dua0
> (BOOT/R5:0 DUA0)
> 
> 
> 
>   2..
> -DUA0
> HALT instruction, PC: 00000C1A (MOVL (R11),SP)


> >>>boot dua1
> (BOOT/R5:0 DUA1)
> 
> 
> 
>   2..
> -DUA1
>   1..0..
> 
> 
> >> NetBSD/vax boot [Aug 19 2001 05:57:49] <<
> >> Press any key to abort autoboot 3
> > boot quasijarus0a -a
> 327204+103384+130352+[29436+24084] total=0x96220
> 4.3 BSD Quasijarus UNIX #0: Sat Oct  2 22:15:38 CDT 1999
>     msokolov at luthien:/usr/src/sys/GENERIC
> real mem  = 33521664
> SYSPTSIZE limits number of buffers to 80
> avail mem = 31697920
> using 80 buffers containing 655360 bytes of memory
> MicroVAX 3000, ucode rev 6
> uda0 at uba0 csr 172150 vec 774, ipl 15
> uda0: version 3 model 3
> uda0: DMA burst size set to 4
> ra0 at uda0 slave 0: RD54, size = 311200 sectors
> ra1 at uda0 slave 1: vaxnetbsd, size = 1216665 sectors
> ra2 at uda0 slave 2: floppy
> ra3 at uda0 slave 3: floppy
> lp0 at uba0 csr 177514 vec 200, ipl 14
> root device? ra0
> WARNING: clock gained 14 days -- CHECK AND RESET THE DATE!
> erase ^?, kill ^U, intr ^C
> #

from this point on, it works as expected.


Ultrix 4.3 gives me:
> 466788+254256+177476+[36984+34990] total=0xecfa2
> machine check 82: vap 82000004 istate1 7c000c00 istate2 c070fe pc 80001c61 psl 41f0008
> r0=8000000c, r1=8000167c, r2=0, r3=211bd0dd, r4=0, r5=dd274
> panic: mchk
> 
> dumping to dev ffffffff, offset 0
> dump machine check 80: vap 78302077 istate1 fb000c00 istate2 c070fd pc 8004eb57 psl 41f0000
> r0=78302073, r1=0, r2=0, r3=211bd0dd, r4=22, r5=80
> panic: mchk
> 
> HALT instruction, PC: 8000165B (XFC)