If the device has booted CE it will be looking for CE boot files which are different to LE boot files. You need to trigger recovery boot again so the device searches for LE bootscripts and loads them. This will stop CE from working.. until you repeat the process and make the stick search for CE bootscripts. NB: LE bootscripts use the dtb name configured in uEnv.ini, we do not use the "rename dtb file to dtb.img" process that CE uses, so if you are doing that, it's why nothing works.
Posts by chewitt
-
-
There are no browsers for Kodi on ARM SoC devices, only for x86_64 harware using the legacy Xorg image (not for GBM).
Best supported device = RPi5. If you need DAC outputs add a HAT that provides the right connectors.
-
Kodi .nfo files are used to provide info to a scraper, e.g. telling a scraper to collect information from a specific online media database resource, or providing info to the local file scaper (which does not check online resources). In both scenarios Kodi scrapes info from the media files (with matching .nfo files) for the defined source, into the library database.
So local .nfo files may be needed, or may-not be needed, depending on what the media files are, whether Kodi has access to the internet (easiest) or not (needs a lot more preparation and effort) and what you're trying to achieve with them.
If you're trying to acheive an "offline" Kodi setup, it's probably easiest to start "online" and scrape all media, then export the DB content to local files, and switch sources from the default online scrapers to the local file scraper. Then if something triggers the source(s) to be scraped it will find the local data from local .nfo/image files and be happy.. (in theory). It's not something I've ever personally attempted though and Kodi is designed-for/biased for online use, so YMMV.
-
169.254.35.186/16 is a link-local (self-assigned) address which normally indicates something has failed at layer2 and prevents layer3 functions like DHCP from succeding .. i.e. you fell off the network.
Issues are unlikely to be from ConnMan as all it really does is instruct the wireless daemon (iwd) to start/stop connections. It might be worth seeing if iwd itself is the issue by doing a clean compile of LE with ye olde wpa_supplicant not iwd, the choice is configured in the distributions/LibreELEC/options file IIRC.
-
In that case it could be the reverse and the add-on is looking for Python2 (K18 and older) when LE only offers Python3, and 2.19 is the add-on version not the Python version.
-
Is pass-through audio enabled?
-
It sounds like you are using LE9 (K18) or LE10 (K19) which use Python2 for add-ons, while the add-on version that you are trying to use has been updated for Kodi Nexus (K20) or newer where Python3 is used. So you either need to source a Python2 compatible version of the add-on, or update to LE11 or a current LE12 nightly so Python3 is available.
-
LE settings > System > Logging > Use Persistent Logs > .. then reboot
The systemd journal is now logged to /storage/.cache/log/journal (IIRC) and if Kodi settings has "Show hidden files and directories" enabled you can use the Kodi File Manager to navigate to that dir and copy the file to USB.
-
stop > disable > mask ?
ConnMan is deliberately compiled with no support for OpenVPN connections so ConnMan-VPN does not attempt management of NIC interfaces that are created by OpenVPN.
-
should I check the log files to find out the error?
Log files are normally more productive than our attempts at ESP
-
Should be supported in future nightlies: https://github.com/LibreELEC/LibreELEC.tv/pull/8673
-
We really need to see the boot log (dmesg) to understand if there are any issues/errors showing. Insert a USB stick, dump the log to a text file on the USB, then unplug and move it to another machine to upload here or (better) pastebin it.
-
Thanks, that points fingers to somethig changing in u-boot. The question is what ??
-
I have a hunch the keyboard issue means the BIOS battery-backup needs replacing?
-
Please update to this LE12 image and then share "pastekodi" output again:
https://chewitt.libreelec.tv/testing/LibreELEC-gbm.x86_64-11.80.0.tar
I've enabled support for the RTW89 driver. The log will show if that works (or not) and/or if there's firmware needed too.
-
The current firmware should support USB boot already, but it's never a bad idea or update and run the lastest boot firmware.
-
Driver problem?
Are you running from eMMC or SD card?
If using eMMC can you try installing a current LE11 nightly (to use an older u-boot version) and then update to a current LE12 nightly. Same problem, or does Ethernet work now?
-
The repo version changed several times since pre-Alpha LE12 images started due to Kodi add-on API bumps, and in development we do not maintain multiple repos to support older nightly images. Once a new repo version has been published we cleanup/delete the earlier ones and users need to update to current images to maintain repo access.
In short: update all your devices to a current image and they'll all be able to access the matching (current) repo.
