RetroPie / RetroPie-Setup

Shell script to set up a Raspberry Pi/Odroid/PC with RetroArch emulator and various cores
Other
10.08k stars 1.39k forks source link

Minor issue while installing #534

Closed cpg closed 9 years ago

cpg commented 9 years ago

Great job on the installer, guys!

I got some errors, so I thought I would report them as a Clueless End User, in the hopes that this is useful to the team.

Considering the amount of bits that have to lined up here, this is a remarkable feat!

My setup is RetroPieImage_ver2.3.img with the RetroPie-Setup as of master/c782fdc706e74. The mention that the install is likely broken is a bit unsettling, even if it provides a work-around.

First error:

...
Processing triggers for hicolor-icon-theme ...

(gtk-update-icon-cache:29514): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/arm-linux-gnueabihf/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
  gdk-pixbuf-query-loaders > /usr/lib/arm-linux-gnueabihf/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.
Setting up libc-dev-bin (2.13-38+rpi2+deb7u3) ...
Setting up libc6-dev:armhf (2.13-38+rpi2+deb7u3) ...
...

The second error is:

= = = = = = = = = = = = = = = = = = = = =
Installing Modules UInput, Joydev, ALSA
= = = = = = = = = = = = = = = = = = = = =

libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/3.12.22+/modules.dep.bin'
libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/3.12.22+/modules.dep.bin'
uinput module already contained in /etc/modules
joydev module already contained in /etc/modules

The third error is:

= = = = = = = = = = = = = = = = = = = = =
Installing SNESDev (Driver for the RetroPie GPIO-Adapter)
= = = = = = = = = = = = = = = = = = = = =

/home/pi/RetroPie-Setup/scriptmodules/supplementary/snesdev.sh: line 16: cd: /home/pi/RetroPie-Setup/tmp/build/snesdev: No such file or directory
make: *** No rule to make target 'install'.  Stop.
cp: cannot stat `src/SNESDev': No such file or directory
cp: cannot stat `src/Makefile': No such file or directory
cp: cannot stat `Makefile': No such file or directory
cp: cannot stat `scripts/Makefile': No such file or directory
cp: cannot stat `scripts/SNESDev': No such file or directory
cp: cannot stat `supplementary/snesdev.cfg': No such file or directory

Fourth error:

= = = = = = = = = = = = = = = = = = = = =
Configuring N64 LibretroCore Mupen64Plus
= = = = = = = = = = = = = = = = = = = = =

Setting mupen64-gfxplugin = rice in /opt/retropie/configs/all/retroarch-core-options.cfg
Setting mupen64-gfxplugin-accuracy = low in /opt/retropie/configs/all/retroarch-core-options.cfg
Setting mupen64-screensize = 640x480 in /opt/retropie/configs/all/retroarch-core-options.cfg
cp: cannot stat `/opt/retropie/libretrocores/mupen64plus/data/mupen64plus.cht': No such file or directory
cp: cannot stat `/opt/retropie/libretrocores/mupen64plus/data/mupencheat.txt': No such file or directory
cp: cannot stat `/opt/retropie/libretrocores/mupen64plus/data/mupen64plus.ini': No such file or directory
cp: cannot stat `/opt/retropie/libretrocores/mupen64plus/data/font.ttf': No such file or directory
[esconfedit.py] Successfully saved to file /etc/emulationstation/es_systems.cfg
/opt/retropie/libretrocores/neslibretro /home/pi/RetroPie-Setup
joolswills commented 9 years ago

first / second error can be ignored

Will check snesdev, was this from selecting it from the setup menu ?

libretrocore mupen64plus will need rebuilding from source to rectify that error (until a new binaries package is available - it was an issue that has been fixed but will require a new distribution of the binaries)

cpg commented 9 years ago

This was doing the whole binary install.

joolswills commented 9 years ago

probably related to changes that have happened since the binaries were last packaged. you can re-run the snes dev stuff manually from the setup menu, or by doing

sudo ./retropie_packages.sh snesdev

if you don't use snes controllers you can just ignore it though.

joolswills commented 9 years ago

(Will leave this ticket open until we have a new binary package and I'll run through and test it - we have had some changes in recent weeks that may have introduced a few glitches here and there). Thanks for the feedback.

cpg commented 9 years ago

Running sudo ./retropie_packages.sh snesdev seems to have worked, though it brings me to an option to run it on boot, which, I think?, would conflict with ES?

In any case that part worked. I was also able to run the GBA emulator, so the install was not completely broken after all. Good going.

cpg commented 9 years ago

Incidentally, I am not sure if this weird root prompt is added by the rp-setup script or RP or raspbian, but it's weird, because I (as a new user) do not know what a "system" is per se, though I think it's talking about an emulator, based on the next sentence. Also, I do have some games on at least the GBA emulator.

No, I do not know what es_systemc.cfg is, what is the "for XML" context or why the system is somehow waiting for ... I have to type ctrl-c to get going ...

pi@raspberrypi ~/RetroPie-Setup $ sudo su -
lvl0:   No systems found! Does at least one system have a game present? (check that extensions match!)
(Also, make sure you've updated your es_systems.cfg for XML!)

^Croot@raspberrypi:~#

If this is part of the rp-setup script, it would probably make sense to not do this or explain why it's trying this ... However, since most users will never need to do things as root, hopefully, this is not a major issue.

joolswills commented 9 years ago

It's due to the way emulationstation is configured to run on startup.

You can just "sudo -s" for a non login shell to run stuff as root.