error running z80pack on Raspberry Pi 4

[mmaseda12]

I downloaded the latest version and built on the latest version of RaspberryPi 64 bit OS. When I go to run I get the following error:

E (953) IO: can't exec cpmrecv process, compile/install the tools dude
E (8370) IO: can't open pipe auxout

I did install the tools. Any ideas what I might be doing wrong?

Regards,
Manuel

[udo-munk]

This is because the directory where you installed the tools is not included in $PATH.
What I usually do is create a directory bin in my home and then extend the path in the shell's rc file, like this:
export PATH=${HOME}/bin:$PATH

[mmaseda12]

Thanks !!ManuelOn Jun 5, 2024, at 10:49 AM, Udo Munk ***@***.***> wrote: This is because the directory where you installed the tools is not included in $PATH. What I usually do is create a directory bin in my home and then extend the path in the shell's rc file, like this: export PATH=${HOME}/bin:$PATH —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[udo-munk]

You are welcome. How is it working on Pi 4? I still need to get one sometime, but to busy with other things.

[mmaseda12]

I just started using but the performance seems to be much better than the 3B I was using.On Jun 5, 2024, at 11:02 AM, Udo Munk ***@***.***> wrote: You are welcome. How is it working on Pi 4? I still need to get one sometime, but to busy with other things. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[udo-munk]

From what I read I would expect that it performs better. How about the FPS for the front panel, does it work with the default 60 or do you have to reduce it?

[mmaseda12]

I haven’t built it for Imsai with front panel yet.  Can you point me to the build instructions.  Sent from my iPhoneOn Jun 5, 2024, at 11:34 AM, Udo Munk ***@***.***> wrote: From what I read I would expect that it performs better. How about the FPS for the front panel, does it work with the default 60 or do you have to reduce it? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[udo-munk]

Sure, updated documentation is here: https://github.com/udo-munk/z80pack/tree/master/doc

Start with reading README-frontpanel, then maybe README-wsl, that is an Ubuntu Linux running under WSL on Windows. Don't know what Linux brand one uses on the Pi 4, might need other package names.

[mmaseda12]

Thanks,Will build and test in the morning.  Pi uses Debian bookworm.ManuelSent from my iPhoneOn Jun 5, 2024, at 12:33 PM, Udo Munk ***@***.***> wrote: Sure, updated documentation is here: https://github.com/udo-munk/z80pack/tree/master/doc Start with reading README-frontpanel, then maybe README-wsl, that is an Ubuntu Linux running under WSL on Windows. Don't know what Linux brand one uses on the Pi 4, might need other package names. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[udo-munk]

Good luck. Don't know bookworm, but if you run into problems just ask, will see if we can help.

[mmaseda12]

I have everything built and installed and can run Imsai with front panel in 2D mode.  When I try and config for 3D I set a segmentation fault when I click a button on the front panel.  I also tried on a Pi 4 running Ubuntu with the same issue.  Anything I should try?ManuelOn Jun 5, 2024, at 12:39 PM, Udo Munk ***@***.***> wrote: Good luck. Don't know bookworm, but if you run into problems just ask, will see if we can help. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[udo-munk]

Excellent. This likely is caused by bugs in Mesa OpenGL and/or the drivers for the GPU. Not much one can do about this other, than updating all the graphics libs and drivers to the latest version. Whenever I tried to figure a problem on Ubuntu with gdb the segmentation faults happened deep inside some X11 graphics lib. Went away after an update, came again with next update ...

[mmaseda12]

I’ll try a few other Linux machines I have around here.On Jun 6, 2024, at 10:17 AM, Udo Munk ***@***.***> wrote: Excellent. This likely is caused by bugs in Mesa OpenGL and/or the drivers for the GPU. Not much one can do about this other, than updating all the graphics libs and drivers to the latest version. Whenever I tried to figure a problem on Ubuntu with gdb the segmentation faults happened deep inside some X11 graphics lib. Went away after an update, came again with next update ... —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[mmaseda12]

I tried installing on several versions of Debian and Ubuntu 32 and 64 on both Pi 4 and Pi 5 and still get the segmentation fault in 3D mode.  I even tried on an Intel I7 pc running Mint and get the same error.  In all cases I loaded the most recent drivers and graphics libraries.  I installed on my Intel I7 iMac running Sonoma and it worked perfectly.  Any other suggestions?Regards,ManuelOn Jun 6, 2024, at 10:17 AM, Udo Munk ***@***.***> wrote: Excellent. This likely is caused by bugs in Mesa OpenGL and/or the drivers for the GPU. Not much one can do about this other, than updating all the graphics libs and drivers to the latest version. Whenever I tried to figure a problem on Ubuntu with gdb the segmentation faults happened deep inside some X11 graphics lib. Went away after an update, came again with next update ... —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[udo-munk]

I have an older MacBookPro with Intel i5 and a new one with Apple M3, no such problems of course. Currently it works in Windows + WSL with the latest Ubuntu bits, machine has AMD CPU with AMD GPU and current drivers. This is broken from time to time, but right now it works.

Hope you are familiar with gdb, what you can do to locate the problem is this:

Build imsaisim debug version with DEBUG=1 make build
Then rund 'gdb imsaisim' and do what causes the segfault.
When back at the gdb prompt enter command bt (backtrace) and post the output here.

[mmaseda12]

ThanksSent from my iPhoneOn Jun 7, 2024, at 11:33 AM, Udo Munk ***@***.***> wrote: I have an older MacBookPro with Intel i5 and a new one with Apple M3, no such problems of course. Currently it works in Windows + WSL with the latest Ubuntu bits, machine has AMD CPU with AMD GPU and current drivers. This is broken from time to time, but right now it works. Hope you are familiar with gdb, what you can do to locate the problem is this: Build imsaisim debug version with DEBUG=1 make build Then rund 'gdb imsaisim' and do what causes the segfault. When back at the gdb prompt enter command bt (backtrace) and post the output here. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[udo-munk]

One could try the current dev driver:

The driver code for both GPU models is available in the Mesa upstream repository. The codename for the VideoCore IV driver is VC4, and the codename for the VideoCore VI driver is V3D. There are no downstream repositories – all development happens directly upstream, which has a number of benefits for end users:

It is relatively easy for the more adventurous users to experiment with development builds of the driver.

[udo-munk]

I tried one more thing. I noticed that the OS I installed was the 32-bit version, but I got a Pi with 8 GB memory. For this one needs a 64-bit OS to take full advantage, and that should avoid several of the usual problems to access memory > 4 GB with the 32 bits. Machine is more performant with the 64-bit OS, but the problem with the GPU driver still is there, so we have to wait for a better GPU driver.

[mmaseda12]

I wasn’t able to get Arch installed but I did install Tumbleweed with Mesa 24.0.8 and I still get the segmentation fault in 3D mode.  Perhaps 24.1.1 fixes that.ManuelOn Jun 12, 2024, at 10:39 AM, sneakywumpus ***@***.***> wrote: It runs fine on my PC with Arch Linux and Mesa 24.1.1 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[RanchoHam]

I'm running RPI4's (Bullseye) with good performance with only 2D front panels. (BTW I don't really see the point of 3D, so 2D works for me.) I have been looking through 1.37 for months to find why I wasn't getting the web server to work. When I upgraded to 1.38, I noticed a message that the Web server builtin, but disabled which explains things. But how does one turn it on?

[sneakywumpus]

Use option -n to enable to web server. Port number is 8080, which can be changed in conf/system.conf (ns_port).

[udo-munk]

Well, the point of 3D is, that John who wrote the frontpanel library, is a sophisticated OpenGL programmer, and wanted to show off some 3D modelling. Even the frontpanel is reflective plexi glas and seems to show the environment. It is nice to look at, but for using the machines the 2D view is more comfortable of course, and all this is configurable for the end user.

In releases 1.36 & 1.37 the web server was not compiled in by default, it was a compile time option in sim.h of the machines, and one had to enable it there. With 1.38 the web server always is compiled into the machines, but by default it is disabled. Enable with running the machines with -n.

[RanchoHam]

Thanks @sneakywumpus and @udo-munk for the -n hint. I tried it in both the imsai and cromemco directories and it looks good.

But the LIB: only contains the disks in the ./disks directory not the ./disks/library directory. Further examination of the SYS: shows the DISKSDIR=(null). I have Dave's Cromemco Z-1; and it shows DISKSDIR=/sdcard/cromemco/disks, so I tried export DISKDIR=<full path to ./disks/library>, but that did not help. What am I doing wrong?

[udo-munk]

The used disk directories are compiled in and cannot be changed with environment variables. For the PC version you can define another path with disk images with the option -r . However, the web lib manager will only look in ./disks, so copy the disk images you wish to use into this directory.

[RanchoHam]

Thanks @udo-munk, I have imsai and cromemco sims working on a Windows WSL2/Ubuntu 22 installation (although it seg faults on exit) and on a Raspberry Pi 4/Raspberry Pi OS (Bullseye 64) with normal closure.

[udo-munk]

Here is how you can run the z80pack 3D models on the Raspberry Pi, by not using their broken graphics drivers, but using a working remote one. For example I am using Linux Ubuntu in WSL2 running on a machine with AMD hardware (RYZEN 7 with AMD RADEON). On the Windows system I am using MobaXTerm and in the setting make sure that X11 -> OpenGL acceleration is set to Hardware.
With this now ssh to your Raspberry Pi, make sure that X11 tunneling is configured for the session. On Pi command line enter:

export LIBGL_ALWAYS_INDIRECT=1

Now the frontpanel gets drawn by your PC GPU hardware with it's drivers.

[udo-munk]

Tested z80pack with SDL2 graphics as added by Thomas. Unlike the X11 version the 3D IMSAI model works OK. Performance is good and box looks same nice as the X11 version on larger workstations.

[mmaseda12]

Great, I’m out of town but I’ll try on Sunday when I get home.

[mmaseda12]

Did a clean install on a Pi4 with Ubuntu and 3D works perfectly.

[udo-munk]

Excellent. And also with sound, I have that enabled via the HDMI output to the monitor, which also has speakers builtin, this also works on the Pi systems.

[mmaseda12]

How do I enable sound? I already have Ubuntu configured to send sound over HDMI.

[udo-munk]

I use Raspberry Pi OS 64bit, this is Debian based and the GUI probably is different in the Ubuntu distribution. However, there should be a system setting, that allows to route audio to HDMI or the audio jack. I set it to HDMI, set audio volume to 50% and checked with YouTube if sound is working.

In the latest z80pack sources audio is enabled for the switches, but disabled for the cooling fan. The configuration for the sounds is in sim/conf/panel.conf.

[mmaseda12]

Must be a Ubuntu issue. Works fine on a Pi running PI OS 64. But doesn’t work on a Pi running Ubuntu 64 24.10. I have confirmed that that the sound is configured properly to work over HDMI. I can use YouTube and play WAV files.

[mmaseda12]

Problem solved. Ubuntu 24.10 uses Rhythmbox as the default media player. Pi OS uses VLC. I removed Rhythmbox on Ubuntu and replaced it with VLC and everything works now. Perhaps there is a problem between SDL2 and Rhythmbox.

[udo-munk]

Today I have some news for those using z80pack on Raspberry Pi computers :-)
Today I updated my system and the huge updates included low level graphics drivers and mesa libraries. So I just tried the IMSAI 3D X11 model with a fresh build and guess what, it now works. Looks like they finaly fixed these issues with the 3D graphics.

[mmaseda12]

Great, I’ll do a fresh install on a Pi 5 this weekend and check it out.

[mmaseda12]

Worked fine. Thanks !!

[udo-munk]

Excellent, glad it works on your machine too.