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.
Posts by heitbaum
-
-
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.
-
Hi cartman74 - enabled debug crash logs may help pinpoint the issue.
-
I don't know what a "PR" is. In this case, it could be "Product Recall".
Hi synrgii ”Pull Request” (referred to as a PR) - https://wiki.libreelec.tv/development-1/…al#pullrequests
-
I wouldn’t create it as a custom image. As an addon, with a little bit of patching or sed. The addon can be made to work right. It is all done by the build scripts.
One I have been looking at recently is net-snmp (so DATADIR would be replaced as below)
LibreELEC.tv/package.mk at 9670b47b41c8c5bdada28ed21474af33e2d2bdf3 · LibreELEC/LibreELEC.tvJust enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.github.com -
I had a look for you and this mpd plugin is no longer maintained.
https://github.com/lzoubek/xbmc-plugin-mpdc (probably not much required to get is Matrix compatible though)
does using the mpd-mpc command line give you the output you are looking for? Also does the android/iOS/web client give you the result. https://www.musicpd.org/clients/ The mpd service included in LE is the server component of MPD.
-
Whitesak - I have started looking at your issue - but could you please share the error / missing dependency that you are getting.
There were some build issues with mpd a while ago, but these are closed.
I checked the currency of mpd and it is the latest - a minor update to mpd-mpc is the only potential update.
-
Please enable debug and share the logs. Crystal ball is cloudy. 🙂
