mirror of
https://github.com/gopher64/gopher64.git
synced 2026-04-24 22:45:59 +03:00
[GH-ISSUE #466] [Raspberry Pi] Gopher64 stuck with window not responding after opening up any game #48
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/gopher64#48
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ell1e on GitHub (Jul 4, 2025).
Original GitHub issue: https://github.com/gopher64/gopher64/issues/466
My apologies if this is an obvious user error of some sort. But for me Gopher64 will always be stuck with window not responding after I tried opening up any game:
I'm on a Raspberry Pi 5, Duckstation works flawlessly on this. Based on that, I expected Gopher64 to be usable as well, but something seems to be going wrong;
Affected hardware: Raspberry Pi 5 (ARM64)
Affected operating system: postmarketOS Edge based on Alpine Edge
Affected Gopher64 version: v1.0.18 installed via Flathub
@loganmc10 commented on GitHub (Jul 4, 2025):
I'll be honest, I've never tested gopher64 on a raspberry pi, or even on ARM for that matter.
I may get around one day to picking up a Pi and troubleshooting it, but for now I don't really have any advice, I'm not sure what the issue could be.
@ell1e commented on GitHub (Jul 4, 2025):
The GPU of the Raspberry Pi 5 is rather weak, so perhaps that could be a factor? I know it supports Vulkan, but probably not the latest modern extensions. KDE Plasma 6 runs perfectly fine with all the usual 3d effects though, so 3d acceleration definitely works.
@acidnine commented on GitHub (Aug 26, 2025):
I decided to test with my Pi 5, I was unable to launch it on the stock Raspberry Pi OS with Bookworm so I tested with Ubuntu 25.04 and the GUI appears to run fine but on launching a rom it appears to crash the same way. I'm not sure what else to do to get more detailed logging but am up to help out if I can.
Console output:
@fac3l3ss79 commented on GitHub (Sep 21, 2025):
I successfully compiled in a Raspberry pi 5 with Bookworm and I get a similar console output as above with gopher64 not launching properly.
@loganmc10 commented on GitHub (Sep 23, 2025):
Can someone try to run a debug build, or
cargo build --profile=release-with-debugand run it with gdb to see exactly where it crashed?@synthic commented on GitHub (Nov 15, 2025):
I ran a debug build on Trixie and this was the result:
Looks like it's getting stuck somewhere in the main function (line 78), hopefully this helps.
@loganmc10 commented on GitHub (Nov 15, 2025):
I think it is just the case that the video card doesn't support VK_EXT_external_memory_host
I know that it lists it as a warning in the logs, but in the readme for parallel-rdp it says:
I don't think it works without that extension.
@synthic commented on GitHub (Nov 15, 2025):
Maybe it's a bug in parallel-rdp, or possibly in the Raspberry Pi v3d driver implementation. When running
vulkaninfoit prints this:It looks like the extension is available so I guess it's just not being detected for some reason.
@synthic commented on GitHub (Nov 16, 2025):
Update: I was looking at the wrong device apparently. That list was for the
llvmpipedevice (software renderer). Unfortunately,V3Ddoes not currently support theVK_EXT_external_memory_hostextension.I tried to run gopher64 with
GRANITE_VULKAN_DEVICE_INDEX=1set and it actually works! However, the FPS is quite low as could be expected from a software renderer.Looks like there is an open issue regarding this here, so at least they are working on adding it:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/5222