Posts by heitbaum

    Yes. Maybe. No.
    Answer will depend.


    In my case - I run nightly+ on my daily system (Generic ADL) , but am developing everyday as you would see. The operating system is starting to take shape for the LE13 release, in that the big changes - compilers, libraries, kernels are pretty much done. So no major changes at the operating system level that would impact are expected. We will be updating to the next Mesa soon.

    As a developer, I run RC software packages, so that we try and address issues with “new packages” before they are released - thus I try to be on the front foot so that the commits are soak tested first. The team in both Kodi and LE do the same.


    There are kodi changes happening (api) that will mandate changes/updates to addons, and this will continue through to the release of Kodi Piers. These may cause you to have to update - if you use these.

    You will need to decide what’s best for you, but if you stay on a version “eg the early sept one” and don’t have fixed the issue you are trying to address, then when the LE13 does come out, the issue may still not be fixed in the release version. In the case of using “new hardware”, I would stay using recent nightlies, to make sure that they work with your system. Older hardware is usually more stable in the linux kernels/graphics software.


    based on Chewitts answers - I would fix your system so that it can play all, as if there is another issue that comes, it might not get fixed. If there is a further problem that is not whitelist. So GUI in 1920x1080 and whitelist max 3840x2160.

    I can see a few things.

    You are using the xe driver - good (as the kernel log indicates that 4908 is not supported properly by the i915 driver.)

    The Kodi gui is 4096x2160 - suggest setting this back to HD

    I believe from the logs that the GUI is working - please confirm

    I believe from the logs the “bootsplash” is working - please confirm

    From the playback logs, you can see that koi probably picks the wrong resolution for playback of the HD stream. Use the whitelist, get it to use a HD resolution.

    The stream you are playing is broken - see ffmpeg logs.

    Please test a known working file. E.g. 2D BBB - http://bbb3d.renderfarming.net/download.html

    I am compiling a nightly image for you to test (current master + the 6.12-rc4 linux) download from https://heitbaum.libreelec.tv - will be there shortly.


    Guessing kernel 6.11 upset it.

    Comparing b5d3f6e...master · LibreELEC/LibreELEC.tv
    Just enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.
    github.com
    Comparing b5d3f6e...8602b53 · LibreELEC/LibreELEC.tv
    Just enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.
    github.com

    So the 29 September 8602b53 image fails?


    Can you share the pastekodi?

    So it’s this one, (you can confirm by remove/adding it in between running lspci)

    Bus 001 Device 003: ID 2013:0462 PCTV Systems PCTV 461

    ==
    Can you please run lsusb -d 2013:0462 -v

    Also journalctl -f when you insert the USB, as the dmesg in the debug log does not show the device at all.

    ==
    Answer seems to be here (Message 8 - no go) - https://tvheadend.org/d/8633-dvb-s2-…configuration/8 not sure if there have been changes since.

    There are lots of references here -

    Missing support for Pinnacle 461e Rev 3 BBH9 · Issue #170 · b-rad-NDi/Ubuntu-media-tree-kernel-builder
    This appears to use a newer Montage M88DS3103C demodulator USB details Bus 003 Device 007: ID 2013:0462 PCTV Systems PCTV 461 Inserting device under Fedora 40…
    github.com
    WinTV-Nova-S2 USB revision BAH9 (PCTV_461E) support, work around and fix · Issue #162 · b-rad-NDi/Ubuntu-media-tree-kernel-builder
    Just repeating the issue raised here: b-rad-NDi/media_tree#12 I created a /etc/modprobe.d/dvb.conf with the contents: options em28xx card=92 Ran a depmod -a…
    github.com


    And 12, 13, ….


    There are some modprobes in 12 that might be worth testing to confirm your card version.

    Fix identified and added

    podman: update to 5.2.2 and addon (1) by heitbaum · Pull Request #9297 · LibreELEC/LibreELEC.tv
    conmon: update to 2.1.12 libassuan: update to 3.0.1 netavark: update to 1.12.2 and fix cross-compile build podman-bin: update to 5.2.2 Fixes [BUG] netavark is…
    github.com
    [le12] podman: update to 5.2.2 and addon (1) by heitbaum · Pull Request #9298 · LibreELEC/LibreELEC.tv
    conmon: update to 2.1.12 libassuan: update to 3.0.1 netavark: update to 1.12.2 and fix cross-compile build podman-bin: update to 5.2.2 Fixes [BUG] netavark is…
    github.com

    You have the syslinux.cfg file correct for the “xe” driver now.

    The MEI and GSC errors are now gone (I have marked the Pull Request as ready for LE13)

    You still have a warning with “Port F asks to use VBT vswing/preemph tables” - here is the code and it is not implemented - https://github.com/torvalds/linux…2253f4035d3be2e - something you could research / check with the kernel (Intel) team - https://lore.kernel.org/all/[email protected]/


    You may want to test using both the i915 versus xe drivers, and see which one works better for you. Officially the i915 driver is suppose to support your card (as you had it working yesterday) - so will leave you to experiment.

    The only error I can see on the i915 is

    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.