@mitu I need you to unlock that recent post of mine about the splashscreen. I reposted on that topic because nobody was able to help me with my previous post and the one that you locked had more detail and pictures that might be able to be diagnosed by someone who actually knows how to fix my issue.

If the RetroPie menu is still function then you can copy your roms to external storage with the help of the file manager, you will need a keyboard.

When you open the file manager you will saw two same panels, from here you have access to all system files. You can choose panel with tab button. Choose to one panel your external storage and to the other panels the files you want to copy/paste. Then choose the file/folder you want to transfer and press the F5 button, they will copy to the external storage.

managed to resolve myself.
Apparently these are just warning messages and are only preventing successful compilation because of the -Werror flag in the makefile. Removed that flag and it now compiles successfully

@mitu I've enabled both the options u showed in your post. It successfully. I was quite baffled because I saw the the Dt overlay option twice in the end of my boot config.

Thank you for your help

Ok. Nevermind i have managed to fix this issue by formatting the SD card and flashing the image again.

@mitu said in Hash sum mismatch error:

don't have SSH enabled, then

I just enabled SSH, and updated the thread info with read-me-first topic.

I have installed the 4.4 image from the RetroPie site, and I have internet connection, I made a ping to www.google.com and work.

I now with PuTTy connected to the RetroPie.

What should do I do? Where is the path to get the log files?

E: Failure to obtain http://espejito.fder.edu.uy/raspbian/raspbian/pool/main/u/unzip/unzip_6.0-21+deb9u1_armhf.deb Hash sum mismatch Hashes of expected file: - SHA256:d69087f3500527bd24f0ee8870a41ac9e45eb34f6b73081a7775fd7ef8825208 - SHA1:9156bdc618af94d53ac6a864ef8d93c0f9af0fa7 [weak] - MD5Sum:76f6caff8c43590c18bf7b4d622adc2f [weak] - Filesize:149042 [weak] Hashes of received file: - SHA256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 - SHA1:da39a3ee5e6b4b0d3255bfef95601890afd80709 [weak] - MD5Sum:d41d8cd98f00b204e9800998ecf8427e [weak] - Filesize:0 [weak] Last modification reported: Sat, 27 Apr 2019 16:08:06 +0000

Looking into it, the web

http://espejito.fder.edu.uy/raspbian/raspbian/pool/main/u/unzip/unzip_6.0-21+deb9u1_armhf.deb

isn't working, I copied that URL in my Google Chrome browser and a error file was downloaded.

But

https://espejito.fder.edu.uy/raspbian/raspbian/pool/main/u/unzip/unzip_6.0-21+deb9u1_armhf.deb

Work's just fine, so look's like

sudo apt-get upgrade

command isn't working because that http isn't https.

EDIT:

I have changed the /etc/apt/source.list

and added

deb http://mirrordirector.raspbian.org/raspbian/ stretch main contrib non-free rpi firmware deb http://archive.raspberrypi.org/debian/ stretch main ui

it seems it working now, the upgrade is doing downloading files without error.

But, is ok to use those repositories?

My guess? Is a problem for South American people (I'm from Argentina), that the source list is unupdated or wrong setted, because when I got the url it use http and not https, looks like that's the main reason.

I tried to install the retropie-manager (after the update & upgrade) and I got this error

Could not install packages(s): python-dev virtualenv.

EDIT 2:

I have it working, to workaround I just change /etc/apt/source.list.p/retropie.list (or something like that)

and added (can't edit because the Akinet detect that is a spam, but add deb before the url)

https://espejito.fder.edu.uy/raspbian/raspbian stretch main

After saving the file, I use sudo apt-get clean and sudo apt-get update and everything is working just fine (or it seem's like that).

The error is that the URL is unupdated, but isn't the best option.

Idk if I have to send an email to the RetroPie developers to update the repo url for Argentina.

@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.

See https://retropie.org.uk/docs/FAQ/#why-emulationstation-doesnt-start-automatically-after-an-update. Fix your auto-login and then reboot, it will work again.

@mitu thank you

@herb_fargus I see. I was going to modify the Wiki script to send a browser User-Agent with the wget download command, but in this case I better not.

@pyterj Unfortunately it seems the download site doesn't allow direct download of the games, so you'll have to find a way to install them yourself. Sorry about that - as @herb_fargus said, there is a reason this script is not included in RetroPie proper and we can't get around that.

@michelrivas I have removed the section. Changes will show up soon.

@spider910 For my project, I simply made my own using Cat5 wiring. This allowed me to cut an exact length, kept everything nicely bundled inside the insulation, and made it very easy to know which wire was going where as opposed to everything black which would be a bit of a visual nightmare. I simply crimped on my own spade-type connectors to mate with the microswitches (most arcade parts sellers sell these in bulk, or easily found at hardware stores). The encoder end for me uses screw terminals (IPAC) so this was ideal, but I could have added header connectors too.

Because your not using an official inage

@gametravaler try removing the USB stick and reboot and see if it works. I had a issue recently where a folder went corrupt on the stick and was causing the issue. Retropie told me in the command line what directory was giving me issues, removed it and all is well.