DietPI 10.2 - Amiberry broken?

Troubleshooting
1

Morning,

After doing a dietpi-update amiberry seems to have broken. During boot it doesn’t auto start and if I do a systemctl start amiberry it starts to load in a bad display and crashes. If I also press F12, it crashes.

Any suggestions?

As for hardware, I’m using a GMKTec NucBox G3

2

After some more troubleshooting. It appears F12 open if I load Amiberry from xorg.

I had to fix some settings under my AmigaOS with display to get that portion working.

So as of now, it will load on boot like it should, but as soon as I press F12 it crashes. SDL issues?

3

Similar issues on 10.2 with Amiberry. Can start emulator and reset, Pressing F12 sometimes crashes Amiberry GUI. Hitting ‘Restart’ crashes it every time, end up at a blue/grey window + linux cursor. F12 swaps to the emulator running and back to the crashed window manager. Amiberry-Lite still works.

Raspberry Pi 4b

4

You are using our Amiberry builds, right? Because they start via KMS/DRM only. Can you verify in Amiberry GUI Info page that it is started via KMSDRM SDL backend? That way, it should not make a difference whether it is started from Xorg or console.

Also, how did you start it? The “correct” way to use the prepared directory and stuff is

systemctl start amiberry

Since that systemd unit is an entirely independent environment, it should make even less a difference where this is done. However, if you just run amiberry command, then it will run as current user with a fresh config etc. If that is what makes the difference, then the config below /mnt/dietpi_userdata/amiberry is the culprit, probably due to some missing migration step with Amiberry v8.

But that said, I did face crashes as well when e.g. starting a ROM again after “Restart”, and in some other situations, or an empty grey/greenish screen when hitting F12. But that was with v8.0.x, while we are at v8.1.4 in the meantime.

Amiberry v8 was a huge update, which quite a bunch of bugs (in Amiberry as well as in SDL3), from which we fixed some, and subsequent Amiberry releases fixed a bunch more. Please test with v8.1.4 again. If it still fails, please report at Issues · BlitterStudio/amiberry · GitHub. Ping me, so I am informed if there is anything we can fix/patch/workaround our end.