Posts by escalade

Minor update with mesa 18.2-git, improved kms detection and fixed reicast. Also added the new OIT reicast core.

I think upgrading might be fine, but downgrading would probably require restoring the backup.

Indeed, didn't actually test it yet -o is only valid when using [ or test. It's ugly, was always thinking to make it a choice under LE settings when I had the time.

1. Beetle-psx doesn't use hw unless you specify that in core options

2. Don't use cores from the updater as they are built for a different distribution (i believe debian)

3. Last I heard gamestarter just picked binary cores from my builds, not sure about these days

As you can see, it's using DRM/KMS with a resolution of 1360x768 @ 60Hz. The X.org DDX driver uses modesetting to set the refresh rate, so DRM/KMS will use the same refresh rate. Which is why I suggest switching to the modesetting driver, to see if it will run at 60Hz.

X.org, not RA.

Refresh rate problem after update from Openelec

Look in your RA logs to see if you're on KMS. I can't speak for what's been done in this build.

If your X.org is locked to 30Hz for some reason, then using X11/opengl for RA will definitely not be a smooth experience. I'd try switching to the X modesetting driver, and also make sure that you are using KMS in RA.

Impossible, as drivers reside in the kernel which is not upgradeable in LE.

Blindly trying different things is not the best way to diagnose a problem. Try comparing the RA logs and find the actual difference. Like I said, my build is LE9 more or less.

Not correct, except for Kodi (which has nothing to do at all with emulators) most of the core components in my build is more recent than in LE9.

If you're not running at 60Hz, that's your problem. Try turning off vsync.

Updated avx build: reverted to 4.17.5 (due to unresolved build issues with 4.18 and openssl 1.1), llvm 6.0.1, fixed qemu-arm, use kms by default if using modesetting driver, updated libretro cores (reicast, mgba, mame2016, fbalpha, dosbox, desmume, citra)

I've also updated my escalade1/arch-build container on the Docker hub, instructions how to build with it has been added to the first post. It's a container based on base/archlinux with the minimal package set needed for building LibreELEC.

Quote from 5schatten

So would your ps2 Docker container theoretically run when used inside the LE Docker addon?

Yes, why not? That's how it's supposed to run. I recommend going through the Docker "get started" part of the documentation to get an understanding of how Docker and its containers work.

Depends what you're looking for. The docker-system package is an older version of the docker addon, just modified to install to target. The docker-containers package was used to launch my custom containers from the Docker hub.

Quote from Frits1980

Have you even read what I've done? Then you should know that I've done exactly what everybody said I should do. So no need to make accusations like that. I know that I have to try everything people give as possible answers to the problem. The problem is just not resolved. So that is why I'm saying it just might be a bug in the software, even though everybody is convinced it is not.

Yes I have. There is no accusation from my side, if you are still claiming that it's an LE issue after having the problem explained for you several times then you are ignoring the answers. I've personally used the workarounds mentioned in this thread successfully, it's a well known KODI issue.

I suppose it feels like that if you ignore all the answers that are right in front of you.

Do a backup/restore of /storage/.kodi when upgrading and downgrading and it should be no problem.

Updated avx build: linux 4.18-rc2, systemd 239, bluez 5.50, fixed spotify

If the goal is to simply play BD, you don't actually need MakeMKV. A proper KEYDB.cfg in /storage/.config/aacs should do the trick (I think).