[petrockblog]

have you tried updating the binary (updating retropie-setup script first, then menu 5 to install individual emulators, then choosing gpsp) ?

If that still doesn’t work I’ll have to check myself – never actually tested this emulator :)

[petrockblog]

oh wait, that’s an ancient test file – so unsure which version you are on – es_systems.cfg is in /etc/emulationstation

[petrockblog]

Please can you try with the latest retropie image – the binary hasn’t lived in that location since retropie 2.3 and a lot has changed since then.

[petrockblog]

yeh the description, but I think the actual repository names should be more distinct if they are going to have two ongoing developments – maybe the word mainline should be included. anyway, it’s not a big deal :)

[petrockblog]

[quote=89257]I’m going to try compiling this core:

https://github.com/libretro/libretro-fba

to see if that works.

It says it’s only 6 days old and there’s nothing about FBA in the recent commits to RetroPie-Setup, so I’m guessing the one RetroPie-Setup installed is this one:

https://github.com/libretro/fba-libretro

It’s got to be worth a shot.
[/quote]

you think they could come up with a slightly more descriptive repository name than switching the order of the name – confusing!

[petrockblog]

Glad that you made the ControlBlock work now!

Looking at
[quote=89605]joypad port #0 (SNES-to-Gamepad Device) configured
joypad port #2 (ControlBlock SNES gamepad) configured
joypad port #3 (ControlBlock SNES gamepad) configured
joypad port #1 (SNES-to-Gamepad Device) configured[/quote]
I can see that SNESDev is also running. I recommend to disable that! It is a driver for the RetroPie GPIO Adapter and you do not need it when you are using the ControlBlock! To uninstall the service you need to do follow these commands:

cd /opt/retropie/supplementary/snesdev
sudo make uninstallservice

That will remove the devices “SNES-to-Gamepad Device” that you do not need anyway.

[petrockblog]

I suspect you may have actually bumped into the very issue I mention.

the log files are gzipped text files. You need to copy them off the pi elsewhere, using scp, or commandline ftp, or copying them to ~/RetroPie which is available via a samba share or another method. I’m afraid I don’t have time right now but you can find some basic guides on copying files etc on the net.

But I would just go with the 2.6 image as is (it’s brand new) :)

[petrockblog]

It would just be better to do the binary install and go from there. The binaries are not old. It doesn’t say this in the menu, but I wouldn’t recommend building from source unless you are comfortable in the linux console, as although it mostly does just work, sometimes things break. Retroarch was for example broken for a few days until this morning – so if you built from source during this time, you will end up with a non working system.

The binaries have been tested, so it’s best just to use them.

[petrockblog]

if you have installed the 2.6 image, then there is no need to do any source updates – I would recommend just downloading the image and going from there, or using the binaries install if installing on top of raspbian.

If you really want to use the source install, then I will need the build logfile from logs/ to help further.

[petrockblog]

There is a pull request on the gamelistdb dev branch for system options, which would allow us to do stuff like have multiple emulator choices for a single list of roms, or be able to select zx spectrum model etc.

Just waiting on the upstream development.

https://github.com/Aloshi/EmulationStation/pull/391

[petrockblog]

maybe the file is elsewhere that it is reading somehow ? Worth doing a locate/find on the filesystem and checking

$HOME/.ssh/known_hosts
/etc/ssh/ssh_known_hosts

[petrockblog]

remove line 1 of /home/user/.ssh/known_hosts

[petrockblog]

there is another patch here for this problem – which just involves a new definition line to enable some quirks

https://github.com/VladislavVesely/linux/commit/2f94af3f19689b014817990fe1cb500f6121f339

[petrockblog]

The ControlBLock should not interfere with the wireless controllers. The ControlBlock driver installs two additional ControlBlock gamepads in the operating system. These gamepads appear besides any other gamepad in the operating system. However, I have no real possibility to test this.

[petrockblog]

Just to confirm – when you say “start the emulator” do you mean launching a game, or you don’t even get the uae4all menu / config up first ?

[petrockblog]

did you try it first without updating ? the 2.6.0 image has the latest version pre-installed.

[petrockblog]

Your windows PC will most probably not show all partitions of the SD card. What ist the output now when you type df -h?
If you have expanded the file system after you observed the problems with the installation, I would suggest to try and re-install the ControlBlockService from scratch again (e.g., remove the ControlBlockService folder and rebuild/reinstall it).

[petrockblog]

[quote=89216]I manually added the snes9x-next core (https://github.com/libretro/snes9x-next), and then compared it to all the options that are currently offered in RetroPie (experimental and otherwise) and overall I liked it best. Can it be officially added to RetroPie?
[/quote]

Please create an “enhancement” issue in the RetroPie-Setup repository here.

[petrockblog]

You might be interested in the ControlBlock: https://www.petrockblock.com/2014/12/29/controlblock-power-switch-and-io-for-the-raspberry-pi/

A new batch of those is being produced in these days and will soon be available again.

[petrockblog]

well, there is no longer an “update binaries” function. you can update individual emulators though, or do a new binary install (which could wipe some settings, so good to backup first).

[petrockblog]

what version of retropie ?

[petrockblog]

Glad that it is working for you now!

[petrockblog]

Just that I understand correctly: The ControlBlock is working correctly on your Raspberry Pi 1. If you attach the ControlBlock on your Raspberry Pi 2 and use the same SD card image for the RPi 2 that you used for the RPi 1, you observe the random button presses?

In that case you would need to recompile the ControlBlockService for the Raspberry Pi 2 (as described at https://www.petrockblock.com/2014/12/29/controlblock-power-switch-and-io-for-the-raspberry-pi/). Due to differences in the RPi hardware the original version of the ControlBlock driver does not work on the Raspberry Pi 2, hence the need for recompiling.

[petrockblog]

sounds like you didn’t update the retropie-setup script first ? But you need to give more information than “no luck” – what didn’t work, was there any errors displayed, what was logged (logfiles compressed in ~/RetroPie-Setup/logs folder)

[petrockblog]

I suspect the image was somehow not written correctly or there is something wrong with the sdcard. Perhaps try another card, and try something like win32 imager to write it ?

An A to Z Beginners Guide to Installing RetroPie on a Raspberry Pi 2 B+

You could also try raspbian to see if that works for you (retropie is based on raspbian)

[petrockblog]

Glad you are all sorted. cheers.

[petrockblog]

SNESDev, the driver for the adapter, needs an updated GPIO library for the RPi 2. It might be that you need to re-compile SNESDev as described at https://github.com/petrockblog/SNESDev-RPi#installation.

Does that help?

[petrockblog]

The ControlBlock is also compatible with the Raspberry Pi 2. I have tested that myself.

Can you explain your configuration and setup in more detail so that I can get an idea about the problem?

What have you attached to the ControlBlock?
How does your configuration look like?
Which SD-Card image are you using?

[petrockblog]

need to see the log as to “why” it didn’t work. the error above happened because it didn’t successfully compile. there will be a log in ~/RetroPie-Setup/logs/

[petrockblog]

Don’t try and format anything. Please read and answer the questions I am asking – I’m trying to find out if this is a newly written image.

Please write the the latest retropie image onto the sdcard – using Win32 Disk Imager – I have no idea if you are starting with a fresh image or not. It shouldn’t be out of space completely if you are.

see below for some instructions on how to write the image and resize after first boot.

An A to Z Beginners Guide to Installing RetroPie on a Raspberry Pi 2 B+

[petrockblog]

sorry – but please answer all the questions I have asked or I won’t be able to advise.

I need to know if you are starting with a fresh image – there should be some free space unless you have copied files there already, or changed something. If you are using the existing set up as from earlier, we need to try again from writing the initial image to the sd card, and doing the first boot.

[petrockblog]

this is after writing a new image ?

So you are saying emulationstation (the emulator launch menu), didn’t load or you exited from it ?

is there any error printed above the text you mention ?

[petrockblog]

The link to the image in your post is broken.

Just to make sure: Did you expand your file system after you copied the RetroPie SD Card image and booted for the first time? This is necessary, otherwise you would only have about 60 MB of free disk space.

[petrockblog]

no – the boot partition should not be resized. sounds like the partitions are already correct – maybe the filesystem didn’t resize for some reason..

rewrite the downloaded retropie image to your sd card, boot into it, exit emulationstation and run

sudo raspi-config

and try expanding again.

if that doesn’t work I will try and help debug further. it shouldn’t give an error when resizing.

[petrockblog]

after it failed was there a config.log in tmp/build/retroarch – that might give a clue.

I’m unable to reproduce it here, but it can’t find your c compiler for whatever reason – so something is wrong with your image. Have you adjusted the system in any way ? You changed your hostname at least I see.

It might just be worth trying with a fresh image, but if there is anything further in config.log I can try and advise.

[Author]

Posts