If you have a working setup, make backups.
In all other cases, provide debug kodi.log files for further details.
Posts by Klojum
-
-
Have you updated the NUC bios to the latest version?
Can you perhaps do a test with the NUC connected directly to your TV?
If so, please enable debugging and provide the kodi.log of that test session via SSH: paste ~/.kodi/temp/kodi.log
Just to see if the AVR is a problem with the 8.2.0 build.
-
We will not say 'no' to a fitting donation
-
"does not work"...
Sure.
-
Kodi / LibreELEC does not supply content in any way.
You can use Google for getting "good" channel lists.
-
You don't need an addon for that, a good hammer will get you the same result.
Also, don't open 2 different threads on the same topic.
-
If you need to make changes to the system partition, you first need to make it writeable. For example, the /flash folder:
Codemount -o remount,rw /flashNote, that with every LibreELEC upgrade, this partition will be rewritten, and any manual changes will be lost. Perhaps the /storage partition is a better location for keeping data/settings.
-
I would be interested to know which organization(?) has 70 iMac's running LibreELEC, as they are not the typical choice of hardware for running Kodi.
Using CloneZilla is one way, or just installing LibreELEC fresh and restoring a good backup for the storage data is another.
Additonal skins, when installed, will be placed in the .kodi/addons folder. Subsequent settings will be placed in .kodi/userdata/addon_data/skin.<name>.
If you have a redesigned Estuary system skin, those files will be placed in the readonly section of the system partition. Settings of Estuary are located in .kodi/userdata/addon_data/skin.estuary .
All data is stored on the storage partition. There is a backup/restore section in the LibreELEC Settings add-on. You can use that to transfer/copy settings from one computer to the next. I'm not sure if the CloneZilla method is faster, but there is more than one way to get to Rome.
-
Any plans to fix the CEC bug?
Sorry, we can't be bothered to really answer such a vague and undetailed question.
-
No. All the usual drivers are onboard. If you want to add more drivers, then you will need to recompile LibreELEC.
Which onboard GPU do you have?
-
The built-in wifi on the RPi3 is not of the greatest quality. So either a better usb wifi dongle, or better yet, a cable connection will improve things anyway.
For the rest, provide a kodi.log file for all the internal details.
-
Moved to AMlogic section
-
Let's start with you providing a full, debug enabled kodi.log as I'm not seeing any further details on your Kodi device.
-
Place the mount command in the .config/autostart.sh file
-
Might eventually be supported
No guarantees, no promises.
-
Kodi is open-source and should be able to fix this without problem.
Sure, because we are wizards we can fix anything and without any problems with the snap of our fingers. Right?
There is also a lot that could be fixed if we had the proper manpower with the proper coding skills. From the simple things (auto-update languages for the LE Settings Add-on) to the very difficult things (creating CUVID support for 10bit Nvidia video in Linux, or keeping up with Apple's policy of constant breaking Airplay protocols).
Kodi is limited as a streaming application. Support via UPnP streaming is limited, and Airplay support is more often broken than functional. Kodi has no Chromecast support because that means proprietary software, and that clashes with the whole open-source concept. Bluetooth (at least in LibreELEC) has only limited audio support, not video.
-
So there is no way to do a DIY HTPC that does x265 and 10bit HDR?
Sure, a Windows 10 setup should do everything just fine. I myself just cannot test the HDR part here since I have no HDR TV or monitor.
I see you mentioned flaky HDMI 2.0 support from Intel. What does that exactly mean?
It means Intel used some DisplayPort-2-HDMI2.0 band aid, and video drivers in Linux (which LibreELEC runs on) can have a hard time adjusting to. Some motherboard manufacturers will implement their own hardware adjustments and again things will work just a little different. Of course Windows drivers will have more support from manufacturers, the Linux community is trying to catch up.
-
If the drive is used by LibreELEC/Linux only, use EXT4.
