[d3s1]

[quote=103928]Okay so what are people’s thoughts on creating a new image based on retropie 3 final? Is it worth it or can the changes be obtained via updating the setup script?

Also, do I go with OSMC or OpenELEC? Let me know.

All the best
Steve

[/quote]

My personal opinion on the matter:

The novelty of releasing multiple images based on multiple distros and over multiple versions of each said distro is going to wear off quickly — and is simple not realistic to maintain in the long run (unless you found a way to automate most of it).

As such I would suggest sticking with “stable” releases, that is the latest stable of Retropie (v3) and OpenELEC (which would be HELIX at the moment). While OpenELEC Helix does have the SDCARD issue, you could simple link to the tar file and tell the user IF they have SDCARD issues to put the .TAR file in the Update folder and the issue will be resolved (or apply the update and build it in). I suggest OpenELEC over OSMC because in my experience there are compatibility issues with OSMC and some plugins.

That now leaves VANILLA vs CUSTOM. While I’m a firm believer in releasing both, if you had to pick then I’d say go with your CUSTOM given all the work you did on the themes.

Just my 2 cents…. :)

[d3s1]

I’ve been playing with this setup/configuration for a few days and I wanted to share my experience thus far.

– FIRST: HUGE thanks to smithers for laying out a “packaged” groundwork for this. Not only does it take time to understand how to use NOOBS, creating the images, but the Skinning of both OpenELEC and integration with Retropie is also time consuming. That said, smithers has provided the basis for anyone to take this model and adjust it to their needs.

For example: I’ve created my own images of OpenELEC and Retropie for backup purposes using NOOBS. As smithers mentioned, this is quite powerful because it allows you to restore to essentially any SDCARD (provided it meets the minimum space needed) without running into sizing issues (not all 16GB cards are the same size for example) as you would with a typical block-type backup/restore using Win32Imager. Also this method allows you to easily restore/install to a larger size SDCARD (and potentially a smaller one too).

Anyway along the way, I’m sharing these tidbits for anyone looking to do the same (requires some technical knowledge and familiarity with linux).

BOOT into OPENELEC
==================
SSH in

mount -o remount,rw /var/media/Media (Mounts the USB stick as writeable)

(Create boot image)
cd /flash
tar -cvpf /var/media/Media/OpenELEC_RPi2_System.tar .

(Create storage image)
cd /storage
tar -cvpf /var/media/Media/OpenELEC_RPi2_Storage.tar .

BOOT up Retropie
================
SSH in

(Create boot image)
cd /boot
tar -cvpf ~/BOOT.tar . –exclude=’System Volume Information’

(Create storage image)
cd /
sudo tar -cvpf ~/retropie.tar . –exclude=proc/ –exclude=sys/ –exclude=dev/pts/ –exclude=home/pi/BOOT.tar –exclude=home/pi/retropie.tar

(this will include the ROMS folder)

THEN

xz -9 -e <label>.tar all the TAR files! I had to do this off the pi because of memory constraints.

THEN

With all your tar.xz files created, you can use smithers download as a starting point to easily replace those images (.tar.xz) with ones you have created.

Don’t forget to edit the NOOBS partitions.json is the respective “os” folders to adjust nominal size of partition and size of the tar file uncompressed. This command is helpful to determine the uncompressed size of a .tar.xz file: sudo xz -l root.tar.xz

Other links that may be helpful:

http://www.i-programmer.info/programming/hardware/7688-real-raspberry-pi-custom-noobs.html?start=1

https://github.com/raspberrypi/noobs

[d3s1]

[quote=103790]Hmmm, I’ve just been looking into Plex and it is not at all what I thought it was. I thought it was another variant of KODI, but it appears not; rather it is a standalone media centre, with no addon support (to speak of)?

From the outset, I dont think it will be possible to create a link to boot RetroPie from in there so I think its a lost cause.

I think instead, when the stable v15 of OpenELEC is released I will include the PlexBMC addon, which kind of gives the best of both worlds (so I read anyway!).

[/quote]

Tried your latest vanilla image.

Have you tried *popular* plugins on OSMC? I just did and they’re not working as expected — video does not come up.

Anyway — I decided to smash your images together. I wanted VANILLA RETROPIE + STABLE OPENELEC. I took your original (first image) based on Retropie & OPENELEC KODI 5.08 HELIX and replaced the RETROPIE portion with the image from the latest VANILLA. Then booted into KODI 5.08 and applied the .TAR SDCARD fix upgrade I’ve been mentioning.

Now all is good in the world – I have VANILLA Retropie + Fully STABLE KODI 5.08 + SDCARD FIX plus all the *popular* plugins working.

[d3s1]

[quote=103748]

Ok so now that I have had time to play with OpenELEC Isengard RC1, I must say I’m a little disappointed with the stability of it. Normally it is rock solid but it’s crashed out on me a few times and I get a constant nag about an ‘extended info’ script needing to be installed. I’m sure any such issues will be ironed out when Isengard is ready for final release but for now, I’m going to move away from it.

Vanilla build is still my first priority! Expect it soon (how many times can I say that until you get annoyed waiting for it? Haha).

All the best,
Steve

[/quote]

If there’s a need to revert to Helix, there is a build that addresses the SDCARD issue in my previous post – here’s the link: http://openelec.tv/forum/124-raspberry-pi/75281-openelec-5-0-3-still-corrupts-sd-card-on-pi2?start=210#137875 The way I’ve done this is in the past is to download the tar file in the 1st link and put it into the “Update” folder when you browse to the IP of your running OpenELEC Helix instance. In other words, install Helix then update using the tar file. There’s also the .img file which could be even easier, though I personnally haven’t tested it.

As for the Vanilla, yes please! :)

[quote=103734]

The thing that makes it important to me personally is that now I can make a backup of my entire 32GB build via a .tar.xz file and use it as a custom installer option via USB drive, making life much easier if I upgrade to a 64GB card, or when my current card breaks (its been abused alot by this venture!), I know that any 32GB replacement card will work (.img files have an exact size that needs to be adhered to whereas this NOOBS method doesn’t).

[/quote]

I’d love to hear more about this feature. I’m sure you’ll release details as to how to do this. Thanks!

[d3s1]

[quote=103669]

mommekjr wrote:

Thanks 4 the build

A link to RetroPie_KODI_DualBoot_V4_SS.zip on Uptobox: RetroPie_KODI_DualBoot_V4_SS.zip – 934.3 MB

My wireless 360 controller, keeps flashing, anybody got that same problem? maybe a solution?

Many thanks fro re-uploading the file!

As for the controller – I have seen this mentioned a few times in the forums and I know there is a fix for it. Have a check in the ‘Controller’ section of the forum and you should find your answer there.

@mayki – is there any added benefit in using the Amber skin over Aeon?

[/quote]

That link doesn’t seem to work everyone — (not all countries). I’ve re-upped in the USA and will also place the vanilla image here when available:

[EDIT] LINKED REMOVED

EDIT: Just linked this thread to reddit for some visibility: http://www.reddit.com/r/raspberry_pi/comments/3gcx7j/rpi2_retropie_openelec_kodi_dual_boot_disc_image/

[d3s1]

[quote=103617]OK then – time to share my new build! I am taking a different approach in that I’m sharing a folder instead of a direct link this time – Let me know if that doesn’t work out for you (I will post a direct link too at the end of this post).

https://www.dropbox.com/sh/ughxu46mu4wy61g/AAC7RzLRXvPwVmsbqU4xLt-Ka?dl=0

So this is v4. I have included a full changelog in the readme file, but in a nutshell:

* Re-built OpenELEC from scratch again, based upon Isengard RC1 (v15). This fixes potential SD card corruption issues (see earlier posts in this thread)
* Re-enabled Apple II, Macintosh and PC and themed them all
* Fixed Atari Lynx emulation by reverting back to an older binary
* Fixed Gameboy theme (and changed it, along with a couple of others)
* Changed the look of KODI – using the same Aeon theme (its not an option to change), but I have changed the backgrounds and added a few extra menu items in.
* Added my own slide in the NOOBS install, instead of using the default OpenELEC slides

So it all seems stable, Ive fixed all bugs / annoyances that I have introduced, so that’s cool, and I have installed the latest KODI beta. First impressions of Isengard are that it runs nice and fast. I haven’t seen any major issues, but I have seen a few little niggles, mainly when installing addons (a persistant box pops up telling you that an extra resource needs to be installed but it never installs itself?), and also the ‘zoom’ animation in iVue is no longer smooth. I decided these weren’t show-stoppers and of course we need to remember this isn’t a final release of Isengard, but everything else seems fine.

So please download, install, let me know what you think!

I will work on the ‘vanilla’ build over the weekend and upload it.

All the best,
Steve

p.s. here is a direct link to the new build if the folder share above didn’t work:

https://www.dropbox.com/s/qpksky7sjozswqf/RetroPie_KODI_DualBoot_V4_SS.zip?dl=0

[/quote]

I can now confirm this latest release of OpenELEC resolves the SDCARD corruption issues. This ROCKS!! A HUGE thank you. Looking forward to the vanilla build!

EDIT: To clarify, I believe we’re all of the same understanding. Vanilla means a KODI menu in Retropie, and in OpenELEC the updated skin to support menu item that boots into Retropie, no other changes.

By the way, I’ve noticed a typo in the OpenELEC menu item for gaming – It reads “Lanch” instead of “Launch”.

Longer term suggestion: A method (script or directions) to update with the latest retropie and openelec vanilla images on our own. The vanilla image will allow power users to do “their thing” — really awesome of you to do this.

EDIT2: Not sure what the OpenELEC skin provides, but menu items for POWER and SETTINGS I assume will also be included.

[d3s1]

[quote=103483]Crikey, I didn’t know anything about the openelec issues at all. I have burned it to Sandisk 4gb/8gb/32gb, toshiba 8gb, Samsung 16gb/32gb cards and never had a single issue with corruption or otherwise? It is the 5.0.8 build that I use (and included in my install files), which is the latest stable build, but reading the thread you linked it would seem that version is affected by the corruption issue.

There is a beta version available (5.95.3) that has the ‘SD Card fix’ built into it – I can use that in my next build if people would prefer? A stable v6 is due soon by the looks of things too.

Wicd-Curses package – this is removed by default in RetroPie due to it (potentially) affecting performance. It can be easily re-installed via the RetroPie Setup Script though if I remember rightly so I would rather leave it out (as default).

Borders vs Stretch – bit of a funny one this really. I spent a massive amount of time setting all the video modes up, even to the extent of ‘per rom’ video modes to make them stretch to the full screen. Un-doing all this would take me some time to do and I would then have to offer 2 builds (16:9 build and 4:3 build), so I’m not sure if its feasible. It will also be a bit counter productive for me to do since its just a preference thing rather than a bug. I did however add in my own comments in the ‘aspect ratio’ section of the main ‘retroarch.fcg’ file showing the different codes you can use to set different aspect ratios. Using that you can at least set the libretro emulators to a different ratio?

OpenELEC timezone setting – this is present in my build, in the same place as it should always be? You need to go to the following to get there:

Settings > Appearance > International

Once in here you can change everything to suit your region.

As for a standard ‘vanilla’ build of both systems – yes I can do that, no problem. However, I could not leave the skin as standard in KODI because the standard skin does not support direct linking to the Advanced Launcher addon that I use to swap the partition boot instruction. This means the user would have to go into Programs > Advanced Launcher > Default > Games to launch RetroPie, which is un-intuitive. I use Aeon because it supports custom menu items but I would be happy to change to a different skin that supports this, if that was the general consensus, however I only know of Aeon that does (and I quite like it as is to be honest).

Hope this helps – happy to hear other opinions on this.

Cheers.
Steve

[/quote]

On using the NEW BETA of OpenELEC w/ SDCARD FIX: YES please! As in its current form this is not usable for me and probably others with the same issue.

On wicd-cuses: Understood. I imagine soon there will be another RC with wicd removed.

On vanilla build: Worth some thought on doing this — essentially the absolute bare minimum changes to make your image work (understood on OpenELEC skin). This will allow others to quickly adjust to their needs from the baseline defaults as opposed to figuring out how to undo your specific changes (like aspect ratio).

Thank you taking these into consideration!

[d3s1]

[quote=103362]

d3s1 wrote:

First off, I have to say this is INCREDIBLE and a huge thanks to smithers for putting this together.

I did give this a spin last night with the latest image and while Retropie boots fine, OpenELEC stalls indefinitely at boot (at the OpenELEC boot logo). Hard rebooting doesn’t help and ultimately leads to corruption of the sd card.

Anyone else have this issue?

Hmmm that doesn’t sound good. Can I ask how you formatted your SD card? NOOBS is a bit funky on how it partitions your card and if you haven’t partitioned it just how it likes it then it can spit out errors when trying to boot.

I had it fail on me once because I had done my own ‘un-partitioning’and formatting via Gparted in Linux – it didn’t like it and had troubles with the fat32 boot partitioning. It was OpenELEC that was affected Funnily enough.

All I can recommend is to use the SD Formatting tool I mentioned in the Readme file. Using that fixed it for me and it all works perfect now.

Has anybody else had this issue?

[/quote]

I formatted the SDCARD exactly per your instructions to begin with. After some testing I’ve determined that it is hit-or-miss on whether OPENELEC will boot. However, I have run across this and here’s the issue to my knowledge:

– OpenELEC has a stability issue on the RPI2 leading to hang on boots and SDCARD corruption. There is a whole thread on the topic here: http://openelec.tv/forum/124-raspberry-pi/75281-openelec-5-0-3-still-corrupts-sd-card-on-pi2?start=210. I specifically refer you to the .IMG file available in this post which resolves the issue: http://openelec.tv/forum/124-raspberry-pi/75281-openelec-5-0-3-still-corrupts-sd-card-on-pi2?start=210#137875

I do not know what build you are running but the fix has been applied to some dev builds. Either way, incorporating the fix (via the IMG file) should help resolve the issue.

OTHER:

– Retropie – the package wicd-curses is missing; hence choosing “configure wifi” from the menu will fail. I do not have an ethernet cable anywhere nearby. My suggestion is to install the package by default until it is otherwise removed or replaced in another version of Retropie.

– Retropie – Some folks may prefer the “black borders” instead of stretch to maintain the original aspect ratio of the game. How does one undo the change you made?

– OpenELEC – There is no way to change the timezone – the option is not available as it would be under the default skin.

Other thoughts:

Would you consider a build that sticks to the bare defaults of both OpenELEC and Retropie (skins and all) with the only modification being the dual boot and the menu options to reboot between the Operating Systems?

Looking forward to seeing these issues sorted out. Keep up the great work!!!

[d3s1]

First off, I have to say this is INCREDIBLE and a huge thanks to smithers for putting this together.

I did give this a spin last night with the latest image and while Retropie boots fine, OpenELEC stalls indefinitely at boot (at the OpenELEC boot logo). Hard rebooting doesn’t help and ultimately leads to corruption of the sd card.

Anyone else have this issue?

[d3s1]

The B+ struggles with SuperFX SNES games (e.g. Yoshi’s Island, StarFox). I’m curious to see if those performance issues will go away :)

[d3s1]

I too was having the same issue with EmulationStation prompting to re-configure the controller (ps3) bindings every time on reboot, also many times the controller would not even be detected.

I finally have my PS3 controller working consistently. It turns out there was a two-year old comment on this very blog that hinted at the the solution. What’s happening is that EmulationStation is starting up too quickly — not allowing enough time for the PS3 controller to sync over bluetooth and setting itself up as a joystick.

The fix:

1. Start the retroie-setup script and disable the splash screen (there’s an option for this)

2. Edit the /etc/rc.local file with your favorite editor:

Above the “exit 0” statement enter the following:

echo "Sleeping for 30s.  Sync your controller now..."
sleep 30s

Now every time you boot the Pi, it will notify you to sync your PS3 controller (simply press the PS button on the controller), then EmulationStation will start thereafter.

On a side note, RetroPie 2.3 has a built-in controller profile for the PS3 controller — meaning you do not have to manually map buttons in RetroArch. The “hotkey” by default is the SELECT button. So SELECT+START exits, SELECT+L loads last save, etc.

[Author]

Posts