[quote=120404]Not trying to be an ass, but will there be a triple boot image for RP3 also? I suddenly got the urge tu use the RP as a computer as well! When/if that happens, can I just copy the .Kodi folder and the PI folder to transfer all my roms, settings, bios etc? Thanks!

[/quote]

Haha, yes there will be. I aim to get it done this week, just a bit busy with work for a few days then I will concentrate on getting it done and out asap. Its the one that takes the most setting up so I will get the Plex build out first then work on triple boot.

And yes – you can copy all your files from your current build, that’s not an issue and that is one of the reasons I love OpenELEC – a dedicated emebedded setup with its own filesystem. Makes it easy to work with and the added benefit of being ‘superuser’ by default means there is less worry about permissions when handling files. On the subject – I have a script that I set up to update KODI with my own build that is outside of the normal ‘Backup’ or ‘Update’ function of OpenELEC. I’m happy to share if you’d find it useful. It can be used to update from USB or from a static link on the web, so for example I create a backup of my KODI build, compress it and upload it to the web as (for example):

http://www.mysite.com/kodi.tar.xz

Then I have a script on my personal OpenELEC setup that I can click on named ‘Update KODI’ and it will download that file, extract it, check that the relevant files are present from the extract (and halt if they are not!), copy the existing custom keymaps I have setup for my KODI remote then proceed to delete my current setup and replace it with the downloaded setup and finally copy over my original keymap files and delete all the downloaded data that is no longer needed then reboot into my new setup. All this is done automatically for me at the click of a button and it means I can tinker with a separate OpenELEC build until I am happy with it then simply upload it to the net (using the same static link, replacing the old file) and update on my master dual boot setup and other Pi’s in the house. It also means that I don’t need to visit my mothers house every time she messes up her KODI setup (bless her!), so if it goes wrong she just has to click ‘update KODI’ at her end and it’ll fix itself automatically. Its a lot easier for me! ;)

Well, sorry that turned into a lengthy post! I will be writing a blog on how to set up that type of script so will post a link if anyone here is interested. It may sound like a faff but it makes things a lot more easy to update, especially if you have a few builds set up yourself or for family & friends.

All the best
Steve

[EDIT: Sorry, I misread your post initially and it looks like you’ve already tried some of the stuff I’ve suggested. Still, the rest should still be useful for narrowing down the problem.]

Hi there shortbuskid, you’ve got perfect timing – I’ve just started coming to these forums again after a while away. If any of the menu options I’m saying are wrong or not there or anything, let me know as I’m away from my Pi at the moment and doing this from memory.

First, I know it’s a hassle, but the most common cause of this not working is either file permissions or capitalisation, so double triple quadruple check those. Also, shootersf makes a very good point that I think I forgot to mention in the OP – this does only work on RetroArch based emulators.

I don’t think your problem lies in the main RetroArch cfg file. How it works is this: First Retroarch looks at its main cfg file to get its settings. Then it looks at the one for the core it’s using – this is the one that’s in the emulator’s individual folder in the configs directory. Any settings in there take priority over the ones in the main retroarch.cfg. Then when it’s done with that, it looks for a .cfg for the individual rom it’s loading. Again, any settings in that config take priority over the ones in the other two configs. What I reckon might be happening is that for some reason it either can’t find or can’t access the cfg files for the roms you’re loading.

Without the full details of what you’ve got running I can’t say exactly what your problem is, but there are a couple of things you might try to narrow it down. It could be because RetroPie has updated since I made this guide, and I’m not sure if its new way of working breaks something in my configs.

First, we’re going to check whether the overlays themselves are working properly in the first place. go into your configs folder, and go into the folder for a different RetroArch emulator that you’ve got some games for. Let’s say SNES, everyone loves SNES games. Back up the retroarch.cfg file in there, then try adding the overlay lines into that one – the lines beginning “input_overlay_enable” and so on. It doesn’t matter which of your bezel cfgs you specify here, just one that you know exists.

Save the file and try starting a SNES game. If it comes up with the overlay on it, then we know it’s not the overlays themselves. Doesn’t matter if it’s all in the wrong places or covers the game or whatever at the moment, we just need it to appear in the first place.

If that works, scroll down.

If it doesn’t, double check all the options you’ve got there – opacity, scale and so on. If it’s a big 1080p overlay which just has a bezel at the bottom and you’re running your emulator at a much lower resolution, the bezel could be working right but you can’t see it because it’s off the bottom of the screen. Remember, you need your retroarch render resolution to be set to “Use video output resolution” in the runcommand menu to get RetroArch to use the resolution you’ve set. You can test whether the bezel is going off the bottom of the screen by setting the scale to something like 0.25 – if that was your problem, you’ll see the bezel up in the top left corner.

So, if your overlay works when it’s in the console’s retroarch.cfg but not when it’s in the individual rom’s .cfg file, try this. Go into the runcommand menu, and open up the option for using a specific per-game config file. If the contents of that rom’s .cfg file appear there, then RetroArch will see it and you’ll have to come back to me to try something else. If they don’t appear, try entering in the contents of the .cfg file into that box, then running it and see what happens.

If none of this works, please feel free to come back on here and ask again. I’ve just wiped my Pi and started over and I’m just about to do the arcade games, so if I run into anything useful I’ll let you know. If you do need more help, it’d be really useful to know:

– What model of Pi you’re using.
– What version of RetroPie you’re using.
– Whether it’s from a clean install or whether it’s upgraded from an earlier RetroPie.
– Which rom and overlay you’re testing it with (assuming it’s one of the ones I made).
– What other emulators / games you have on the system.

The more I know, the better I can help – because knowing is half the battle ;-)

[quote=120041]Hi Steve,

Thanks a lot for creating these multi-boot images. Greatly appreciated.

I’m just wondering, is there any possibility to include Volumio as another OS that we can switch to?

The current stable version is v1.55. FYI, version 2 is in beta stage.

If this can be done, it will be an ultimate entertainment machine.

Thanks.

Cheers,
YungYaw

[/quote]

Hi. Its on my todo list so I will certainly give it a try yes! I have never used Volumio before so not sure if it supports running script shortcuts etc. but if it does then it shouldn’t be a problem, in theory.

[quote=120050]Amazing project! I am looking to migrate my exisitng openelec setup to this openelec/retropie dual boot. In the past I have kept all my openelec data as backup, by copying the whole “storage” partition. When I tried to do this with the dual boot sd card, I couldn’t find any kind of folder structure that was familiar to me, ie no storage and boot partitions. I know they are there somewhere, because when I ssh into openelec I can see them. However how can I access them when I connect the sd card to my laptop?

Thank you very much

PS: Is this openelec setup working with plexbmc?

[/quote]

Hmmm that is strange because the folder structure should be exactly the same aside from the storage and boot partitions will be numbered differently. Are you trying to view your SD card on a Windows machine? If so then you will only see the boot partition as that is the only ‘FAT’ formatted partition on the card. You’d need a Linux machine to view the other EXT4 partitions where the KODI data is held (or you can use a program to view and backup from within Windows).

Plexbmc should work fine for this, however I have never tried it.

[quote=120217]hey guys im new to this can anybody help me im trying to add my snes roms, do i add them to my sd card or to the usb drive help please

[/quote]

Hi.

You add your roms onto the SD card but to do this you will need to either SSH into your Pi or use a Linux PC to transfer them directly onto the SD card. I think you can also use a memory stick and it will transfer the roms automatically for you, but I have never tried this myself (have a search through the Wiki guide and Im sure it will explain in better detail than me). Good luck!

-I’m using the official power supply bundled with the pi3, so I’m guessing that’s not going to be an issue?
-I might give installing the broadcom bluetooth software a go and see if that helps.

Initially I was trying with my Dualshock….then I tried with an older SixAxis I have, then I went back to trying with the Dualshock….and….it worked?!

..I unplugged it, it vibrated and I could see that it had paired by the LEDs on the side of the controller. I was then able to configure all of the buttons within EmulationStation. I haven’t tried it again since, so god knows if it’s going to work next time I fire it up.

Seems like the pi does not like the controller being connected by a cable very much?

My problems are not over however – the controller does not work in all games.

-Doom, works fine.
-Quake, completely spazzes out inputting random buttons without me pressing anything.
-Duke Nukem, sort of works, some of the buttons don’t do anything.
Can anyone advise on this?

Also, Could we possibly try and get a collection of helpful commands concerning controller setup together? Such as
– how to clear the existing controller config?
– how to manually input the config with the references for the buttons included.
– how to manually pair the controller and then load emulationstation without disconnecting the controller.
– etc etc

Thanks guys.

[quote=119622]Hi,

Just to tell you smithers, great setup you have done.
I have a question, I’m curious how you did the dual boot, do you have a procedure on how to do the dual boot

Thank you

[/quote]

Thanks! I have full intentions on creating a guide on how to make these, I’m just currently looking for some reasonabley priced web hosting so I can create a blog style page to share it on (and also to host my builds on). Its not a majorly hard process really, just very time consuming!

[quote=119592] what do I do with my RP2 overclock setting “config.txt”? It’s set up with RP2 overclocking settings.. I want it to be properly configured for RP3 when I boot it up :). [/quote]

All you need to do there is comment all the overclocking lines out using a # symbol at the start of each line, and then it will boot into the standard clock settings for the device it detects (Pi2 or Pi3). Or you could dabble with Pi3 overclocking values of course but I don’t know what they are so can’t advise until I get one to play with myself!

[quote=119592]
Your duaboot image is the best I’ve ever tried by the way. I would never go back to running Kodi on Raspbian via Retropie. The performance difference is like night and day!

[/quote]

Thanks! I find it very stable and great performance too but like I said above I haven’t tried the Raspbian installer version of KODI in a long time so wasn’t sure if that was now as good as OpenELEC or not. Personally I prefer to have OpenELEC regardless and keep its own filesystem setup etc. It makes it easier to work with when its on its own partition and there’s no chance of one OS affecting the other.

[quote=119553]Hi,

thanks for the image file. i have been wanting to do this for ages.

i having an issue with the roms appearing in the ‘combined arcade menu’ i have added roms into imame4all, advmame and pifba. and roms appear in those menu items. (i end up with 2 classic arcade menus) but they dont appear under the arcade one.

also no artwork is appearing for any roms?

any help would be appreciated.

thanks

[/quote]

Hmm I’m not sure what could be wrong as it works at my end? Can I check you are using ‘.zip’ files for the roms? I’m guessing you must be as that is standard format (and they are appearing when placed in the other folders). I see that one of the recent changes to RetroPie incorporates an ‘Arcade’ rom folder as standard now so maybe my folder clashes with it (if you have updated RetroPie)? Not sure but I guess the issue will be eradicated when I use the latest version of RetroPie on my next dual boot build.

*Edit* – Ahh just realised as I pressed ‘submit’ – it sounds like you haven’t put the rom files into the /home/pi/RetroPie/roms/arcade folder, am I right? I made it so you had the option of using the separate folders as normal (ie mame4all, lr-mame etc), OR use the /arcade/ folder as a catch-all for every arcade system. You need to place the roms files into that folder before the ‘Arcade’ menu appears in Emulation Station, and you will also see screenshots appear (but bare in mind there will be a number of games that are not yet screenshotted due to the new versions of MAME now included that weren’t out when I originally made my image).

Hope this makes sense and Im not barking up the wrong tree but it sounds like that is where the issue is.

Cheers.
Steve

Hi.

I will be ordering my Pi3 in the next couple of days so will create a vanilla image using RetroPie 3.6 and OpenELEC 15.2 / 16. I’ll post a link soon as it’s ready.

As for “what is the advantage of a dual boot setup vs standard single partition setup” – well when I first made my dual boot setup it was the only way to guarantee a stable KODI experience by using OpenELEC rather than the Raspbian installer version of KODI (which had bugs at that time). You cannot install OpenELEC alongside RetroPie (as far as I know), so it has to be in its own partition. It makes for a rock solid KODI experience with a dedicated RetroPie partition with only it’s own filesystem layout and I can have a nice menu to be able to switch between the two OS’s seamlessly. It may not be for everyone, but for me it’s perfect. Its also the only way you can use Plex and RetroPie together (as far as I know). Not that I use Plex, but a lot of folk were looking for a solution to that.

Hope that answers your question! I guess If you’re having no issues with the Rasbian installer version of KODI then there’s no need for a dual boot build. I prefer OpenELEC so this is my only option. It was also a good Linux learning tool for me along the way!

All the best
Steve

From Retropie:

Bus 001 Device 009: ID 0810:0001 Personal Communication Systems, Inc. Dual PSX Adaptor
Bus 001 Device 007: ID 0781:5575 SanDisk Corp.
Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 008: ID 0609:031d SMK Manufacturing, Inc. eHome Infrared Receiver
Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 004: ID 24ed:0451
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

From Raspian:

Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 0781:5575 SanDisk Corp.
Bus 001 Device 005: ID 0e6f:011f Logic3
Bus 001 Device 004: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@raspberrypi:~ $