Posts by chewitt

  • VideoStrong KII Pro S905 - No tv adapters

    I made an effort about 2-years back to clean-up the Linux 3.14 era drivers so they compiled against a modern kernel. These can be found here: https://github.com/chewitt/linux/commits/dvb-sucks and I rebased them against Linux 6.12.y only last week. However there's no Amlogic demux driver in the upstream kernel (which is essential) and we need tuner/demod drivers to be independent rather than interdependent so we can describe a box configuration in device-tree rather than compiling everything into a single monolithic driver as the Amlogic vendor kernel does. The monolithic approach works for box manufacturers who need to support a single box with a single driver recipe, but doesn't work or scale when you need to support a range of devices; each with a different tuner/demod/demux driver combo.

    It's not a huge amount of work to get done, but it takes a certain skillset and mindset to hande the code archaeology and writing of modern kernel drivers. It's already been 'years' and nobody volunteered, so I have low expectations of it ever happening.

  • VideoStrong KII Pro S905 - No tv adapters

    The 12.0.1 release notes that nobody reads describes some "no" items for the AMLGX image:

    • No support for updates from older LibreELEC and CE releases (clean install is mandatory)
    • No support for internal eMMC install on box hardware except WeTek Hub/Play2
    • No support for SSV6501 and S908CS WiFi chips
    • No drivers for in-box DVB tuners
    • No hardware deinterlacing
    • No HDR to SDR tonemapping

    The latest and last release that might support them is LE 9.0.1 although dtech has an LE 9.2.8 image that might also contain them (but I don't track it, so no guarantees). The upstream kernel in LE 12/13 has reasonable support for USB tuners.

  • Jellyfin playback stops or skips to next episode

    You can start with a Kodi debug log, but I suspect that's not going to be enlightening. If you're able to test and replicate the issue with Kodi running on a general purpose Linux OS like Ubuntu that would be helpful to eliminate LE itself from suspicion and allow you to concentrate on the add-on; which will have a support thread in the Kodi forum where the add-on authors hang out.

  • [RPi5] 4K/60Hz on LibreELEC 12.0.1

    MatteN is probably on the right track with his answer. Remove EDID captures and connect the RPi4 board directly to the TV until you get things working. You probably need to experiment with different TV ports and/or port settings to ensure it can accept 12-bit 4:2:2 input, which is what the RPi board uses when 10-bit YUV 4:2:0 (which it cannot output) is needed by media.

    See https://wiki.libreelec.tv/configuration/4k-hdr#id-4k-60hz

    Note that RPi4 (not RPi5) also requires 4K modes to be enabled in config.txt. You do not want to force the Kodi desktop to 4K60 unless you want the UI to be slow and annoying. Mode switching for playback is fine, but the UI is best in 1080p.

  • SmartTV+LibreelecPC

    I'd guess that "no signal" refers to the HDMI input signal and when the LE device is powered on the HDMI input is being switched, but the TV fails to lock on the resolution and you see an appropriate message. Killing the antenna signal sounds really weird and I heard nothing like that before.

  • S912 TICTID X9T (Tanix TX9 clone) - LED/VFD

    The FD628/TM1628 driver was submitted upstream and then bike-shed'ed to a standstill, so it remains un-merged and the author has no plans to resurrect the effort. I have been including patches in the Amlogic kernel that I maintain for the AMLGX image for some time. To have the driver work, the VFD layout needs to be correctly described in device-tree. I've created device-tree files for other boxes in the past, but the only one I still have in the AMLGX image is for the TX3-mini. The driver is not designed for use with openvfd or lcdproc userspace tools, although the openvfd repo is useful for figuring out the pins that need to be bit-banged to make things work. The nearest you can get with userspace configuration is issuing a sequence of fdtput commands to modify the device-tree file that boots the box (which updates will overwrite).

    This kernel branch has the commits to add the driver, and a device-tree for Tanix TX9-pro with the VFD described:

    Commits · chewitt/linux
    Linux kernel source tree -- WARNING I REBASE MY BRANCHES! - Commits · chewitt/linux
    github.com

    Note that this was 10x kernel releases ago and I've no idea now if these patches were ever proven on a real TX9-pro, or whether your TX9 (non-pro) clone will need/use the same layout; although I'd guess the spec difference is limited to RAM size and WiFi/BT module used. Typically users show-up excited that AMLGX exists and then go quiet once they realise playback is not as polished as the older vendor kernel images (not that these are perfect either) so not all device-tree files that I create get tested and sent upstream.

    The device-tree compatible also needs to be in to https://github.com/LibreELEC/Libr…s/vfd-clock#L25 .. although it looks like I've done that for the tx9-pro in the past and never cleaned it up.

    There are build instructions for creating your own LE images in the wiki if you're that way inclined and want to experiement. I can also pick the patches back into my LE13 test images; although I'm currently working on a kernel driver fix for a long-running bug and it might be a few days before I have that resolved and release a public image again.

  • Jellyfin playback stops or skips to next episode

    I'd guess that if you have Kodi configured to play the next episode and media is opened from a view that lists multiple episodes .. it will do what it's been told to do.

    No ideas on the stop/exit although Kodi should buffer if the connectivity is poor, so it sounds more like an issue with media itself or something server-side or how the add-on works /shrug

  • Settings Tutorial

    Kodi has a comprehensive wiki here: https://kodi.wiki/view/Main_Page and a reasonable amount of LE specific things are covered here: https://libreelec.wiki .. there are no tutorials largely because it's an effort to write them (anyone could contribute them to the wiki but nobody does) and there are lots of use-cases (so more effort).

    NB: It's generally easier to ask a specific question and then people will give you specific help and answers.

  • [x86-64] Chrome Browser on Dell Wyse 3040

    Quote from Da Flex

    Chrome is only available on Generic-legacy, because it needs X11 as display server.

    I would assume he knows that since he tried to boot Legacy.

    basubasu see if adding something like video=HDMI-A-1:1920x1080M@60 to kernel boot params in syslinux.cfg has impact. If not, add ssh to boot params so you can login over Ethernet to run "pastekodi" and share the log URL generated. The rest of the OS will be functional even if Kodi/Xorg has an issue with something.