Was working perfectly now stuck on welcome screen - no gamepads detected and no keyboard response after my 4yr old did something

simonster

...actually on further reading of your log file, it looks like it isn't even finding the rom files. Could you navigate to ~/retropie/roms/megadrive and check whether the files are still there?

mediamogul

@Ummagitcha

https://retropie.org.uk/forum/topic/3/read-this-first

Format your posts! - put small logs in code blocks - see http://commonmark.org/help/ - and put large logs on a pastebin type site like http://paste.ubuntu.com/ http://pastebin.com/ or similar.

I formatted the previous post for you just to keep the thread moving.

Ummagitcha

By the way thank you so much for trying to help me! I really appreciate it!! Im sorry about that. Im brand new to this type of format and read over the rules but didnt understand some of them including the pastebin so i appreciate you fixing that.

Ummagitcha

@simonster the megadrive folder is empty. but the roms i originally installed are all in each of the corresponding folders (nes, snes, etc)

Also - how do go about SSH? im a little confused on that as well. I do have the retropie image file (retropie-4.2-rpi2_rpi3.img) is that what you are referring to? I will def attempt the steps you suggested if you can poss help give me a little more details in actual steps to take

A Former User

SSH means using a client to go into the Raspberry Pi and searching through the files.
ETA Prime has a lot of videos on that, including this one:

Ummagitcha

@itsnitro ok thank you!

Ummagitcha

@itsnitro see the problem is...i can only get into the files through my network on an ethernet. I cant access the actual retropie at all once it boots.

edmaul69

@Ummagitcha well through your network is what you need. If you are on a windows computer, you can use a program called putty to ssh in and run the retropie setup from the commandline.

Ummagitcha

@edmaul69 I was using WinSCP but it also will NOT allow me access anymore. :/

pjft

Ok. If you haven't ever updated anything or made any significant changes, my recommendation would probably be to backup your Roms, if they're on the SD card, and just reinstall the image you have and put the Roms back in.

Might feel like a pain at this stage, but might be better for you in the long run. We don't know what might've broken there, so you're just fixing one thing at a time.

Also, while RetroPie package upgrades are something we could attempt, I've heard a few recent reports on things not working as intended that make me suspicious of updating the kernel - so I'd refrain from doing that if you go the update route, at least for now.

If you plug the Pi into your home network via Ethernet, you should be able to login via ssh. If you can't, I'd plug a keyboard to the Pi, exit EmulationStation and see if it has a valid IP and what else might be happening there.

Hope these help :/

Ummagitcha

@pjft How can i exit emulationstation (or stop it from opening during the boot up)? Because again, once it gets to ES, nothing responds. No controllers, keyboard, or mouse. is there something I can hit during boot up to stop it and then something I can type in to go from there? Because It does seem like the keyboard responds during boot up, just not after.

edmaul69

@Ummagitcha when you boot try repeatedly pressing f4 on the keyboard. If it isnt completely messed up before booting into the welcome screen it should kick you out to the command line.

AlexMurphy

@Ummagitcha Press F4 or make the Pi boot to the Terminal.

AlexMurphy

@Ummagitcha Reading through this... You are having issues that you should not be having. I would suggest a new SD card or at the very least re-imaging the one you have.

pjft

@Ummagitcha Either what has already been suggested, or Ctrl+C during boot/loading time.

Alternatively, if you can SSH into the Pi, you can kill the process yourself.