[HowTo] RetroPie and OSMC: Retrosmc - Retrogaming on OSMC

Rather strange. But it is a crude hack anyway.
if you run some command with cec-client from commandline, will kodi still stop responding to cec commands from the remote?

Could you also post the contents of your retropie-watchdog script please? You didn’t change anything in there manually, right?

Also you can try to run the update scripts command in the installscript again.

After last update (to Kodi 16) i installed RetrOSMC and it works fine :slightly_smiling: (so I can confirm that is still working fine in last version with a fresh install)

1 Like

Something new about the support of the Logitech Rumblepad 2?

Not really. PR for more rumblepad modules is open.

Hallo everyone! Installed now RetroPie using this script over OSMC (with latest release & upgrades).
Everything works, including a wireless keyboard and 2 PS3 controllers over BT.
I’ve only one problem, that somebody already reported and that I can confirm: PSP emulation is someway broken.
It works out of the box in a normal RetroPie 3.5 install by SD card image, but doesn’t work with the Retrosmc script install method.
I tried with a Space Invaders Extreme image (which I’m shure is 100% working): it starts the emu, loads the PS3 controller and than just quits back to Emulationstation.
Exactly the same happens with other games. Has somebody figured out a solution or workaround to this?

Just to let you know:
It also works on the Pi 3 :slight_smile:

3 Likes

It sure took me a while to get back to this…

if you run some command with cec-client from commandline, will kodi still stop responding to cec commands from the remote?

Unfortunately, I only use cec for turning the tv off when OSMC is left idle and back on when a key is pressed again. I use a flirc plugged into the pie for my remote control. In other words, I don’t have a way to test this out. However, I have in past versions (before a clean install) played around with cec-client and found that triggering it via commandline would disable (until reboot) the on/off function of cec within kodi. Prior to you adding this hack into the script, I had attempted to do my own similar hack…however, clearly, I was never successful.

Could you also post the contents of your retropie-watchdog script please? You didn’t change anything in there manually, right?

I never made any changes to the retropie-watchdog script. However, here is the contents of the script as it is currently on my pi:

#!/bin/bash

# Script by mcobit

. /home/osmc/RetroPie/scripts/retrosmc-config.cfg

# ugly fix for people having trouble with CEC

if [ "$CECFIX" = 1 ]; then
sudo /usr/osmc/bin/cec-client -p 1 &
sleep 1
sudo kill -9 $(pidof cec-client)
fi

# deactivate the hyperion deamon if it is running

if [ "$HYPERIONFIX" = 1 ]; then
   if [ $(pgrep hyperion) ]; then
      sudo service hyperion stop
   fi
fi
# give emulationstation time to start up

sleep 8

# activate hyperion daemon if it is not running

if [ "$HYPERIONFIX" = 1 ]; then
   if [ ! $(pgrep hyperion) ]; then
  sudo service hyperion start
   fi
fi
# check for emulationstation running

while [ true ]; do
    VAR1="$(pgrep emulatio)"

# if emulationstation is quit, clear the screen of virtual terminal 7 and show a message


            if [ ! "$VAR1" ]; then
                    sudo openvt -c 7 -s -f clear

# restart kodi
    sudo su -c "sudo systemctl restart mediacenter &" &

# exit script

                    exit
            else

   # if emulationstation is still running, wait 2 seconds and check again (could probably be longer, but doesn't seem to impact performance by much)


                    sleep 2
fi
done
exit

Also you can try to run the update scripts command in the installscript again.

I will try this and see if anything changes.

In the end, this fix would be nice but certainly not a huge deal. Thanks again for all your help.

I fixed the problem on my Rpi2 with Osmc.

It took me ages, but I narrowed it down to the file: http://lxr.free-electrons.com/source/drivers/hid/hid-lg.c#L728

I have come to the conclusion that rumble option is just not working. I changed:
785 { HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_RUMBLEPAD),
786 .driver_data = LG_FF },
787 { HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_RUMBLEPAD2_2),
788 .driver_data = LG_FF },

To:
785 { HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_RUMBLEPAD),
786 .driver_data = LG_NOGET },
787 { HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_RUMBLEPAD2_2),
788 .driver_data = LG_NOGET },

Recompiled the kernel module hid-logitech.ko and it started working. Previously running jstest /dev/input/js0 on

the Cordless RumblePad 2 would just not respond. No response at all. I got rid of the message: "logitech: probe of

0003:046D:C219.0001 failed with error -1".

To recompile the kernel module, well, I can list resources I used:

I did not try to figure out why the Rumble was not working. I only got it working on jstest, but I must see what

happens in Kodi and when I get moonlight working.

1 Like

Hello. I’ve recently installed oscm to my RPi 2 and even more recently added retropie to osmc with the script provided by mcobit (thank you for that) and it seems to be working without any issues. I may have simply overlooked this but can you tell me how to get my roms installed?

This is cool. Can you do a pullrequest with those changes at osmc github?
The rumble feature is not working because it needs a separate module. A pullrequest for that is still waiting to be merged.

Edit: Maybe the RumblePad will start working with my PR as it seems to need the rumble module for correct initialisation.

You copy the roms into /home/osmc/RetroPie/roms/systemname/

BIOS files go to
/home/osmc/RetroPie/BIOS/

Sorry,

I am not expert on linux, but this option can make my Four Rumblepads run fine under OSMC with retropie and Moonlight?

I am waiting to use my gamepads, I know its needed time to solve problems and I will wait. Only want to know if this can help to solve it, and if I must only wait for official update with this fix :slightly_smiling:

thanks @mcobit @chimerahitman

The additional modules will be in the next update.

1 Like

Could you do me a favor?
You seem to know how to compile the osmc kernel, so could you recert your changes and instead build it with all the LOGITECH modules activated and see if it works then, too?

Edit: I don’t have this pad so I cannot check myself unfortunately.

So, I received my Pi3 today. I setup OSMC and my other stuff, all works great. Now, before I install RetrOSMC with your script (As I did with my Pi2 last year, worked great!) I was curious: I saw on the EmulationStation website, they have 64bit builds for x64 architectures. I guess, the downloaded RPI image is 32bit.

My questions: Could I compile a 64bit build? And would it even make sense, since osmc (and the kernel and everything at that point) is 32bit? Would 64bit have some advantage in emulation against 32bit?

I know, you just provide our cool installer, but the topic is already 750 posts long, so I assume, you know one thing or two about this stuff.

Last question: Should I wait for your 0.008 update you mentioned 2 posts earlier?
I’m just curious if N64 games now work without a hassle. With my Pi2 PSX Games worked flawlessly, but N64, some games did (Mario64), some games had really bad frame rates (Conquers Bad Fur Day, Waverace)…

edit: Followup question: I just browsed a little more, and emualtionstation seems dead, at least from their github. I saw other front ends like attract mode, big box (currently only win) and Hyperspin and others… Does it make sense to change to a frontend, that is actively maintained? Would it be possible to launch games directly from Kodi? Like browsing and starting movies, but with games?

tl;dr: 64bit? Yes, no? does it even make sense now? will it have an advantage if debian (osmc) will go 64bit?

I think osmc will not go 64Bit in the short term.
64Bit can have advantages but they will not be huge in case of emulation. N64 running all games flawlessly will also not happen because of other things than processor speed or architecture. So don’t worry about 64Bit.

I meant osmc update not retrosmc update :wink:

Hi mcobit, firstly thank you so much for your work, it is awesome!

I have some doubts about updates, I have installed 0.007 some time ago, however, RetroPie has update his Setup Script to build 3.6.

Do you know how can we update our RetroPie version to get the same version than RetroPie releases?
When I select option 4) in 0.007 Retrosmc Script, it updates the Retropie Scripts via wget command, but we should execute other command to do the update right?

Thanks in advance :slightly_smiling:

Basically just do the installation again.
Back up altered config files before.
It will update to the latest RetroPie version.

I have tried with no luck :frowning:

---- Scenario 1 -----
1st.- Click on option 4) for update scripts.
2nd.- I see RetroPie-Script Setup version 3.5, then, click on Update RetroPie Script.
3rd.- Install binaries & reboot
4th.- When I try to launch RetroPie via Retrosmc launcher, RPi2 reboots, I can see Emulestation screen only 1sec. & reboots automatically

---- Scenario 2 -----
1st. Uninstall Retropie version 3.5 via Retropie-Script Setup
2nd.- Repeat Scenario 1

Maybe I should try without updates and install with version 3.5 Retropie-Script Setup, but I’m so tired for today :blush:

Not sure what you are doing…
Best would be to start with a fresh card I think.
I have no clue what the status of retropie or your system is right now.