[petrockblog]

yes.

[petrockblog]

I cannot support 3rd party images.

Please try from the latest official image, and use the bluetooth pairing module from retropie-setup to pair the keyboard.

[petrockblog]

the user is su ? you mean you created a new user called “su” or you are using the “su” comment ? you can’t su to root, as root doesn’t have a password – use sudo, or create a password for root.

[petrockblog]

ok. I have debugged it and opened a bug report and updated the retropie-setup script to use an older revision. should build if you update retropie-setup firt

[petrockblog]

you can use xboxdrv on any event device to map joystick to keypresses, so that should work.

[petrockblog]

It’s to do with upstream changes. I didn’t think about that before, as I had built it only a few days ago. I am debugging now, to report the problem to the developers, and then I will temporarily switch our module to build a version before it stopped working.

[petrockblog]

Sorry – I can actually confirm the issue – maybe I broke it with some recent changes will check and get back to you. Actually, I think it could be due to upstream changes…

[petrockblog]

you can try – but you may have the same problem – I think something is wrong with your development headers or something related. Another route would be to start with our image and try building it on there as that should work. Or provide me with an image of your card so I can check it.

[petrockblog]

I would start with their officially supported os (ubuntu). Might include the mali fbdev package also as with the odroid c1

[petrockblog]

yeh I checked the code – we would need some additional changes to make vector games render at higher resolution

[petrockblog]

the rpi version doesn’t work like that – and none of the modeline data is used – we have some generated modes built in (the rpi framebuffer doesn’t care about frequencies etc so we just generate fake modes). I think though because of this vector games will be locked at 640×480

[petrockblog]

The RPI will not send audio down HDMI by default when using DVI video mode.

Can also add hdmi_drive=2 into /boot/config.txt

http://elinux.org/RPiconfig

[petrockblog]

Which version of RetroPie ? Jessie or Wheezy ?

[petrockblog]

Did you try using the bluetooth configuration tool in retropie-setup ?

[petrockblog]

This is really going to require a developer with this board to contribute to RetroPie-Setup to get it properly working though really.

[petrockblog]

I think the XU4 needs a different fbdev driver, and it looks as though it isn’t packaged (yet) as it is for the odroid-c1

you could manually install it

http://forum.odroid.com/viewtopic.php?f=29&t=16272

and then remove the dependency for the fbdev-mali package – this is going to require development knowledge though – unless you just built things for running under X11

(__platform=generic-x11)

[petrockblog]

should be fine yes.

[petrockblog]

please make sure your system is up to date also – sudo apt-get update; sudo apt-get dist-upgrade

are you running wheezy or jessie ?

[petrockblog]

I’m not sure. If you create an image of your sdcard and share it with me via google drive or something I can take a look (buzz [at] exotica.org.uk)

[petrockblog]

nope.

[petrockblog]

I’m sort of glad it all went wrong, as it helped find a bug ;-) So thanks for that.

[petrockblog]

just re-install mame2003 from menu 5 (from binary) – this will trigger the es config to be re-added.

[petrockblog]

Aha, I think I found the problem. the lr-imame4all module which you installed after had some old code when some folders were changed. I will fix this, but basically it removed the old libretro folder and the es config for it (Not spotted this before as the lr-imame4all usually gets installed first, and it comes with the default image etc)

[petrockblog]

You are missing the config entry for mame-libretro in es_systems.cfg – you can correct this by manually installing lr-mame2003 from retropie-setup (from menu 5).

Have you manually edited the config at any point ?

[petrockblog]

it would work, but it would miss out emulator optimisations for the rpi2 – at least until you did a “full binary install” from retropie-setup

[petrockblog]

I suspect you have a RPI 1. I have updated the wiki as it said it runs best on a RPI 2 – but actually, the module is disabled for the RPI 1, so i not available.

[petrockblog]

If that is not working, please post via pastebin.com or similar a copy of /etc/emulationstation/es_systems.cfg and the output of

ls -la ~/RetroPie/roms/mame-libretro | head -n20

[petrockblog]

0.139 roms go in in the mame-libretro folder. If you have roms in mame-mame4all and mame-libretro they will both appear in ES (same logo, but different numbers of games)

[petrockblog]

If you have debian or ubuntu with working x11 environment with opengl then some of retropie will work.

[petrockblog]

Do you have a RPI 2?

[petrockblog]

Wheezy will be unsupported in the future as far as binaries etc.

[petrockblog]

lr-mame4all is shared with mame4all as they use the same romset version.

[petrockblog]

sounds like you downloaded the files as root or something first – should do it without sudo. make sure you have gcc/g++ installed

[petrockblog]

lr-mame4all is installed by default – perhaps you can provide some more information? Where did you put your roms – can you give some example file listing of a few with the path etc

[petrockblog]

if you want to quickly disable joystick control for that you can remove the file /opt/retropie/supplementary/runcommand/joy2key.py (Note it will get re-installed when updating etc)

[Author]

Posts