I can see remains of an older OE install in the logs and there's some odd VAAPI errors so I'd SSH in and stop Kodi, rename /storage/.kodi out of the way and then wget a Kodi 18 development (milhouse) build .tar file to /storage/.update - then the box will update itself and restart with clean Kodi defaults. If it now works it's either a bug resolved in newer drivers (or Kodi) or bad config on the Krypton install. If you stick on Leia you can do some stop/move/restart to restore essential files (sources.xml, thumbs and DB's) before reinstalling add-ons.
Posts by chewitt
-
-
It should read gputemp
On AML devices the gputemp script is a symlink to cputemp and the cpu/gpu output is determined by how the script is called by Kodi.
-
PXE booting is niche but the code bits haven't been touched in years and require no maintenance so it's no issue to leave it in the codebase. Glad you got it working
-
I'd guess (and with no Kodi debug log guessing is all we can do) that the ISO RIP is using a native uncompressed codec/format that your older NUC device cannot hardware decode, and it doesn't have enough CPU grunt to cope with software decoding. Compress to H.264 which will be harware decoded and it shouldn't skip.
-
Well if you're running an official release the repo is embedded into the OS image and you cannot remove it so there's no need to add it, just browser add-ons by repo. If you're not running an official release it's up to whoever built the image to provide add-ons for it.
-
For official release it's in the LibreELEC repo not the Kodi repo.
-
It sounds like the install was successful (even if no video) so you can probably access the logfiles samba share to grab logs and see if there are any clues present. The red failed text is probably Xorg failing to start, which usually indicates a GPU driver issue.
-
Server issues are resolved. Add-ons should be available again.
-
LE is (was) not vulnerable as we don't build with printer support and the $IPC path required for the exploit is not present.
-
32-bit or 64-bit CPU?
-
The first step is to figure out what chipset is in the device. Android runs on many things we do not support and the older the Android device the greater the chance of their being no hope of installing something.
-
Please start all investigations from a current 9.0 development (milhouse) release because Krypton has been a dead codebase for ~6 months now. If the issue is not already resolved in Kodi v18 .. then start posting logs etc.
-
Mirrors [LibreELEC.wiki] now has a listing of mirror sites, but add-ons are not currently mirrored
-
Two things I learned in 7-years supporting people here and pre-fork OE forums:
a) Wireless is frequently affected by things outside your control (neighbours, other devices sharing the contended network)
b) Wireless is never a substitute for Ethernet.
-
Just a professional Q , I'm a software developer myself yet wouldn't know the first thing about modifying the kernel and the various other bits and bobs that you do. How did you pick that up? Professional background, curiosity? I've always looked upon the guys dealing closer to the hardware as the real guru's yet I dont see how I myself can go from a regular software guy to a on the bare metal dev like yourself.
The only qualification required is the initiative to poke code and hardware with a hint of curiosity and method and see what happens. Our current extended contributor team includes a Carpenter, Paramedic, and an Airline Pilot, and sometimes the "least-qualified" folks are the most prolific creators
-
If it's the latest generation of Intel CPU you will probably need a Milhouse 9.0 nightly to boot it.
-
-
30 seconds in Google shows it may have an card that requires the ath10k driver which is not present in LE 8.2.x so load a current Milhouse build and see if that works; it has a newer kernel with the ath10k driver.
