AFAIK the images Oleg was building are/were largely the same as official nightlies (other than nightlies now being on newer kernels and other packages). I've not heard of audio issues with current nightlies. Are you using HDMI output or the analogue port?
Posts by chewitt
-
-
Is that what you meant by "manually update"?
As nightlies can contain breaking changes we don't publish a 'releases.xml' file so neither manual update from the GUI or auto-update are possible. You need to download the update file to /storage/.update and reboot.
-
Papaya5595 I've updated the RK3588 images in my test share to include newer iwlwifi firmware.
-
I assume this is because the build I'm using is an old alpha build and the repository doesn't support older alpha builds.
As a general rule we keep the current and current -1 repo versions for development images online, but we remove older repos to reclaim disk space. The repo version aligned to that image has probably been deleted.
You should be able to run touch /storage/.update/.nocompat and manually 'update' to a current LE13 nightly. The compat check needs to be skipped as the image name changes from ARMv8 to RK3399.
-
Thanks for confirming. I've submitted https://github.com/LibreELEC/LibreELEC.tv/pull/10859. Once merged support will be in LE13 nightly images and you can remove the /storage/.config overrrides.
-
I'm a bit confused.
Most people get confused with Docker and containers so don't sweat it
Containers virtualise an app within a supporting environment. In our case the app binary is 'make' although this is not that clear unless you understand how our buildsystem works.
The docker steps are correct. The info that's probably missing is an instruction to git clone the LE sources first.
Then you need to 'docker build' the container by 'pulling' from a docker source. This is a local Dockerfile and not a URL or a pre-built container from the online docker 'hub' repo. From a cloned LibreELEC.tv source folder the source files are in tools/docker/
Then you need to 'docker run' the container, with the run command providing instructions to the docker runtime on directories to map, and buildsystem variables (PROJECT=X, DEVICE=Y, ARCH=Z, etc.) that are passed to 'make' to define what image to create.
It might be easier to run an Ubuntu server LTS release VM under proxmox and SSH into that environment to install dependencies, clone sources, and build using the CLI commands that you can see in the normal build instructions. The main reason we support Docker building is for our own CI use-cases building nightlies etc. .. not because it's a better/easier option.
-
Why don't you just publish a list of common channels that work?
If an add-on is published in the Kodi repo, the Kodi ecosystem assumes it works and is maintained. If it doesn't work, that's an issue to be reported to the add-on maintainer(s) via their add-on support thread in the Kodi forum.
My back story is irrelevant but yours somehow transcends all criticism. how relevant is it that you as a moderator have a Pi that works to a new user whose doesn't?
My backstory and role as a moderator doesn't have any relevance to your inability to provide basic information. Six paragraphs of wordage in your last post enlightened us to one piece of useful info: You have an RPi5. The rest of your posts are just complaining about add-ons not working without even bothering to mention the name of one of them. I've suggested twice that you provide us with logs and more specific info. The ball is firmly in your hands to provide facts to help the people who are (or in my case, were) trying to help you.
Good luck
-
I have a bunch of add-ons installed (on an RPi5) and everything works. Add-ons like YouTube need personal API keys to work. Add-ons that access legal streaming services increasingly need some kind of working credentials, and some add-ons access services that are geolocked to specific countries.
Again, without logs or knowing any specifics of what you are trying to install and use (preferrably with less irrelevant backstory) we cannot provide any specific advise.
-
Yes, same image name (but image content is updated). Just drop into /storage/.update and reboot.
-
Most add-ons are not authored by LE staff and 'legal' media content/streaming ones are generally supported via threads in the Kodi forum where the add-on creators hang out. If you want us to help, you'll need to divulge clues like the type of hardware used, image version, specific add-on details (no idea what "esa" is) and likely provide some logs (read the wiki).
Otherwise it's a bit like saying "my car doesn't work, it's a red one, what's wrong?" ..
-
Code
Dec 29 04:17:50 LibreELEC kernel: bluetooth hci0: Direct firmware load for qca/rampatch_usb_00190200.bin failed with error -2 Dec 29 04:17:50 LibreELEC kernel: Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00190200.bin (-2)I've pushed an updated version of the image with that ^ file added. Hopefully that's the only one. In case it's not, chase down files from https://git.kernel.org/pub/scm/linux/…re.git/tree/qca and let me know what others are needed so I can add them to the pick list.
-
I thought if I copied them to my local LE build 'sources' folder the build would work, but the build process actually ignores the existing file and attempts to d/l anyway
You can fake/do that *if* you add the .url and .sha256 files alongside the source file. If you only add the source file, the buildsystem sees it as an incomplete package and reattempts download.
-
See if this LE13 image works? https://chewitt.libreelec.tv/testing/LibreE…-12.90.1.img.gz
If not working, run journalctl | paste and share the resulting URL so I can see the system log for clues.
-
-
swever the images include the latest rtw88/rtw8821a_fw.bin firmware from the upstream linux-firmware repo and nothing has changed with that in the last few months. If you have files in /storage/.config/firmware/rtw88 these override the lastest upstream files so I would suggest removing them and using upstream firmware. If that doesn't fix something; clean boot then "journalctl | paste" and share the log URL so we can look for error messages etc.
-
The Generic image is not currently built with CONFIG_ATH12K enabled hence adding firmware doesn't achieve anything. I'll share an LE13 test image later in the day that includes the missing module and firmware. If you can confirm that works I'll send the changes upstream to our main repo.
-
This is unlikely to be an LE issue as we're not doing anything more than packaging Tvheadend. It is possible that differences in the two versions are due to changes in Tvheadend itself. It's also possible that the issue resides in the browser.
I'm wondering if this is the same as https://tvheadend.org/d/9323-recordings-dont-play-anymore/8 ?
NB: Although there are quite a few Tvheadend users around here the best place to report and debug Tvheadend problems is normally the Tvheadend forum.
-
flydt Please reply in this forum thread. If you continue to "report" the post and reply that way, a) nobody except admins can see the reply/report, b) you'll be receiving a temporary ban for annoying the admins with unjustified reports to review.
