@meleu Perfect, many thanks for this! Exactly what I was looking for. I always take routine backups.

Did you disable the retropie splashscreen ? Please post the contents of your /boot/cmdline.txt

Note you can speed up boot by disabling "wait for network" in raspi-config.

Also - 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

Please provide as much information as possible.

@herb_fargus It's not a 3rd party image, it's someone's preconfigured noobs setup with 3 partitions: one with Retropie, one with Kodi, and one with Raspbian. It's still the default Retropie image on top of a headless raspbian os. It was done this way so you would have less overhead when running Retropie (rather than having Raspbian with the GUI with both Kodi and Retropie installed and running on it).

Thanks columboscoat! That fixed it!

@stahl80 wheezy has been unsupported for months and RetroPie-Setup has been warning this when launched for some time.

@kassult said in RPi B doesn't boot into controller setup:

If I remember correctly the B only needs 0.5A so I figured I was fine.

It needs more than twice that - 1.2 A
https://www.raspberrypi.org/help/faqs/#powerReqs

Heh that's great news! Will it work with the runcommand menus as well, or just the retropie-setup menus? In either case, that's a superb improvement! :)

@sinfolmatt Please use the official installation instructions

https://github.com/retropie/retropie-setup/wiki/First-Installation

Note the part where it refers to downloading the correct image / number of raspberries shown on boot.

@buzz Thanks so much for this !!!!!! I am not sure what happened with last update a few months ago but I had the exact same problem when I tried to to get the latest update. None of the retropie menu options worked and the command like setup did nothing. Your command has certainly helped a huge amount. Now I am just getting "Temporary failure resolving 'raspbian.raspberrypi.org'" errors and "error cannot lock ref 'refs/tags/4.7': unable to resolve reference. But great progress, thank you

@johnnyskullhead

Does a micro SD with retropie on it need to sit in the pi still ?

@Darksavior check the instructions made by joolswills in the comments here:
https://github.com/RetroPie/RetroPie-Setup/pull/1602

Maybe it get some improvements in the future, but you can change it currently.

@magiclamp

The menu will populate with systems/ports when you add roms/game data.
https://github.com/RetroPie/RetroPie-Setup/wiki/First-Installation#transferring-roms

I want to create a scriptmodule for OpenBOR to add version 6315. I see the flag rp_module_id="openbor" that makes the module visiable into script screen. To avoid confusion I want annother name like rp_module_id="openbor_6xxx but want to use the old pathes.

Now all instances of $md_id, $md_config... uses the name that is given by rp_module_id so how to change names? I can include a function strip () { }that sets internal variables to openbor but this is not good code. So how to achive this?

Again: the goal is to use one config directory and one directory that contains several versions of OpenBOR.

Besides thank you BuZz for the platforms flags, I may exclude 6xxx for rpi1.
Is there a dedicated WIKI about script modules?

if you have mapped to keyboard, you will have to either change it so one is mapped to enter, or just use a small wireless keyboard for configuring etc.

@meleu
Okay thank you :)
And what about a simple keyimport. Just import KEY and SSID from /boot/wlankey.txt to /etc/wpa_supplicant/wpa_supplicant.conf? That's just a simple grep command :)
But somebody has to put this small script tool to the standard image file :) and make it somehow executable via joypad :)

@tfpHumorBlog yes I have actually, it's because the joy2key script is configured to use input of js0 by default but my controller was js1
So make sure your joystick is js0 input