RetroELEC Kodi+Wayland+Emulationstation+RetroArch (x86/XU4/RPi)

  • slacker666

    Should be in the "quit" submenu, I think the logic that built the option was faulty indeed. Try the latest images, except for RPi2 which I haven't updated yet. I will build it with vc4 driver and Wayland in time.

    Same issue I'm afraid, Kodi not visible from shutdown menu. Tried your VMWare image though to test with.

  • New generic image is out:

    • Kodi 18.5
    • Starts up with Kodi, but can be changed through kernel command line options frontend=ra/frontend=es/frontend=kodi/frontend=none
    • Polished and simplified systemd units for a faster startup
    • Linux 5.4-rc8
    • Mesa 19.3-rc3
    • Latest Wayland/Sway/wlroots git
    • Updated RetroArch and libretro cores
    • Updated RPCS3
    • Improved Plymouth boot splash routines
    • Set default alpha sorting for Flycast core to "per-pixel (accurate)" to solve black screen issue
    • Fixed Emulationstation menu items, working terminal etc.
    • Included glmark2 and mesa-demos (glxinfo etc.)
    • Antimicro is still included but not started by default

    I've dropped the builds without Kodi to avoid confusion. I've no outstanding issues with Wayland, so I declare that the future is here :) Everything except Kodi (GBM/GLES) and PCSX2 (OpenGL/Xwayland) is now running natively.

    slacker666

    Can you test now? ;)

  • New generic image is out:

    • Linux 5.4.1
    • Mesa 20 git with glthreads enabled by default
    • Systemd 244
    • Latest Xwayland git brings multi-buffering (fixed some noise in the picture that I experienced with PCSX2)
    • Latest RPCS3 and LLVM 10
    • Installing from LibreELEC addon repository in Kodi works again
    • Latest puae/vice libretro cores reduces input lag by 1 frame
    • Kodi on GBM/OpenGL (previously GLES)
    • audiodecoder.sidplay plugin included
  • Do you (or anybody) have any idea why I cannot even boot the image in KVM? (from inside unRAID)

    It just freezes in the initial selection (5 sec timeout).
    I cannot even type.
    Sometime if I am fast enough I can type one of the options, but it stays there.

    Any ideas?

  • Try typing "installer", I'm guessing it freezes after boot and not at the prompt although it may not be displayed. The installer will skip boot splash and maybe give a clue on what's wrong.

  • I am trying.

    Even when I have the time to type "installer", it freezes right then and there - doesn't even give an indication if it freezes after I press enter (and because I press it) or before.

    I will try more and let you know.

    Note that I tried other LibreElec custom version and I can go forward way more (but I prefer yours) - still not finish it though.

    Can the whole issue stem from that I don't share my GPU (and any of the hardware)?

    I don't plan to use it "properly" yet (and don't expect realistic performance), just link to it through VNC. Is this an unsupported scenario?

    Does it expect to address the GPU so early in the boot?

  • One difference could be that I compile with -march=silvermont, so your CPU needs to be not ancient. I use the same bootloader as other LibreELEC builds so can't see a reason why this should work any differently. I have tested on VMware and VirtualBox no problems.

    There's no VNC, Kodi runs directly on GBM/OpenGL and emulators run on Sway/Wayland.

  • CPU is i5, not fresh, not ancient.

    I know you don't supply VNC, VNC is supplied by KVM that I try to run this from.

    Probably that is the problem - although I find it strange that it happens in the first 2 seconds of the boot.

  • New generic image is out:

    • Kodi 18.5
    • Starts up with Kodi, but can be changed through kernel command line options frontend=ra/frontend=es/frontend=kodi/frontend=none
    • Polished and simplified systemd units for a faster startup
    • Linux 5.4-rc8
    • Mesa 19.3-rc3
    • Latest Wayland/Sway/wlroots git
    • Updated RetroArch and libretro cores
    • Updated RPCS3
    • Improved Plymouth boot splash routines
    • Set default alpha sorting for Flycast core to "per-pixel (accurate)" to solve black screen issue
    • Fixed Emulationstation menu items, working terminal etc.
    • Included glmark2 and mesa-demos (glxinfo etc.)
    • Antimicro is still included but not started by default

    I've dropped the builds without Kodi to avoid confusion. I've no outstanding issues with Wayland, so I declare that the future is here :) Everything except Kodi (GBM/GLES) and PCSX2 (OpenGL/Xwayland) is now running natively.

    slacker666

    Can you test now? ;)

    Sorry for being away/not respondig. At the moment I do not have a box that I can try it out with. Currently using your old LibreELEC v8.2 custom image which works fine for me. Will get back once I get a box to test it out with.

    I have/had this issue with my Intel NUC with an Atom J3455 CPU and one of the images here (cant remember which, solved by using a different image (back when kodi wasnt integrated), but went back to an older image (based on Kodi v17.x) from escalade and that works. And I havent tried it out after that.

  • Hi. Sorry for my English. But I have the same problem on the virtual machine after typing the installer writes that the folder was not found and the installation from a USB stick prompts that it cannot mount flash memory.

  • The RPi image is severely outdated, I've removed it for now. Will move to vc4 and wayland for RPi later.

    New generic image is out:

    • Linux 5.5-rc2
    • Qt 5.14
    • Updated Mesa/LLVM, RPCS3 and libretro cores
    • PPSSPP does not work with Wayland (or KMS) at the moment, solved it by running in Xwayland which runs great
    • Updated xfstools, f2fs-tools and btrfs-progs
  • question for you. Does the build work on RPi4 ? I really want to combine a media center and game center with out dual booting kodi and lakka (which currently is the only emulation distro compatible with my device)

    Retropie does have a kodi addon through experimental packages but it's to wonky to work right on RPi4

  • The RPi image is severely outdated, I've removed it for now. Will move to vc4 and wayland for RPi later.

    New generic image is out:

    • Linux 5.5-rc2
    • Qt 5.14
    • Updated Mesa/LLVM, RPCS3 and libretro cores
    • PPSSPP does not work with Wayland (or KMS) at the moment, solved it by running in Xwayland which runs great
    • Updated xfstools, f2fs-tools and btrfs-progs

    Some initial feedback (Intel i915 platform):

    * Kodi seems to work quite well

    * Emulations station and RetroArch work. Audio on RetroArch is distorted.

    * Firefox hangs while browsing and sometimes crashes when watching videos / movies.

    'dmesg' shows the following:

    [ 253.717593] i915 0000:00:02.0: GPU HANG: ecode 8:1:0x85dffffb, in sway [979], stopped heartbeat on rcs0

    [ 253.717597] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.

    [ 253.717598] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel

    [ 253.717598] drm/i915 developers can then reassign to the right component if it's not a kernel issue.

    [ 253.717599] The GPU crash dump is required to analyze GPU hangs, so please always attach it.

    [ 253.717600] GPU crash dump saved to /sys/class/drm/card0/error

    [ 253.818910] i915 0000:00:02.0: Resetting rcs0 for stopped heartbeat on rcs0

    [ 277.700806] i915 0000:00:02.0: Resetting rcs0 for stopped heartbeat on rcs0

    [ 305.328406] docker0: port 1(veth9015086) entered disabled state

    [ 305.328580] vethd92864a: renamed from eth0

    [ 305.406963] docker0: port 1(veth9015086) entered disabled state

    [ 305.418372] device veth9015086 left promiscuous mode

    [ 305.418379] docker0: port 1(veth9015086) entered disabled state

    [ 310.665831] Asynchronous wait on fence i915:sway[979]:291c timed out (hint:intel_atomic_commit_ready+0x0/0x54)

    [ 315.674310] i915 0000:00:02.0: Resetting rcs0 for stopped heartbeat on rcs0

    [ 375.530248] docker0: port 1(veth9dbe76f) entered blocking state

    [ 375.530253] docker0: port 1(veth9dbe76f) entered disabled state

    [ 375.530353] device veth9dbe76f entered promiscuous mode

    [ 375.920760] eth0: renamed from vethe38bd60

    [ 375.934393] IPv6: ADDRCONF(NETDEV_CHANGE): veth9dbe76f: link becomes ready

    [ 375.934454] docker0: port 1(veth9dbe76f) entered blocking state

    [ 375.934457] docker0: port 1(veth9dbe76f) entered forwarding state

    [ 713.673405] perf: interrupt took too long (2521 > 2500), lowering kernel.perf_event_max_sample_rate to 79200

    [ 867.629023] perf: interrupt took too long (3164 > 3151), lowering kernel.perf_event_max_sample_rate to 63000

    [ 1121.589470] perf: interrupt took too long (3979 > 3955), lowering kernel.perf_event_max_sample_rate to 50100

    [ 1296.659249] Asynchronous wait on fence i915:sway[1589]:10b6a timed out (hint:intel_atomic_commit_ready+0x0/0x54)

    [ 1300.813647] i915 0000:00:02.0: Resetting rcs0 for stopped heartbeat on rcs0

    [ 1365.662484] i915 0000:00:02.0: Resetting rcs0 for stopped heartbeat on rcs0

    [ 1521.139933] perf: interrupt took too long (5051 > 4973), lowering kernel.perf_event_max_sample_rate to 39600

    [ 1934.711125] Asynchronous wait on fence i915:sway[1589]:1b8a0 timed out (hint:intel_atomic_commit_ready+0x0/0x54)

    [ 1939.719734] i915 0000:00:02.0: Resetting rcs0 for stopped heartbeat on rcs0

    [ 1939.946970] vethe38bd60: renamed from eth0

    [ 1939.987282] docker0: port 1(veth9dbe76f) entered disabled state

    [ 1940.005109] docker0: port 1(veth9dbe76f) entered disabled state

    [ 1940.017128] device veth9dbe76f left promiscuous mode

    [ 1940.017134] docker0: port 1(veth9dbe76f) entered disabled state

    [ 3640.563563] perf: interrupt took too long (6363 > 6313), lowering kernel.perf_event_max_sample_rate to 31200

    [ 8388.785593] perf: interrupt took too long (9279 > 7953), lowering kernel.perf_event_max_sample_rate to 21300

    card0-error.txt