Posts by 5schatten

    OK, but we don't get the new script until next beta I suppose.

    Shouldn't take too long since I'm going to upload Beta14a for generic systems today which includes Mupen64Plus.

    EDIT:

    Obviously this would be something what bothers me myself if a failed upgrade attempt breaks Chrome as a whole. So I've updated & reworked the script and now it should test if a) the PKG version can be received and b) if the download url is valid. If there is no valid url it will drop a message in the chrome log file but still start the old version without any updating attempts.

    I've got problems with Chrome in beta 14. First message about downloading update, but nothing seems to happen after that. Then I delete /storage/.cache/app.chrome/ and there is message that it's first time that Chrome is started so it will be downloaded and installed. But again nothing seems to happen.

    I see no errors in the logg. Maybe the download link in the google-chrome-stable script doesn't work?

    Google changed the format of the repodata so I had to adjust the script a bit.

    Well I've tried to run Pilotwings64 on my generic system and I had no glitches with mupen64plus only with ParaLLEL-64 so what was your test system that had these black triangle bug? Generic builds come with both n64 emulators & ARM stuff mupen64plus only. If you prefer mupen64plus just update es_systems.cfg according to your needs.

    About m64p it is just a "buildsystem" or better call it a quite hacky script that glues the plugins together. To build them I would have to patch every single plugin to make it work because of stupid Makefile configs :/ And in the end it would only run on systems with QT so generic builds. All in all it doesn't make much sense to me. But let's see if I can grab the important stuff from this script /shrug

    mupen64plus-GLideN64/build.sh at master · m64p/mupen64plus-GLideN64 · GitHub

    EDIT:

    After several hours of fishing in murky waters...

    mupen64plus: initial package git version 3d4288b · 5schatten/LibreELEC.tv@cbc562f · GitHub

    Beta 14 is partly online (Odroid C2 uploading):

    • updated to latest LE9.0 upstream
    • updated to Kodi 18 beta 5
    • updated Generic & RPi kernel to 4.19.1
    • added back crazycat dvb addons
    • updated mesa to 18.3-rc2
    • updated vulkan-loader to 1.1.91
    • updated several libretro-cores
    • updated dolphin & citra
    • fixed es_systems.cfg for Amlogic & RPi -> ! delete your es_systems.cfg before you update !

    MakeMKV 1.14.1 is online:

    • minor fixes in upstream

    I tested your LE9 version with the makemkv addon and it works perfectly!

    So it is defentively a problem with LE 8, but with kodi 18 just around the corner it isn't worth to fix it i guess

    If version 1.12.3 still works with the older Kodi version there is no need to update anyway and I guess there won't be any fix for this. The problem was that MakeMKV was not compatible to Kodi 18 and this patch added some missing functions. The latest version is now compatible I guess it also breaks compatibility to Kodi 17.x. because the compatibility is achieved by different code changes.

    But since Kodi 18 beta 5 is already available I guess we'll see the final version around Xmas anyway and from my experience after months of usage it works quite fine.

    5schatten

    Tested makemkv on my stock LE 8.2.5

    Installs fine, i removed the old version first

    When i try to play a blu-ray kodi crashes instantly.

    Crashlog attachedkodi_crashlog_20181108194140.log

    Well as I said this package is build for LE9 so I'm not surprised. /shrug

    Does version 1.12.3 work flawless? The official MakeMKV page states:

    • libmmbd: Added compatibility for latest libaacs API (Kodi no longer crashes)

    so I dropped this patch:

    libmmbd with kodi18 - Page 2 - www.makemkv.com

    Either MakeMKV needs this patch in an updated version, it won't build with it anymore, or your Kodi is outdated and so it won't run.

    So someone with a recent alpha or remix build based on LE9 schould test it first to make sure it fails to run and is not just incompatible to older Kodi versions :/

    create an empty file called nokms in /storage/.config/retroarch looks like AMD cards don't like KMS

    Maybe another option could be to create a file called radeon-kms.conf in /storage/.config/modprobe.d which contains this line:

    Code
    options radeon modeset=1

    I can't test it but this file is used at debian systems to tell the kernel to use kms for the radeon module. I haven't checked how LE handles this & I can't test it myself but maybe this is needed for LE too.

    If you create radeon-kms.conf delete the nokms file to test if kms finally works.

    will try to disable the IGP tonight.

    What hardware are you looking for?

    Right now I'm thinking what could be "handy" to cover the usual generic system environments. Probably some crappy i3-2xxx with Intel IGP & a dedicated AMD & Nvidia lowend gpu would be useful. In the end I need a setup that uses the same drivers so I can pretest all stuff with other GPU vendors.

    I have two Intel ITX boards in my HTPC setup and it's not really an option to rip them out everytime and happy swap some gpus while my gf tries to kill me because no tv/music/games/amazon vod is working then ;)

    Can you check your video_monitor_index = in your retroarch.cfg ?

    [INFO] [DRM]: Found 4 connectors.

    [INFO] [DRM]: Connector 0 connected: no

    [INFO] [DRM]: Connector 0 has 0 modes.

    [INFO] [DRM]: Connector 1 connected: yes

    [INFO] [DRM]: Connector 1 has 41 modes.

    [INFO] [DRM]: Connector 1 assigned to monitor index: #1.

    [INFO] [DRM]: Connector 2 connected: no

    [INFO] [DRM]: Connector 2 has 0 modes.

    [INFO] [DRM]: Connector 3 connected: no

    [INFO] [DRM]: Connector 3 has 0 modes.

    If you run RA in kms mode can you set it manually to video_monitor_index = "1" ? Because your log file tells me you use connector 1 and not 0 someone had a somewhat similar setup and it also failed to run in kms mode if the monitor index wasn't set properly.

    LibreELEC 9.0 Reborn Remix [ Emulationstation | Retroarch | DolphinQT | Moonlight | Chrome | Spotify | MakeMKV ]


    m64p is booting, the gui is displayed, but it can't open it's core files.

    When I open the log it says it's missing "libminizip.so.1"

    Code
    GUI error: dlopen('./libmupen64plus.so.2') failed : libminizip.so.1: cannot open shared object file: No such file or directory

    Since LE does not come with minizip it's normal that it fails.

    "Couldn't load core library, please set the path in settings." · Issue #97 · m64p/mupen64plus-GLideN64 · GitHub <- same error

    IMHO it's pretty strange(awkward) that they use minizip even though zlib is a build dependecy... :rolleyes:

    I'm not sure if I understood your problem -> so you can launch games in ES but if you start RA from the Kodi main menu it fails to run?

    Can you get me a copy of your retroarch.log ? It's located in /var/log or you check out your logfiles smb directory and upload the whole zip after you run retroarch. Then the log file is included in varlog.

    You have to manually set your dpi first otherwise menus won't fit.

    LibreELEC 9.0 Reborn Remix [ Emulationstation | Retroarch | DolphinQT | Moonlight | Chrome | Spotify | MakeMKV ]

    Xorg - ArchWiki

    The sound settings in Kodi have nothing to do with your settings in ES or RA or other emulators. They will always depend on your asound.conf do have altered any settings in Retroarch? I mean have you changed an drivers in RA?

    http://www.lakka.tv/doc/audio-settings/

    So can you pass me a logfile of a RA in nokms while you play a game? I have several logs but none of this condition.

    I'm not sure it related but if you google a bit it sounds (huehuehue) as if AMD has trouble with proper sound output overall.

    Radeon/AMDGPU DRM Drivers Get HD Audio Component Support - Phoronix

    Even With AMDGPU DC, HDMI/DP Audio Isn't Working Out For All Radeon Linux Users - Phoronix

    Audio issue using HDMI - Lakka - Libretro Forums

    Lakka 2.1.1 Audio Issues Using HDMI - Lakka - Libretro Forums

    HDMI Audio Out not working · Issue #321 · libretro/Lakka-LibreELEC · GitHub

    It was the first run on Beta 13, never use it before. Yes a Onkyo TX-NR676E.

    Can you disable your IGP? Or run it without the GTX card?

    Failed to create the opengl context. Check your drivers support openGL 3.3. Hint: opensource drivers don't

    I guess the problem is that you run a system with two GPUs /shrug

    I found thisbut lib32-mesa is already the latest version. Well maybe you need to wait for my next build because the Docker arch image comes with mesa 18.2.4

    The thing is, as it looks to me, dedicated GPUs are quite troublesome in one way or another and unfortunately I have to system for tests with an AMD or Nvidia card.:/

    5schatten what do you mean? Using both HDMI outputs together?

    PCSX2 also won't start.

    Does PCSX2 start with beta 12? Because it won't quit in Beta 13 anyway since either Docker is outdated or Kernel 4.19 screwed something... About the HDMI output do you use an AVR?

    same error in dolphin.

    also tried the usepulseaudio file, retroarch correctly change it's driver to "pulse" but there is no sound at all.

    In your logfiles emulationstation.conf tells me:

    lvl0: AudioManager Error - Unable to open SDL audio: ALSA: Couldn't open audio device: Device or resource busy

    So I'm pretty sure there is something wrong with you asound.conf because otherwise the audio device should not be busy. And if this device is busy you'll have no sound in any emulator or frontend. So double check if your device in asound.conf is correct.

    Which device have you selected in Kodi? And which in the asound.conf?

    Same error if you chose Vulkan as renderer?