Posts by 5schatten

Kupo91
Yes you can delete the file & rr-config dir.

This could work:

#!/bin/sh
# SPDX-License-Identifier: GPL-2.0-or-later
# Copyright (C) 0riginally created by Escalade (https://github.com/escalade)
# Copyright (C) 2018-present 5schatten (https://github.com/5schatten)

. /etc/profile
oe_setup_addon service.rr-config-tool

DOCKER_PATH=/storage/.kodi/addons/service.system.docker/bin/docker
DOCKER_IMAGE=5schatten/arch-pcsx2
PCSX2_LOG=/var/log/pcsx2.log

if [ -x ${DOCKER_PATH} ]; then
  ${DOCKER_PATH} -v >> ${PCSX2_LOG} 2>&1

  if ! docker images | grep ${DOCKER_IMAGE} > /dev/null; then
    echo "############################" >> ${PCSX2_LOG} 2>&1
    echo "# Pulling the Docker image #" >> ${PCSX2_LOG} 2>&1
    echo "############################" >> ${PCSX2_LOG} 2>&1
    docker pull ${DOCKER_IMAGE} >> ${PCSX2_LOG} 2>&1
  fi

  if docker images | grep ${DOCKER_IMAGE} > /dev/null; then
    echo "######################################################" >> ${PCSX2_LOG} 2>&1
    echo "# Checking for image updates & clean up if necessary #" >> ${PCSX2_LOG} 2>&1
    echo "######################################################" >> ${PCSX2_LOG} 2>&1
    docker pull ${DOCKER_IMAGE}:latest >> ${PCSX2_LOG} 2>&1
    docker image prune -f >> ${PCSX2_LOG} 2>&1

    echo "##################" >> ${PCSX2_LOG} 2>&1
    echo "# Starting PCSX2 #" >> ${PCSX2_LOG} 2>&1
    echo "##################" >> ${PCSX2_LOG} 2>&1

    # Set audio driver to ALSA
    export SDL_AUDIODRIVER=alsa

    DOCKER_ARGS=" \
    --rm \
    --name arch-pcsx2 \
    --privileged \
    -i \
    -e DISPLAY=:0.0 \
    -v /dev/shm:/dev/shm \
    -v /var/media:/media \
    -v /var/run/localtime:/etc/localtime
    -v /storage:/storage \
    -v /storage/.config/asound.conf:/etc/asound.conf \
    -v /storage/.config/PCSX2:/root/.config/PCSX2 \
    -v /storage/roms/bios:/root/.config/PCSX2/bios \
    -v /tmp/.X11-unix:/tmp/.X11-unix"

    ${DOCKER_PATH} run ${DOCKER_ARGS} ${DOCKER_IMAGE} /usr/bin/PCSX2 "$@" >> ${PCSX2_LOG} 2>&1
  fi
else
  echo "######################################################################################################" > ${PCSX2_LOG} 2>&1
  echo "# The Docker addon is missing. Please check out the Kodi addons, install Docker and run PCSX2 again. #" >> ${PCSX2_LOG} 2>&1
  echo "######################################################################################################" >> ${PCSX2_LOG} 2>&1
fi

Quote from Kupo91

The advanced.conf file says

Code

# Enable Kernel Mode Setting (KMS) for Retroarch which can reduce 
# your input lag and overall gaming experience for certain lr-cores
# valid options: false / true
RR_KMS=false

Btw. you should read the last changelogs...

Well you could try to delete this completely:

# Freeze Kodi / stop audio
kodifreeze.sh freeze muteonly

# Switch back to Kodi & start audio
kodifreeze.sh unfreeze muteonly

Quote from Kupo91

Didnt we fix this with

(just with retroarch, not ppsspp) ?

..using the solo mode doesnt work. Then it doesnt even start the game

Did you enable KMS?

Quote from Kupo91

Thanks a lot! I did the same with my other issue (doesnt return to rcb after playing). Maybe you could take a look of it too and say what is missing in retroarch.start script. Log is probably longer than necessary because I didnt know where it ends.

Thats how it looks like when launching /usr/bin/retroarch (returning to rcb works)

https://paste.ubuntu.com/p/nxqbbqxhcq/

And thats how it looks like when launching retroarch.start (doesnt return to rcb)

https://paste.ubuntu.com/p/37w4p6zcvg/

If you use my retroarch.start script it can't return to RCB because my script stops Kodi before it launches any frontend.

Again if you want to run anything else you have to export the audio drivers or else to Retroarch. As long as Kodi is running there is no guarantee that your emulator will gain access to your ALSA device for example.

Btw. you probably have to use the "solo mode" mode anyway

[RELEASE] Rom Collection Browser - Browse and launch emulator game ROMs

Quote from Kupo91

I maybe found the reason why rcb doesnt start dolphin..

I compared the logparts of ppsspp and dolphin and here are the differences:

PPSSPP:

Code

 2019-03-05 19:08:51.595 T:139917485143808   DEBUG: RCB_INFO launcher.buildCmd
2019-03-05 19:08:51.595 T:139917485143808   DEBUG: RCB_INFO emuCommandLine: /storage/.kodi/userdata/addon_data/script.games.rom.collection.browser/scriptfiles/PPSSPP.start
2019-03-05 19:08:51.595 T:139917485143808   DEBUG: RCB_INFO preCmdLine:
2019-03-05 19:08:51.595 T:139917485143808   DEBUG: RCB_INFO postCmdLine:
2019-03-05 19:08:51.595 T:139917485143808   DEBUG: RCB_INFO Getting Multiple Disc Parameter
2019-03-05 19:08:51.595 T:139917485143808   DEBUG: RCB_INFO emuParams: "%ROM%"
2019-03-05 19:08:51.595 T:139917485143808   DEBUG: RCB_INFO rom: /var/media/SPIELE/PSP/Roms/FlatOut - Head On/FlatOut - Head On [D][ULES-00969].cso
2019-03-05 19:08:51.596 T:139917485143808   DEBUG: RCB_INFO No precmd created.
2019-03-05 19:08:51.596 T:139917485143808   DEBUG: RCB_INFO No postcmd created.
2019-03-05 19:08:51.602 T:139917485143808   DEBUG: RCB_INFO cmd: "/storage/.kodi/userdata/addon_data/script.games.rom.collection.browser/scriptfiles/PPSSPP.start" "/var/media/SPIELE/PSP/Roms/FlatOut - Head On/FlatOut - Head On [D][ULES-00969].cso"
2019-03-05 19:08:51.602 T:139917485143808   DEBUG: RCB_INFO precmd:
2019-03-05 19:08:51.602 T:139917485143808   DEBUG: RCB_INFO postcmd:
2019-03-05 19:08:51.602 T:139917485143808   DEBUG: RCB_INFO launchEmu on non-xbox
2019-03-05 19:08:51.602 T:139917485143808   DEBUG: RCB_INFO screenMode: HDMI1: 1920x1080 @ 60.00Hz
2019-03-05 19:08:51.602 T:139917485143808   DEBUG: RCB_INFO launch emu
2019-03-05 19:08:51.702 T:139917485143808   DEBUG: RCB_INFO: onAction: 7
2019-03-05 19:08:52.603 T:139917485143808   DEBUG: RCB_INFO __executeCommand
2019-03-05 19:08:52.604 T:139917485143808   DEBUG: RCB_INFO execute command with os.system
2019-03-05 19:08:52.715 T:139917476751104   DEBUG: Thread LanguageInvoker start, auto delete: false
2019-03-05 19:08:52.715 T:139917476751104    INFO: initializing python engine.
2019-03-05 19:08:52.715 T:139917476751104   DEBUG: CPythonInvoker(16, /usr/bin/audio-suspend.py): start processing
2019-03-05 19:08:59.266 T:139919213188864   DEBUG: BUTTON [ 2 ] on "Gasia Co.,Ltd PS(R) Gamepad" pressed
2019-03-05 19:08:59.444 T:139919213188864   DEBUG: BUTTON [ 2 ] on "Gasia Co.,Ltd PS(R) Gamepad" released
2019-03-05 19:09:08.062 T:139919213188864   DEBUG: BUTTON [ 9 ] on "Gasia Co.,Ltd PS(R) Gamepad" pressed
2019-03-05 19:09:08.240 T:139919213188864   DEBUG: BUTTON [ 9 ] on "Gasia Co.,Ltd PS(R) Gamepad" released
2019-03-05 19:09:17.208 T:139919565518592   DEBUG: Thread JobWorker 139919565518592 terminating (autodelete)
2019-03-05 19:09:17.208 T:139919857952512   DEBUG: Thread JobWorker 139919857952512 terminating (autodelete)
2019-03-05 19:09:17.208 T:139918214948608   DEBUG: Thread JobWorker 139918214948608 terminating (autodelete)
2019-03-05 19:09:17.217 T:139919557125888   DEBUG: Thread JobWorker 139919557125888 terminating (autodelete)
2019-03-05 19:09:17.646 T:139919213188864   DEBUG: BUTTON [ 10 ] on "Gasia Co.,Ltd PS(R) Gamepad" pressed
2019-03-05 19:09:17.809 T:139919213188864   DEBUG: BUTTON [ 10 ] on "Gasia Co.,Ltd PS(R) Gamepad" released
2019-03-05 19:09:20.420 T:139919213188864   DEBUG: BUTTON [ 2 ] on "Gasia Co.,Ltd PS(R) Gamepad" pressed
2019-03-05 19:09:20.534 T:139919213188864   DEBUG: BUTTON [ 2 ] on "Gasia Co.,Ltd PS(R) Gamepad" released
2019-03-05 19:09:25.066 T:139919213188864   DEBUG: BUTTON [ 2 ] on "Gasia Co.,Ltd PS(R) Gamepad" pressed
2019-03-05 19:09:25.181 T:139919213188864   DEBUG: BUTTON [ 2 ] on "Gasia Co.,Ltd PS(R) Gamepad" released
2019-03-05 19:09:25.583 T:139917485143808   DEBUG: RCB_INFO launch emu done
2019-03-05 19:09:25.588 T:139919557125888   DEBUG: Thread LanguageInvoker start, auto delete: false
2019-03-05 19:09:25.588 T:139919557125888    INFO: initializing python engine.
2019-03-05 19:09:25.588 T:139919557125888   DEBUG: CPythonInvoker(17, /usr/bin/audio-resume.py): start processing
2019-03-05 19:09:25.683 T:139917485143808   DEBUG: RCB_INFO: onAction: 122
2019-03-05 19:09:25.683 T:139917485143808   DEBUG: RCB_INFO: onAction: ACTION_CANCEL_DIALOG
2019-03-05 19:09:25.683 T:139917485143808   DEBUG: RCB_INFO: exit
2019-03-05 19:09:25.683 T:139917485143808   DEBUG: RCB_INFO: Begin saveViewState
2019-03-05 19:09:25.689 T:139917485143808   DEBUG: RCB_INFO: Begin saveViewMode

Display More

dolphin:

Code

2019-03-05 19:10:01.520 T:139919557125888   DEBUG: RCB_INFO launcher.buildCmd
2019-03-05 19:10:01.520 T:139919557125888   DEBUG: RCB_INFO emuCommandLine: /storage/.kodi/userdata/addon_data/script.games.rom.collection.browser/scriptfiles/dolphin.start
2019-03-05 19:10:01.520 T:139919557125888   DEBUG: RCB_INFO preCmdLine:
2019-03-05 19:10:01.520 T:139919557125888   DEBUG: RCB_INFO postCmdLine:
2019-03-05 19:10:01.520 T:139919557125888   DEBUG: RCB_INFO Getting Multiple Disc Parameter
2019-03-05 19:10:01.523 T:139919557125888   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <type 'exceptions.UnicodeEncodeError'>
                                            Error Contents: 'ascii' codec can't encode character u'\xa0' in position 21: ordinal not in range(128)
                                            Traceback (most recent call last):
                                              File "/storage/.kodi/addons/script.games.rom.collection.browser/resources/lib/gui.py", line 365, in onClick
                                                self.launchEmu()
                                              File "/storage/.kodi/addons/script.games.rom.collection.browser/resources/lib/gui.py", line 1017, in launchEmu
                                                launcher.launchEmu(self.gdb, self, gameId, self.config, selectedGame)
                                              File "/storage/.kodi/addons/script.games.rom.collection.browser/resources/lib/launcher.py", line 47, in launchEmu
                                                cmd, precmd, postcmd, roms = self._buildCmd(gui, filenameRows, gameRow, False)
                                              File "/storage/.kodi/addons/script.games.rom.collection.browser/resources/lib/launcher.py", line 145, in _buildCmd
                                                match = re.search(self.romCollection.diskPrefix.lower(), str(gamename).lower())
                                            UnicodeEncodeError: 'ascii' codec can't encode character u'\xa0' in position 21: ordinal not in range(128)
                                            -->End of Python script error report<--
2019-03-05 19:10:01.523 T:139919557125888   DEBUG: RCB_INFO: onAction: 7
2019-03-05 19:10:19.589 T:139920001240384   DEBUG: Keyboard: scancode: 0x09, sym: 0x001b, unicode: 0x001b, modifier: 0x0
2019-03-05 19:10:19.723 T:139920001240384   DEBUG: Keyboard: scancode: 0x09, sym: 0x001b, unicode: 0x0000, modifier: 0x0
2019-03-05 19:10:19.723 T:139920001240384   DEBUG: HandleKey: escape (0xf01b) pressed, action is PreviousMenu
2019-03-05 19:10:19.723 T:139919557125888   DEBUG: RCB_INFO: onAction: 10
2019-03-05 19:10:19.723 T:139919557125888   DEBUG: RCB_INFO: onAction: ACTION_CANCEL_DIALOG
2019-03-05 19:10:19.723 T:139919557125888   DEBUG: RCB_INFO: exit
2019-03-05 19:10:19.723 T:139919557125888   DEBUG: RCB_INFO: Begin saveViewState
2019-03-05 19:10:19.742 T:139919557125888   DEBUG: RCB_INFO: Begin saveViewMode

Display More

Don't know what this means though. However I attached the files that are named in the error note. Maybe you want to check it..

This is most likely a RCB bug bug exporting game db to nfo's · Issue #202 · maloep/romcollectionbrowser · GitHub so you should report it there so it might get finally fixed at some day.

UnicodeEncodeError: 'ascii' codec can't encode character u'\xa0' in position 21: ordinal not in range(128)

Quote from newuser_

Hi,

awesome build. However compared to the rest dolphin is extremely loud and the volume bar in its settings is greyed out. Is there a solution for this?

And is there a way to change kodi leia splash screen?

Regards

Try alsamixer in a terminal to reduce the volume.

About the Kodi splash screen you might be able to use this guide How to Change Kodi Splash Screen - Custom Startup Image - Home Media Portal and place a splash file in ~/.kodi/media

Or disable it Bootscreen von Libreelec ändern - Raspberry Pi - Kodinerds.net - Deutschsprachiges Forum zum Kodi Entertainment Center

EDIT:
Something like pactl set-sink-volume alsa_output.temp_sink 75% works for PulseAudio. I guess I'll add some volume option to the RR Config later.

Quote from emperorgr

dear friends,

i got a Minix Z83-4U which doesn't seem to want to load with the current Build RR-20190305-fed2e29 neither with official 9.0.1.

As far i understood, the problem is that it wants a 32bit EFI, which is present, however doesn't simply works...

any idea how to get around this and load the latest build?

i got after some trouble to load official 8.2.5 but again with the update method 9.0.1 doesn't work,

perhaps something changed and messed things up?

Display More

It seems to work in one way or another Z83 mini PC

milhouse  chewitt

Any hints how to switch to grub2 to boot 32bit UEFI based systems?

Actually I have no clue about that but if it's idle there should be much demand. I mean we're talking about rendering a menu which should be done by the GPU anyway...

Quote from Christophe14

Hi,

There are more and more mini PC available using low cost x86 ICs from Intel such as Intel Atom and Intel Celeron.

Therefore I have 2 main questions:

1) I am using LibreELEC 8.0.2.1 specific version for Intel Compute Stick STCK1A8LFC (Intel Compute Stick BOXSTCK1A8LFCL) and it is working well.

The Intel Atom chips such as Z3735F Bay Trail and x5-Z8300 Cherry Trail are using a 32 bit EFI boot from what I have understood.

Is it possible to have a clear status on LibreELEC 9 vs Intel Atom chips ?

There are different contradicting posts on 32 bit boot support for LE 9.

Is LibreELEC 9 working on STCK1A8LFC or STK1AW32SC ?

2) Are Intel Apollo Lake processor (N3xx0) or Intel Gemini Lake processor (N4x00) also concerned with 32 bit boot ?

Are they compatible natively with LibreELEC 9 ?

Thanks !

Display More

If you considering to go for a NUC, mITX board or Odroid H2 there should be no problems. I use a Asrock J3455-ITX and it boots up flawless.

Quote from forkless

I hear what you are saying but you are comparing apples to oranges. The GT520M is not a desktop GPU, nor does it have the same type of cooling.

While 70 degrees Celcius is warm, it anything but critical -- The machine ran idle like that for years, quite happily so.

If one wanted to make a fair comparison I would have to add a decent heat sink and fan like any normal desktop GPU, which would drive down the temperature easily down by another 15-20C, putting it right at the level of where your micro-tower based unit is at.

Anyways, the bigger issue here seems the excessive idle temperature on Kodi 18.x/LE 9.0.1. The 95C (or 70-75C when there was desktop GPU cooling in place) range temperatures are more the ones I would expect when putting the GPU to task with a heavy load.

Display More

Klojum
Well if temperatures are okay with LE 8.2.5 there must be a reason why they are much higher now regardless if 70°C are pretty high for idle load or not.

What's your clock speed when you reach the thermal limit? Or is the clock speed completely fixed at your Atom D2700?

Quote from forkless

Hi there,

I have been running LE 8.9.x (and recently upgraded to 9.01) for some while on my x86_64 with a GeForce GT520M GPU (Xtreamer Ultra 2). I recently noticed that;

- The CPU and GPU where running 22-25 degrees C higher in idle mode

- Subtitle positions (or screen adjustments if not setting the TV on scan only) did not persistently store the changed settings, they were gone after each reboot. (Probably a separate issue from the overheating)
- Due to the severe overheating the USB ports also stopped functioning properly as a side-effect.

What I don't know is when the overheating started, the system seemed work OK on the earlier 8.9.x RC builds. Anyway, once I rolled back to LE 8.2.5 the CPU and GPU dropped back from 95C to roughly 70C (it's a passive cooled unit)

Has anyone experienced similar overheating issues?

Display More

Could you upload your logfile zips? Your GT520M uses the 340.107 Nvidia driver which should be pretty stable while the Atom D2700 CPU should be well supported too but lacks EIST so no Speedstep support.

The device is running into the thermal limit when it's idle or while you watch anything?

EDIT:

LE 8.2.5 used 390.42 which also supports the GT 520M so it might be a regression with the older 340.107 driver.

Quote from Brainarts65

Once again you defend your position blindly by attacking and questionning each and every sentences i wrote. Just because you are offended by my frustration and you just can't admit your own failure. PERIOD. You do not explain me and to all why the strict and limited 500 megs part...... A SD Card can be parted... a HD Too.... i see no clear need to preserve it as it is when a lot of people would like it with few choice of a bigger first part from the start.

There is LE9 Remix ain't it... What is it for if we can't get there?

I Know that LibreElec is a fabulous piece of software and that it is the top in its own category. Open source also mean open to explain your own little secrets and directions on how use it to achieve our goal....

So instead of playing the poor offended guy as you do why not tell me how to do it simply please?

Well maybe I don't get your point but what exactly is your problem? The standard partition size of 512MB is more than enough for vanilla LE since all addons are stored on a different partition. If you want to use my community build follow the steps as described in the first post of my thread, download my images and install them cleanly and you have nothing else to do.

Btw. open source means basically the source code is available for everyone. GitHub - LibreELEC/LibreELEC.tv: Just enough OS for KODI go and grab the code and do what you like.

Build RR-20190305-fed2e29 is online

• Spotify installer should be fixed
• updated Skyscraper to v3.1.0
• added lr-bsnes-mercury-balanced to Generic build
• updated Emulationstation to v2.8.2
• updated VLC MMAL patch for RPi builds
• updated several libretro-cores
• updated citra & dolphin

Quote from Kupo91

I just noticed that when I created that logfile the path to dolphin.start in my rcb config file was incorrect. Here is another logfile that hopefully shows my issue. log-2019-03-05-18.11.44.zip

Alucard since you are using the same NUC and the same build like me I wondered if you also experienced that sometimes the NUC stucks in bootscreen?

Well if you provide logs -> reboot the system once the try out what should work but doesn't and grab the log package otherwise it's a pain in the @$$ to figure out what's wrong.

I didn't find anything in particular why it does not run so can you start LE, log into a terminal and run the script which you want to use by hand and see if it starts fine? If it does RCB starts the script in a wrong way.

Quote from mrness

But I've already checked the dtoverlay -l output, its output was the one expected under the circumstances:

rpi:~ # dtoverlay -l

Overlays (in load order):

0:  w1-gpio  gpiopin=4

Did try it? If not do it otherwise post a full dmesg log.

Quote from mrness

Hi,

The latest RR build (20190221) has an issue with w1-gpio support. My .config/autostart.sh contains the following commands:

dtoverlay w1-gpio gpiopin=4

modprobe w1-gpio

modprobe w1-therm

In this build loading w1-gpio module fails with the following errors:

[ 6.854425] w1-gpio onewire@4: prop pinctrl-0 index 0 invalid phandle

[ 6.854453] w1-gpio: probe of onewire@4 failed with error -22

Display More

Add dtoverlay=w1-gpio,gpiopin=4 to config.txt instead of using the dtoverlay command in autostart.sh if this still fails upload a full dmesg log.

Quote from Alucard

The issue is still there: there is a "colored line" glitch on top of the screen that appears from time to time (not a big deal but annoying). Still no fix for now unfortunatly...

Regarding mame I didn't test. I only tested the following plateforms:

-Snes

-PC engine

-PSX

-GBA

-Genesis/Megadrive

Only emulator that I found was too much for little J5005 was the BSNES accuracy in some games (seiken desentsu 3), bsnes balanced works perfectly on the other hand.

Display More

real_cyma

My generic builds come with MAME 2003 Plus & MAME 2016 also FB Alpha so I guess bascially all important roms are covered in one way or another.

About BSNES I've added the balanced core to my build if it's suitable, but snes9x is also included.

Quote from Alucard

x1 on beetle psx software. I think I tried to go higher at some point without much slowdown but from what I remember it activated the GPU and I had graphical gitches in some games (CTR in particular)...so x1 software all the way for me: good accuracy, good performances ==> PSX as in the 90s.

Note that I'm not talking about RR version but regular libreelec 18 with retroarch and beetle psx installed...but beetle psx is the same piece of software in the end...

Regular LibreELEC 9.x comes with Retroplayer not Retroarch but basically it uses the same API and cores. Or did you use any stuff like Gamestarter?