I've uploaded testbuilds for Generic & RPi to Index of /testing/
Both are based on latest master with a huge load of updated packages packages: mega bump by MilhouseVH · Pull Request #3537 · LibreELEC/LibreELEC.tv · GitHub & many libretro cores & standalone emulators have been bumped too so feel free to test and report if something is broken. Both should boot fine btw. so don't worry about that.
Sorry but this isn't working for me.
What logs do you need to see what's is going wrong?
It either works or works not. But ofc you have to reboot after you've created the file.
About the Chrome tearing problem Intel users should be able to fix it by creating a xorg.conf in configfiles root dir with the following content:
Section "Device"
Identifier "Device0"
Driver "intel"
VendorName "INTEL Corporation"
Option "TripleBuffer" "true"
Option "TearFree" "true"
EndSectionWorks for so far.
Thnx but i can’t download the file.
It’s forbidden. 403 forbidden
fixed -> file permissions where screwed for whatever reasons 
Can you try this build with Displayport? Index of /testing/nvidia-430.26/
Can you check if your controller works again?
I can do some testing if you want.
I try to add it to the package then
I can add this package probably too GitHub - coelckers/gzdoom: GZDoom adds an OpenGL renderer to the ZDoom source port.
Display MoreDisclaimer: Most of these experiences only apply to Generic x86_64 system.
So... I had to think many things before I've built my ultimate all-in-one retrogaming USB.
And after leaving out some limitations of other distributions, I came to Libreelec RR and it just works. fantastic!!
(I ditched RecalBox and its cousin Batocera for their limited implementation of emulationstation - no game video playback.)
Here are some of my observations:
1) Yes, we've got PrBoom included in this release, but I'm much more familiar to GzDoom and I had to try.
And surprisingly, I don't know what happend to all the dependencies, but GzDoom ubuntu x86_64 package (encapsulated inside .deb file) works ootb without any signs of whining for missing libraries. That means, now I can play most of the modern doom mods such as Brutal Doom v21 without much consideration!
(Depending on the sound output device you're using, you may have to restart audio driver in gzdoom settings menu a few times. And I strongly recommend you to use ALSA as pulseaudio doesn't seem to work...)
TL;DR: GzDoom for ubuntu works just fine if you unpack the excutable from .deb file. And also you need to write an .sh file...
Bash#!/bin/bash cd /storage/roms/games/gzdoom ./gzdoom -file doom.wad ... ...2) While most of the usecases will encourage you to open up an ssh session or similar from another computer to edit es_systems.cfg file, in my particular usecase, I prefer it to be right on the emulationstation, just like on RetroPie.
I've installed System Tools addon to do this, and wrote a simple script...
This shell script file is currently on the 'games' folder under 'roms' folder, but we could always write a new configuration entry on the es_systems.cfg...
Bash#!/bin/bash mrxvt -e /usr/bin/nano /storage/.emulationstation/es_systems.cfgand I also thought it would be great to be able to launch a real terminal inside the emulationstation...
Bash#!/bin/bash systemd-run sh -c . /etc/profile;cd;exec mrxvt -lsTL;DR: You may wish to use a terminal and an editor inside emulationstation... now you can.
3) I wish I also had PCem (a nice PC emulator) to play Win16-Win32 games on this platform, but dependencies turned out to be a great hassle so I gave up on that. It fills the gap between modern NT age of windows and Dosbox while emulating late-90s hardware such as Pentium MMX and Voodoo 2 card.
4) Would there be any chance of RPCS3 docker image be implemented on this platform? I know it's just too much to ask for but if you think it's worth it I'd greatly appreciate it...
RPCS3 docker image (rather unstable PS3 emulator)
In short, thanks for gathering all the necessary parts of EVERYTHING in one tiny package! I'm spending much of my time in this great emulation-OS-thing.
About your GzDoom start script I recommend to adopt my typical standalone start script
and change the es_systems file to run your script then es_systems.cfg#l382
Have you ever tried to run GitHub - libretro/libretro-pcem: Libretro port of PCem, based on mooch's personal fork of PCem, based on OBattler's experimental branch. ?
IIRC RPCS3 should build fine on 64bit so I probably can add the emulator but since I've never owned a PS3 & I only use a IGP I can't really test it.
I will upload a testbuild soon -> DS3 connection should be fixed then 
5schatten How difficult would it be to include 32-bit system libraries (like multilib on Arch) so we can run Steam on LibreElec? It looks like it might amount to tearing apart LibreELEC and building another distro.
The only approach that makes sense to me would be something like this:
so either use an Arch or SteamOS based Docker container to run your Steam games. Or get a Nvidia GPU and use Gamestream. 
Still Having issures with playstation here are the log files
ES Log-
External Content pastebin.comContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.is there any other information you need?
I guess you should start over and read the first post of this thread and the FAQ. Read the wikis for the emulators if you run into trouble first. Then look in the start post how to gather logs & which logs are needed. There is a reason why I spent quite some time to gather these information & wrote them down
looks like it's an upstream issue LibreELEC Testbuilds for RaspberryPi (Kodi 19.0) so probably something to dig a bit deeper first 
Here is the most recent log file:
External Content pastebin.comContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
1. this is not a Retroarch logfile
2. you don't use .cue files as I suggested and needed for beetle-psx
3. you probably didn't read the linked libretro psx wiki
Got another one for the group that is throwing me for a loop PlayStation roms will not launch when using the emulationstation or pegasus front ends but they will launch just fine if i use retroarch there's gotta be something rather simple I would assume that I am missing here, just not too sure what it is also with multi disk games what is the proper naming convention that needs to be used to "stack" the files so each disk does not show up in the front ends (if thats even possible) thanks all.
Sony - PlayStation (Beetle PSX HW) - Libretro Docs
Sony - PlayStation (Beetle PSX HW) - Libretro Docs
You should use a pair of bin+cue fles for psx -> if you still run into trouble provide the emulationstation+retroarch log file.
Turns out its an error 512, here is the log file:
External Content pastebin.comContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
It should look like:
lvl2: Attempting to launch game...
lvl2: /bin/sh -C /storage/roms/prboom/Doom.sh
lvl2: Creating surface...
lvl2: Created window successfully.rename the .wad files to lower case so doom2.wad & make sure your Doom entry in es_systems.cfg looks like this:
<system>
<fullname>PrBoom</fullname>
<name>prboom</name>
<path>/storage/roms/prboom</path>
<extension>.sh</extension>
<command>/bin/sh -C %ROM%</command>
<platform>pc</platform>
<theme>prboom</theme>
</system>The point is that you do not start the .wad files directly because otherwise ES would list the game & prboom wad. Once a matching doom.wad is found a function creates symlinks to doom.sh script files that launch the game then. So long story short make sure you place the files in the correct dirs & revert your changes to es_systems.cfg
PS: it works the same way for Quake 
Been trying to work this out for what seems like an eternity but its probably only been a few weeks but with the emulationstation front end how do I get the doom port (prboom) to show up with my other emulators and stand alone games? Ive been looking but cant seem to find a straight forward answer. thanks for your help
Create a Doom or Doom2 directory in /storage/roms/proboom & place the doom.wad or doom2.wad in the matching directory. The normally it show up in ES. It's a somewhat hacky additions I made otherwise just use Retroarch & scan the proboom directory to start them. You can also google for "Roland SC-55 Music Packs" if you want to play Doom with the original soundtrack sampled from the MIDI files.
FBAlpha is dead, FBneo will be the active branch, all the people working on alpha have moved on after what Barry did
Related to Capcom arcade stick?
Capcom Home Arcade stick using FB Alpha Emulation
It's just for the record because once fbalpha is dropped the old es_systems.cfg files will point to an emulator that won't be included anymore.
I pointed out that the core-info file was missing & should be fixed now [Missing] add core info file for FBNeo · Issue #13 · libretro/libretro-core-info · GitHub also the db files now list fbneo FBAlphaFB to FBNeo · libretro/libretro-database@05e9ff9 · GitHub so in future releases it's probably safe to drop the old fbalpha core.
I can pair them with your build from 20190423
But not in latest testbuild 20190522.
What log do you need?
Update to the latest build & reboot your system to clean all logs. Enable debug logging for Kodi.
1. try to connect your controller that was paired before -> grab the logfile.zip in logfiles
2. reboot again & delete the paired controller
3. try to pair the controller again -> grab the logfile.zip in logfiles
This should provide an overview what could be wrong at the pairing & connecting state. The logfiles zips are needed because several logfiles contain information what's going on, the LibreELEC-Settings addon will probably log to Kodi while dmesg maybe give some information what's wrong on a lower level.
Hi updating from build RR-20190423-716b9f8 to Build RR-20190522-5448d50 i can't pair my PS3 controllers anymore on my NUC7i5BNH.
I know this is a testbuild but just want to let you know.
Reverting to RR-20190423-716b9f8 pairing PS3 dualshock controllers is working.
Thank you for the testbuild.
Well they don't connect if you've paired them with an older build or you can't pair them at all, so even if you've deleted the old pair entry and "repair" then?
Can you provide logs? Maybe the Kernel bump has broken something
