pidp11 re-install problems

[Geoffrey McDermott]

I've been having some minor issues that I couldn't solve, like the nankervis stuff wouldn't run, so I decided to blow away the /opt/pidp11 directory, and start from scratch,

Simple, really, except I've done all the install stuff like this:

sudo mkdir /opt/pidp11
cd /opt/pidp11
sudo wget https://www3.ispnet.net/pidp11/pidp11.tar.gz
sudo tar -xvf pidp11.tar.gz
sudo /opt/pidp11/install/install.sh

sudo wget https://www3.ispnet.net/pidp11/systems.tar.gz
sudo tar -xvf systems.tar.gz

sudo wget https://www3.ispnet.net/pidp11/pidp11.tar.gz
sudo tar -xvf pidp11.tar.gz
sudo /opt/pidp11/install/install.sh

​sudo wget https://www3.ispnet.net/pidp11/systems.tar.gz
sudo tar -xvf systems.tar.gz

and when I reboot the RPI, I don't get any simh fuinctionality at all.

Obviously, the RPI is functional, and I'm connecting wirelessly using putty/ssh, but nothing pidp11 related appears to work.

login as: pi
p...@192.168.1.128's password:
Linux raspberrypi 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed May 13 17:48:37 2020 from 192.168.1.154
0
pi@raspberrypi:~ $ pwd
/home/pi
pi@raspberrypi:~ $ ./pdp.sh
0
pi@raspberrypi:~ $

Why can't this be just a simple thing to accomplish?

Obviously, I didn't download and install the Nankervis stuff.

[Geoffrey McDermott]

I didn't do the install twice in sequence......cut and paste error.

[Adam Thornton]

Maybe tar xvpf ?  I’m guessing that something wants to be root or setuid.  I can’t check right now because the work VPN doesn’t allow me to connect to the 192.168/16 network while connected, which is very annoying.

Begin forwarded message:

--
You received this message because you are subscribed to the Google Groups "[PiDP-11]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pidp-11+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pidp-11/ffed4600-90aa-4a31-8b16-9ffffc65d00f%40googlegroups.com.

[Steve Tockey]

It sounds like your problems might be more fundamental if you can't get any PiDP-11/70 action at all, but FWIW I couldn't get the Nankervis stuff to run when the basic PiDP-11/70 was originally running. The problem was that all of the paths in the Nankervis scripts didn't match the paths in how everything was installed. I had to edit a bunch of paths in the script files before things ran.

[Geoffrey McDermott]

And how do I resolve this?

[Steve Tockey]

I'm certainly not the expert in this part, but I think one place to start is to enter the command "ps -a" in a terminal window on the Pi. You should see both "client11" and "server11" listed, as in:

pi@raspberrypi:~ $ ps -a

  PID TTY          TIME CMD

  597 pts/1    00:00:00 sudo

  602 pts/1    00:02:36 server11

  726 pts/1    00:00:00 sudo

  739 pts/1    00:00:31 client11

 1260 pts/0    00:00:00 bash

 1272 pts/0    00:00:00 sudo

 1276 pts/0    00:00:00 screen

 2083 pts/2    00:00:00 ps

pi@raspberrypi:~ $ 

If client11 isn't there then there was some kind of problem getting simh to run. If server11 isn't there then the thing that the ~/pdp.sh command is trying to connect to (screen) isn't running. If both are there, then the problem seems to be with the ~/pdp.sh script making the connection to server11.

BTW, the names client11 and server11 are bass-ackwards from what they should really be. The simh process should really be called the server and the screen connection should really be called the client (IMHO).

Sorry I can't help any more than this, but this might at least give you a place to start figuring out what's going wrong.

[Geoffrey McDermott]

Well, I re-flashed the SD card with the same version that I originally used, did a compete reinstalln using the supplied commands that were copied and pasted to the SSH session opened to the RPI, and it still doesn't do anything.

When I try to do a ./pidp11.sh, it returns a single 0 character. Then I tried this:

pi@raspberrypi:/opt/pidp11/bin $ ./pidp11.sh
*** Start portmapper for RPC service, OK to fail if already running
rpcbind: another rpcbind is already running. Aborting
*** booting idled ***
*** Start client/server ***
./client11: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not found (required by ./client11)
pi@raspberrypi:/opt/pidp11/bin $

AFAICT, the installation process ran with no errors reported.......

I'm at a loss as to what to do next.

pi@raspberrypi:~ $ ps a
  PID TTY      STAT   TIME COMMAND
  480 tty1     Ss     0:00 /bin/login -f
  664 tty1     S+     0:00 -bash
  964 pts/0    Ss     0:00 -bash
 1576 pts/0    R+     0:00 ps a
pi@raspberrypi:~ $

HELP!!!!!! Something is really broken in the current SW package/setup,so can someone try to install the SW just to prove I'm not completely insane.

[Jeff Thieleke]

Maybe try rebuilding client11 on your system? 

cd /home/pi/pidp11/src

./makeclient.sh

sudo cp /home/pi/pidp11/src/02.3_simh/4.x+realcons/bin-rpi/pdp11_realcons /opt/pidp11/bin/client11

[Steve Tockey]

Jeff,

It seems to be complaining about GLIBC_2.28 not being found, so simply rebuilding client11 may not work since Geoffrey already ran the basic PiDP-11/70 build scripts.

Goeffrey,

Have you updated Raspbian OS since you installed it? See:

https://www.raspberrypi.org/documentation/raspbian/updating.md

If you didn't update Raspbian then you might have an old (i.e., incompatible) version of GLIBC. Doing the "sudo apt update" and "sudo apt full-upgrade" would make sure you have the latest libraries for everything. Then, try rebuilding the PiDP-11/70 software with:

cd /opt/pidp11
sudo /opt/pidp11/install/install.sh

Good luck,

-- steve

[oscarv]

Geoffrey,

I just read through your trials & tribulations...

I am baffled - the reference to a missing GLIBC would mean that your Raspbian SD card is missing a fundamental bit (the fundamental bit) of C.

(but -- see the end of the post for what I now think your problem is: an old Raspbian version?)

To establish what is going on:

- Did you download the Raspbian image from here (https://www.raspberrypi.org/downloads/raspbian/)? The regular Raspbian Buster with desktop and recommended software)?

- Once that has booted up the Raspberry Pi, did you do these steps as er the manual:

Download & Install

1 Make a /opt/pidp11 directory and go there:

sudo mkdir /opt/pidp11

cd /opt/pidp11

2 Download the pidp11 software:

sudo wget https://www3.ispnet.net/pidp11/pidp11.tar.gz

3 Unpack it so the software lives in its designated /opt/pidp11/ directory:

sudo tar -xvf pidp11.tar.gz

4 Run the install script so the PDP-11 autoboots when you switch on the Pi:

sudo /opt/pidp11/install/install.sh

5 Reboot and see the lights:

sudo reboot

Adding the PDP-11 operating systems collection

The above gives you the PiDP-11, but only a demo program (idled) to run. The next step is thus to download all the operating systems. Download and unpack the ‘systems’ collection of disk images:

cd /opt/pidp11

sudo wget https://www3.ispnet.net/pidp11/systems.tar.gz

sudo tar -xvf systems.tar.gz

After that, a reboot must show the PiDP-11 blinking away.

... Wait! Some Googling on the error line

"/lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not found"

results in this link: https://github.com/domoticz/domoticz/issues/3886 .

Which leads me to ask -- are you really using Raspbian Buster? This error message is related to running an old Raspbian version (probably the Jessie version!).

Kind regards,

Oscar.

[Geoffrey McDermott]

I used the same version that I initially used when I built the kit......it was Rasbian-stretch-full dated April 08 2019. When it started, it updated automatically. I saw no reason to use Bustert since I don't have a RPI4, just an RPI3B.

That still doesn't explain why just deleting the pidp11 directory and reinstalling failed.

[Oscar Vermeulen]

Geoffrey,

I assume the reason is that the binaries in the latest tarball were built on Buster

So the solution is to download the new version of Raspbian. Alternatively, you can run the build scripts to recompile for the older Buster version of Raspbian, that should work. But why do that...

Kind regards,

Oscar.

(later edit: it was Buster, not Jessie that caused your GLIB issue)

[Geoffrey McDermott]

I'll install buster and reinstall. The binaries should be labeled as to what they were made with, or what OS version they need to run.

A simple notice in the documentation is really needed beyond saying:

"This page assumes you have already set up your Raspberry Pi like you would do for any Pi"

OR

".......set up your Pi to the point where you have an internet connection going, and then install the pidp11 software."

Anyway, I understand what the problem is, and expect everything to work fine.

Thanks as always for your response and advice and understanding.

[Geoffrey McDermott]

Well, I installed Buster and did a complete reinstall, and I have blinkenlights again, BUT (there's always a but) I still have the original issue that I did a reinstall originally......

When I try to boot to nankervis from rt11 in this case, I get this:

RT-11SJ (S) V05.03

.
--> Rebooting...

Simulation stopped, PC: 153744 (MOV (SP)+,R4)
exit
sim> exit
Goodbye
*** booting nankervis ***
*** Start client/server ***

PDP-11 simulator V4.0-0 Current  REALCONS build Aug 14 2019
Disabling XQ
RL1: 'rl1.dsk' Contains an ODS1 File system
RL1: Volume Name:       RSXM26 Format: DECFILE11A   Sectors In Volume: 20480
RP3: 'rp3.dsk' Contains an ODS1 File system
RP3: Volume Name:       RSXM56 Format: DECFILE11A   Sectors In Volume: 171798
Searching realcons controller "11/70" ...
Connecting to host localhost ...
sim>

If I continue simh, it just reports a stop instruction.

[Oscar Vermeulen]

Geoffrey,

On Mon, 18 May 2020 at 19:28, Geoffrey McDermott <crusade...@gmail.com> wrote:

When I try to boot to nankervis from rt11 in this case, I get this:

RT-11SJ (S) V05.03

I never tried the RT-11 on the Nankervis collection (the regular RT-11 boot option is fine for me) but maybe someone can have a look at it? I've been away from my PiDPs for a good few weeks by now, although I hope to finally, finally make it home again by tomorrow night, after weeks of hassle due to some obscure virus I didn't even catch myself.

On the regular RT-11 boot option: do make sure you use 'sudo raspi-config' to set a default resolution for the display. Otherwise the GT-40 display that's set up for it can get confused if you do not use a physical HDMI monitor.

Kind regards,

Oscar.

[Geoffrey McDermott]

The RT-11 shown on the screen was the version loaded from the standard configuration(003 switch setting). I was in that when I pressed the reboot switch with the 1000 in the switches to load nankervis, so Nanmkervis never really started.

Nankervis operates(yes I did have it running right after the original kit build) by loading the appropriate 'disk drive', but it never even gets that far.....

[Geoffrey McDermott]

All I really want to accomplish is the get Adventure running on the PiDP11, and Nankervis was the only way that I could get it to work.

I chose RT11 because it doesn't require any shutdown sequence. If there was a DETAILED set of instructions to get Adventure running on the installed RT11, I could care less about the Nankervis stuff.

[Steve Tockey]

FWIW, I'm getting the same behavior on my PiDP-11/70 as Geoffry is getting:

*** booting nankervis ***

*** Start client/server ***

*** RPi 2/3/Z detected

PDP-11 simulator V4.0-0 Current  REALCONS build Mar 21 2020

Disabling XQ

RL1: 'rl1.dsk' Contains an ODS1 File system

RL1: Volume Name:       RSXM26 Format: DECFILE11A   Sectors In Volume: 20480

RP3: 'rp3.dsk' Contains an ODS1 File system

RP3: Volume Name:       RSXM56 Format: DECFILE11A   Sectors In Volume: 171798

Searching realcons controller "11/70" ...

Connecting to host localhost ...

sim> 

That said, however, I don't think Paul Nankervis' stuff was ever intended to run "out of the box" on the PiDP-11/70. I think it's intended for use with the emulator as described in Paul N's manual (see "/opt/pidp11/systems/nankervis/Guide from Paul Nankervis.pdf"). One major thing I found was that the attach commands in /opt/pidp11/systems/nankervis/boot.ini are all of the form "attach rk0 ../bootscripts/21/rk0.dsk" where the path segment /bootscripts/21/ is not in the PiDP-11/70 directory structure. At a dead minimum, all of those path names need to be edited to match the actual PiDP-11/70 directory structure. Another major thing is that Paul N's boot.ini file never actually boots any system. In, for example, /opt/pidp11/systems/rt11/boot.ini the last line is boot rl0 to get the RT-11 system booted. No such boot command is in /opt/pidp11/systems/nankervis/boot.ini.

The bottom line for me was to copy a Paul N disk that I wanted to look at into the corresponding PiDP-11/70 directory and then just add an attach line inside the relevant boot.ini file. For example, copy /opt/pidp11/systems/nankervis/rk1.dsk into /opt/pidp11/systems/rt11/ then edit /opt/pidp11/systems/rt11/boot.ini to add the lines:

;try to attach Nankervis' rk1

set rk1 enable

attach rk1 rk1.dsk

Once the normal PiDP-11/70 RT-11 system is booted up, you can then:

*) Remove one of the unused devices because the existing RT-11 device table is full. Candidates for removal are (IMHO) DD or CT. For example, .REMOVE CT will drop the card reader driver and make room for a new driver like RK.

*) Install the RK driver using the command .INSTALL RK

You can now .DIR RK1: to see what's on Paul N's disk.

Alternatively, if you are more adventurous, it's actually reasonably easy to set up your own new systems. Notice the file /opt/pidp11/systems/selections maps PiDP-11/70 front panel switch configurations into /opt/pidp11/systems/ directories. So start with an existing runnable PiDP-11/70 system directory, clone it as a new directory under /opt/pidp11/systems/, edit the /opt/pidp11/systems/selections file to reference it, then edit the boot.ini file in the cloned system directory to boot to the disk from the Nankervis collection.

Hope this helps,

-- steve

[Steve Tockey]

Geoffrey,

"All I really want to accomplish is the get Adventure running on the PiDP11 ... If there was a DETAILED set of instructions to get Adventure running on the installed RT11, I could care less about the Nankervis stuff."

Hopefully this will get you on the air:

1) In Raspbian, copy the file /opt/pidp11/systems/nankervis/rk1.dsk into the directory /opt/pidp11/systems/rt11/  Note that I am assuming ADVENTURE is on Paul N's rk1.dsk. If it's not there, then just substitute the name of the .dsk file it is on both here and in step 2

2) In Raspbian, edit the file /opt/pidp11/systems/rt11/boot.ini to add these two lines anywhere in the middle:

set rk1 enable

attach rk1 rk1.dsk

3) Boot the PiDP-11/70 into RT-11 as you normally would

4) In RT-11, do these three commands:

.REMOVE CT

.INSTALL RK

.DIR RK1:

5) Find the files on RK1: that you need to be able to run ADVENTURE. Sorry, I don't know what files they are. Hopefully you do know.

6) Copy those files from RK1: to SY:.

You should now be able to run ADVENTURE on your RT-11 system.