Posts by heitbaum

  • [x86-64] LE 12.0.1 on Intel Meteor Lake

    The only error I can see on the i915 is

  • [x86-64] LE 12.0.1 on Intel Meteor Lake

    Quote from drjackel

    Therefore I have to reinstall with this added in the syslinux.cfg ?

    If I am adding it like this

    7d01 is matching my ID, the installer is coming up with an error saying that the files are not found

    Its a single line. My installed line looks like:

    Bash
    nuc12:~ # more /flash/syslinux.cfg
DEFAULT linux
PROMPT 0
LABEL linux
KERNEL /KERNEL
APPEND boot=UUID=779D-1827 disk=LABEL=Storage ssh i915.force_probe=!4626 xe.force_probe=4626

    you can edit this by remounting /flash on the installed copy. (I am running 6.10)

    e.g.

    Bash
    mount -o rw,remount /flash/syslinux.cfg
vi /flash/syslinux.cfg
mount -o ro,remount /flash/syslinux.cfg
sync
reboot


    Suggest removing quiet if you are debugging.

  • [x86-64] LE 12.0.1 on Intel Meteor Lake

    Now you have a mostly working system, can you share the debug logs.

    Note: I don’t have any whitelists/etc on my Alder Lake for 4K HDR playback (LG tv)

    usual suggestions to test - nothing between your TV and PC - no AVR…. Compliant HDMI cable…


    Jumping ahead - I have begun testing the “xe” driver versus the “i915” driver which requires an edit to the /flash/syslinux.cfg APPEND line - in my case i915.force_probe=!4626 xe.force_probe=4626 - not saying that this is a fix, but is where Intel are investing time in for the modern iGPU driver. You will need your VGA cards PCIid if you are testing this.

  • [x86-64] LE 12.0.1 on Intel Meteor Lake

    LE12 will only be release with the 6.6 kernel.


    There is an Omega image in the LE13 nightlies (before we switched to K22 Piers) is has kernel 6.9.5 - link below. Otherwise it would require a custom image.

    GitHub - LibreELEC/LibreELEC.tv at c780187ec307e84c97391f8e37a03f31738747a8
    Just enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.
    github.com

    Everything after that is K22.
    https://test.libreelec.tv/13.0/Generic/Generic/LibreELEC-Generic.x86_64-13.0-nightly-20240714-c780187.img.gz

  • 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.