Correct. 5.12 at a minimum and really 5.15 for good function. There are also a lot of Intel patches in nighties over the last 12 months.
Posts by heitbaum
-
-
Hi Mettbrot I haven’t had an out of sync screen for a while now. I have connected the nuc11 via the AVR too. I am running my dev branch image - but nightly Generic is pretty similar for the purposes of the Intel packages.
-
Hi debarr Matrix was moved to Python3 - more info here - https://kodi.wiki/view/General_i…ion_to_Python_3
-
Hi succo - the nightlies use GBM (not x11) - you will need to use a (wl or x11) image - which has some nvidia support - this is not compiled as a nightly - so you will need to compile your own.
-
Looking at the R&D we have now undertaken - I think the sentence could be written something like:
using samba to serve files from kernel ntfs3 …… whereas using samba to serve files from ext4 ….. In earlier kernel versions …. using ntfs-3g, samba was able to serve files from the ntfs external drive … (without issue) …..
I’m not sure that we have validated anything else yet? What does
Codetime dd if=file.mov of=/dev/null bs=4m(or similar) show from a performance perspective? From each of the file system types?
-
Hi beredim - looks like it was added in 5.13-rc1 - https://lkml.org/lkml/2021/4/27/526
Any reason why you would want to run the PN50 with LE10 versus the nightlies? I know I had to run 5.12+ to get a good experience with the Intel TGL. Naming patch files is done via git-format-patch. And the numbering is not really formalised in the Linux patches - whilst the Kodi patches are “999.* - patches backported from upstream”? I’m probably not in favour of backporting that patch into the libreelec-10.0 branch as a patch. Was the patch backported in into the 5.10.x series? (Could be an option to bump the kernel to 5.10.x) From a testing perspective - any patch in default should,be tested against all of the other architectures.)
An alternative option for you could be to backport the couple of 5.15 commits from HEAD into your development branch and run with your community image. The planned release schedule of 10.0.x is definitely not fast and furious
At some stage there will be a kernel bump for Generic (but probably not till 10.2 and would probably be a backport of something from nightlies). But none planned for 10.0.x at this time.
-
mo123 as someone in the last 18 months who has learnt the ropes on what is required to maintain the packages for a distribution (and the occasional other bits and pieces) a challenging - but rewarding investment of time. As you you will have seen in my Kernel / u-boot PRs started out getting a build system together and the list of tests… then a lot of test / update. Even a patch into 5.17-rc6 to fix the Qualcomm build issue.. For packages spending time testing pre-releases, discussing, fixes to and testing upstream, so that we can use the released versions. For the RK - happy to test against RK3308, RK3399pro, RK3568, RK3388 - though only have the 3308 on my desk at the moment… might be an excuse to get the others back on my desk.
-
Can you believe that I have not yet been offered a Samba bugzilla account or got any feedback from them after 3 attempts?
Also, the Samba 4.16 inclusion in LE11 must have taken a back seat in favour of more pressing matters.
on my work list … not forgotten but kernel 5.16.11 and gcc / glib and binutils trumped it. ETA on 4.16 in nightlies would be mid/late march at this stage. Waiting till 4.13 goes EOL and I push the final 4.13 into LE11/LE10 - then can drop 4.16 in. There is still compile error (probably I need to update the patch - but only did the basics on the PR to get it unpacking and compiling as my WIP) -
offbeat - message from the PR - so looking like the addons, etc.
==
crashes are skin related (estuary mod v2), I contacted author.
_Originally posted by @polojoe in https://github.com/LibreELEC/Libr…ent-1045970954_
-
Included in media-driver 22.2.1 now - https://github.com/LibreELEC/LibreELEC.tv/pull/6242
-
On versioning - Samba 4.13 is being tracked as it is in LE10(and one of the few packages that is backport Ed - for its security fixes). In March/April - security patches will stop being released for 4.13 and the :master will start tracking the to be released 4.16 release of Samba.
-
As a note - the Ntfs version being used in nightlies is now ntfs3 - https://github.com/LibreELEC/LibreELEC.tv/pull/5838 - which is the Paragon Kernel version. but it is a different version to the ntfs3g that we and other distributions were using before kernel 5.15.
-
That seems to be working perfectly. Thanks a lot.
Welcome. Backport added to LE10 code base.
-
Please try this zip file - if ok. Ill complete the PR.
-
Hi tomera69 - as a Gen11 TigerLake user - it didn't work until a mid release kernel 5.11 - a challenge playing catchup on hardware versus software. Intel generally do a good job in having the software ready. But there have been a large number of updates into the kernel mainline in the last 12 months. The LibreELEC 10 kernel (5.10.x - was released 2020-12-13) The Linux Kernel Archives - Releases which is why the 2021 CPU is not "fully supported / has issues" - we keep our LibreELEC nightlies up to date - we currently have 5.16.5 in place (Released 1st Feb 2022) - linux: update to 5.16.y by heitbaum · Pull Request #6141 · LibreELEC/LibreELEC.tv (github.com) - which should support ALL available shipping Intel CPUs.
>> There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees. <<
Here is a diagram showing how mainline kernel development occurs. As you can see features are NOT backported to a Long Term Support (LTS) kernel. And given that the CPU would be after the LTS 5.10 kernel was released - the support may / may not be in the 5.10 kernel.
-
Hi LibDisPro - just checking what hardware and version of LibreELEC you are using? (assume you are using LE10 or LE9)
With LibreELEC nightlies it is in:
- Add-ons / Services / Prometheus Node Exporter
- it is not in LibreELEC 10 or earlier (but could potentially be backported to LE10)
It was added to the LibreELEC master from this PR:
-
GDPR-7 - is your comment for the flickering - https://github.com/LibreELEC/Libr…ment-1027400840 - the same as - vhgroup's video? Kodi Flickering TV Menu
-
Starting to collate here - [BUG] Collated x86 GBM issues · Issue #6180 · LibreELEC/LibreELEC.tv (github.com)
I have been threating to do for a while.
Can you all please share the debugs
- any custom boot settings
- also what settings have you set in hardware decode.
