Posts by Mario77

Quote from kuzuryu01

How do I properly configure AEL to launch games using Retroarch? I looked around and couldn't find a definite answer.

First step you should download AEL assets from retroarch addon settings and then import in AEL to create Gamestarter..

Quote from Borygo77

I've got same problem on generic.. Need to have TV connected to get running. Where do I need to add hdmi force hotplug thing?

I don't think that will work on generic..probably is just for raspberry pi...for generic see here

Quote from zl3ix

I'm running Kodi on RPi 4 and I have enabled VNC. My purpose is to use remote desktop from Win 10 to start music playing on Pi, but I cannot connect unless there is a monitor connected via HDMI. To me this seems to defeat the purpose of the remote login. If I connect a monitor everything works again, but I can't run like that permanently.

I have ordered an HDMI dummy plug with which I hope to fool LibreELEC that there is a monitor connected, but this is a very clunky workaround. Is there no way to force Kodi and VNC server to start IRRESPECTIVE of whether there is a monitor connected or not?

If there is no way to do this at present, I would suggest it as a future upgrade.

Kodi and VNC are 2 different services...VNC works even with kodi disabled..

No need of a dummy..you can add

hdmi_force_hotplug=1

in config.txt

Quote from Mister Floppy

Did you try Lakka on a spare sd card?see if N64 work and pull core from latest lakka version..should work with RetroArch on Gamestarter

Quote from megaprime421

you can also use keymaper add on on kodi to do this, its easy to setup and it works with most of remotes , for me it's working very good

Dont't think that will work for 2 commands on 1 keypress..great addon tough..makes life easier

Quote from Mister Floppy

@Mario66:

Okay, after having downloaded the cores from the addon settings again, I also tried it under LibreElec 9.2.0 (KODI v18.5) and LibreElec 9.2.1 (KODI v18.6), unfortunately with the same failing result

And yes, the library /usr/lib/libstdc++.so.6 is there actually.

Do you have any idea what I can try next?

I would try these 2 emulators:

parallel_n64_libretro.so

mupen64plus_libretro.so

Quote from Mister Floppy

Mario77

I'm using the cores downloaded from the "RetroArch" addon setting via "Download Libretto cores full package". Maybe that's the cause for the problem?

Okay, following the other option and to first get a "clean" start, I've tried the following:

- I logged into "LibreElec" via SSH

- I deleted all files under "\storage\.kodi\userdata\addon_data\game.retroarch\cores\"

When then running "RetroArch" and selecting "Load Core/Download a core" in the menu, a list of cores is displayed. but there are no entries for "Nintendo N64" - I've searched through the whole list, but apparently these cores are missing. (Other cores, for example, "Nintendo - SNES / SFC (Snes9x - Current)" are there, can be installed and are working fine with games made for this console).

What can i do now?

Display More

You should download the cores from addon settings not from retroarch menu..

Did you try another version of LE?

Did you check that the library is there /usr/lib/libstdc++.so.6?

Quote from Mister Floppy

Error "GLIBCXX_3.4.26' not found

Hi guys,

I've installed the gamestarter addon on my RaspberryPie 4 under "LibreElec v9.2.3 (KODI v18.7)".

When trying to load a Nintendo N64 game with "RetroArch v9.186.20" " using "Mupen64Plus Next" as core, I'm getting the error message "Failed to load Libretro Core"

The log file has an entry saying "Error(s): /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by /storage/.kodi/userdata/addon_data/game.retroarch/cores/mupen64plus_next_libretro.so)"

I've attached the packed files "retroarch.cfg" and "retroarch.log".

Being a NOOB regarding this issue, I'm totally clueless how to solve this problem and would appreciate if someone could help. Thank you in advance!

Display More

Are you using the cores downloaded from retoarch UI menu or the cores downloaded from retroarch addon settings?

Quote from spontex

Hi,

I have been running TVH 4.2 for years, but I just reinstalled my computer from scratch and told myself that it would be nice to try TVH 4.3, since there is a feature I would like (better image cache management to avoid thousands of temporary files and slow startup).

So I took the latest LibreElec (9.2.3) and the latest TVH nightly (4.3-1885-08.06.2020) and installed it.

It worked a few hours, but now it does not anymore, due to a crash (log attached).

I have read on the forum that I might be due to a mismatch between the config file version and the TVH version.

It happened just after I set up my EPG by using the Kodi addon and pointing it to my XMLTV file location.

Many thanks

Display More

If you want to use TVH 4.3 try LE9.0..never had issues on UK freeview antenna reception...

Quote from PureEvil

sorry guys i'm really too stupid. I installed the add on SFTP support from spiff version 1.0.6.1. If I want to add network share now, there is no protocol for SFTP. Please don't let me die stupid.

file manager_add source?

Quote from nikstra

Remove the colon in the timestamp as it is not allowed in filenames in Windows.

That took me almost a whole day...silly me...thanks!

Hi,

I got a cron job running which outputs a log everytime it runs..

Issue is the log I can only open trough ssh and cannot open it in windows pc through samba..it's clearly a permission issue...is there any way i can set permissions to each log to be readable ..

cron looks like this..

Thanks for any help

30 4 * * * /storage/.kodi/userdata/Backup/backup.sh >> /storage/.kodi/userdata/Backup/Backup_logs/backup_log_`date +%d-%m-%Y_%H:%M`.log 2>&1

Quote from popcornmix

I've found an issue with over_voltage=4 (or higher) on Pi2.
Can you test this firmware
Unzip and replace http://start.elf/fixup.dat on boot partition with start_x.elf/fixup_x.dat from zip file.
Let me know if over_voltage=4 starts to work again.

Hi just tested,replaced firmware and can confirm I can now set over_voltage=4 or higher..but had to remove "_x" from firmware file names otherwise it didn't boot.Thanks.

Quote from DennisHilhorst

If just installed the newest update un my Raspberry Pi 2.

After the installation, the system went out/black/no power...

When I shut down the power and reconnect it, it tried to startup, but after a few seconds it went out again.

Who has the same problem or knows how to solve it !?

BR, Dennis

Display More

Hi Dennis

If you'r overvolting set it to over_voltage=3 or lower and it should boot up normally.

HiassofT

Issue is over voltage

Cannot be set higher then

 over_voltage=3

from =4 upwards LE 9.2.3 doesn't start..at least mine..on RPi2.

overclock settings don't matter..tried a few and they all work..

Thanks..

HiassofT

Fresh install works fine..but if I update from 9.2.1 it doesn't start...

journalctl

cat /proc/cpuinfo

@DennisHilhorst post #8 got same issue as me.

cmd line is this

boot=UUID=0303-2219 disk=UUID=535ef1f2-87b8-43f9-ad36-036077bb50d3 quiet 

Config is this but even tried it with a fresh install of 9.2.3 and then restored a backup from 9.2.1 and did the same..didn't start

# SPDX-License-Identifier: GPL-2.0-or-later
# Copyright (C) 2009-2014 Stephan Raue ([email protected])
# Copyright (C) 2016-present Team LibreELEC (https://libreelec.tv)
################################################################################
# Bootloader configuration - config.txt
################################################################################

################################################################################
# Memory (System/GPU configuration )
################################################################################

# Default GPU memory split (do not change if you do not know what you are doing)
  gpu_mem=128

# Configure GPU memory based on SDRAM size - overrides above setting
  gpu_mem_256=112
  gpu_mem_512=160
  gpu_mem_1024=256

################################################################################
# For overclocking and various other settings, see:
# https://www.raspberrypi.org/documentation/configuration/config-txt.md
################################################################################
# Set 'force_turbo=1' to disable dynamic overclocking and enable overclocking always.
  force_turbo=1

# Make display smaller to stop text spilling off the screen
#
# Note that the overscan settings only affect the splash screen and not Kodi.
#
# If you experience overscan/underscan issues the best solution is to adjust
# your TV settings ("full pixel", "1-1 pixel" etc.). Alternatively, there is a
# calibration menu in the Kodi GUI.
  disable_overscan=0

# Force HDMI even if unplugged or powered off
  hdmi_force_hotplug=0

# Doesn't sent initial active source message.
# Avoids bringing CEC (enabled TV) out of standby and channel switch when
# rebooting.
  hdmi_ignore_cec_init=0

################################################################################
# License keys to enable GPU hardware decoding for various codecs
# to obtain keys visit the shop at http://www.raspberrypi.com
################################################################################

  decode_MPG2=0x00000000
# decode_WVC1=0x00000000

################################################################################
# End of default configuration
################################################################################

################################################################################
# Include distribution specific config file if it exists.
################################################################################
[all]
include distroconfig.txt
  arm_freq=950
  core_freq=500
  sdram_freq=500
  over_voltage=4
  over_voltage_sdram=0
  initial_turbo=0
  hdmi_drive=2
  hdmi_force_edid_audio=0
  hdmi_pixel_encoding=0
  hdmi_ignore_hotplug=0
  hdmi_edid_file=0
  config_hdmi_booxx=0
  sdtv_mode=0
  sdtv_aspect=1
  overscan_scale=0
  overscan_left=0
  overscan_right=0
  overscan_top=0
  overscan_bottom=0
  hdmi_ignore_cec=0
  disable_splash=1
  max_usb_current=1
  dtparam=audio=on

Typo in config_hdmi_booxx=0 is because is the real word is censored..wouldn't let me post it..

its a rpi2 ...will post later when home.