Is pass-through audio enabled?
Posts by chewitt
-
-
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.
-
How do I get the latest eeprom update?
And what is different between the LE 12 nightly instead of LE 11.0.6 ?"rpi-eeprom-update -a" .. then reboot, and the main difference is another 18+ months of Kodi development, and a newer RPi kernel and drivers. We will be forking the release branch soon; nightlies are stable (except for the name).
-
LE repo > Virtual Filesystems > Archive Support .. it was moved to a binary add-on some Kodi releases ago
The next issue will be that some of the subs providers have moved to a freemium/subscription model .. and that's not something we can really guide anyone on.
-
The last line contains the clue .. that's the Hub u-boot binary not the WP2 one. I'll see if I can regenerate the WP2 one (needs some setup as those files were last built on some other machine).
-
Nice. I'll add the module change to the next kernel defconfig bump that I push.
-
There are no errors from the IPTV add-ons repo. So as told already in the other thread: If it reports no add-ons, you need to discuss that with the people who created that repo (which is not LE and not Team Kodi, so not our problem to solve).
