Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VH not working in Ultrix 4.5 #365

Closed
hbent opened this issue Dec 17, 2016 · 4 comments
Closed

VH not working in Ultrix 4.5 #365

hbent opened this issue Dec 17, 2016 · 4 comments

Comments

@hbent
Copy link

hbent commented Dec 17, 2016

One of the recent changes seems to have broken VH (DHU mode) support in Ultrix 4.5.

ULTRIX V4.5 (Rev. 47) System #8: Thu Apr 14 22:20:36 EDT 2016
...
Warning: DHU device failed to exit self-test                         
dhu0 at uba0 csr 160440 didn't interrupt    

sim> show version
VAX 8600 simulator V4.0-0 Beta
    Simulator Framework Capabilities:
	    64b data
	    64b addresses
	    Ethernet Packet transports:PCAP:TAP:VDE:NAT:UDP
	    Idle/Throttling support is available
	    Virtual Hard Disk (VHD) support
	    RAW disk and CD/DVD ROM support
	    Asynchronous I/O support
	    Asynchronous Clock support
	    FrontPanel API Version 2
    Host Platform:
	    Compiler: GCC 7.0.0 20161125 (experimental)
	    Simulator Compiled as C arch: x64 (Release Build) on Dec 17 2016 at 09:25:34
	    Memory Access: Little Endian
	    Memory Pointer Size: 64 bits
	    Large File (>2GB) support
	    SDL Video support: No Video Support
	    PCRE RegEx support for EXPECT commands
	    OS clock resolution: 1ms
	    Time taken by msleep(1): 1ms
	    OS: Linux aelfric 4.9.0-gentoo #1 SMP Mon Dec 12 10:36:05 EST 2016 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GenuineIntel GNU/Linux
        git commit id: 7dd1f0b8

sim> sh c
VAX 8600 simulator configuration

CPU	idle=ULTRIX, idle enabled, model=VAX 8600
    260MB, HALT to SIMH
TLB	2 units
  TLB0	8192W
  TLB1	8192W
ABUS
SBIA
UBA	nexus=3, address=20006000, autoconfiguration enabled
MBA0	disabled
MBA1	disabled
TODR
    12B, attached to vax8600.todr
TMR
TTI	4 units
  TTI0	8b
  TTI1	8b
  TTI2	8b
  TTI3	8b
TTO	4 units
  TTO0	8b
  TTO1	8b
  TTO2	8b
  TTO3	8b
CS
    5242KW, attached to consolerl, write enabled
TC	disabled
TDC	disabled
DZ	disabled
VH	address=2013E120-2013E12F*, vector=C0-C4*, lines=16
    attached to 4500, DHU mode, 0 current connections
CR	disabled
LPT	disabled
RP	disabled
RL	disabled
HK	disabled
RK	disabled
RQ	address=2013F468-2013F46B, vector=1FC*, UDA50, 4 units
  RQ0	1216MB, attached to ra90.dsk, write enabled
    RA90, autosize, SIMH format
  RQ1	2007MB, attached to ra73-1.dsk, write enabled
    RA73, autosize, SIMH format
  RQ2	2007MB, attached to ra73-2.dsk, write enabled
    RA73, autosize, SIMH format
  RQ3	681MB, not attached, read only
    RRD40, autosize, SIMH format
RQB	disabled
RQC	disabled
RQD	disabled
RY	disabled
TU	disabled
TS	address=2013F550-2013F553, vector=94
    not attached, write locked, SIMH format
    unlimited capacity
TQ	disabled
XU	address=2013F948-2013F94F, vector=50, MAC=08:00:2B:1C:45:99
    type=DEUNA, throttle=disabled
    attached to tap:tap1
XUB	disabled
DMC	disabled
@markpizz
Copy link
Member

Can you provide a configuration file and a boot disk image?

@hbent
Copy link
Author

hbent commented Dec 17, 2016

Ultrix V4.3 was easier to pack up and has the exact same problem. Here's a configuration file and disk image with no root password. Kernel sources are included, /usr/sys/io/uba/dhu.c is the driver source.
https://www.dropbox.com/s/uhkdagay3h6lm2s/ultrix43.tar.xz?dl=0

@markpizz
Copy link
Member

It should work now. While migrating timer changes from the VAX780 an improper argument was passed as the delay value when calling sim_clock_coschedule(). This typo appeared in both the VAX8600 and VAX750,

@markpizz
Copy link
Member

Henry,

Can you test with the latest code and close this issue if Ultrix both boots AND you can actually connect to the system using the VH ports.

Thanks.

  • Mark

@hbent hbent closed this as completed Jan 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants