Posts by jim_p

    First bad impression on le11b1 on my rpi3b+. It still has that wireless connectivity issue that made me stop using the nightly 4 months ago. I made a fresh installation on a spare sd card yesterday, connected it to my wifi and configured some basic stuff like the skin and region. And today it just failed to connect to my wifi and I had to reenter the credentials.

    I was using the nightly from late May 2022 to early September 2022, I did not miss a single one all those months, and I was troubleshooting its wifi almost daily until I got fed up with it and flashed the card with another os for the rpi. I do not know if the transition to iwd is eventually to blame, but I will probably skip le 11 on the rpi.

    For the record, I tried 2 other oses since then (armbian and debian stable aarch64, on the same rpi and on the same card) and none had the same issue.

    Is it just me or the links in the download page for x64 download the same file, regardless of generic and generic-legacy? Proof

    Code
    $ sha256sum Desktop/LibreELEC-Generic.x86_64-10.95.0.img.gz Downloads/LibreELEC-Generic.x86_64-10.95.0.img.gz
    507ff3f94cf443b58313a116ceb1f0a8a61c670f26bbf3361aba3a25caacc598  Desktop/LibreELEC-Generic.x86_64-10.95.0.img.gz
    507ff3f94cf443b58313a116ceb1f0a8a61c670f26bbf3361aba3a25caacc598  Downloads/LibreELEC-Generic.x86_64-10.95.0.img.gz

    The file in the downloads folder is the generic image and the file in the desktop folder is, hypothetically, the generic-legacy one.

    Neither of them can boot from ventoy though, on my old bios-only system, but ventoy is to blame for that.

    Ok, first attempt to boot your amlmx 10.88.0 image on the existing le 9.2.6 on s805 failed completely. In detail.

    I wrote it on both an sd card and a usb stick with rufus and I tried to boot from any of them.

    The toothpick method failed because, regardless of where I tried to boot it from, it was always getting to an adroid recovery screen... which I had no way to use with the remote.

    Leaving the unwanted recovery mode aside, the next best thing that happened was for the box to show the mxq logo and then the tv to pop an "unsupported" message (possibly its way of informing the user for something "out of range"), which was followed by booting to existing libreelec installation.

    Any ideas?

    Hello and happy 2023 to everyone!

    A couple of hours ago I noticed that lekma's addon for invidious has stopped supporting python2 since early August of 2021! Assuming that more will follow soon, I started searching here and there for any solutions and I came accross this entry from the wiki.

    https://wiki.libreelec.tv/hardware/amlogic

    The 2 images that are mentioned there no longer exist as it seems. The closest ones seem to be the AMLGX nightlies for le 11 the Amlogic/box folder. Assuming there is a relevant device tree file in there (which is something I can not verify unless I flash an image to an sd card and then check... some subfolder in there) what are the chances that it will work on an s805 or an s905 device?

    p.s. Please excuse my long absense from the forum. I had a really hard time with covid in 2022 :(

    So, provided that one can wait bit longer, the "available versions" button does show the available images from the server and works like it should (downloads the image etc). I think that the delay is because the amount of images on the json file, which are now 10 compared to only 2 in the past.

    This happens on le 11 nightly though. On le 10 nightly, nothing shows up, no matter how long I wait. I will check the log later for any info.

    ---edit

    Here is the 8+MB log from le 10 nightly with a ton of errors! At least the json file is parsed correctly.

    It was too big for pastebin I guess, so I took it from le and zipped it on my system to make it smaller than 1MB.

    p.s. Please excuse any misclicks that made kodi parse the file twice.

    A couple of days ago, I noticed that the main server's json file is back in place and lists all nightly images for 10 and 11

    So I added the url to libreelec's settings > updates as a custom channel and libreelec 11 showed up under update channels, which means it does read the json file with success. However, when selecting available versions, nothing happens.

    Tested on le 10 nightly on x64 and on le 11 nightly on rpi2, by selecting the relevant update channel on each installation.

    Changing the server, which is removing a comment from somewhere or deleting a line completely so as to make it work, is a major update. Changing your name at the top of the script to add your info is a minor update.

    Things that impact the general usability of the script should be considered major updates.

    What you are asking me right now is to start fresh and waste even more time going through the things that I have already finished, just because kodi (or anything that kodi uses) has issues in those last 3 builds. We are talking about days of work and sorry I can not do that. I'd rather install something else on the rpi, e.g. armbian that caught my eye last month, to waste my time than start over.

    Sadly, unlike x64, the rpi images do not provide a way for "live booting" with no configuration or addons. If they did, I would happily provide any sort of log.

    I have to backup my stuff, then reset le and hope it pops the same errors, then post any logs and then restore my backup to continue with anything that I am doing. Rinse and repeat for every time there is a log needed.

    I remind you that those 2 months that I am on nightly, I had to troubleshoot a corrupted filesystem, which was not an card issue but more of a "bad imaging on the card" issue and the wireless that still fails to connect every second or third day. Compared to the time I spend on what was important for me, those 2 issues took like 2/3rds of my time. And I am talking about the rpi only, leaving x64 aside.

    Yes, I understand and respect your views about third party addons, but at this point I am not willing to waste any more of my time for le itself.

    p.s. Aren't the above considered "full logs"?