Posts by chewitt

  • LE13 Testing for RK3288, RK3328, RK3399, RK3566, RK3568, RK3576, RK3588

    Code
    Machine model: Rockchip RK3566 BOX DEMO V10 ANDROID Board

    I'm not sure if this ^ is the same as the evalation (evb) boards present in u-boot/kernel, but if I was building an image to experiment from that would be my starting point. That said, device-tree changes/improvements to RK boards in the kernel seem to be made on a very individual basis (no bulk enablements etc.) so you may also find the evb files need some fixups; they are inherently often the first board to be added for each SoC type, and then development focus quickly switches to commercially available boards, so the evb boards fall behind current driver capabilities over time.

  • [x86-64] Asus NUC 15 Pro not displaying on LG OLED TV

    Code
    video=HDMI-A-1:1920x1080M@60D

    Make /flash writeable with mount -o remount,rw /flash then edit /flash/syslinux.cfg in nano and append ^ to kernel boot params (put everything on a single line). Reboot with the HDMI cable connected to HDMI-A-1 and see if forcing the initial DRM connector state to 1080@60 solves the problem?

    If not, create /storage/.kodi/userdata/advancedsettings.xml with the content below and reboot:

    XML
    <?xml version="1.0" encoding="utf-8" ?>
<advancedsettings version="1.0">
  <general>
    <settinglevel>3</settinglevel>
  </general>
</advancedsettings>

  • [x86-64] What to log to find the reason for hangs?

    Code
    journalctl > /storage/journal.log && journalctl -f >> /storage/journal.log

    SSH in and run ^ after boot. It will dump the initial log to file then tail/append future journal content to the same file. Now go start something playing until it hangs. The logging task will die when the system hangs but the file will remain on-disk after you power cycle and log back in. Then do:

    a) cat /storage/journal.log | paste

    b) cat /storage/.kodi/temp/kodi.old.log | paste

    Share the URL's and if you're lucky there's a trace of something in the system log that correlates to the kodi old log.

  • LibreELEC (Omega) 12.2.1

    The Kodi release manager tagged the 21.3 release :)

    The same release manager has then paused the push of release notes and wider rollout after noting a minor issue for a couple of the platforms that Kodi ships binaries for. That seems to be taking time; such is the nature of all-volunteer FOSS projects where folk have real-world commitments that need their attention too.

    Until something changes, the tagged 21.3 release is still the tagged 21.3 release and Kodi still seems to play movies and tv shows. Go watch something instead of obsessing over release numbers.

  • [x86-64] What to log to find the reason for hangs?

    There is no need for multiple threads on the same issue so I have merged the latest post into here.

    Using the latest log we can see the following:

    So playback starts at 7:38p, is paused at 8:00pm, resumed at 8:03pm, then the state tracker goes schizoid at 8:43pm. There is nothing in the log to indicate why, but the most logical explanation is the connection to the media source being interrupted.

    Please run "pastekodi" or "journalctl | paste" and share the URL so we can see what the OS is doing around the same time.

  • Is it posssible to run Libreelec as Docker Container with exclusive access to HDMI Port?

    Quote from Mayoru

    Is there a way to run LibreELEC inside a docker container

    No. You can virtualise an OS with a hypervisor. You can virtualise an app with a container. LE is an OS, not an app.

    So you either install Docker on LE (which exists) and then add (and you support) the containers you need. Or you can run another OS that supports containers and run Kodi via a container (something probably exists). Or you run another OS with a hypervisor and run LE as a guest OS on that hypervisor. An OVA for vmware hypervisors exists for project staff to use for dev work and some users are known to run LE that way. Note that the OVA is unsupported; meaning that all other use of it must be self-supported.