Test again with an 11.0 nightly..
Posts by chewitt
-
-
IR power on requires the correct bl301 blob from the manufacturer when compiling u-boot. LE does not support reading remote.conf files on the SD card - that's somehing that CE built that requires their boot firmware - and that's supported in their forum, not here.
-
-
Read post #3 again.
-
Moved to the Allwinner subforum as the eBay listing claims it's an Allwinner H616 box
-
Impossible to say without seeing the full earlier boot log (which will be challenging to collect). I'd guess a corrupted or failing SD card.
-
All you need to do is hit a key to interrupt boot (else it will do "install" the default) and type the alternative boot mode
^ ahem.
-
LE has supported "live" (temp boot from USB) and "run" (persistent boot from USB) modes in the Generic/x86_64 installer for aeons. All you need to do is hit a key to interrupt boot (else it will do "install" the default) and type the alternative boot mode. There is no need to use mkusb or other tools.
-
do you know if the database files have changed between version 9 and version 10 of LE?
Yes, Kodi major version change will always increment the DB files.
-
Borygo77 .. no support for Pirate add-on users.
-
https://wiki.libreelec.tv/configuration/edid <= Capture the EDID data from the HDMI connection and set this in kernel boot params and then the HTPC device sees the AVR/TV as always connected.
-
It's rather unlikely that our software killed an RPi board (would be the first time it happens that I can recall) and if there was a general issue or risk with software/hardware we'd have seen it lots due to the volume of RPi users we have. Was the same PSU used with both boards? - that would be a more likely route to damage.
-
LE/Kodi can do all of the above, and boring is good (doesn't involve drama/excitement and support effort). RPi4 would be strongly preferred over RPi3 these days.
-
Code
systemctl stop kodi mv /storage/.kodi /storage/.kodi-old systemctl start kodi^ that will give you a clean instance of Kodi to work with. If you have important content (thumbs/libraray/etc.) you can stop/move/start Kodi to restore individual items to the active instance. Pirate add-ons are frequent causes of problems, but that's self-inflicted punishment. In this forum you *will* be judged; by being politely asked to go look for support somewhere else if you have them installed.
-
I'd like everyone to stop "testing" and try watching some movies instead, or go play outdoors with the kids for a while instead of trying to act like uptime monitors for infrastructure that's being actively changed and fiddled with.
-
Full debug log here: https://paste.kodi.tv/jodirerixo
The log shows LE 7.0.3! .. so please find a spare SD card and try the LE 9.2.8 image.
-
Yes, if the local Samba server has been turned on (which it should be, by default). Expect tagging with Piccard to be slower though as that requires files to be read and written to the remote share. I'd suggest you map the source in Kodi to one dir on the USB, and place new but not-yet-processed files in a separate location - in Piccard you can have it move files to a new location (the source dir) after tagging. This way the filing structure is effectively managed by Piccard.
-
btw, doing some testing and I confirm that when you shutdown the box, it restarts itself again after a few seconds. I'll ping kernel maintainers on the topic but I'm not sure it will be resolved (or resolved quickly).
