minimum software

[Carl Marbach]

I've downloaded all the software and attached my Pi5 to the front panel. I have a screen on the monitor, but no lights. The test, pidp10-test, blinks all the lights fine.

If all I want right now is the front panel lights, what can I do to fix this?

Thanks

Carl

[Francis King]

> I've downloaded all the software and attached my Pi5 to the front panel.

So, you've installed the software, and set it to run automatically on power up?

Set the data switches to all zeroes, and switch it on. It should run Blinky. Does it?

PiDP-10 manual

F.

[Carl Marbach]

I've reloaded software several times. No lights.

How can I just run Blinky manually?

Carl

[Ric Werme]

Try:

 $ pdpcontrol start 0

E.g.:

werme@raspberrypi:~$ which pdpcontrol
/usr/local/bin/pdpcontrol

werme@raspberrypi:~$ pdpcontrol start 0

Starting PiDP-10 with boot option 0
screen -dmS pidp10 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
0

werme@raspberrypi:~$ pdpcontrol stop

Stopping PiDP-10 pidp
spawn screen -x pidp10
0

werme@raspberrypi:~$ pdpcontrol start 3   [won't work for you]
Starting PiDP-10 with boot option 3
screen -dmS pidp10 ./pidp10 /opt/pidp10/systems/ejw-lights/boot.pi
0

[Tim Radde]

Where did you download from?  Aren't there multiple repositories?  Have the directions been updated to point to the most current?

This may have been fixed but I beleve Oscar's listed repository is not fully up to date?  Correct me if I am wrong.

[Ric Werme]

I started out with a Raspberry Pi 4 and directions on page 7 of https://obsolescence.dev/pidp10-sw/PiDP-10_Manual.pdf so I installed from "sudo git clone https://github.com/obsolescence/pidp10"  .  When I realized that the memory display was wrong, I reinstalled and included simh/pidp10 source to fix that, I don't believe Eric Swenson's similar changes are incorporated into the distribution yet.

Between that and my interest in getting my lights program running standalone, I often ignore the pdpcontrol/screen/etc stuff and run pidp10 directly.

You say "No lights."  That's not very useful debugging info.  How much Unix/Linux experience do you have?  Is the emulator even running?  I.e. What does "ps" say:

werme@raspberrypi:~$ pdpcontrol start 0
Starting PiDP-10 with boot option 0
screen -dmS pidp10 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
0

werme@raspberrypi:~$ ps axl | grep pidp10
1  1000    5009       1  20   0   7048  2272 do_sel Ss   ?          0:00 SCREEN -dmS pidp10 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
4  1000    5010    5009  30  10 382044 65692 -      RNsl+ pts/2     0:02 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
0  1000    5027    3863  20   0   6092  2020 pipe_r S+   pts/1      0:00 grep --color=auto pidp10
werme@raspberrypi:~$ unalias grep

If pidp10, the simh variant, is running, can you get to it and stop it with ^E?

Do you have all the console switches set to zero/off (top side down - backwards from normal thought, and something I somehow forgot!)?

[Carl Marbach]

ps says:

PID   TTY         TIME         CMD

2466 pts /0   00:"00:00 Bash

The pdpcontrol start 0    just lights, dimly, a few on the bottom row stagnantly and very dim

cntl E dows nothing

I don't have a lot of UNIX experience

I did all the downloads from github as per the latest instructions

I am back at the pi@raspberrypi prompt

what next?

Thanks

Carl

--
You received this message because you are subscribed to a topic in the Google Groups "PiDP-10" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pidp-10/-ucRo1hmzZQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pidp-10+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pidp-10/4d8dda65-0d0d-453e-b20a-b5f2afa49af7n%40googlegroups.com.

[Ric Werme]

> The pdpcontrol start 0    just lights, dimly, a few on the bottom row stagnantly and very dim

I hope it also printed something on the terminal.  I don't see how it can "just lights, dimly" without printing anything.

> cntl E dows nothing

My instruction "can you get to it and stop it with ^E?" assumed you were familiar with Linux and somewhat familiar with the PiDP-10 manual and its references to the simh emulator's Ctrl-E interrupt.  I've been running it directly lately, but remotely from my main Linux Mint system and didn't take the time spell things out better.

> I don't have a lot of UNIX experience

Yeah, not using the ps command I offered shows that.  This is not the best group for a "Unix 101" teaching.  I got my start on Unix in 1980.

> I did all the downloads from github as per the latest instructions

> I am back at the pi@raspberrypi prompt

Linux is a text/terminal/type-in system.  Don't tell us "I am back at the pi@raspberrypi prompt" when you can cut and paste your dialog from the terminal window.  Did you manually retype the output from "ps"?  It looks that way - clues include capitalized "Bash" and the space in "pts /1".

I explicitly showed you what I see when I run "pdpcontrol start 0" - you seem to say you just get dim lights and nothing on the terminal.

I explicitly showed you the ps command and  argument to run.  "alx" says:

a: Look at all processes running on a terminal
x: Look at all processes not tied to a terminal
l: Print long-format status.

Let's rewind.  What does your PiDP-10 system look like?  Does it have (yeah, the first few are obvious):

A Raspberry Pi 5
A PiDP-10 front panel
A keyboard and display
A mouse (this is not quite so obvious - Linux doesn't require a mouse)
A window/desktop manager
A terminal window that does not take up the full screen area.
A column of icons on the left of the screen include one labeled "SIMH".
A working network connection.
A web browser.

If you have all that, then you can get to this group on the browser and cut 'n paste text from your terminal window.  And to your terminal window.

What I wanted from that "ps alx" command was to see if the PDP-10 emulator was running - the " | grep pidp10" was to direct the command's output to something that only listed lines that have something to do with the emulator.  The real question it would answer is "Is simh running?"  If simh isn't running, that would likely leave all the lights off.  If simh is running, then we can poke it to get an idea of why lights are off or explore other avenues.

  -Ric

[Carl Marbach]

pi@raspberrypi:~ $ pdpcontrol start 0

Starting PiDP-10 with boot option 0
screen -dmS pidp10 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
0

pi@raspberrypi:~ $ pdpcontrol start 0

Starting PiDP-10 with boot option 0
screen -dmS pidp10 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
0

pi@raspberrypi:~ $ pdpcontrol start 0

Starting PiDP-10 with boot option 0
screen -dmS pidp10 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
0

pi@raspberrypi:~ $ sudo pdpcontrol start 0

Starting PiDP-10 with boot option 0
screen -dmS pidp10 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
0

pi@raspberrypi:~ $ ps
    PID TTY          TIME CMD
   2486 pts/0    00:00:00 bash
   3026 pts/0    00:00:00 ps
pi@raspberrypi:~ $ sudo pdpcontrol start 0

Starting PiDP-10 with boot option 0
screen -dmS pidp10 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
0

pi@raspberrypi:~ $ ps alx
F   UID     PID    PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
4     0       1       0  20   0  25568 15168 -      Ss   ?          0:01 /sbin/i
1     0       2       0  20   0      0     0 -      S    ?          0:00 [kthrea
1     0       3       2  20   0      0     0 -      S    ?          0:00 [pool_w
1     0       4       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0       5       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0       6       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0       7       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0       8       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      13       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      14       2  20   0      0     0 -      I    ?          0:00 [rcu_ta
1     0      15       2  20   0      0     0 -      I    ?          0:00 [rcu_ta
1     0      16       2  20   0      0     0 -      I    ?          0:00 [rcu_ta
1     0      17       2  20   0      0     0 -      S    ?          0:00 [ksofti
1     0      18       2  20   0      0     0 -      I    ?          0:04 [rcu_pr
1     0      19       2  20   0      0     0 -      S    ?          0:00 [rcu_ex
1     0      20       2  20   0      0     0 -      S    ?          0:00 [rcu_ex
1     0      21       2 -100  -      0     0 -      S    ?          0:00 [migrat
1     0      22       2  20   0      0     0 -      S    ?          0:00 [cpuhp/
1     0      23       2  20   0      0     0 -      S    ?          0:00 [cpuhp/
1     0      24       2 -100  -      0     0 -      S    ?          0:00 [migrat
1     0      25       2  20   0      0     0 -      S    ?          0:00 [ksofti
1     0      28       2  20   0      0     0 -      S    ?          0:00 [cpuhp/
1     0      29       2 -100  -      0     0 -      S    ?          0:00 [migrat
1     0      30       2  20   0      0     0 -      S    ?          0:00 [ksofti
1     0      33       2  20   0      0     0 -      S    ?          0:00 [cpuhp/
1     0      34       2 -100  -      0     0 -      S    ?          0:00 [migrat
1     0      35       2  20   0      0     0 -      S    ?          0:00 [ksofti
5     0      42       2  20   0      0     0 -      S    ?          0:00 [kdevtm
1     0      43       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      44       2  20   0      0     0 -      S    ?          0:00 [kaudit
1     0      45       2  20   0      0     0 -      S    ?          0:00 [khungt
1     0      46       2  20   0      0     0 -      S    ?          0:00 [oom_re
1     0      48       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      49       2  20   0      0     0 -      S    ?          0:00 [kcompa
1     0      50       2  20   0      0     0 -      S    ?          0:00 [kcompa
1     0      51       2  20   0      0     0 -      S    ?          0:00 [kcompa
1     0      52       2  20   0      0     0 -      S    ?          0:00 [kcompa
1     0      53       2  20   0      0     0 -      S    ?          0:00 [kcompa
1     0      54       2  20   0      0     0 -      S    ?          0:00 [kcompa
1     0      55       2  20   0      0     0 -      S    ?          0:00 [kcompa
1     0      56       2  20   0      0     0 -      S    ?          0:00 [kcompa
1     0      58       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      59       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      60       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      63       2 -51   -      0     0 -      S    ?          0:00 [watchd
1     0      65       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      66       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      67       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      69       2  20   0      0     0 -      S    ?          0:00 [kswapd
1     0      70       2  20   0      0     0 -      S    ?          0:00 [kswapd
1     0      71       2  20   0      0     0 -      S    ?          0:00 [kswapd
1     0      72       2  20   0      0     0 -      S    ?          0:00 [kswapd
1     0      73       2  20   0      0     0 -      S    ?          0:00 [kswapd
1     0      74       2  20   0      0     0 -      S    ?          0:00 [kswapd
1     0      75       2  20   0      0     0 -      S    ?          0:00 [kswapd
1     0      76       2  20   0      0     0 -      S    ?          0:00 [kswapd
1     0      77       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      78       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      84       2  20   0      0     0 -      S    ?          0:00 [hwrng]
1     0      85       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      86       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      87       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      88       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      89       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      90       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      91       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      92       2   0 -20      0     0 -      I<   ?          0:05 [kworke
1     0      93       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      94       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      95       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      96       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0      97       2 -51   -      0     0 -      S    ?          0:00 [irq/38
1     0      98       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     101       2 -51   -      0     0 -      S    ?          0:00 [irq/16
1     0     104       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     105       2 -51   -      0     0 -      S    ?          0:00 [irq/16
1     0     110       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     134       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     168       2  20   0      0     0 -      S    ?          0:00 [spi10]
1     0     169       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     170       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     171       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     172       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     173       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     174       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     175       2 -51   -      0     0 -      S    ?          0:00 [irq/17
1     0     176       2 -51   -      0     0 -      S    ?          0:00 [irq/17
1     0     177       2  20   0      0     0 -      S    ?          0:00 [cec-vc
1     0     178       2 -51   -      0     0 -      S    ?          0:00 [irq/17
1     0     179       2 -51   -      0     0 -      S    ?          0:00 [irq/17
1     0     180       2 -51   -      0     0 -      S    ?          0:00 [irq/17
1     0     181       2 -51   -      0     0 -      S    ?          0:00 [irq/17
1     0     182       2  20   0      0     0 -      S    ?          0:00 [cec-vc
1     0     183       2 -51   -      0     0 -      S    ?          0:00 [irq/17
1     0     184       2 -51   -      0     0 -      S    ?          0:00 [irq/17
1     0     185       2 -51   -      0     0 -      S    ?          0:00 [card1-
1     0     186       2 -51   -      0     0 -      S    ?          0:00 [card1-
1     0     187       2 -51   -      0     0 -      S    ?          0:00 [card1-
1     0     188       2 -51   -      0     0 -      S    ?          0:00 [card1-
1     0     224       2  20   0      0     0 -      D    ?          0:00 [jbd2/m
1     0     225       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     244       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     245       2   0 -20      0     0 -      I<   ?          0:00 [kworke
4     0     345       1  20   0  26992 10592 -      Ss   ?          0:00 /usr/li
1     0     368       2  20   0      0     0 -      S    ?          0:00 [ext4la
4   991     422       1  20   0  92560  8320 -      Ssl  ?          0:00 /usr/li
4     0     430       1  20   0  36496 11664 -      Ss   ?          0:00 /usr/li
1     0     431       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     620       2 -51   -      0     0 -      S    ?          0:00 [irq/18
1     0     632       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     647       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     652       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0     653       2  20   0      0     0 -      S    ?          0:00 [brcmf_
4   102     681       1  20   0   7056  3536 -      Ss   ?          0:00 /usr/sb
1     0     684       1  20   0   5168  1680 -      Ss   ?          0:00 /usr/sb
4     0     740       1  20   0 310368  7552 -      Ssl  ?          0:00 /usr/li
4   101     742       1  20   0   6608  4256 -      Ss   ?          5:51 avahi-d
4     0     743       1  20   0  13472  6768 -      Ss   ?          0:00 /usr/li
4     0     744       1  20   0   7152  2912 -      Ss   ?          0:00 /usr/sb
4   990     746       1  20   0  10000  6496 -      Ss   ?          0:06 /usr/bi
4   988     751       1  20   0 309600  9968 -      Ssl  ?          0:00 /usr/li
4     0     755       1  20   0  19200  9168 -      Ss   ?          0:00 /usr/li
4     0     756       1  20   0 409456 15232 -      Ssl  ?          0:00 /usr/li
1   101     777     742  20   0   5856  1888 -      S    ?          0:00 avahi-d
4     0     862       1  20   0 343136 21168 -      Ssl  ?          0:34 /usr/sb
4     0     863       1  20   0  18816 11968 -      Ss   ?          0:03 /usr/sb
4     0     885       1  20   0 325440 14128 -      Ssl  ?          0:00 /usr/sb
5     0     887       2  10 -10      0     0 -      S<   ?          0:00 [krfcom
4   985    1004       1  20   0   2480  1616 -      Ss   ?          0:00 /bin/sh
0   985    1022    1004  20   0 259888 44080 -      Sl   ?          0:00 wayvnc
4     0    1024       1  20   0 382144  7504 -      Ssl  ?          0:00 /usr/sb
4   108    1049       1  20   0 318368 14688 -      Ssl  ?          0:00 /usr/li
4     0    1055       1  20   0   9536  4576 -      Ss   ?          0:00 login -
4     0    1056       1  20   0   7456  2640 -      Ss+  ?          0:06 /sbin/a
4     0    1058    1024  20   0 173056  8800 -      Sl   ?          0:00 lightdm
4  1000    1082       1  20   0  23888 13344 -      Ss   ?          0:00 /usr/li
5  1000    1086    1082  20   0  24400  4640 -      S    ?          0:00 (sd-pam
0  1000    1135    1082  20   0   8624  4944 do_epo Ss   ?          0:00 /usr/bi
0  1000    1136    1082  20   0 114336 15024 do_epo Ssl  ?          0:00 /usr/bi
4  1000    1137    1058  20   0 677600 121200 do_epo Ssl ?          1:10 /usr/bi
0  1000    1139    1082  20   0  85504  4960 do_epo Ssl  ?          0:00 /usr/bi
0  1000    1140    1082  20   0 770880 43024 do_sys Ssl  ?          0:01 /usr/bi
0  1000    1142    1082  20   0 101776  9200 do_epo Ssl  ?          0:00 /usr/bi
0  1000    1169    1082  20   0   7616  3760 do_sys Ss   ?          0:00 /usr/bi
1  1000    1921    1137  20   0  10288  2048 -      Ss   ?          0:00 /usr/bi
4  1000    2045    1055  20   0   9008  5824 do_sel Ss+  tty1       0:00 -bash
4     0    2060       1  20   0  33136 20944 -      Ss   ?          0:00 python
0  1000    2118       1  20   0   2480  1616 do_wai S    ?          0:00 /bin/sh
0  1000    2119       1  20   0   2480  1600 do_wai S    ?          0:00 /bin/sh
0  1000    2120       1  20   0   2704  1744 do_sys S    ?          0:00 /usr/bi
0  1000    2165       1  20   0 414432 21520 do_sys Sl   ?          0:00 /usr/li
0  1000    2167    2118  20   0   2480  1552 do_wai S    ?          0:00 /bin/sh
0  1000    2168    2119  20   0 924144 63216 do_sys Sl   ?          1:10 /usr/bi
0  1000    2169    2167  20   0 669984 55696 do_sys Sl   ?          0:04 pcmanfm
0  1000    2171       1  20   0  18576  7344 do_wai S    ?          0:00 systemd
0  1000    2174    2171  20   0 414048 20896 do_sys Sl   ?          0:00 gtk-nop
0  1000    2204    1082  20   0 314192  8528 do_sys Ssl  ?          0:00 /usr/li
0  1000    2214    1082  20   0 473584  7584 futex_ Sl   ?          0:00 /usr/li
0  1000    2230    1082  20   0 710432 21328 do_sys Ssl  ?          0:00 /usr/li
0  1000    2238    1082  20   0 310992  7728 do_sys Ssl  ?          0:00 /usr/li
0  1000    2243    1082  20   0 393584 12160 do_sys Ssl  ?          0:00 /usr/li
0  1000    2244    1082  20   0 692112  7664 do_sys Ssl  ?          0:00 /usr/li
4     0    2254    2244  20   0   2384  1808 -      Ss   ?          0:00 fusermo
0  1000    2260    1082  20   0 309168  7024 do_sys Ssl  ?          0:00 /usr/li
0  1000    2261    1082  20   0 427760 35440 do_sys Ssl  ?          0:00 /usr/li
0  1000    2266    1082  20   0 308896  6672 do_sys Ssl  ?          0:00 /usr/li
0  1000    2280    1082  20   0 310560  7488 do_sys Ssl  ?          0:00 /usr/li
0  1000    2287    1082  20   0 391248  9008 do_sys Ssl  ?          0:00 /usr/li
0  1000    2289    1082  20   0 352912 57360 do_sys Ssl  ?          0:00 /usr/li
0  1000    2300    2204  20   0 535920  9568 do_sys Sl   ?          0:00 /usr/li
0  1000    2471       1  20   0 595536 79472 do_sys Sl   ?          0:03 tilix
0  1000    2486    2471  20   0   8992  5776 do_wai Ss   pts/0      0:00 /bin/ba
4     0    3613       1  20   0 320832 11104 -      Ssl  ?          0:01 /usr/li
4     0    4397       1  20   0  23312  9824 -      Ss   ?          0:00 /usr/sb
4     7    4398    4397  20   0  16688  6656 -      S    ?          0:00 /usr/li
4     0    4399       1  20   0 200560 22432 -      Ssl  ?          0:00 /usr/sb
4     7    4406    4397  20   0  16688  6688 -      S    ?          0:00 /usr/li
1     0    4802       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    4835       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    4871       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    5034       2  20   0      0     0 -      D    ?          0:00 [kworke
1     0    5036       2  20   0      0     0 -      D    ?          0:00 [kworke
1     0    5048       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    5051       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    5052       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    5061       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    5065       2  20   0      0     0 -      I    ?          0:00 [kworke
0  1000    5079    2471  20   0   8992  5744 do_sel Ss+  pts/5      0:00 /bin/ba
1     0    5459       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    5521       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    5546       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    6220       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    6309       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    6522       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    6524       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0    6528       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    6569       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    6570       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0    6573       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0    6574       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    6575       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    6577       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    6578       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0    6589       2  20   0      0     0 -      I    ?          0:00 [kworke
4  1000    6592       1  20   0 34516496 293520 do_get Dl ?         0:09 /usr/li
0  1000    6612       1  20   0 33569216 4704 do_epo Sl  ?          0:00 /usr/li
0  1000    6614       1  20   0 33560896 3728 do_epo S   ?          0:00 /usr/li
0  1000    6618    6592  20   0 33919328 65888 do_sys S  ?          0:00 /usr/li
4  1000    6619    6592  20   0 33919472 66160 do_wai S  ?          0:00 /usr/li
5  1000    6621    6619  20   0 33919472 21408 do_sys S  ?          0:00 /usr/li
0  1000    6657    6592  20   0 33995648 97168 futex_ Sl ?          0:01 /usr/li
1  1000    6658    6621  20   0 33978768 49232 futex_ Sl ?          0:00 /usr/li
1  1000    6684    6621  20   0 1283359152 240992 futex_ Sl ?       0:01 /usr/li
1  1000    6735    6618  20   0 34016128 87808 futex_ Sl ?          0:09 /usr/li
1  1000    6738    6735  20   0 33936416 21408 skb_wa S  ?          0:00 /usr/li
1     0    6745       2  20   0      0     0 -      D    ?          0:00 [kworke
1     0    6746       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    6747       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0    6749       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    6750       2  20   0      0     0 -      I    ?          0:00 [kworke
1  1000    6758    6621  20   0 1283248496 124064 futex_ Sl ?       0:00 /usr/li
1     0    6823       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1  1000    6826    6621  20   0 1283281328 218176 futex_ Sl ?       0:09 /usr/li
1     0    6835       2   0 -20      0     0 -      I<   ?          0:00 [kworke
0  1000    6927    6592  20   0 34018944 71872 futex_ Sl ?          0:00 /usr/li
1     0    7072       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    7092       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    7102       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1     0    7167       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    7168       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    7269       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    7552       2  20   0      0     0 -      I    ?          0:00 [kworke
1     0    7589       2   0 -20      0     0 -      I<   ?          0:00 [kworke
1  1000    7590    6621  20   0 1283248176 120672 futex_ Sl ?       0:00 /usr/li
1  1000    7611    6621  20   0 1283239008 74304 futex_ Sl ?        0:00 /usr/li
1     0    7648       2  20   0      0     0 -      I    ?          0:00 [kworke
4  1000    7776    2486  20   0   9488  3920 -      R+   pts/0      0:00 ps alx
pi@raspberrypi:~ $

[Carl Marbach]

pi@raspberrypi:~ $ sudo pdpcontrol start 0
Starting PiDP-10 with boot option 0
screen -dmS pidp10 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
0
pi@raspberrypi:~ $

[Ric Werme]

A few things:

1) I forgot to ask that you enlarge the terminal window horizontally to capture more of the ps output.

2) My previous post shows ps output being "piped" into grep to limit some of the output we're not interested in, see my sample below.

3) Your posts showing multiple uses of "pdpcontrol" should have produced an error.

However, it looks as though simh/pidp10 isn't starting, or if it does, exits quickly.   Both your ps output and your multiple uses of pdpcontrol suggests it's not running.

On my system (N.B.: I've added blank line before new commands for readability):

werme@raspberrypi:~$ pdpcontrol start 0
Starting PiDP-10 with boot option 0
screen -dmS pidp10 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
0

werme@raspberrypi:~$ pdpcontrol start 0
PiDP-10 is already running, not starting again.

werme@raspberrypi:~$ ps alx | grep pidp10
1  1000    9919       1  20   0   7048  2272 do_sel Ss   ?          0:00 SCREEN -dmS pidp10 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
4  1000    9920    9919  30  10 382044 65732 -      SNsl+ pts/2     0:06 ./pidp10 /opt/pidp10/systems/hills-blinky/boot.pi
0  1000    9949    3863  20   0   6092  2020 pipe_r S+   pts/1      0:00 grep pidp10

werme@raspberrypi:~$ pdpcontrol stop
Stopping PiDP-10 pidp
spawn screen -x pidp10

1

werme@raspberrypi:~$

My guess is that pidp10 isn't starting but that pdpcontrol isn't noticing that.  It may involve the "screen" command.  That command is used to run pidp10 from another terminal.  It may be that screen runs okay, but pidp10 fails and that news doesn't make it back.  I've never used screen much.

I'll describe what to do in my next post.

[Ric Werme]

You asked a while back "How can I just run Blinky manually?"

That's exactly what we'll do here with two commands.  The first switches to the directory where all your PiDP-10 software should be.  (Saves some typing or long command lines.)  The second command runs simh, which should read in the Blinky command file.  That should produce a whole bunch of output that we normally never see and start execution.  If either command fails, that will be interesting, if Blinky runs or if you don't get a new shell prompt, then see my mention of Ctrl-E and the quit command below.

werme@raspberrypi:~$ cd /opt/pidp10
werme@raspberrypi:/opt/pidp10$ bin/pidp10 systems/hills-blinky/boot.pi
%SIM-INFO: Created blink_thread
%SIM-INFO: PiDP-10 FP on

KA-10 simulator Open SIMH V4.1-0 Current

=====================================================================

/opt/pidp10/systems/hills-blinky/boot.pi-7> set cons telnet=1025
%SIM-INFO: Listening on port 1025

use 'telnet localhost 1025'
or 'pdp con'  or 'pdp telcon' for PDP-10 console

=====================================================================

Initializing SIMH for BLINKY-10 ...
Loading BLINKY10 for the PDP-10 ...

Console DATA SWITCH definitions (others do nothing) ...

       00  (h)  HALT before starting the next TICK (learning by doing)
       01  (f)  Select FAST CPU mode (slows the TICKs by 32x)
       03  (i)  Turn off INDIRECT mode in the TICK loop instruction
       04  (x)  Turn off INDEXED AC in the TICK loop instruction
       08  (e)  Set PCNT equal to ADDR (ignore the PCNT table)
       09  (q)  Set DATA equal to ADDR (ignore the DATA table)
       10  (s)  Swap the DATA RHS with LHS
       11  (r)  Set the DATA RHS to the same as LHS
       12  (p)  Complement PCNT lamps
       13  (a)  Complement ADDR lamps
       14  (d)  Complement DATA lamps
    15-17  (O)  Pattern offset (0-7)
    18-20  (I)  INST speed relative to T
    21-23  (P)  PCNT speed relative to T
    24-26  (A)  ADDR speed relative to T
    27-29  (D)  DATA speed relative to T
    30-35* (T)  TICK speed (basic time unit ~1/63s)

    *  At least one 'T' switch must be ON to enable the above functions
       Set switch 35 for comfortable speed, then play with other switches

Running BLINKY-10 for the PDP-10 ...
/opt/pidp10/systems/hills-blinky/boot.pi-615> cont
                                                  %SIM-INFO: Running with Buffered Console

At this point, Blinky should be running its light display and there should not be a prompt on your terminal.  Let it run, play with the switches.  Ctrl-C is generally use to stop programs, but not in this case.  Instead, type Ctrl/E and you should see the lights freeze and something like:

Simulation stopped, PC: 040007 (SOJGE 1,@40010(10))
sim> 

This is the simh prompt. the simplest thing to do is use "quit" to exit and get back to the shell prompt.  "continue" should resume execution (and need Ctrl-E to get back to the prompt).  "go 100" should restart the program, I think. "help" will list other commands but not tell you how to use them.  Commands can be abbreviated, to get back to where you were and change back to your home directory:

Simulation stopped, PC: 010037 (SOJG 4,@10040(2))
sim> q
Goodbye
werme@raspberrypi:/opt/pidp10$ cd ~  [cd without the tilde works too, as does staying in /opt/pidp10.]
werme@raspberrypi:~$ 

[Carl Marbach]

What am I doing wwrong?

pi@raspberrypi:/opt/pidp10/systems/hills-blinky $ ./boot.pi
./boot.pi: line 1: cd: $'/opt/pidp10/systems/hills-blinky\r': No such file or directory
./boot.pi: line 2: $'\r': command not found
./boot.pi: line 3: $'echo\r': command not found
=====================================================================
./boot.pi: line 5: $'echo\r': command not found
./boot.pi: line 6: SET: command not found
./boot.pi: line 8: $'echo\r': command not found

use telnet localhost 1025
or pdp con or pdp telcon for PDP-10 console

./boot.pi: line 11: $'echo\r': command not found
=====================================================================
./boot.pi: line 13: $'echo\r': command not found
./boot.pi: line 14: syntax error near unexpected token `;'
'/boot.pi: line 14: `; TITLE BLINKY-10 V2.0
pi@raspberrypi:/opt/pidp10/systems/hills-blinky $

[Tim Radde]

Looks like you copied a file from Windows to a Linux box (Rasp PI).  Windows uses \r\n to end lines.  Linux just uses \n.  So these files are confusing Linux.

There are tools to convert.  I thiink they are called dos2unix or unix2dos, depending on which way you are going.  Or you could just edit the small file on

Linux and remove the \r's.  I think they show up as Ctrl-M's at the end of each line.  Because of this it can't process the file correctly.

To view this discussion visit https://groups.google.com/d/msgid/pidp-10/9254b20a-b400-4607-babd-db1cc31599acn%40googlegroups.com.

[Ric Werme]

This line:

pi@raspberrypi:/opt/pidp10/systems/hills-blinky $ ./boot.pi

tells me that you cd'd to directory /opt/pidp10/systems/hills-blinky instead of opt/pidp10.  Then you executed boot.pi as a shell script.  However, it s a command file/script for simh.  It also has carriage returns in it which apparently simh can handle, and shells cannot:

werme@raspberrypi:/opt/pidp10$ head systems/hills-blinky/boot.pi | od -c
0000000   c   d       /   o   p   t   /   p   i   d   p   1   0   /   s
0000020   y   s   t   e   m   s   /   h   i   l   l   s   -   b   l   i
0000040   n   k   y  \r  \n  \r  \n   e   c   h   o  \r  \n   e   c   h
0000060   o       =   =   =   =   =   =   =   =   =   =   =   =   =   =

The head command copies the first  few lines of a file to stdout, which is piped to od (octal dump) which I've told to dump things out character by character.  '\r' is C (et al) syntax for the CR/carriage-return character, '\n' is Unix-speack for newline. or LF/line-feed on other systems.  Teletypes, PDP-10s and Windows use CRLFs to go to the next line.  Bell Labs decided one character was plenty, an act that still has repercussions today.

At any rate, boot.pi is a script interpreted by simh, in the guise as the pidp10 command.

My two commands, with lots of extra spaces and bold text for what to enter:

werme@raspberrypi:~$    cd     /opt/pidp10
werme@raspberrypi:/opt/pidp10$     bin/pidp10     systems/hills-blinky/boot.pi

The second line runs the program pidp10 that's in the bin directory.  That program takes commands from the file whose name follows.

More info that you don't need but should find interesting:

werme@raspberrypi:/opt/pidp10$     ls    -l     bin/p*   [Look at some of the bin directory]
-rwxr-xr-x 1 werme werme 1762552 Aug  3 17:30 bin/pdp10-ka
-rwxr-xr-x 1 werme werme 1492432 Aug  3 17:30 bin/pdp10-ki
-rwxr-xr-x 1 werme werme 1558488 Aug  3 17:30 bin/pdp10-kl
-rwxr-xr-x 1 werme werme 1385480 Aug  3 17:30 bin/pdp10-ks
-rwxr-xr-x 1 werme werme 1243048 Aug  3 17:30 bin/pdp6
-rwxr-xr-x 1 werme werme     969 Aug  3 17:30 bin/pdp.bak
-rwxr-xr-x 1 werme werme    3340 Aug  3 17:30 bin/pdpcontrol.sh
-rwxr-xr-x 1 werme werme    1886 Aug  3 17:30 bin/pdp.sh
-rwsr-sr-x 1 werme werme 1762552 Aug  3 17:30 bin/pidp10   [This is the simh program you want to run]
-rwxr-xr-x 1 werme werme 3414576 Aug  3 17:30 bin/pidp10.panama
-rwxr-xr-x 1 werme werme  213688 Aug  3 17:30 bin/pidp10-test
-rw-r--r-- 1 werme werme      24 Oct 29 21:22 bin/pitime.simh  [A personal file - it has commands to pass the current time to my lights program]
-rw-r--r-- 1 werme werme   39122 Oct 31 23:49 bin/ps.log  [ps output saved while being mystified about when autostart.sh does things during startup]

The best way to see the whole boot.pi file is to use the "less" command instead of "head".  It will need you to type the space bar to page through the file. and thebn type 'q' to exit the command when you get to the bottom.  (Or want to stop early.)

werme@raspberrypi:/opt/pidp10$    head    systems/hills-blinky/boot.pi
cd /opt/pidp10/systems/hills-blinky

echo
echo =====================================================================
echo
SET CONSOLE TELNET=BUFFERED=144
set cons telnet=1025
echo
echo use 'telnet localhost 1025'
echo or 'pdp con'  or 'pdp telcon' for PDP-10 console

[Ric Werme]

timr...@gmail.com wrote:

to cmar...@marbachs.com, PiDP-10

Looks like you copied a file from Windows to a Linux box (Rasp PI).

No, he didn't.  The file in question is the Blinky boot.pi file that is part of the PiDP-10 distribution.  simh can handle it just fine, as simh is designed to run on non-Unix platforms too.  Carl fed the file to bash.

Bash cannot handle carriage returns, nor will it understand most of the boot.pi file.

[terri-...@glaver.org]

On Monday, November 3, 2025 at 4:35:50 PM UTC-5 r...@wermenh.com wrote:

However, it looks as though simh/pidp10 isn't starting, or if it does, exits quickly.   Both your ps output and your multiple uses of pdpcontrol suggests it's not running.

Yes. The "0" is reporting that screen couldn't find any sessions. It isn't very informative. On the PiDP-11, I edited pdp.sh as follows. Note that this is for the PiDP-11, not the -10.

procs=`screen -ls pidp11 | egrep '[0-9]+\.pidp11' | wc -l`
if [ $procs -eq 0 ]; then
    echo No PDP-11 emulator detected as running - check with pidp11control.
    exit 1
fi

if [ $procs -gt 1 ]; then
    echo More than one screen session found; results may be unpredictable.
fi

if [ $procs -ne 0 ]; then
    screen -d -r
fi
 

[Carl Marbach]

now I get this error:

pi@raspberrypi:/opt/pidp10/systems/hills-blinky $ cd /opt/pidp10
pi@raspberrypi:/opt/pidp10 $ bin/pidp10 systenms/hills-blinky/boot.pi
bin/pidp10: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory
pi@raspberrypi:/opt/pidp10 $

[Ric Werme]

Hmm.  That may is covered in message https://groups.google.com/g/pidp-10/c/hMhTa5W4qWk/m/vewD_nyBAAAJ

However, It says to rebuild things.  Hmm,  hang on.  You've done the first step, I think.  I've added extra space characters for clarity.

- run install.sh to clone Cornwell's PIDP-10 repository,
- cd     opt/pidp10/src/pidp10/src/pdp10
- make     PIDP10=1
- cp     BIN/p*     /opt/pidp10/bin

I don't recall running into this problem.  However, my notes are a bit confusing, but I do recall:

Redid install with typing 'y'.  [IIRC, as opposed to typing all three letters Yes.]

Much better.

I forget if that rebuilt the program files - the "make PIDP10=1" definitely does.

That command reads instructions from a file called makefile, and part of it says:

  # Find PCRE RegEx library.
  ifneq (,$(call find_include,pcre))
    ifneq (,$(call find_lib,pcre))
      OS_CCDEFS += -DHAVE_PCRE_H
      OS_LDFLAGS += -lpcre
      $(info using libpcre: $(call find_lib,pcre) $(call find_include,pcre))
      ifeq ($(LD_SEARCH_NEEDED),$(call need_search,pcre))
        OS_LDFLAGS += -L$(dir $(call find_lib,pcre))
      endif
    endif
  endif

I think that will look around, decide that you (and I) don't have the PCRE RegEx library, which ought to be some string processing library.  It then avoids loading the library.  It may be that your pidp10 program was built expecting to use that library.

What to do, what to do?

I guess there are two fairly easy choices.

1) Rebuild stuff.

I assume that means redoing the installation, and ask that it install source code.

The command "cd opt/pidp10/src/pidp10/src/pdp10" refers to a pidp10 directory in two places and a pdp10 directory in the there.  Yes, it's confusing.

The make command will do things, I think four times, once for each variation of PDP-10 hardware.

The cp (copy) command will copy all the new executable files to where you run them from.

When I was mucking inside simh, I see a note telling me to just run the new code without the copy, e.g.:

BIN/pdp10-ka /opt/pidp10/systems/hills-blinky/boot.pi

2) I could send you my code.

It's built on a Pi 4 system, I don't know if that's a problem.

I don't have a git repository of my own, but I'm thinking I may have to make one to share my lights hack.

That's not a big deal, we can try just sending you just a pdp10-ka file that you can try without stomping on other stuff.  It will have my changes to fix the memory display on the console, but that's not a factor with Blinky.

Let's see what other people suggest.

[terri-...@glaver.org]

On Monday, November 3, 2025 at 10:27:00 PM UTC-5 r...@wermenh.com wrote:

Let's see what other people suggest.

The install script handles this as long as you answer "Y" to the "Install required dependencies for running the PiDP-10?" question.

Rather than giving the manual steps to install the missing library/libraries, I'd suggest re-running install.sh as this suggests there may be other problems with the install. The Installation script says:

Too Long, Didn't Read?
Just say Yes to everything except say No to 'install source code'
and to 'install source code dependencies'.

[Carl Marbach]

I've done this twice. Still no luck.

--
You received this message because you are subscribed to the Google Groups "PiDP-10" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pidp-10+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pidp-10/e93d3df6-45d0-4f3d-9c25-140f94dd7487n%40googlegroups.com.

[Ric Werme]

Let's see if libpcre3 is installed.

The install.sh portion that loads dependencies is:

read -p "Install required dependencies for running the PiDP-10? " yn
case $yn in
    [Yy]* )
        # update first...
        sudo apt-get update
        # for simh:
        sudo apt install -y libpcre3
        sudo apt install -y libsdl2-image-dev
        sudo apt install -y libsdl2-net-dev
        sudo apt install -y libvdeplug2
        sudo apt install -y libpcap-dev
        #the Pi does not come with telnet installed, so --
        sudo apt-get install -y telnet
        sudo apt-get install -y telnetd
        # for pdpcontrol:
        sudo apt-get -y install expect
        # Install screen
        sudo apt-get install -y screen
        # Install Tilix, used for pdp view
        sudo apt -y install tilix
        sudo apt -y install dconf-editor dconf-cli
        dconf load /com/gexperts/Tilix/ </opt/pidp10/install/pidp10tilix.conf
        ;;
    [Nn]* ) ;;
        * ) echo "Please answer yes or no.";;
esac

So it should have installed libpcre3.  It's not obvious to see what comes in that package, but "apt list libpcre3" should tell you if it's installed:

werme@raspberrypi:/opt/pidp10/install$    apt    list      libpcre3
Listing... Done
libpcre3/oldstable,now 2:8.39-15 arm64 [installed]
libpcre3/oldstable 2:8.39-15 armhf

Apparently this is lists the contents of that package - do you have this file and these contents?  ("cat", from concatentate, copies files to stdout, i.e. it prints the file to the terminal.)

werme@raspberrypi:~$     cat     /var/lib/dpkg/info/libpcre3:arm64.list
/.
/lib
/lib/aarch64-linux-gnu
/lib/aarch64-linux-gnu/libpcre.so.3.13.3
/usr
/usr/bin
/usr/lib
/usr/lib/aarch64-linux-gnu
/usr/lib/aarch64-linux-gnu/libpcreposix.so.3.13.3
/usr/sbin
/usr/share
/usr/share/doc
/usr/share/doc/libpcre3
/usr/share/doc/libpcre3/AUTHORS
/usr/share/doc/libpcre3/NEWS.gz
/usr/share/doc/libpcre3/README.Debian
/usr/share/doc/libpcre3/README.gz
/usr/share/doc/libpcre3/changelog.Debian.gz
/usr/share/doc/libpcre3/changelog.gz
/usr/share/doc/libpcre3/copyright
/usr/share/man
/usr/share/man/man3
/usr/share/man/man3/pcrepattern.3.gz
/lib/aarch64-linux-gnu/libpcre.so.3
/usr/lib/aarch64-linux-gnu/libpcreposix.so.3

It's not entirely clear to me where an executable finds shared libraries, but presumably it's trying to read through this symbolic link:

werme@raspberrypi:/opt/pidp10/install$     ls   -l   /lib/aarch64-linux-gnu/libpcre.so.3
lrwxrwxrwx 1 root root 17 Dec 22  2022 /lib/aarch64-linux-gnu/libpcre.so.3 -> libpcre.so.3.13.3
werme@raspberrypi:/opt/pidp10/install$     ls   -l   /lib/aarch64-linux-gnu/libpcre.so.3.13.3
-rw-r--r-- 1 root root 460680 Dec 22  2022 /lib/aarch64-linux-gnu/libpcre.so.3.13.3

Do those commands work?

If not, we'd probably want to see the output from install.sh when it installs dependencies, and maybe what happens if you do "sudo   apt   install   -y   libpcre3" manually.

[terri-...@glaver.org]

On Tuesday, November 4, 2025 at 5:43:24 PM UTC-5 r...@wermenh.com wrote:

If not, we'd probably want to see the output from install.sh when it installs dependencies, and maybe what happens if you do "sudo   apt   install   -y   libpcre3" manually.

Something seems to be seriously wonky on the user's system, either from a previous attempt

to install the PiDP-10 software or in the Raspberry Pi OS itself.

Let's start with:

 cat /etc/os-release

 uname -a

Next, let's get a log of the entire installation process (proceed as if from a clean install, answer-

ing "Y" to all questions except  'install source code' and 'install source code dependencies') :

 script

 /opt/pidp10/install/install.sh

 exit

The above will produce a file called 'typescript' containing the entire contents of the in-

stall. The typescript file should be provided as an attached file and not posted in-line, 

as otherwise we'll see various line-wrap and other artifacts which will make it harder to dig

through.

[Carl Marbach]

pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.1
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

[Carl Marbach]

pi@raspberrypi:/ $ uname -a
Linux raspberrypi 6.12.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 GNU/Linux
pi@raspberrypi:/ $
pi@raspberrypi:/ $ uname -a
Linux raspberrypi 6.12.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 GNU/Linux
pi@raspberrypi:/ $ 

[Carl Marbach]

I suspect this is the problem:

   Release file created at: Wed, 05 Nov 2025 06:32:22 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.
E: Unable to parse package file /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_trixie_InRelease (1)
E: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
Error: Unable to parse package file /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_trixie_InRelease (1)
Error: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
Error: Unable to parse package file /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_trixie_InRelease (1)
Error: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
Error: Unable to parse package file /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_trixie_InRelease (1)
Error: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
Error: Unable to parse package file /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_trixie_InRelease (1)
Error: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
Error: Unable to parse package file /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_trixie_InRelease (1)
Error: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
E: Unable to parse package file /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_trixie_InRelease (1)
E: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
E: Unable to parse package file /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_trixie_InRelease (1)
E: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
E: Unable to parse package file /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_trixie_InRelease (1)
E: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
E: Unable to parse package file /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_trixie_InRelease (1)
E: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
Error: Unable to parse package file /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_trixie_InRelease (1)
Error: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
Error: Unable to parse package file /var/lib/apt/lists/archive.raspberrypi.com_debian_dists_trixie_InRelease (1)
Error: The package lists or status file could not be parsed or opened.

Download manual to /opt/pidp10/bin/manual.docx (MS Word format)? no

Download and install ITS disk images? yes
-----------------------

[Ric Werme]

I'm no Raspberry Pi expert, but let me congratulate you for apparently scouting out new lands.  (The scouts are the first ones to get shot at, I guess in the computer era, the first ones to hit brick walls and or make new pit falls.)  My previous Pi experience is with a "Raspberry Shake and Boom" seismometer that is such an amazing device that I've let it be instead using it as a toy that would be the avenue to learn about Pis.

I'll just note two things here but offer no suggestions.

1) https://obsolescence.dev/pidp10-sw/PiDP-10_Manual.pdf starts out with:

Using the PiDP-10
Installing
Prepare a regular Raspberry Pi SD card using the Raspberry Pi Imager program. Make sure you
pick the 64 bit version of the OS. At the time of writing, the latest OS version was ‘Bookworm’;
older versions of the OS will not work. Boot up the Pi, and get Wifi going.

2) On my system:

$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm

....

$ uname -a
Linux raspberrypi 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1~bookworm (2025-09-16) aarch64 GNU/Linux

It may well be that you have discovered that _newer_ versions of the OS will not work, though your later comments suggests there are other pits to explore.

If you need a break, check out https://wermenh.com/rsb/ - it's about my Raspberry Shake and Boom recording all sorts of neat stuff.

[terri-...@glaver.org]

On Wednesday, November 5, 2025 at 5:28:37 AM UTC-5 cmar...@marbachs.com wrote:

pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"

This could very well be the cause of your issues. The PiDP software was

developed and tested under Bookworm (Debian 12) and you're using

Trixie (Debian 13).

Trixie was just released last month and has a number of open bugs which

may affect you. In theory, software built for an older operating system vers-

ion should "just work", but on the Raspberry Pi there are generally breaking

changes which require the PiDP package to be modified each time there

is a new OS major version change.

On the PiDP-11 side, I have added experimental support for Trixie, but only

one user was brave enough to try it out (they didn't report any problems). I

am not involved in the PiDP-10 stuff except as a regular user.

I suggest you start over completely by  downloading "Raspberry Pi OS 

(Legacy) Full" using the Raspberry Pi Imager, write it to a SD card, then

proceed with a re-install of the PiDP-10 software.

[Darryll Truchan]

libpcre3 is gone under trixie.  

follow the instructions in /opt/pidp10/src/compiling-pdp10-readme.txt

• run install.sh to clone Cornwell's PIDP-10 repository,

• cd opt/pidp10/src/pidp10/src/pdp10
• make PIDP10=1
• cp BIN/p* /opt/pidp10/bin

this got it working for me

[Carl Marbach]

I went back to bootworm and now Github is asking for a username and password??

What do I do now?

[terri-...@glaver.org]

On Wednesday, November 5, 2025 at 9:12:54 PM UTC-5 cmar...@marbachs.com wrote:

I went back to bootworm and now Github is asking for a username and password??

What do I do now?

I just checked and the "git clone" does not ask for either.

What happens if you type:

sudo echo Hi

Does the system say "Hi" or do you get prompted for a password? If you get a password

prompt, there's something wrong with your Raspberry Pi OS install - perhaps you used a

username other than the recommended 'pi'.

[Carl Marbach]

Ran it again and it did not ask.

I can't find any errors.

PDPCONTROL start 0

and.....LIGHTS!!!!!

It is working.

Thank you all!!!

Carl

[Ric Werme]

> and.....LIGHTS!!!!!

Yay!

This experience probably warrants a "Trixie is broken, use Bookworm" post with details and cut 'n paste instructions for installing "Raspberry Pi OS  (Legacy) Full".  (Hey, I can't remember creating my Pi image....)

I won't hazard a guess as to how long it will take for us to support Trixie, so we show steer people away from it for now.