You can browse the linux-vax modules via http://linux-vax.sourceforge.net/download/index.html.
Connect to the source-code repository for linux-vax
$ cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/linux-vax login
and checkout the module (ie you want to download the module sources to your local machine).
co modulename
or do it in one command (the -z3 just says to compress things using gzip)
$ cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/linux-vax co modulename
Once you have everything down, you can also keep it up-to-date by issuing an update command from within your source dir.
$ cvs update -dP
First, you need the cross-compiler tools to compile on your alternate Linux OS and hardware
to generate the Linux VAX binaries.
$ mkdir vax
$ cd vax
$ cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/linux-vax login
$ cvs -z9 -d:pserver:anonymous@cvs.linux-vax.sourceforge.net:/cvsroot/linux-vax co toolchain
There's a supplied script (build-vax.sh) to help you here. (change it if you want different locations,etc)
$ cd toolchain
$ ./build-vax.sh
$ su
# ./build-vax.sh install
NOTE: on my RH 7.2 alpha system I had to install gperf before this would complete.
http://ftp.gnu.org/gnu/gperf/gperf-3.0.1.tar.gz
OK, the cross-compiler stuff is ready!
So, go grab the kernel-2.5 module (at time of writing, the best bet)
$ cd ..
$ cvs -z9 -d:pserver:anonymous@cvs.linux-vax.sourceforge.net:/cvsroot/linux-vax co kernel-2.5
cd into the kernel dir created by cvs and check the Makefile
$ cd kernel-2.5
Look into /kernel-2.5/arch/vax/configs and someone's made it easy!
Just choose the appropriate one for your hardware.
eg for SIMH, you'd use ka650_defconfig
I have an ancient KA41-D, so I'll select ka42_defconfig.
$ make ka42_defconfig
$ make
NOTE: this was built with a wired-in kernel command line of:
"root=/dev/nfs nfsroot=/home/disk_vax/vaxroot ip=bootp rw debug"
So, first off, you need to get mopd! Grab from http://linux-vax.sourceforge.net/download/mopd-linux.tar.gz
Because I'm on an ALPHA that doesn't support a.out formats, I have to edit the Makefile to say
AOUT_SUPPORT="-DNOAOUT"
#AOUT_SUPPORT=""
You should be able to build by simply running make. Ignore all the warnings - they are completely harmless.
To remove the warnings, go into the .H files and put comments after the
#endif _blah_ so that it is #endif /* _blah_ */
if you want to put mopd somewhere so you don't have to keep looking for it, /usr/local/bin might be best.
$ su
# cp mopd /usr/local/bin
# cp mopd.8 /usr/local/man/man8
Create the directory /tftpboot/mop as mopd looks here, (ONLY here!) when searching for boot images.
# mkdir /tftpboot/mop
Put your ethernet into promiscuous mode
# ifconfig eth0 promisc
Now we can start up the mopd service
# mopd eth0
Create a link from /tftpboot/mop/
On your VAX, issue the command
>>> SHOW ETHER which returned 08-00-2B-31-5F-25
$ cd /tftpboot/mop
$ su
# ln -s /home/lukeb/vax/kernel-2.5/vmlinux.SYS 08002b315f25.SYS
(if you're not sure that the VAX is MOP loading this, run MOPTRACE and TCPDUMP to watch things)
Once your VAX can mopboot, it'll need to access the vaxroot remote file-system. You'll need your NFS service running. Locate the Services control under foot->Programs->System->Service Configuration and tick nfs. If nfs isn't there, you'll have to go find/install the rpm.
Now add an entry into the NFS config file /etc/exports so that it exports your root as expected by the mopboot kernel.
The IP mask just says let all-and-sundry on my home network get to the thing.
# emacs /etc/exports
/home/disk_vax/vaxroot 192.168.0.0/24(sync,rw,no_root_squash)
and make this known to NFS (see /var/lib/nfs/xtab)
# exportfs -a
allow bootp;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.5 192.168.0.200;
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.0.1;
option domain-name "eastwood";
host uVAX {
hardware ethernet 08:00:2b:31:5F:25;
fixed-address 192.168.0.110;
option host-name "uVAX";
server-name "alpha";
option root-path "/home/disk_vax/vaxroot";
}
}
Now restart DHCPD to pick up this new config.If I've done all the above correctly, I should be able to power-up the VAX. Say >>> BOOT ESA0 and watch it boot up. (or XQA0 or whatever)
Under Linux and Windows, SIMH can emulate a DELQA.
on UNIX you'll want to have a current libpcap library
http://tcpdump.org
For Win2000/XP you'll want a current WinPcap
http://winpcap.polito.it/install/default.htm
OK, we're now ready to build SIMH itself and get going!
$ mkdir BIN
$ make USE_NETWORK=1 BIN/vax
(Assuming you've been able to build a kernel successfully as described above)
Now, grab the Linux/VAX kernel-2.5 tree and compile with:
$ make ka650_defconfig
$ make
this kernel should be able to boot in SIMH.
Copy your vmlinux.dsk into the SIMH vax directory (or link to it) and you should be able to boot.
To be able to get networking going between the Linux host and SIMH on the same host, you'll need the "mirror"
(kernel-mode) network driver.
Download from
http://linux-vax.sourceforge.net/download/mirror.tar.gz
This should compile without drama - just make sure KERNEL_DIR in Makefile is pointing at your kernel sources.
Note1: if your host Linux box sources aren't there, go install from the kernel-source-X.Y.Z.ARCH.src.rpm
Note2: if you don't have the exact-match sources to your currently running kernel, it may still compile,
however do NOT try to -force an install !
My machine blew up... I then located and installed the correct sources...
$ su
# gunzip mirror.tar.gz
# tar -xvf mirror.tar
$ cd mirror
$ make
Next, you have to make this known as a kernel installable module and make it available to your
running host's kernel. Use insmod to do this.
$ su
# insmod mirror.o
Now bring up the mirror0 interface and give it an address on a DIFFERENT subnet to your hosts subnet.
(as you saw I've done for simhVAX in my dhcpd.conf above)
# ip addr add 192.168.201.1 dev mirror0
# ip link set mirror0 up
For your dhcpd.conf, you'll want something along these lines:
# utilise a dummy network using mirror.o
# so that SIMH can run via a loopback bridge.
# if not using loopback, just have simhVAX in the
# normal subnet and it should work from whatever remote
# machine it's on.
subnet 192.168.201.0 netmask 255.255.255.0 {
option routers 192.168.201.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.201.1;
host simhVAX {
hardware ethernet 08:00:2b:aa:bb:cc;
# fixed-address 192.168.0.120;
fixed-address 192.168.201.2;
option host-name "simhVAX";
server-name "alpha";
option root-path "/home/disk_vax/vaxroot";
}
}
As per a normal VAX mopboot, you'll still doUnder WindowsXP, I installed the latest WinPcap as mentioned above, downloaded the precompiled exe (with ethernet support) and configured the dhcpd.conf on the NFS server (alpha) as normal (no special subnet for SIMH). So, I configured my dhcpd.conf as:
# emacs /etc/dhcpd.conf
allow bootp;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.5 192.168.0.200;
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.0.1;
host uVAX {
hardware ethernet 08:00:2b:31:5F:25;
fixed-address 192.168.0.110;
option host-name "uVAX";
server-name "alpha";
option root-path "/home/disk_vax/vaxroot";
}
host simhVAX {
hardware ethernet 08:00:2b:31:5F:25;
fixed-address 192.168.0.120;
option host-name "simhVAX";
server-name "alpha";
option root-path "/home/disk_vax/vaxroot";
}
}
and then restarted dhcpd.
Over onto the WinXP box, into the \SIMH\VAX directory and start VAX.exe
C:\SIMH\VAX> vax vax.ini
I successully boot using
sim> set cpu conhalt
sim> set cpu 64m
sim> load -r ka655.bin
sim> attach NVR ka655.nvr
sim> set rq0 ra92
sim> set rq1 rrd40
sim> att rq0 vmlinux.dsk
sim> att xq eth0
sim> boot cpu
KA655-B V5.3, VMB 2.7
>>> BOOT XQA0
and it chugs away and you'll see a 'vax login: '
login as root and you get the '#' prompt - YAHOO!!!