If I don't select DECwindows Motif, then OpenVMS installs just fine. I guess there may be something wrong with the Motif PCSI package. Fortunately, I have no need for it to be installed, so I'll redo the installation without it and get a clean install going.
I've succesfully installed ovms 8.3 w/ DECwindows Motif from two different ISO images.
All works fine for me.
I ran into some strange problems with my Alpha CD. I was told that there were "bad blocks" found in the PCSI database during verification. The machine came up, so it appears to be okay, but I don't know that my installation completed successfully. I tried reimaging the CD I have into fresh ISOs, but they all come out the same.
For anyone who is curious how this ended up, I looked at Bob's image, and it was identical to mine, same size and same checksum.
I did some reinstallation attempts and finally tracked down the problem to trying to install DECwindows Motif. If I selected that package (not just the libraries, but the actual server component), I get this error during installation:
Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%
%PCSI-E-PDBFAILVAL, the product database failed verification due to an internal inconsistency
%PCSI-E-PDBFILERR, file PCSI$UPDATE_8.PCSI$DATABASE;1 failed with the following error:
-LIB-F-BADBLOSIZ, bad block size
%PCSI-E-PDBFAILVAL, the product database failed verification due to an internal inconsistency
%PCSI-E-S_OPFAIL, operation failed
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition
If I don't select DECwindows Motif, then OpenVMS installs just fine. I guess there may be something wrong with the Motif PCSI package. Fortunately, I have no need for it to be installed, so I'll redo the installation without it and get a clean install going.
--Marc
I'm running ovms 8.3 w/ DECnet & TCP/IP under charon-nce.
eth0 used by host OS, eth1 used by emulator (no entry for eth1 in
`intefaces' file), both connected to the same switch.
Thanks, Oleg - that's basically the same setup I've got (except for the
interfaces file).
Gotta go now, but I'll fool with this some more tonight.
Bob
I don't know DECnet for Linux, but is there a way that you could
manually disable the eth1 circuit on sketti? Kind of a "define circuit
eth1 state off"?
DECnet/Linux is not supposed to be touching eth1. My /etc/default/decnet
says -
# DNET_INTERFACES specifies the names of ethernet interfaces whose
# MAC address is to be set to the DECnet node address
DNET_INTERFACES="eth0"
and also the /etc/decnet.conf says
#Node Node Name Node Line Line
#Type Address Tag Name Tag
Device
#----- ------- ----- ----- -----
------
executor 2.16 name sketti line eth0
So AFAIK the host DECnet should only be listening on eth0. Chrissy would
probably know for sure.
Bob
Bob Armstrong wrote:
Guys -
Sorry to bother you with a question, but I was wondering if anyone who had
tried Charon-AXP-nce was successful at getting DECnet running on OVMS 8.3
under the Charon emulation?
I'm running ovms 8.3 w/ DECnet & TCP/IP under charon-nce.
I't runnign right now (CTEPBA:: 1.301).
No problems found.
Host OS is Ubuntu 9.10, startup script:
--
#!/bin/sh
export CHARON_RAM_SIZE="256"
export CHARON_DKA0="dka0.vdisk"
export CHARON_DKA100="dka100.vdisk"
export CHARON_CDROM="ovms83-axp.iso"
export CHARON_EWA0="eth1"
cd /emul/charon && exec taskset -c 0-2 /emul/charon/es40_nce
--
eth0 used by host OS, eth1 used by emulator (no entry for eth1 in `intefaces' file), both connected to the same switch.
Hmmm.... Maybe I should uninstall DECnet/Linux from the host and try
again...
I don't know DECnet for Linux, but is there a way that you could manually disable the eth1 circuit on sketti? Kind of a "define circuit eth1 state off"?
--Marc
2.16 shouldn't have answered for your Alpha system.
I think that's OK - the Linux host is also running DECnet/Linux and its
(the host, that is) name is SKETTI, 2.16. It took some fooling, but I'm
pretty sure the host DECnet is using eth0 (as it should be).
That is a difference between our systems. I don't have DECnet on the host, so there isn't anything listening on eth1 except for CHARON-AXP.
I'm still concerned that a "TELL 2.17" got answered by the wrong system.
Here are a couple bad examples:
NCP>tell charon show exec
Node Volatile Summary as of 1-NOV-2009 13:16:12
Executor node = 2.17 (CHARON)
State = on
Identification = HP DECnet for OpenVMS Alpha
NCP>tell charon show exec
Node Volatile Summary as of 1-NOV-2009 13:16:13
Executor node = 2.16 (SKETTI)
Circuit = eth0
State = on
Identification = DECnet for Linux V2.6.31-14-generic on x86_64
And this looks worse:
$ set host charon
Welcome to OpenVMS (TM) Alpha Operating System, Version V8.3 Username: Exit Error reading command input
End of file detected
%REM-S-END, control returned to node DUSTY::
$ set host charon
Welcome to OpenVMS (TM) Alpha Operating System, Version V8.3 sketti login: ^Z
Login incorrect
sketti login: Interrupt Interrupt Are you repeating ^Y to abort the remote session on node CHARON? Y
Sometimes when you connect to 2.17, you're getting 2.16 answering instead. That can't be good.
--Marc
NCP>tell 2.17 show exec
Executor node = 2.16 (SKETTI)
Oppss. I take it all back about it being OK. You're right - that is a
problem. This is new, though - it wasn't doing this before.
That's really odd, though - if I log into the host Linux system and do
ifconfig, I see -
eth0 Link encap:Ethernet HWaddr aa:00:04:00:10:08
inet addr:10.1.1.25 Bcast:10.1.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:78ff:fe39:80df/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6419 errors:0 dropped:0 overruns:0 frame:0
TX packets:1049 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:439015 (439.0 KB) TX bytes:215532 (215.5 KB)
Interrupt:17
eth1 Link encap:Ethernet HWaddr aa:00:04:00:11:08
inet6 addr: fe80::a800:4ff:fe00:1108/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5174 errors:0 dropped:0 overruns:0 frame:0
TX packets:661 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:314584 (314.5 KB) TX bytes:42823 (42.8 KB)
Interrupt:18 Base address:0x5000
Note that eth0 and eth1 DON'T have the same MACs, and I believe they're the
correct MACs for 2.16 (eth0) and 2.17 (eth1) respectively.
Hmmm.... Maybe I should uninstall DECnet/Linux from the host and try
again...
Bob
2.16 shouldn't have answered for your Alpha system.
I think that's OK - the Linux host is also running DECnet/Linux and its
(the host, that is) name is SKETTI, 2.16. It took some fooling, but I'm
pretty sure the host DECnet is using eth0 (as it should be).
The emulation is 2.17, which I'm calling CHARON for the moment. Not very
original, but hey :-) It's using eth1.
The password to the SYSTEM account on 2.17 is GUEST. Have your way with
it - there's nothing on there I want to keep :-)
Bob
I think I see something funny going on. It looks as though your Linux host is listening on eth1:
NCP>tell 2.17 show exec
Node Volatile Summary as of 1-NOV-2009 13:05:01
Executor node = 2.16 (SKETTI)
Circuit = eth0
State = on
Identification = DECnet for Linux V2.6.31-14-generic on x86_64
2.16 shouldn't have answered for your Alpha system.
--Marc
