Please test a current LE12 nightly. Same?
Posts by chewitt
-
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
You can use the ultimate one for testing. The sole difference is the WiFi/BT module.
-
-
LE Settings > Networks > Wireless Regdomain (set for your country).
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
-
-
It's hard to comment without seeing the boot log, but failure of ethmactool-config.service suggests the Ethernet NIC isn't working and thus you won't be able to SSH into the box to share that easily. Although: if you remove "quiet" from boot params in uEnv.ini there will be verbose output on screen and you can take/share some pics or a slow-motion video of boot (upload them to a file sharing site somewhere). You can also add "textmode" and it will (or might, depending on the issue) boot to a text console instead of Kodi, allowing you to connect a USB keyboard and poke around to see what's up.
For kicks you can also try the box image from https://chewitt.libreelec.tv/testing which has newer kernel/drivers/everything. It's unlikely to resolve anything though.
-
Seems to be https://github.com/xbmc/skin.confluence/issues/223 - Skins have no CPU architecture dependancy.
-
NB: Team Kodi have merged a couple of changes for Windows and Android installer packaging issues and this will require a Kodi 20.4 release for Appstore/PlayStore submissions. At the curent time 20.4 has no Linux content whatsoever and thus no need for another LE release. If that changes we'll re-evaluate.
-
Read: https://wiki.libreelec.tv/hardware/amlogic and configure the tanix-tx3 device-tree file in uEnv.ini. If you have been using CE on the box you will need to force recovery boot again to force u-boot to search for LE bootscripts (different to CE) and use them.
-
The boot sequence is (at a high level): BIOS > Syslinux > KERNEL > SYSTEM
If you don't see the syslinux prompt on-screen, it's a BIOS or (very old) hardware problem. If you see the syslinux prompt but no LE boot splash it probably hangs early in the KERNEL stage of boot before the splash has been rendered. If you make /flash writeable (mount -o remount,rw /flash) and remove "quiet" from kernel boot params you'll see verbose boot output on screen and messages can sometimes help to pinpoint what the problem is (take an in-focus pic with a phone and share it).
I doubt there's too many users with c.2012 NUC hardware still in use, but in general there aren't reports of "my thing doesn't boot without a keyboard connected" and LE is intentionally designed to run on systems that don't have keyboards connected, so I'd be thinking a BIOS (might need updating) or hardware issues (PSU, coin-cell for BIOS memory, etc.) to be a more likely cause.
-
Legacy images running the vendor kernel tend to support a default featureset regardless of what EDID contains (or lacks) so it doesn't necessarily exempt cables/ports from suspicion. Same p212 dtb should be fine. For WiFi, some countries need the wireless regdomain to be set before the correct channels show up (as radio properties are wrong) or you need to tell what chip is inside the box (not everything has drivers) and/or share the output from "pastekodi" with the box connected to Ethernet and share the URL generated so we can see what might be missing (firmware sometimes).
-
The NFS client defaults to NFSv4, is that going to work for your NFS server?
-
Thanks, reported upstream again

-
It sounds like the difference between full and limited range? .. Settings > System > General
-
You can try manually updating to my LE12 images here: https://chewitt.libreelec.tv/testing/ to rule out problems with the 11.0.6 image. If you see the same I'd try swapping HDMI cables and/or ports on the TV as HDMI audio capabilities (or lack thereof) are normally related to the EDID received (or not received) on the HDMI connection.