@keksninja Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..) Power Supply used: (If using a Pi) RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used) USB Devices connected: Controller used: Error messages received: Log found in /dev/shm/runcommand.log (if relevant): Guide used: (Mention if you followed a guide) File: (File with issue - with FULL path) Emulator: (Name of emulator - if applicable) Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS) How to replicate the problem: Please copy the above and fill in the info. Otherwise we have no idea how to start helping you.

@SeraphisCain The build/install script for the package is not updated right now, you'll need to have a bit more patience - it's not something on your end.

Nevermind, figured it out all on my own. :) It was a literal issue. When I looked at the files directly, the ones I was having this issue with all had filesizes of 1k lol. I replaced them and everything's working again. Thanks anyway for looking!

work fine how, thanks for the help

@markyh444 Oh poop, I thought I was on the Kodi forum... My bad!

@PolarBear123 BIOS files, just like ROMs, are copyrighted assets - they're not distributed with RetroPie and links and request for such items are not within the forum rules.

@mitu Thanks for your reply. I finally figured it out the problem was PEBKAC!!! I had the joystick plugged into the wrong 5 pin port. I thought there was only the one and I was wrong. Totally my bad but thanks for the help. I'm going to leave this up since I could not find any solutions to this problem anywhere and it might help someone.

Can't support that image as it's a 3rd party one. They should open their own forum really. Not a big fan of it tbh as it's a bit of a hack, and they don't feed back anything to our project.

@mitu Okay ,thanks for your help :)

@johny8 How did you determine that ? You claim is rather ridiculous. 'Sabotage' ?

@mitu Thats where i looked, its gone-vanished of the face of the earth, hope the setup script fixes it

@TomoS Emulationstation must be launched from the terminal, it's not going to work from an existing X.org/Desktop session. You'll also have to turn off/stop your login manager/display manager if you have one started.

Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first You have provided no information about your set-up. The error looks like it could be a connectivity issue. But details of your set-up will help.

@Jareth247 Glad you got it working; I don't think the power switch script had anything to do with it - although the incorrect file that was causing the problem for apt could have been produced by an improper shutdown in the middle of an install operation.

@mitu Oh my bad, sorry. You can tell I'm a mega-noob because I have a default profile picture 😁

@mitu said in Retropie_Setup errors after failed update: git clone --depth=1 https://github.com/RetroPie/RetroPie-Setup.git Great tip: it worked ! Currently updating all installed cores. Thank you so much !

Looks like a custom color palette. Which emulator ? What RA version ? Please add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Hey hey, maybe, I have found the solution: In the MAIN MENU / SOUND SETTINGS / AUDIO CARD, I selected <DEFAULT> because the entry was null <>. Just below, in the AUDIO DEVICE, I selected <PCM>. With this config, the error message disapeared. My config is: sound via a HDMI/VGA convertor, jack to mini-amplificator (RCA). Great, no ?

Update: I found the culprit! Turns out that the file libretro.h had this struct definition twice: struct retro_midi_interface { retro_midi_input_enabled_t input_enabled; retro_midi_output_enabled_t output_enabled; retro_midi_read_t read; retro_midi_write_t write; retro_midi_flush_t flush; }; This confused make since you can't redefine a struct once you declare it, causing errors and an eventual crash. Removing one of the struct definitions appears to have fixed this issue.