[petrockblog]

how about some information ? :)

Which version of mame, which version of retropie ?

[petrockblog]

You may have updated retropie-setup without updating everything else – you will need to run a full binary install, but there are some things that may require manual work if upgrading with the script. you can always just rm -rf /opt/retropie and reinstall and it should work.

[petrockblog]

faulty controller, faulty pi, faulty/poor psu? try ruling out somethings. changing psu/cable is a good idea perhaps. this is not a known problem and others are not reporting it.

[petrockblog]

Yes, but will require configuration for fuse – there is a lr-fuse module in experimental which may be easier to try.

[petrockblog]

usb keyboards are very cheap though – handy to have a wireless one available rather than having to do everything remotely.

[petrockblog]

it does if you update retropie-setup and then do

sudo ./retropie_packages.sh runcommand install

it should then allow use of joypad to enter the menu / configure (works on my two controllers at least)

[petrockblog]

Looks like you may have run out of memory when compiling. You may need to lower gpu allocated ram via /boot/config.txt and try again – I’ll check on my 256MB pi and perhaps add some virtual memory for this module.

[petrockblog]

Overclocked ? Which emulators ? Don’t expect fullspeed n64 on the rpi1 though.

[petrockblog]

May be changes upstream that has broken compilation – you can post a logfile from the logs directory to a site like pastebin and I can look more (Or open a ticket on github and I’ll check when I next have a moment)

[petrockblog]

you want to have emulationstation viewed over vnc ? That won’t work on the pi as we are not running emulationstation with X etc.

[petrockblog]

I am unable to reproduce the problem you have – I had though initially when I read you meant it froze after configuring controls. Looks as through it may be having trouble with your controller oas it should ask to configure each key etc. Do you have another controller to test. What controller are you using ?

[petrockblog]

you dont need to modify that to change path for roms – just bind mount your roms real location where it expects them – https://docs.1h.com/Bind_mounts

you are getting permissions denied as it’s a system config owned by root user – you would need to sudo to root to copy over it (or make it readable by other users)

[petrockblog]

you press the “a” button and wait and it will finish. it’s doing stuff in the background. Not crashed just busy.it can take more than 5 seconds on rpi1 etc.

[petrockblog]

Someone posted some here https://www.raspberrypi.org/forums/viewtopic.php?p=777597#p777597

[petrockblog]

Option 1 from retropie-setup

Sounds like you might be better off with a prebuilt SD image.

[petrockblog]

These are two issues – firstly looks like a networking problem or something else happened during install – you can reinstall the bits that failed.

the rpi-update part is unrelated – rpi-update takes a single parameter if required to install an older firmware which is the sha1 of the repository revision. 192 is not valid. You shouldn’t need need to use rpi-update btw – new firmwares are packaged when ready.

[petrockblog]

ok. That’s enough information anyway. The problem you have was due to us handling hat inputs wrong. This was fixed earlier today, so if you update retropie-setup script then re-install emulationstation from binary from menu 5, it should sort it after a reboot when configuring.

[petrockblog]

Assuming you are on Windows (if on Os X whatever is the equivalent software)

please install the latest beta version onto an SD card.

Then boot it up on the pi (with the pi connected via ethernet to your network), and configure your joypad on emulationstation. Once this is done, using Putty http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html connect to the Pi (hostname retropie), and use login: pi, password: raspberry

once at a command prompt type

cp ~/.emulationstation/es_temporaryinput.cfg /opt/retropie/configs/

now go to your PC and browse the network – you should see the retropie machine on the network with some shared (roms/configs/bios). Go to configs, and copy the es_temporaryinput.cfg file to your PC.

Then browse to configs/all/retroarch-joypads/ and copy the .cfg file in there to your PC also.

Now go to a retroarch emulator such as lr-picodrive and confirm left/right are not working. If not go back to the PC, and browse again to configs/all/retroarch-joypads/ and remove the file.

Now go to retropie-setup, and the supplementary menu, and choose the option to configure retroarch input devices. Choose joystick and follow the instructions. Once this is sorted, go back to the emulator, and check if controls are all working correctly – they should be.

Now go back to the PC and browse again to configs/all/retroarch-joypads/ there should be another config in there. Please copy this to the PC also (renaming it if it has the same name as the previous config file we copied off).

These are the 3 files I need. The es_temporaryinput.cfg file – the first joypad configuration file (which we generate), then the second joypad configuration file made using the retropie-setup retroarch input configuration option.

Thanks.

[petrockblog]

Would you be able to help me with the information above ? Will help us work out what was generated incorrectly in the config. Much appreciated thanks.

[petrockblog]

oh and also a copy of /home/pi/.emulationstation/es_temporaryinput.cfg – thanks :)

[petrockblog]

Please post a copy of the joypad configuration after using emulationstation set up – file is in /opt/retropie/configs/all/retroarch-joypads

then delete it, and configure retroarch joystick using the option in supplementary menu of retropie-setup (Configure input devices for RetroArch) – then post a copy of that too, and I will check the differences. you can still use this configuration to set up your joypads for retroarch as before – please let me know if this makes it work correctly too.

[petrockblog]

The settings are stored in /etc/splashscreen.list – the file you mention is the init.d script for launching the splashscreen. If you need to customise that it has moved to scriptmodules/supplementary/splashscreen/asplashscreen

If you need details like this you can reference the changes on github

https://github.com/RetroPie/RetroPie-Setup/commits/master

[petrockblog]

retropie 3 has a single n64 folder – you can press x or m on game launch to configure which emulator is used by default, and which emulator to use per rom (and choices of emulator vs render driver).

https://github.com/RetroPie/RetroPie-Setup/wiki/Nintendo-64

[petrockblog]

You would have to write a bash script and adapt the EmulationStation file ~/.emulationstation/es_systems.cfg accordingly.

[petrockblog]

just include the path when lauching. No need to add it to the system path. if you really want that – google adding paths to linux via bashrc etc

[petrockblog]

yep – although some with fastloaders may fail. but glad you sorted it :-)

[petrockblog]

(Note the search dialog will still crash – be careful – we need to re-disable that again)

[petrockblog]

re-install retroarch from binary from menu 5 in retropie-setup. we have reverted to an older version.

[petrockblog]

Ahh yeh sorry – there wont be – and of course some things are in experimental for a reason. I forgot it was. I will have a look at this when I next get a moment – feel free to open a ticket on retropie github, but basically if it did work, and now it doesn’t its likely an upstream bug :/

[petrockblog]

known issue – please reinstall retroarch from binary from menu 5 – and it should sort it.

[petrockblog]

and if you install it from binary rather than source does it work ? if a change in it has broken you will need to report it back to the libretro project page on github.

[petrockblog]

Actually he didn’t (and me neither) – he just decided to put some of his free time into helping others out on the project – including much needed work on the wiki etc – video tutorials and so on.

[petrockblog]

Having centralised / automated controller set up has been something people have been asking for for ages. Unfortunately some bugs slipped through – mostly due to lack of controllers for testing. The RetroArch freezing issue is annoying too – Bugs sometimes slip through. We also not responsible for every piece of software that comes with retropie – so sometimes something is updated and bugs appear.

You are free to stay on beta 2. I am giving up my free time and working hard to try and sort this all out. You could sound a little bit more appreciative.

[petrockblog]

Originally we pulled from the repository by the person who ported it to the rpi – but then his repository was missing some fixes that were needed, so I forked it and fixed up our copy. Since then he has moved his repository and made a few additional changes, so we need to either switch and test, or just pull those changes back into our version.

[petrockblog]

You have a networking issue – possibly dns – Make sure the pi has full internet access and try again perhaps. How is your pi connected ?

[Author]

Posts