[HOW-TO ] retrOSMCmk2: a RetroPie installer on the Vero4K

Greeting and happy New Years I installed this GitHub - hissingshark/retrOSMCmk2: RetroPie installer for OSMC on the RPi, Vero4k/4K+ and the VeroV
Thought it would work but it does not open when I launch from Games section of the GUI.

This is after a clean install so not sure how or why the files would be corrupt or missing. This is from my log file. I am using a Vero V.

2025-01-10 18:59:52.137 T:5307 info : retrOSMCmk2 Launcher: “/home/osmc/.kodi/userdata/addon_data/script.launch.retropie/data.xml” missing or corrupt on this run
2025-01-10 18:59:52.137 T:5307 info : retrOSMCmk2 Launcher: “/home/osmc/.kodi/userdata/addon_data/script.launch.retropie/settings.xml” missing or corrupt on this run
2025-01-10 18:59:54.175 T:5222 info : Loading skin file: DialogAddonSettings.xml, load type: KEEP_IN_MEMORY

Any assistance I would greatly appreciate. Thanks in advance.

After another new install of OSMC and trying your script I receive the following error :
submodule/RetroPie-Setup/retropie_packages.sh: line 20: /home/osmc/retrOSMCmk2/submodule/RetroPie-Setup/retropie_packages.hidden: No such file or directory
FAILED!───

Interesting. Unclear why you got two different errors, despite using the same installer on clean OSMC installs. I’ll have a look when I’m back on the grid.

I tried it twice and receive the same error both times. I even tried installing the penultimate OSMC for the Vero V and it gave me the same error.

Sorry, I can’t reproduce your error.

I’ve just:
Cloned and run my installer on my clean VeroV.
Performed the Basic Install from the RetroPie-Setup menu.
Put ROMs in the folder.
Installed the addon.zip in Kodi ( without the pyxbmct module error that is occasionally reported above).
Launched the addon from the games section.
Tested GB and SNES.


Your initial logs from the “failed open” were actually normal. It is just reporting that you haven’t saved any settings in the addon yet.
Did the addon fail to start at all? Or did the addon window open, and it failed then you clicked on “Launch!”?

The second error looked like it was when you were running the install script from the command line. As does the third/screenshot.
Strange you get this now - when you successfully installed it on your earlier attempt. The inconsistency makes it hard to diagnose.

Does this matter? I am ssh-ing into the machine doing this? What version of VeroV OS are you using?

The addon window never opened. I shall attempt a clean install again once I double check the version operating system you are on.

No, that’s how most people would access the command line on the Vero.
I’m running the latest version.

Running on OSMC Vero V with Open Source Media Center 2024.10-1, kernel: Linux ARM 32-bit version 4.9.269-70-osmc

$ cat /etc/os-release                ┌───────────SDL2 Installation──────────────┐
PRETTY_NAME="Open Source Media Center"                             │                                          │  
NAME="OSMC"                                                        │ Just (re)installing SDL2 libraries to    │  
VERSION="October 2024"                                             │ ensure custom versions are in place...   │  
VERSION_ID="2024.10-1"                                             │                                          │  
ID=osmc                                                            └──────────────────────────────────────────┘  
ID_LIKE=debian                                                       

ANSI_COLOR="1;31"
HOME_URL="https://osmc.tv"
SUPPORT_URL="https://osmc.tv"
BUG_REPORT_URL="https://osmc.tv"

$ uname -a
Linux osmc 4.9.269-70-osmc #1 SMP PREEMPT Thu Oct 17 19:43:19 UTC 2024 aarch64 GNU/Linux

This is what I have.

] SOLVED SOLUTION [

I was copying the OSMC install image to the USB using the following command.

gunzip -c OSMC_TGT_vero5_20241104.img.gz | dd of=/dev/sdb status=progress

I changed the series of commands to the following.

Uncompressed the image

gzip -d OSMC_TGT_vero5_20241104.img.gz

Then copied the image to the USB stick like this.

dd if=OSMC_TGT_vero5_20241104.img of=/dev/sdb status=“progress”

After reinstalling I sshed into the OSMC VeroV

Changed to OSMC home directory, this : /home/osmc with the following command.

cd

Installed git :

sudo apt-get install git

Downloaded hissingshark awesome code retrOSMCmk2.

git clone GitHub - hissingshark/retrOSMCmk2: RetroPie installer for OSMC on the RPi, Vero4k/4K+ and the VeroV

This is where I did things differently. I exited the ssh session and in the GUI Power / Exit. When I see the blue screen with my keyboard attached to the VeroV I hit esc key. This dropped me to terminal and killed the OSMC media center.

Once there changed directory to the git installation folder.

cd retrOSMCmk2

Start the installation process.

sudo ./setup.sh

Doing it this way and not through ssh solved my issue.

Thanks for the help.

Hi,
I know that the RPI 4 is officially not supported. But others have also tried. I apologize, but I stopped reading the thread after 50 posts or so - is there any way now to install tetrosmcmk2 on the RPI4? I did a fresh install of OSMC yesterday, but I struggled to install all cores / packages (due to gpg: assuming signed data - … - cant check signature no public key). I know someone tried to deactivate the fifo protection, but I would rather avoid this, since it can be a security risk…
Also, i installed the Addon, but I can’t launch it… It goes immediately back to the OSMC library.
https://paste.osmc.tv/tinalomega

Sorry - I still don’t own an RPi4 to test.

Hello,
I installed retropie retrOSMCmk2 script on my Rpi 4 and everything went fine: installed emulators and some ports works very well :grinning_face:

Now, I would like to update retropie-setup and the other retropie scripts because I discovered a repo with some, almost experimental, launcher scripts not yet included in the current Retropie version, but they require RetroPie version 4.8.9 version to run.
If I try to update Retropie scripts executing retropie_setup.sh, the version stucks at 3.8.5 because retrOSMCmk2 fetch updates from the fork at GitHub - hissingshark/RetroPie-Setup: Shell script to set up a Raspberry Pi/Odroid/PC with RetroArch emulator and various cores which is not in sync with the official repo GitHub - RetroPie/RetroPie-Setup: Shell script to set up a Raspberry Pi/Odroid/PC with RetroArch emulator and various cores.

My question: is there a simple path to upgrade Retropie at latest official version 4.8.9 ?

Thank you for the attention.

Kranz

1 Like

I had it point to my own fork due to the regularity of breaking changes that were occurring. Too much for me to stay on top of. And at no point did any of them actually seem to be changes that enhanced the available experience on the platform. So it made sense.

I don’t own an RPi4 to test so as it’s very YMMV. But I’m glad you’re getting some positive results there.

1 Like

Yes, on Pi 4 retrOSMCmk2 works fine but I had to manually add the Ububtu server key with:

sudo gpg --keyserver hkps://keyserver.ubuntu.com:443 --recv-keys DC9D77FF8208FFC51D8F50CCF1B030906A3B0D31

Thank you for the retrOSMCmk2 script.

Kranz

Hi there,

What’s the current best solution to have UAE (and maybe other game emulations) on a Vero V ? Is it the official Retropie Setup script, the retrOSMCmk2 or something else ?
(Oh how I dream about a simple “Add game emulators” option in the MyOSMC menu …)

If all is still well, then it should be this script.

The vanilla RetroPie-Setup won’t work out of the box on a Vero.

Amiga emulation is fiddly with settings and configs, but has worked previously under Amiberry.

Ok thanks a lot for the quick answer !

Well it didn’t work because my gamepad isn’t supported. I opened a separate topic.


(Editing my post because of discourse limitiation)

So now I have a working gamepad, but Retropie doesn’t start anymore. It looks like Kodi has trouble stopping:

2025-12-04 13:20:49.718 T:3002     info <general>: Application stopped
2025-12-04 13:20:49.986 T:3002     info <general>: Loading special://xbmc/system/keymaps/appcommand.xml
2025-12-04 13:20:49.987 T:3002     info <general>: Loading special://xbmc/system/keymaps/customcontroller.AppleRemote.xml
2025-12-04 13:20:49.988 T:3002     info <general>: Loading special://xbmc/system/keymaps/customcontroller.Harmony.xml
2025-12-04 13:20:49.991 T:3002     info <general>: Loading special://xbmc/system/keymaps/customcontroller.SiriRemote.xml
2025-12-04 13:20:49.992 T:3002     info <general>: Loading special://xbmc/system/keymaps/gamepad.xml
2025-12-04 13:20:49.994 T:3002     info <general>: Loading special://xbmc/system/keymaps/hama_mce.xml
2025-12-04 13:20:49.994 T:3002     info <general>: Loading special://xbmc/system/keymaps/joystick.xml
2025-12-04 13:20:49.997 T:3002     info <general>: Loading special://xbmc/system/keymaps/keyboard.xml
2025-12-04 13:20:50.004 T:3002     info <general>: Loading special://xbmc/system/keymaps/mouse.xml
2025-12-04 13:20:50.004 T:3002     info <general>: Loading special://xbmc/system/keymaps/osmc_classic.xml
2025-12-04 13:20:50.005 T:3002     info <general>: Loading special://xbmc/system/keymaps/remote.xml
2025-12-04 13:20:50.010 T:3002     info <general>: Loading special://xbmc/system/keymaps/touchscreen.xml
2025-12-04 13:20:50.595 T:3002     info <general>: AddOnLog: peripheral.joystick: Disabling joystick interface "linux"
2025-12-04 13:20:50.596 T:3002     info <general>: ADDON: Dll Destroyed - Joystick Support
2025-12-04 13:20:50.596 T:3002     info <general>: unload skin
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture lists/focus.png
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture dialogs/separator-grey.png
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture /usr/share/kodi/addons/script.module.osmcsetting.services/resources/lib/osmcservices/osmc/FX_Icon.png
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture /usr/share/kodi/addons/script.module.osmcsetting.logging/resources/lib/osmclogging/osmc/FX_Icon.png
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture /usr/share/kodi/addons/script.module.osmcsetting.updates/resources/lib/osmcupdates/osmc/FX_Icon.png
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture OSMC_icon_white.png
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture /usr/share/kodi/addons/script.module.osmcsetting.networking/resources/lib/osmcnetworking/osmc/FX_Icon.png
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture /usr/share/kodi/addons/script.module.osmcsetting.apfstore/resources/lib/apfstore/osmc/FX_Icon.png
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture /usr/share/kodi/addons/script.module.osmcsetting.remotes/resources/lib/osmcremotes/osmc/FX_Icon.png
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture /usr/share/kodi/addons/script.module.osmcsetting.logging/resources/lib/osmclogging/osmc/FO_Icon.png
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture OSMC_icon_line.png
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture white.png
2025-12-04 13:20:50.667 T:3002  warning <general>: Cleanup: Having to cleanup texture logo.png
2025-12-04 13:20:50.746 T:3002     info <general>: Unloaded skin
2025-12-04 13:20:52.941 T:3071    error <general>: Exception ignored in: 
2025-12-04 13:20:52.941 T:3071    error <general>: <module 'threading' from '/usr/lib/python3.9/threading.py'>
2025-12-04 13:20:52.942 T:3071    error <general>: 
                                                   
2025-12-04 13:20:52.942 T:3071    error <general>: Traceback (most recent call last):
                                                   
2025-12-04 13:20:52.942 T:3071    error <general>:   File "/usr/lib/python3.9/threading.py", line 1388, in _shutdown
                                                   
2025-12-04 13:20:52.945 T:3071    error <general>:     
2025-12-04 13:20:52.945 T:3071    error <general>: def _shutdown():
2025-12-04 13:20:52.945 T:3071    error <general>: 
                                                   
2025-12-04 13:20:52.945 T:3071    error <general>: SystemExit
2025-12-04 13:20:52.945 T:3071    error <general>: : 
2025-12-04 13:20:52.945 T:3071    error <general>: 
2025-12-04 13:20:52.945 T:3071    error <general>: 
                                                   
2025-12-04 13:20:53.100 T:3002     info <general>: unload sections
2025-12-04 13:20:53.129 T:3002     info <general>: CWSDiscoveryListenerUDP::Stop - Stopped
2025-12-04 13:20:54.035 T:3002     info <general>: Exiting the application...

Full logs: https://paste.osmc.tv/axefezeged

@hissingshark any hint ?