Replies: 1 comment 4 replies
|
You might want to test with Wayland and see if that helps. The log indicates that x11 was used, but Wayland is the new default on RPI-OS. This is an old-standing SDL issue and their conservative decision to prioritize x11 even in Wayland, but you can override it at least to test what happens (though I'd recommend you keep wayland and get the better performance anyway). The wiki has an entry for this exactly: https://github.com/BlitterStudio/amiberry/wiki/FAQ#q-why-am-i-having-performance-andor-screen-issues-when-using-wayland |
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I just posted this to the English Amiga Board, then found these discussions on GitHub, so I'm posting here as well...
Yesterday, I decided to pull out my old Raspberry Pi out of storage and do some tinkering. The first think I did after imaging my SD card and getting all the updates was to install Amiberry. Unfortunately, I'm running into some issues with RTG causing crashes.
This is a Raspberry Pi 4b. The SD card has a fresh install of Raspberry Pi OS Full, 64 bit - Debian 13.6 "Trixie". The system has all it's updates applied.
Once all the system updates were installed,I installed Amiberry v8.3.0 using APT. I've set up an A1200 system with OS 3.2.2.1 and OS3.2.2 ROMs.The system seems to be working fine, with the exception of RTG.
I installed Picasso96 without any issues. When I open ScreenMode I can see all the UAE display modes. I can choose any of the UAE modes and hit Test. It will show the test display. As soon as I click, or press a key, or let the test time out, Amiberry crashes. There are several "Leaked thread" messages in the CLI, followed by "terminate called without an active exception".
It doesn't matter whether I start Amiberry from a terminal window on my Desktop, or if I boot the pi directly to the CLI and start Amiberry there.
It's probably something I'm doing, but I'm posting just in case others are seeing the same issue.
Does anyone have any troubleshooting suggestions?
Amiberry.log
Steves A1200.uae.txt
All reactions