@MichaIng is this something you could help with?
Thanks for reporting. I actually just successfully tested in on RPi Zero W and faced the same when not raising the GPU memory split as suggested (but leaving it at 16 MiB). Did you raise it to the 76 MiB offered after the install?
Otherwise, after interrupting Amiberry (CTRL+C), can you check:
journalctl -u amiberry
And switch to TTY3 console via F3 key to see whether there are logs. We run Amiberry on TTY3 to not spam or mess with main console settings. Some older SDL version printed a respective character to the console for every key that was pressed while using Amiberry.
You can switch back to TTY1 via F1 key.
Ok, so this is odd. I had the GPU split set to 128Mb but I went back in and re-set it to 128Mb. It asked me to reboot and when it started back up, systemctl start amiberry worked as expected. Anyway, it’s working so thank you for the suggestion.
Okay great that it works now.