or within .sheepshaver_prefs?SheepShaver --sdlrender software
Linux x86 64-bit builds for SheepShaver, Basilisk II
Moderators: Cat_7, Ronald P. Regensburg, ClockWise
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Have you tried setting sdlrender to "software", either via command line
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Hi,
sldrender software does indeed fix the crash. Another pref that should be set by default?
Best.
Cat_7
sldrender software does indeed fix the crash. Another pref that should be set by default?
Best.
Cat_7
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Still trying to find out why specifically Fedora crashes when SDL tries to render using opengl. Arch Linux with KDE desktop, Ubuntu Jammy and Debian Bullseye are fine.
Do you think a statically compiled SDL library would help?
Regards,
Korkman
Do you think a statically compiled SDL library would help?
Regards,
Korkman
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Hi,
That I wouldn't know.
EDIT: When I run gnome on Xorg SheepShaver does not crash without sdlrender setting.
EDIT2: More confusion: after a successful run with gnome/xorg SheepShaver now also runs on the cinnamon desktop.
Best,
Cat_7
That I wouldn't know.
EDIT: When I run gnome on Xorg SheepShaver does not crash without sdlrender setting.
EDIT2: More confusion: after a successful run with gnome/xorg SheepShaver now also runs on the cinnamon desktop.
Best,
Cat_7
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Double check the sdlrender option wasn't transferred to the prefs file
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Haha,
I did
the pref is not there.
Reading ROM file...
selected Ethernet device type slirp
Using SDL_Renderer driver: opengl
Detected CPU features: MMX SSE SSE2 SSE3 SSSE3
PowerPC CPU emulator by Gwenole Beauchesne
WARNING: Unknown DiskStatus(6)
I did
the pref is not there.
Reading ROM file...
selected Ethernet device type slirp
Using SDL_Renderer driver: opengl
Detected CPU features: MMX SSE SSE2 SSE3 SSSE3
PowerPC CPU emulator by Gwenole Beauchesne
WARNING: Unknown DiskStatus(6)
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Was your Cinnamon desktop maybe switched to software rendering? It can run with sdlrender opengl in that case, too. Smells like a Wayland issue.
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Cinnamon warns when using software rendering. It did not warn, and I would have noticed as it becomes dead slow.
But I had an nvidia driver etc update today. That driver provides opengl. The update process is not always as clean as one would want.
I've had issues with sdl/cinnamon/wayland before when running Qemu (blank screen when not explicitly directing some output).
Best,
Cat_7
But I had an nvidia driver etc update today. That driver provides opengl. The update process is not always as clean as one would want.
I've had issues with sdl/cinnamon/wayland before when running Qemu (blank screen when not explicitly directing some output).
Best,
Cat_7
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
New update online.
- Now only a "Continuous release", no history of releases kept automatically (I will likely "pin" some releases)
- The launcher now prepends "--sdlrender software" to increase compatibility
- The GTK theme is now locked to the included "Clearlooks"
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
And another update, in preparation for registering the AppImages. Usage changed quite a bit. The individual AppImages can be downloaded directly now. Installer and mmap hints were moved into the AppImage, rendering the helper scripts obsolete.
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Hi,
I notice there are some inconsistencies in the readme on the github site. The files downloaded are named differently from what the readme says.
(e.g. SheepShaver.AppImage vs macemu-amd64-sheepshaver.AppImage)
Also, downloaded files cannot be executed?
chmod +x macemu-amd64-basilisk2.AppImage
./macemu-amd64-basilisk2.AppImage
bash: ./macemu-amd64-basilisk2.AppImage: No such file or directory
Best,
Cat_7
I notice there are some inconsistencies in the readme on the github site. The files downloaded are named differently from what the readme says.
(e.g. SheepShaver.AppImage vs macemu-amd64-sheepshaver.AppImage)
Also, downloaded files cannot be executed?
chmod +x macemu-amd64-basilisk2.AppImage
./macemu-amd64-basilisk2.AppImage
bash: ./macemu-amd64-basilisk2.AppImage: No such file or directory
Best,
Cat_7
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Hi,
good catch! I adjusted the filenames and added the part about marking files executable.
About the error "No such file or directory": Do you happen to have installed and uninstalled the AppImage Launcher without rebooting afterwards? What AppImage Launcher does is it installs a low-level "handler" which detects execution AppImage binaries and hijacks it to display dialogues. When uninstalled, this handler does not get unregistered from the kernel, which is why a reboot is necessary to be able to execute AppImages again.
This low-level integration is somewhat clever, but can also be annoying. The major drawback is that the registered handler is called inside chroot containers as well but unavailable, which sabotages my Docker based build process, as it utilizes linuxdeploy which is distributed as an AppImage as well. The author is aware of this but can't really fix it. I hope less intrusive alternatives to AppImage Launcher will emerge eventually within the individual desktop environments.
There is also appimaged. But since these helpers are entirely optional, I haven't had a look at it yet.
Should I better not mention the AppImage Launcher in the readme?
Regards,
Korkman
good catch! I adjusted the filenames and added the part about marking files executable.
About the error "No such file or directory": Do you happen to have installed and uninstalled the AppImage Launcher without rebooting afterwards? What AppImage Launcher does is it installs a low-level "handler" which detects execution AppImage binaries and hijacks it to display dialogues. When uninstalled, this handler does not get unregistered from the kernel, which is why a reboot is necessary to be able to execute AppImages again.
This low-level integration is somewhat clever, but can also be annoying. The major drawback is that the registered handler is called inside chroot containers as well but unavailable, which sabotages my Docker based build process, as it utilizes linuxdeploy which is distributed as an AppImage as well. The author is aware of this but can't really fix it. I hope less intrusive alternatives to AppImage Launcher will emerge eventually within the individual desktop environments.
There is also appimaged. But since these helpers are entirely optional, I haven't had a look at it yet.
Should I better not mention the AppImage Launcher in the readme?
Regards,
Korkman
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Yes, I (reluctantly) installed, ran once and then uninstalled without reboot.
On Fedora I was warned about installing a non-trusted third party tool. My first impression from the readme that it was actually required. In my humble opinion using/advertising the appimage launcher creates an additional hurdle. If it is not needed I would suggest merely mentioning it as an option somewhere way down on your page
btw: I'm rewriting our guide and created a new page here: https://www.emaculation.com/doku.php/sh ... skii_linux
Best,
Cat_7
On Fedora I was warned about installing a non-trusted third party tool. My first impression from the readme that it was actually required. In my humble opinion using/advertising the appimage launcher creates an additional hurdle. If it is not needed I would suggest merely mentioning it as an option somewhere way down on your page
btw: I'm rewriting our guide and created a new page here: https://www.emaculation.com/doku.php/sh ... skii_linux
Best,
Cat_7
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
I updated the readme and moved AppImage Launcher down, discouraging the use for now. Also updated the Wiki link. Thanks for you efforts!
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Hello,
I got an Exec format error when I tried to install the SheepShaver-x86_64.AppImage (2022-08-12) on Raspberry Pi OS 64bit.
It keeps showing the error.
Please let me know what I should do.
Thank you
I got an Exec format error when I tried to install the SheepShaver-x86_64.AppImage (2022-08-12) on Raspberry Pi OS 64bit.
It keeps showing the error.
Please let me know what I should do.
Thank you
Re: Linux x86 64-bit builds for SheepShaver, Basilisk II
Hi,
You Raspberry uses an ARM processor, while the downloads are for Intel processors.
You'd need to find builds for ARM, or try to compile yourself.
Some info here: viewtopic.php?t=8147&start=25
Perhaps this walk-through is more helpful: https://www.jhtsbigmistake.com/post/run ... spberry-pi
Best,
Cat_7
You Raspberry uses an ARM processor, while the downloads are for Intel processors.
You'd need to find builds for ARM, or try to compile yourself.
Some info here: viewtopic.php?t=8147&start=25
Perhaps this walk-through is more helpful: https://www.jhtsbigmistake.com/post/run ... spberry-pi
Best,
Cat_7