[petrockblog]

The console blanker is activating – due to a Debian Jessie bug.

2 issues on 3.4 that weren't there on 3.3

[petrockblog]

using win32diskimager will overwrite what is on the card. I keep a copy of my romss on the PC to save time, so you just need to backup configs

This is the easiest way to upgrade to jessie with retropie.

[petrockblog]

the space must be used up somewhere.

install “ncdu” and use that from a terminal to see where the space is used. Maybe you copied something to the wrong location?

[petrockblog]

http://pingus.seul.org/~grumbel/xboxdrv/xboxdrv.html

It is also possible for xboxdrv to read input data directly from an event device, this allows the use of the configurability of xboxdrv on regular PC joysticks, keyboards and mice and thus lets xboxdrv serve a similar purpose as joy2key. See the option –evdev below for more information.

may well still work.

[petrockblog]

using something like xboxdrv perhaps ?

[petrockblog]

(and is written as a quick fix for navigating retropie-setup from a joypad)

[petrockblog]

It won’t work for anything but terminal based software.

[petrockblog]

retropie-setup script has been updated, so you can update and try again

[petrockblog]

missing dependency – install libraspberrypi-dev and it should build.

[petrockblog]

not that I know of – https://github.com/libretro/mame2000-libretro/issues/13

[petrockblog]

Where is the log ? It was attached but then it went – did you remove it ? (unless somehow I accidentally clicked delete). Please use an external site for the log – did you uncompress before pasting into pastebin etc ?

[petrockblog]

Make sure you are logging in with user “pi” lowercase. the password is also lowercase.

[petrockblog]

ssh is enabled by default for the “pi” user on the retropie images. unless it’s been disabled should be no need to enable it

[petrockblog]

please upload it somewhere or use pastebin.com or similar and I’ll take a look.

[petrockblog]

without the build log impossible to say (it’s in the logs/ folder)

[petrockblog]

Can’t be a libretro port unless the sourcecode is released unfortunately.

[petrockblog]

Rom deletion issue is known and confirmed and on our bugtracker.

The blanker issue is known and there is a workaround above. We will sort that in a future image – it’s an underlying OS issue.

Boot time is down to the OS, it’s quite possible Jessie boots slower – not a RetroPie issue though.

Exiting emulatiomstation is actually a bugfix. Before no metadata was saved on exit – so data could be lost. Now it is, and meta data is always saved. Before it was saved if using quit, but not saved is doing shutdown / restart so we tried to make it more consistent. Unfortunately it does take a while to save if you have a lot of roms.

[petrockblog]

:)

[petrockblog]

no since we dont include the basilisk gui – but easier to do on a pc anyway.

[petrockblog]

It is nothing to do with retropie itself but perhaps an issue with the underlying OS (Raspbian). Might be worth rolling back the RPI kernel to see if it is a kernel related problem (and things like trying the old sdcard driver – dtoverlay=mmc to /boot/config.txt)

[petrockblog]

http://www.emaculation.com/forum/viewtopic.php?f=6&t=8068

I would do this with a copy of basiliskii on PC. Note you can access the rpi filesystem from within the emulation also.

[petrockblog]

Known ES issue https://github.com/Aloshi/EmulationStation/issues/222

Someone did make a fix so I will apply it on our branch https://github.com/Aloshi/EmulationStation/pull/346

[petrockblog]

Looks like there is actually a problem in the EmulationStation delete functionality which is causing emulationstation to quit. It only worked before because we forced restart of ES, but it shouldn’t crash when deleting.

[petrockblog]

I will look into the first issue – may need to change one of the function calls.

the second issue is actually a Debian Jessie bug – the console blanker is still active. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771161

Try adding “consoleblank=0” to the end of the existing line in /boot/cmdline.txt

or alternatively (safer as less likely to break booting by messing with cmdline.txt) add “setterm -blank 0” to /etc/rc.local (above the exit 0 line)

[petrockblog]

you should use /etc/rc.local rather than /etc/init.d/rc.local btw – the init.d script isn’t meant to be modified

[petrockblog]

you have an old retroarch.cfg – change the input_joypad_driver to “udev” in configs/all/retroarch.cfg (it is currently set to sdl2). You can do this from “Edit RetroPie/RetroArch configurations” from retropie-setup. Once this is done, reconfigure your controller within emulationstation and try again.

[petrockblog]

That part of the wiki is incorrect – probably written before we had the input configuration code in.

[petrockblog]

Yeh it will need to be working first with ES. I can’t advise as I don’t have one of those controllers. it *should* work when registered and paired in the correct mode. There are people who have used these controllers successfully.

[petrockblog]

you should have more in configs/all/retroarch.cfg than that.

[petrockblog]

possibly – you will need some development knowledge.

you can start by trying out the generic-x11 target (to build emulationstation / retroarch to run under X)

sudo __platform=generic-x11 ./retropie_setup.sh

I can’t really advise though as I don’t have one of these boards.

[petrockblog]

Do not delete es_input.cfg – you will wipe a crucial configuration in there that is needed to trigger the controller scripts. If you do remove it you will need to re-install emulationstation to restore it correctly.

[petrockblog]

what is your current folder structure ? do you have everything in a retropie folder ?

[petrockblog]

Deleting it wipes some needed config. Reinstall ES from menu 5 of retropie-setup and reconfigure pad

[petrockblog]

Which dbus error ? Please update retropie-setup as there are some missing dependencies on the 3.4 image for bluetooth pairing and it may show this error if not updated.

[petrockblog]

Just to double check – you def unregistered the joypads, and then re-registered it with the button combo being pressed down, as well as pressing the combination before pairing ? I have read that is the fix (I don’t actually own this controller).

the config files can be accessed over windows network etc same as the roms etc.

[Author]

Posts