kszaq, can you tell me, what is the situation with libreelec for RK3399 with ARM Mali-T860 MP4 Quad-Core GPU?
Completely unsupported and no near-term plan to support.
I found instruction, how to install Ubuntu on FireFly board with that CPU - Firefly-RK3399/Build Ubuntu rfs/en - Firefly wiki .
Does Ubuntu contains Mali-T860 drivers?
You're asking questions about hardware we don't support on an OS we don't support. Please go ask in the Ubuntu forums.
The update process only replaces files in /flash it does not touch /storage in any way. So update vs. clean install is all about Kodi caching or config and not the type of update file used or the actual update process.
I've seen the random green LED (nearest power socket) a few times on both 8.0.2 and 8.1.0 and I have no clue. I'm wondering if some extra blank pixels need to be added to ensure the LED's are cleared in some scenarios?
[ 3.491608@1] mmcblk0: sd:1388 NCard 14.8 GiB (ro)
[ 3.514280@1] mmcblk0: p1
[ 3.919301@0] mmcblk1: emmc:0001 NCard 7.21 GiB
[ 3.919434@0] mmcblk1boot0: emmc:0001 NCard partition 1 4.00 MiB
[ 3.919562@0] mmcblk1boot1: emmc:0001 NCard partition 2 4.00 MiB
[ 3.920731@0] mmcblk1: p1
[ 3.922404@1] [mmcblk1p01] bootloader offset 0x000000000000, size 0x000000400000
[ 3.922604@1] [mmcblk1p02] reserved offset 0x000002400000, size 0x000004000000
[ 3.922789@1] [mmcblk1p03] cache offset 0x000006c00000, size 0x000020000000
[ 3.922977@1] [mmcblk1p04] env offset 0x000027400000, size 0x000000800000
[ 3.923164@1] [mmcblk1p05] logo offset 0x000028400000, size 0x000002000000
[ 3.923338@1] [mmcblk1p06] recovery offset 0x00002ac00000, size 0x000002000000
[ 3.923506@1] [mmcblk1p07] misc offset 0x00002d400000, size 0x000002000000
[ 3.923720@1] [mmcblk1p08] boot offset 0x00002fc00000, size 0x000002000000
[ 3.923903@1] [mmcblk1p09] system offset 0x000032400000, size 0x000060000000
[ 3.924074@1] [mmcblk1p10] data offset 0x000092c00000, size 0x00013b500000
[ 3.925427@1] mmcblk1boot1: p1
[ 3.925450@1] mmcblk1boot1: p1 start 16065 is beyond EOD, truncated
[ 3.926875@1] mmcblk1boot0: p1
[ 3.926892@1] mmcblk1boot0: p1 start 16065 is beyond EOD, truncated
[ 6.115749@1] EXT3-fs (mmcblk1p9): error: couldn't mount because of unsupported optional features (40)
[ 6.116116@1] EXT2-fs (mmcblk1p9): error: couldn't mount because of unsupported optional features (40)
[ 6.123021@1] EXT4-fs (mmcblk1p9): mounted filesystem with ordered data mode. Opts: (null)
[ 6.272221@1] EXT3-fs (mmcblk1p10): error: couldn't mount because of unsupported optional features (40)
[ 6.272595@1] EXT2-fs (mmcblk1p10): error: couldn't mount because of unsupported optional features (40)
[ 6.280626@2] EXT4-fs (mmcblk1p10): mounted filesystem with ordered data mode. Opts: (null)"It works in Windows" because Windows blindly trusts whatever disk/partition geometry data is presented to the OS before it goes ahead and mounts the partitions on the storage device. In comparison; Linux validates the geometry data presented to prevent data loss issues. In this case the partition data is invalid so Linux correctly refuses to mount the damaged partitions. Id guess the SD card is going bad, or there are traces of previous partition schemes on the storage that cause conflict.
Use our USB/SD creator app to restore bootsector.img to the SD card then reformat the media in Windows (any format scheme you like) and try again.
I don't care how the video is encoded. I care about seeing a debug log from Kodi that shows how it plays.
There's a fix/workaround for addons27.db in LE 8.0.2 and from the description(s) this is a clean install.
For kicks (and if you don't mind) .. make a backup and move off-box; then clean install to the eMMC again and selectively restore the essential bits (sources.xml etc.) from the backup file. If that works we can take another willing victim and see what bits of their Kodi install can be pruned before things start to work right. I have a completely unfounded hunch/suspicion that Kodi image caching is involved.
So just to be clear the tar can not be copied to the update directory on the slice cm3?
If you are updating from LE 8.0.x (the first images to support CM3) to LE 8.1.0 manual update can be done from LE settings in the Kodi GUI. You can also copy the update .tar or install .img.gz file to /storage/.update/ and it will work (.tar is faster).
I've installed 8.1.0 all seems to be good except LED patterns, some work, others like fast rewind and the shutting down red pattern do not, all of the .png patterns seem to be present in /usr/share/kodi/addons/service.slice/resources/media/ledpatterns/ although I thought they used to be in /usr/share/kodi/media/ledpatterns ?
The location of LED patterns has changed because they are now part of the embedded slice.service add-on. I saw some LED issues when I first updated to early versions of the 8.1.0 image where patterns weren't playing right, but I strongly suspect that was due to an install that had became messed-up from testing and with too much background stuff going on (and using WIFI, which seems to make the Slice box suck). Since I clean reinstalled to the eMMC for boot testing and went back to Ethernet, it's been fine.
Amlogic devices with an S905 chipset like the NEO U1 should have great 8-bit/10-bit HEVC playback. If something is failing to play there is either a conflict with Kodi configuration or something bad/broken/non-standard with the media file. First action would be to share a Kodi debug logfile and an explanation of what LE community image you are using (because there is nothing official for Minix boxes). Second action would be sharing 2-3 mins of the media file so we can experiment with other S905 devices and see what happens.
RPi2 might cope with lower-bitrate 8-bit 720p HEVC files, but I doubt 10-bit 1080p will play even if low-bitrate. Everything has limits.
Create an Ubuntu LiveUSB so you can boot the NUC and access the second partition on the internal SSD to find .kodi/temp/kodi.old.log and share it via pastebin so we can see why Kodi is crashing.
What version of OE did you update to LE 8.0.2 from?
It's the same distro that I build official images on. Possibly a little ahead on patches but I've never paid any attention to patch levels (beyond updating when it prompts) so it's not something that should influence the outcome. Most "fail to boot" issues are about the boot media not boot content. Is the good 8.0.2 boot on the same USB stick?
One of the OE contributors had a religious thing about suspend not working on USB sticks so OE wiki entries say this is bad (sky will fall on your head etc.) but ISTR we removed the "big fat warning!!!" texts as for most (not all, but most) users it works okay. That said. I always preach that any installation on USB or SD media is temporary as it will be more prone to wear related media dying issues, so it's the users responsibility to create appropriate periodic backups to guard against data loss.
Nothing looks wrong.. but clearly something is. What distro did you compile on?
PR the changes to the main repo.
Make sure "sync playback to display" it not selected, as this forces output to PCM.
Krypton promotes favourites from home screen icon to proper menu item, but the functionality is not as complete as other menu items (half baked is not a fair comment, but it needs some improvement in Kodi Leia). If you are on the home screen, scroll down to favourites and then scroll right, there is no option to context click the favourites. If you highlight favourites on the menu and then click to enter the favourites screen; now you can context click to delete and reorder the favourites.
