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

[Theetjuh]

I just made a symlink so 4.1.5-1-osmc points to 3.18.11-v7+
That made it work as well

[giovanne]

do you have to add “sudo sixad -start” somewhere in the starting scripts for emulationstation?
I’m struggling with that…

[Theetjuh]

I changed the chroot.sh script abit for this:

sudo HOME="/home/pi" /usr/sbin/chroot --userspec 1000:1000 "$INSTALLDIR/retrosmc" sudo hciconfig hci0 pscan
sudo HOME="/home/pi" /usr/sbin/chroot --userspec 1000:1000 "$INSTALLDIR/retrosmc" sudo service sixad start
sleep 5
sudo HOME="/home/pi" /usr/sbin/chroot --userspec 1000:1000 "$INSTALLDIR/retrosmc" emulationstation

but I think I’m just gonna follow my own guide for installing the ps3 controller and let the chroot only do emulationstation.
gonna try that now, luckily I got multiple sd cards for testing

[giovanne]

Thanks, that is also working for me. (changed to only linking and mod in chroot.sh)

Will waiting for your additional findings…

[dyer]

nevermind… I just removed the (/nfs) part and it seems to have worked.

[Haris1977]

mcobit thanks 4 your script:) It works ok in my rasp1

Well, i am facing a “problem” which i assume has nothing to do with you but with how your script is working.
I guess that when retrosmc starts, kodi somehow stops (the script “kills” kodi). That is a problem, especially if you have enabled “send inactive source command when stopping kodi” in kodi’s hdmi cec settings…

Having that cec command enabled, when retrosmc starts, TV signal is reverting back to were it was. Having that command disabled, retrosmc starts ok, but when you shutdown kodi it stays on hdmi mode (doesn’t revert back to TV) because the command is disabled. So… Any way to use retrosmc with “send inactive source enabled?”

In other words…Is there any way to “pause” kodi when retropie starts-and not killing it?

[Theetjuh]

Just using my ps3 install guide works like a charm with the chroot version of retropie … no hastle within the chroot anymore

[mcobit]

Hmmm. Didn’t even know this option existed

I guess that what it does is to disable the hdmi by tvservice or sending a command that the hdmi source is inactive. If you can find out what the command is to enable it again, you can put that into the chroot.sh file to make the hdmi come up again after kodi closed it probably.

Edit: This seems to be a function in the cec libs. So not sure how to do it from commandline. If anybody knows, please post it here.

[PTM]

Retropie is workin great!

I have a question… y config my joysitcs an worked perfect, but after i unplug my RP2 or make and update to osmc (i don´t no wich of them make the problem), my jpoysticks lost the configuration i have made (several of them inside MAME whith specific behaviours).

Is any way to backup those config? i will loose them any time i update or unplug? can i save them into retropie?

Thanks in advance.

[giovanne]

Can you point me to your ps3 install guide please …

[mcobit]

Are you using a retroarch mame version?
If so you need to put your config into the retroarch.cfg in /opt/retrosmc/opt/retropie/configs/all
Else the config stored there will be loaded by default.

[jboy]

The following command will send an on command through CEC.
echo “on 0” | cec-client -s

However, my experience is that this can cause some issues the next time Kodi attempts to use CEC as the CEC-client command is seen as a different device than Kodi (I think that is the issue, anyway).

[Haris1977]

So…there is nothing we can do:(

[mcobit]

Bah. There’s always something you can do. I’ll try some stuff. Feel free to join.

[Jace055]

I came here just to say thank you!

I just installed the latest OSMC with your latest script and it works perfect with an off brand wired Xbox 360 controller on a Pi2.

Thank you mcobit!

[Theetjuh]

You can find lots here: [HowTo] Installing RetroPie alongside OSMC RC (the easy way):

@Theetjuh

Plug-in USB Bluetooth dongle
Go to My OSMC → Network → Bluetooth
Enable Bluetooth

If Bluetooth isn’t listed you probably don’t have a compatible dongle.

SSH into your RPi device

The command ‘hciconfig’ should display something like this:

hci0:	Type: BR/EDR  Bus: USB
	BD Address: XX:XX:XX:XX:XX:XX  ACL MTU: 1021:8  SCO MTU: 64:1
	UP RUNNING 
	RX bytes:1212 acl:0 sco:0 events:72 errors:0
	TX bytes:2150 acl:0 sco:0 commands:72 errors:0

All necessary build and tool packages:

sudo apt-get update
sudo apt-get install build-essential checkinstall pkg-config joystick lib-usbdev libbluetooth-dev -y

Build the tool which pairs your PS3 controller with your bluetooth device:

wget http://www.pabr.org/sixlinux/sixpair.c
gcc -o sixpair sixpair.c -lusb

Build the Sixaxis Manager which will let use use the controller as an input over bluetooth and USB:

wget http://sourceforge.net/projects/qtsixa/files/QtSixA%201.5.1/QtSixA-1.5.1-src.tar.gz
tar xfvz QtSixA-1.5.1-src.tar.gz

wget https://bugs.launchpad.net/qtsixa/+bug/1036744/+attachment/3260906/+files/compilation_sid.patch
patch ~/QtSixA-1.5.1/sixad/shared.h < compilation_sid.patch

cd QtSixA-1.5.1/sixad
make
sudo mkdir -p /var/lib/sixad/profiles
sudo checkinstall

Create a profile for the controller:

sudo nano /var/lib/sixad/profiles/default
enable_leds 1
enable_joystick 1
enable_input 0
enable_remote 0
enable_rumble 1
enable_timeout 0
led_n_auto 1
led_n_number 1
led_anim 1
enable_buttons 1
enable_sbuttons 1
enable_axis 1
enable_accel 0
enable_accon 0
enable_speed 0
enable_pos 0

Connect your controller with USB to the RPi and run the following command:

cd /home/osmc
sudo ./sixpair

If that succeeded, you can unplug the controller and test if the controller connects with your bluetooth device:

sudo hciconfig hci0 pscan
sudo sixad —start

If the worked you can setup Sixaxis Manager as a service and start it

sudo update-rc.d sixad defaults
sudo service sixad start

You can use the joystick test utility to see of all buttons work:

sudo jstest /dev/input/js0

I tried to make some udev rules to make everybody’s life easier, but that didn’t work for one.
Add ‘hciconfig hci0 pscan’ at the end of /etc/rc.local just before exit 0.

To make it automatically that when you attach an controller with usb to the system, make this udev rule:

sudo nano /etc/udev/rules.d/99-sixpair.rules
ACTION=="add", KERNEL=="js[0-9]*", SUBSYSTEM=="input", SUBSYSTEMS=="usb", RUN+="/home/osmc/sixpair"

Hope this helps most of you, there is still some controller configuration to be done, please have a look here where I got most of the stuff from.

[giovanne]

Thanks. I will try it. What are the advantages doing it like you? Can I use the ps3 controller also in Kodi or is there more?

And what I doesn’t understand is, I thought as commented in the thread that It should also work directly in the OSMC-Bluetooth menu to pair/connect it. Or am I wrong? (Is there sixpair, … missing?)
I think that would be the real target, because then there is no need to ssh into the pi.

At the moment the ps3 controller in bluetooth mode is working well in emulationstation/retropie with our workaround from yesterday

I will follow which way it will be going…

[Haris1977]

+1

[totuccio28]

excuse the delay I solved thanks

[mcobit]

I have to verify it at home, where I have a cec capable tv, but I think I found a way:
If you send a manual cec command via cec-client, the built in cec client in kodi will not function anymore until you kill all instances of cec-client and restart kodi.
It is an ugly hack, but you can send some cec command via cec-client at starting of the retropie.sh script and thus disable kodis ability to send the inactive-source command on quit.
When kodi is restarted by emulationstation quit, it will have control of the cec again and will work as normal when you shut it down from kodi itself.
That’s the theory…