Posts by heitbaum

  • Nightly Builds

    I have explained it a few times now. But I will again for clarity.

    Jobs are scheduled (if there are changes in the last 24 hours and an image will be built, it does not check it an image of that hash exists already.)

    Jobs are also run manually, in this case the RPi ones were run to address a RPi 2GB built “quickly.”


    There is nothing to be read into the images with different dates and the same hash. There maybe many of the same hash, you are welcome to use any off them, though the contents will have different compile dates, they will be from the same source.


    Hope this fully answers the questions.

  • [x86-64] No HDMI Signal with LE 12.0.1

    dipswitch the pastekodi log is from "Starting Kodi (20.3 (20.3.0) Git:20.3-Nexus). Platform: Linux x86 64-bit" and the smb log is from "Starting Kodi (21.1 (21.1.0) Git:21.1-Omega). Platform: Linux x86 64-bit"

    I can see Nvidia in the nexus log

    Code
    2024-08-27 21:56:32.916 T:1101     info <general>: CRenderSystemGL::InitRenderSystem - Version: 4.6.0 NVIDIA 470.161.03, Major: 4, Minor: 6
2024-08-27 21:56:32.916 T:1101     info <general>: GL_VENDOR = NVIDIA Corporation
2024-08-27 21:56:32.916 T:1101     info <general>: GL_RENDERER = NVIDIA GeForce GT 1030/PCIe/SSE2
2024-08-27 21:56:32.916 T:1101     info <general>: GL_VERSION = 4.6.0 NVIDIA 470.161.03
2024-08-27 21:56:32.916 T:1101     info <general>: GL_SHADING_LANGUAGE_VERSION = 4.60 NVIDIA
2024-08-27 21:56:32.916 T:1101     info <general>: GL_GPU_MEMORY_INFO_TOTAL_AVAILABLE_MEMORY_NVX = 2097152
2024-08-27 21:56:32.916 T:1101     info <general>: GL_GPU_MEMORY_INFO_DEDICATED_VIDMEM_NVX = 2097152

    the pastekodi is a mix of nexus and omega:

    the "journalctl -a -b -0" is Omega and the "/storage/.kodi/temp/kodi.log" is Nexus


    Suggest using the USB Key boot (using the run option) before doing too much - this will isolate what is happening.

  • Nightly Builds

    Your probably reading too much into it. The build system runs many workflows and then many jobs within those workflows. We have been doing extra LE12 builds recently which will push out or cancel other builds. When a workflow runs - it runs 2 jobs at a time (in random order for the target architectures) and will pick the hash at the time of the job kick off - not the workflow kickoff.

    Whilst the job is scheduled nightly - it doesn’t mean there will always be a nightly.


    You can always check the scheduler for LE13 builds at https://github.com/LibreELEC/acti…/build-LE13.yml
    Or in total at https://github.com/LibreELEC/actions/actions

    may help the crystal ball be less cloudy.

  • Nightly Builds

    You can check the inner workings of the CI/CD environment here. https://github.com/LibreELEC/actions/actions builds of LE12 and LE13 take 18 hours each, and addons take 10-12 hours each. Builds only get kicked off if there have been changes in the last 24 hours. Workflows can only be in the queue for 24 hours. Priority is given to binary addons when required.

    So when only LE12 or LE13 are getting changes, you will see images and addons updated every 28-30 hours, but when changes are occurring on both LE12 and LE13 - you will see a 60 hour cycle.

    Workflows are cancelled automatically when passing 24 hours. Workflows (addons / images) are also cancelled when they won’t actually make change - eg addon update doesn’t need images rebuilt - because they were the same.

    Hope that answers your questions.

  • [x86-64] Open-iSCSI Support

    This bit I can’t help with, as I haven’t used iscsi.

  • [x86-64] Open-iSCSI Support

    👍 Glad you got your build working.

  • [x86-64] Open-iSCSI Support

    Quote from Kleiner

    I update gcc and g++ to version 14.1.0.

    I tried lunch build (with fix and without fix(loading new git) ) , but not success.
    Now error cmake (013/313)

    I installed cmake, but not success.

    We build our own copy of cmake (it is failing for some reason)

    Details will be in the build.LibreELEC-Generic.x86_64-13.0-devel/.threads/logs/13.log log file


    1. But first go back to “your working machine” before you added gcc14. Ubuntu doesn’t have a gcc-14

    2. Check the build. Run something like the following commands

    cd /home/tod

    mv LibreELEC.tv old

    git clone https://github.com/LibreELEC/LibreELEC.tv.git

    cd LibreELEC.tv

    # wget … as above

    # git am … as above

    # we are not going to build open-iscsi yet

    # let’s test you build environment

    make image

    # share your success/logs

    # move on to scripts/build open-iscsi


    Booting an image with iscsi may not/probably won’t work (or you might need to do some/a lot of work) we haven’t tested an iscsi build for a long time.

  • [x86-64] Open-iSCSI Support

    Quote from Kleiner

    Thx.
    On the computer where I am building libreelec (x64 Ubuntu 22.04 - 64bit) is installed. At the moment I am compiling gcc-14, because... This fix, as I understand it, requires version 14. The terminal showed this: Application: open-iscsi: fix build with gcc-14.
    I try it and write here.

    You won’t need gcc-14 to do the build (it will cause other issues), it looks like it has made your build host unstable.

    The patches themselves are for the LE build system (as we compile a copy of gcc during the build)

    The LE build will run with no problems on a “clean Ubuntu 22.04 or 24.04” system.

  • [x86-64] Open-iSCSI Support

    If in your LibreELEC.tv directory you do the following, that patches to fix the compile error will be added.


    Code
    wget https://github.com/LibreELEC/LibreELEC.tv/pull/9163.patch
git am 9163.patch

    # or the following if you are not using a git clone

    Code
    patch -p1 < 9163.patch