[herbfargus]

This is a good tutorial, it is more specific to the raspberry pi but if you timed the splash screen right it would hide the bulk of the boot text until emulationstation starts up.

This method uses omxplayer:

There is also a method utilising fbi here:

http://www.edv-huber.com/index.php/problemloesungen/15-custom-splash-screen-for-raspberry-pi-raspbian

This can also be used to hide some of the text in the boot sequence:

http://pi.bek.no/hideBootMessages/
or this: http://www.raspberrypi.org/forums/viewtopic.php?f=78&t=88408

Google raspberry pi boot splashscreen/ hide boot text … between all of the sources you could probably piece something together for RetroPie. I for one would be interested to see what you come up with.

[herbfargus]

The best tutorial would be to locate the retropie foundation website, find a supplier for the Raspberry Pi Model 2, order it- and then try again with image 2.5.

I’ve messed with just about every setting I could to try and get the Nintendo 64 games working on the B+ and could never come up with satisfactory results. I had to come to the realisation that the processor on the B+ just isn’t quite up to snuff for N64 emulation.

This can give you some ideas to start with though. Maybe you’ll figure something out that I didn’t.

https://github.com/ricrpi/mupen64plus/wiki/Performance

[herbfargus]

I’m not quite sure what to tell you. If the retroarch config thing doesn’t work another option you can do is edit the retroarch.cfg manually (that’s what I ended up doing)

From terminal:

sudo nano /opt/retropie/configs/all/retroarch.cfg

save by using control and x, then y for yes, then enter for filename (make sure you don’t accidentally hit a key and mess it up)

This is an example of what you would add:

input_player1_joypad_index = 0
input_player1_b_btn = 2
input_player1_a_btn = 1
input_player1_y_btn = 3
input_player1_x_btn = 0
input_player1_l_btn = 4
input_player1_r_btn = 5
input_player1_start_btn = 9
input_player1_select_btn = 8
input_player1_l_y_plus = -1
input_player1_up_axis = -1
input_player1_l_y_minus = +1
input_player1_down_axis = +1
input_player1_l_x_minus = -0
input_player1_left_axis = -0
input_player1_l_x_plus = +0
input_player1_right_axis = +0

[herbfargus]

I think what you are referring to when you say raspbian is the LXDE GUI (which was removed starting with version 2.4 to trim unnecessary bloatware.) As far as I understand it retropie is still built on raspbian but just lacks the GUI.

Starting with a fresh 2.5 image, to get the GUI back:

Sudo apt-get install lxde
Reboot

Then you should be able to open like you used to with startx.

PS. The reason 2.3 won’t boot on your cards isn’t an issue with your cards. The 2.3 image isn’t optimised for the newer processor of the model 2 raspberry pi. It works fine on the raspberry pi B+.

PPS. I would also look into using winscp if you like the whole windows type looking through folders thing. I used to use the GUI but I’ve replaced it with learning the terminal and occasionally utilising winscp.

[herbfargus]

There may have been some changes in the file structure from when those videos were made. What version of Raspberry Pi are you using? B+ or Model 2? Did you install from source or are you using the 2.5 SD image? Which USB controller are you using (SNES ibuffalo… n64?) Specifying the details of your hardware and software can help identify the issue.

[herbfargus]

You need to configure the controller for retroarch. You only have it configured for emulation station. (There are also separate configs for mame which are utilised by pressing the tab key during the game, GBA you press F10, and FBA has a config file called fba2x.cfg)

Floob made some good videos detailing how to do this:

(For future reference spend a little more effort looking through the forum because it is very likely that someone else has the same issue that you have. It helps to keep the forum clean of duplicate posts plus you learn things better when you work for it ;) )

[herbfargus]

I can confirm the same issue with the 3.5 mm jack. It isn’t as bad on my old tube televisions but it is more pronounced on my newer LED television (especially when routed through an optical cable to my soundbar)

As mentioned by others this is most likely a Raspberry Pi hardware issue rather than specific to the RetroPie project.

As for me, I’ll be sticking with HDMI.

[herbfargus]

Glad it worked

Be sure to mark threads that solve your problem “resolved” (using the dropdown menu at the top of the thread) as it makes it convenient for others who may have the same issue.

[herbfargus]

That usually means that you are out of available memory on your microsd card. In order to preserve space and accommodate various sizes of SD cards, the provided SD image from PetRockBlog is the bare minimum unexpanded.

You will need to expand your SD card using:

sudo raspi-config
Select option 1- expand filesystem
reboot

That should solve your issue.

[herbfargus]

Thank you for clarifying.

[herbfargus]

In theory yes that is possible. Might take a bit of configuring. Just make sure you update the setup script first before you install/update from binary or source.

[herbfargus]

@petrockblog

I really liked the mushberry concept: https://www.petrockblock.com/forums/topic/mushberry/

Is there a specific set of stipulations that you have for the logo other than trademarks with the raspberry pi? (which btw would mushberry be too close to the real logo to be a viable option?)

What are the aspects you are looking for?

-8-16 bit pixelated vs. true color vectors?
-concept of a pie vs a variation of the raspberry pi logo?
-should it have a slogan?

I have some friends that are good artists and I’d like to work on some logos with them to submit. Some general perametres would be useful to us and the community to give us an idea of what will work best.

Once enough logos are submitted I think it would be cool to have a contest or vote of sorts through the forum to establish the official RetroPie logo.

[herbfargus]

I just left it at 1 and it worked for me but it may be different for different monitors. The TV I’m using is vizio 42″ 1080p. The only thing I changed was deleting the “#” right before disable_overscan=1 and it solved the black border issue. You can mess around with the overscan settings as well if that doesn’t fix it.
Floob made some great videos discussing video settings that may be useful to you: http://m.youtube.com/watch?v=AYB6r7q9JkU

[herbfargus]

@fqpl

You might want to uncomment disable_overscan=1 in /boot/config.txt and that should solve the black border issue.

[herbfargus]

Its pretty easy to set up the WiFi dongle through the terminal without the need for the wpa-gui. See post #6436 at https://www.petrockblock.com/forums/topic/getting-wifi-working-with-retropie/

It worked well for me. I then used winscp to connect. IP typically will be 192.168.0.110 with username pi and password raspberry. (Or username root depending on if you need to modify other files)

[herbfargus]

Essentially. One of the most recent updates even allows for multiple emulators- for example it will have a folder called mame4all and another folder called mame. Both use the same ROMs but they each have their own advantages so if one ROM doesn’t work on one emulator you can try another emulator and see If you get better results. Once you get a little more experienced with the raspberry pi I highly recommend updating to newer versions of retropie. I just purchased the raspberry pi 2 and i’ll be installing retropie 2.5 on my microsd card.

[herbfargus]

In the ROMS folder there should be a folder called mame. You put your ROMs in there. If the mame folder is in _unused then move it back into the ROMs folder, add your ROMs to the recently moved mame folder and restart emulationstation and mame will show up as an option. Once in a game you’ll use tab on the keyboard to configure your controllers since mame is different than retroarch configs. (https://www.petrockblock.com/forums/topic/configuring-usb-controller-with-mame/) You’ll also need to make sure your mame ROMs are from the 037b5 set (https://code.google.com/p/imame4all/wiki/GameList) otherwise they may not work.

[herbfargus]

Kinda the same way that you update the usbromservice. I apologise if this isn’t exact I’m going off the top of my head as I don’t have access to my pi right now.
cd RetroPie
sudo ./retropie_setup.sh

Select update script
Reboot

Then update usbromservice like you did before

[herbfargus]

The only thing I can think of that I made a mistake with was not updating the retropie setup script first. When I fixed it I updated the script first, rebooted, and then went back into the setup script and installed the usbromservice

[herbfargus]

Yep sorry I wasn’t more help. Glad its at least some of it works :)

[herbfargus]

When I configured it I used ssh to start the program and then once it told me to enter the keys I used the controller, even though it wasn’t showing on my TV screen what was happening on my computer it would still register the joypad buttons.

You can also change the controls manually:

sudo nano /opt/retropie/configs/all/retroarch.cfg

This shows an example of where to add the joypad configs:

[Solved] Issues with retroarch.cfg configuration for joypads – exit emulator

[herbfargus]

https://www.petrockblock.com/forums/topic/getting-wifi-working-with-retropie/ post #6436 is what you will use to configure your WiFi dongle

[herbfargus]

@ buzz
[quote=86550]
A user reported the other day about a black screen on scummvm. I am now getting that myself. I suspect it might be connected to the last firmware/kernel update, but I need to do more testing.
[/quote]

Thank you. I had updated my kernel, and that is what broke Scummvm. That is good to know.

[herbfargus]

Good to know, let me know what you figure out.
(in case you weren’t aware win32diskimager also can create sd images by clicking read instead of write. You just have to name the file first with a .img ending.)

[herbfargus]

I’m not sure how helpful this will be but I ended up corrupting the microsd card somehow and it wouldn’t boot, it gave a similar response. Other times it would hang on the rainbow splash screen.
A few things to check:

-make sure you have an adequate power supply (mine is 2a 5v) but I’ve seen people do with less.

-if you compiled it yourself it could have been an error in the setup process otherwise try redownloading the SD card image petrockblog supplies

-try using win32diskimager instead of hddrawcopy

– I ended up corrupting things trying to transfer ROMs with a USB stick with image 2.4.2 beta as a result of the usbromservice not being configured properly (I don’t know if that has been fixed yet or not) but you can update the usbromservice from the setup script if it hasn’t been fixed.

-check to see if your microsd card is compatible http://elinux.org/RPi_SD_cards

In my case I guess I broke things beyond repair and ended up needing a new microsd card. I bought a new 32 gb sandisk ultra from amazon, downloaded the SD card image 2.4.2 off of petrockblog and used win32diskimager to put the image on the microsd card, updated the usbromservice from the setup script (cd RetroPie sudo .retropie_setup.sh) and it worked for me.

[herbfargus]

It looks like you may have only configured the controllers for emulation station and not necessarily the emulators themselves. Floob has some good tutorials on how to do this: http://m.youtube.com/watch?v=OBloKEbBRAU

[herbfargus]

I think the beauty of this project is the variability it allows- for some it entails building entire arcade cabinets and coding the software specifically to mame. Others (such as myself) use it as an all in one console and 3d print custom NES cases for the pi. For the do-It-yourselfer a preconfigured all in one system may not suffice.
I do think you are onto something though- for the average person who wants a nostalgic walk down memory lane and may not have the technical experience to configure all the controllers- all it would essentially take is the equivalent of a canakit (except replace the stock case with something more retroish) some cheap SNES USB controllers from China, and a customised version of retropie on a microsd preconfigured to the aforementioned controllers. Then add a quick how to for hot keys, how to add ROMs with a USB, and away you go. ( all the while respecting copyrights as to not be sued)

In short- I for one second your proposition.

[herbfargus]

Amazon or eBay. I purchased the games and copied the data files over from the CD. As far as locations for ROMs, those are outside of the terms and conditions of this forum.

(https://www.petrockblock.com/forums/topic/forum-rules-on-posting-in-regards-to-romsgame-images/)

[herbfargus]

Which version of retropie are you using?
In my case I’ve never tried uploading a zip file in the scummvm ROM folder. I extracted the zip file and put each game in their own folder. (This site will tell you which data files need to be in which folder for each game: http://wiki.scummvm.org/index.php/Datafiles)
I’m using the 2.4.2 BETA image. How I set up my games
-made sure all of the right data files were there and were in unzipped folders (or you can just have all of the data files in the same folder but that confuses me, I like to have my games organised in the backend)
-opened up launch.GUI from emulationstation (which opens up into the scummvm GUI)
-In the scummvm GUI I held down shift and clicked on mass add.
-I selected the scummvm ROMs folder and clicked add. (My games all showed up in the GUI)
– I then quit the GUI and restarted emulation station.
– with the 2.4.2 image it has a script that will automatically create .svm files for each of your games you added in scummvm in emulation station so you don’t necessarily have to go into the scummvm GUI all of the time, you can just open up and play your game right away.

– hopefully that will point you in the right direction for your needs.

P.s. if that doesn’t work it is potential that you might have downloaded a bad ROM (I’ve had issues with some from the source you cite)

[herbfargus]

I have a similar problem, I have been scraping the games through emulationstation, and the games that show up by default stay saved but when I scrape them manually one by one (by selecting and typing in different input until the right title shows up) It doesn’t save those changes. Any ideas on what I am doing wrong?

**EDIT

I take it back, I found out what I was doing wrong. For some reason if you are manually putting in metadata for roms through emulationstation if you shutdown or restart the system the changes are not saved. On the other hand, if you quit emulationstation back into the terminal the metadata will be saved.

[herbfargus]

That’s what I ended up doing, I started with a new image and it works just fine. I must have messed something up with the configs somehow (wish I knew what I broke). Sorry for my inexperience with all of this.

Thanks for all of the hard work on the project.

**EDIT

Updating the RPI kernel is what broke Scummvm

[herbfargus]

I switched the screen mode to 640×480 and it shows blurry start up text and loads with sound but no video

I enabled dispmanx and it said : “the program is calling SDL_GetVideoInfo. That shouldn’t happen”

I’m at a loss

[herbfargus]

Beautiful. I did what you said and it worked perfectly. Now all my games are working again.

Just as a reference for others, to document what I did:

CD RetroPie-Setup
Sudo ./retropie_setup.sh
Update setup script
Reboot
Option 5
Psxlibretro
Binary
Reboot

[herbfargus]

I must apologise as I am new to the whole raspberry pi/ Linux/ retropie thing.

Just for more information on the psx games I’ve been working with, on the 2.3 image rayman, harry potter and the chamber of secrets and philosophers stone all worked but all crashed on 2.42 image.

I understand that the most recent updates may have fixed some issues including the games I have.

Could anyone lead me in the right direction on how to update those binaries so I can test to see if those games now work?

[herbfargus]

For anyone that has issues with black borders, in my case in /boot/config.txt all I did was uncomment

disable_overscan=1

It worked like a dream, then with the 2.4.2 added video options as floob generously showed us on youtube (https://m.youtube.com/watch?v=3f9ldh2H7js) and changing my TV settings to “stretch” I’ve been able to get just about every game full screen.

[Author]

Posts