Starting Amiberry lha files results in black screen
-
Pi Model or other hardware: 3B+
Power Supply used: (If using a Pi) 2.5A
RetroPie Version Used 4.4
Built From: Pre made SD Image on RetroPie website.
USB Devices connected: Dualshock controller 4, Mouse, Keyboard.
Controller used: Dual Shcok Controller 4
Error messages received: Just a Black screen.
Log found in /dev/shm/runcommand.log (if relevant):
Parameters:
Executing: /opt/retropie/emulators/amiberry/amiberry.sh auto "/home/pi/RetroPie/roms/amiga/KidGloves_v1.2_1372.lha"
~Guide used: Midwan's Github Amiberry Setup
File: (File with issue - with FULL path)
Emulator: Amiberry 2.21
Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS)
How to replicate the problem:I installed Amiberry following Midwan's Amiberry setup on his Github page and then put the 3 kickstart files in the bios folder and checked they had the correct md5 checksums. I copied KidGloves_v1.2_1372.lha into the amiga roms folder.
After restarting Emulationstation I tried playing the game and it worked just fine.
This morning using Filezilla I copied about 70 other games into the roms folder and scraped them with Skyscraper.
I rebooted the system and tried playing some games and none of them worked!
Not even kid gloves which worked before. I tried removing all the games and removing the new game list.xml file and media folder that Skyscraper made and reinstalled Kid gloves but it never ran again.
When starting the game I see the screen change color a few times but it then stays black. There is no prompt to put in a kickstart disk either. I am able to press F12 and get into the Amiberry menu.
I am at a complete loss as what to do now. Does anybody have an idea?
Sorry for the long post but I wanted to be as complete as possible. Thanks! -
@apekop123 Amiberry does produce debug reports which are stored in
/opt/retropie/configs/amiga/amiberry/whdboot/save-data/Debugs
. The first thing I would do is check the report for Kid Gloves.My suspicion is that symlinks to the kickstart roms have broken. You can check with the following commands:
cd /opt/retropie/configs/amiga/amiberry/whdboot/save-data/Kickstarts find -xtype l -ls
The command will only list broken symlinks so if there is any output from the command, then you have broken symlinks. You should be able to fix these following the steps in this post.
-
@dudleydes I found the kid Gloves debug file where you pointed me but it seems to be empty. I opened it with Textedit on my Mac and there was nothing there. It is also 0Kb small.
Executing the 'find -xtype l -ls' command gives no results.
This is the contents of that folder:
pi@retropie:/opt/retropie/configs/amiga/amiberry/whdboot/save-data/Kickstarts $ ls -la
total 12
drwxr-xr-x 2 pi pi 4096 Sep 6 15:16 .
drwxr-xr-x 6 pi pi 4096 Sep 6 14:46 ..
-rw-r--r-- 1 pi pi 1 Sep 6 14:46 foo.txt
lrwxrwxrwx 1 pi pi 54 Sep 6 15:16 kick34005.A500 -> /opt/retropie/emulators/amiberry/kickstarts/kick13.rom
lrwxrwxrwx 1 pi pi 54 Sep 6 15:16 kick37175.A500 -> /opt/retropie/emulators/amiberry/kickstarts/kick20.rom
lrwxrwxrwx 1 pi pi 54 Sep 6 15:16 kick40063.A600 -> /opt/retropie/emulators/amiberry/kickstarts/kick31.romHmmm, not sure if my kickstart roms are wrong. Is there anything else I can check?
-
@apekop123 According to the Amiberry wiki,
the A1200 Kickstart 3.1 ROM is essential for running the WHDLoad Auto-Booter.
The symlink name for this rom is
kick40068.A1200
so it may worthwhile to add this. You can find the common names for the kickstart roms at the wiki page. -
@dudleydes Wow! That was it! I put in that extra rom and now everything works!
I just went by the roms that are shown in the Retropie Manager (in the browser). That only shows 3 roms but probably needs to be updated.
It's just strange that it worked once yesterday without that rom?!
Anyway, thanks a lot for your help! I'm now of to play some games! -
Re: Starting Amiberry lha files results in black screen
Hello, I have attempt to launch Amiberry with LHA and BIOS taken from working device. However I get black screen after Amiberry logo, and can see no logs are created when looking via WinSCP. I attempt to follow instruction to check broken symbolic links from above thread but no results are returned.
I have most all BIOS files in place, and have told Amiberry to rescan paths previously. Since it's not writing to Debugs folder could this be some permissions issue?
Any help would be greatly appreciated
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.