Amiberry broken on Pi 4/Buster
-
Amiberry install from both source/binary, gives the error:
malloc(): unsorted double linked list corrupted Aborted
https://github.com/BlitterStudio/amiberry/issues/1366
https://github.com/BlitterStudio/amiberry/discussions/1295
Replacing
amiberry
binary with one extracted from the releases page, does work:https://github.com/BlitterStudio/amiberry/releases/tag/v5.7.1
Discussions on github point to a missing
capsimg.so
library, which is accounted for in the RP scriptmodule, but absent from the package repository (from the 5.7.1 version used, anyway -- it is present in the current master branch.)It looks like it used to be a submodule, but then rolled the sources in manually?
https://github.com/BlitterStudio/amiberry/pull/1374
I don't know what to do with any of that. I've only just started to explore the amiga and its library, and hit this immediate roadblock.
ETA: in the build log it looks like it's still cloning into the capsimg submodule but then something goes wrong and it don't get the output file in the end (L129):
cp: cannot stat '*capsimg.so': No such file or directory
-
[...]
Discussions on github point to a missing capsimg.so library, which is accounted for in the RP scriptmodule, but absent from the package repository (from the 5.7.1 version used, anyway -- it is present in the current master branch.)
The
capsimg.so
is indeed missing (binary or source install) and this should be fixed in the build script. However, I don't think that's the cause of the crash - even with the.so
included it still crashes. The binary package from the Amiberry releases does indeed work, despite the fact that the.zip
also doesn't have thecapsimage.so
file in the plugins folder.I'll try to see where the crash occurs and what's causing it.
-
I noticed an error when building recently (relating to capsimg location). It's on my list to check.
-
@BuZz Yes, the copying of the
campsimg.so
build artifact to$md_build/plugins
is not working, but the error occurs whether that's fixed or not. I'm starting to suspect is configuration related, since the backtrace from the crash is pointing to a simple static var initialization - can't see how that triggers a SIGABRT. -
Hm, after fixing the
capsimg.so
plugin installation and trying to compare our build to the one produced upstream, I can't reproduce the issue anymore.@sleve_mcdichael can you test to see if https://github.com/RetroPie/RetroPie-Setup/pull/3978 fixes the issue for you ? Make sure you have the necessary Kickstart files in
$HOME/RetroPie/BIOS/amiga
just to rule out any missing model KS files.EDIT: PR has been merged, so you can just update RetroPie-Setup then try a source update.
-
@mitu yes install from source works now, thanks.
Re: kickstart roms -- I had a hard time figuring out which of the many different given filenames I was supposed to be using, but I think I've got it mostly sorted out, now.
...
I've found that, using
BrutalFootball_v1.21_CD32.lha
for example, none of the following:kick40063.A600 #as distributed, "somewhere" kick40063.a600 40063.A600 40063.a600 #as named in the error message
...none of those work. The error shown is as:
...which appears to be looking for
40063.a600
even while that file is present, and does not work.However, that same file renamed as either of:
Kickstart v3.1 rev 40.63 (1993)(Commodore)(A500-A600-A2000)[!].rom Kickstart v3.1 rev 40.063 (1993)(Commodore)(A500-A600-A2000)[!].rom
(nb. .63 vs .063) ...both these does work.
On the Amiberry github, I do see this filename format for several of the kickstarts, but I still don't know what to do with these last two remaining:
42baa124 kick34005.CDTV 89da1838a24460e4b93f4f0c5d92d48d 9e6ac152 kick39106.A4000 9b8bdd5a3fd32c2a5a6f5b1aefc799a5
Maybe these just aren't used by Amiberry? I see the
kick34005.CDTV
listed only in the lr-puae section, and the other one doesn't seem to be mentioned anywhere...
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.