Posts by chewitt

    The upstream vdec supports H264 and VP9 currently. HEVC is still work in progress so it will be software decoded. Other (older) codecs like MPEG4 and MPEG2 are a low priority for hardware support as even lowly S905 can software decode everything fine. You S912 nox should be able to handle 1080p media in the current state, but not 4K (as most 4K media is HEVC). The kernel stateful API changed in the semi-recent past and this broke seeking .. we're still trying to figure out what and where things need to be changed to make it work again.

    /etc/fstab is not editable (or overwriteable) as it is not used or required in LE - it exists solely as a dummy file because some packages expect it to be present and fail to start if it is not. In LE locally attached drives that recognised (and not corrupted or unclean) filesystems will be auto-mounted by udevil, and network drives can be handled through systemd .mount files (see /storage/.config/system.d).

    From what I've read WireGuard requires monotonic time, i.e. time can change but must always move forwards, so it shouldn't be affected by the time-jump seen when NTP kicks in (unlike TLS certs which are invalid until current time is greater than cert start dateTime) as time starts from libc compile time (some date in April?) but I'm not an expert in these things. I suspect the timing/sequencing for WireGuard in the .service file could be improved as I'm a novice with systemd things.

    It should be impossible to update from older LE (3.14 kernel) to nightly (mainline kernel) images .. I added an explicit check to detect this and abort:

    LibreELEC.tv/canupdate.sh at master · LibreELEC/LibreELEC.tv · GitHub

    I haven't been adding the realtek vendor-binary drivers to the LE master branch for Amlogic as I'm typically working on an rc kernel and these things break all the time, but I have enable most of the in-kernel drivers and rtl8188ee should support that device. Can you run "dmesg | paste" when using Ethernet (but with the WiFi device connected) and share the URL, it might me something simple like missing firmware.

    lumpi I can't say much about Tartiflette until LibreComputer publish more themselves, but it's packaged for industrial use-cases and will also ship as an S905D device so it probably won't appeal to LE users. It's relevance will be that it's a device LibreComputer will want broad "out of box" upstream Linux and distro support for, and since they're one of the few entities that supports (funds) upstream work, that's ultimately good for anyone else with an S912 device.

    GitHub - chewitt/amlogic-boot-fip: Firmware Image Pacakge (FIP) sources used to sign Amlogic u-boot binaries in LibreELEC images <= has all the FIP sources that I've found, and the VIM2 sources seem to work on a number of the other S912 boards and box devices I have. Focus on learning how to build mainline u-boot from sources and then run through the Amlogic signing process to make a bootable firmware. The signing recipe is documented in u-boot sources, see u-boot/board/amlogic/q200 at master · u-boot/u-boot · GitHub

    Code
    2020-05-27 15:29:27.805 T:2875597680   DEBUG: FindMovie: Searching for 'Die Fosters' using The Movie Database scraper (path: '/storage/.kodi/addons/metadata.tvshows.themoviedb.org', content: 'tvshows', version: '3.5.3')
    2020-05-27 15:29:27.825 T:2875597680   DEBUG: scraper: CreateSearchUrl returned <url cache="tmdb-search-Die%20Fosters-de.json">https://api.tmdb.org/3/search/tv?api_key=6a5be4999abf74eba1f9a8311294c267&amp;query=Die%20Fosters&amp;language=de&amp;append_to_response=credits,external_ids,images&amp;include_image_language=de,en,null</url>
    2020-05-27 15:29:27.825 T:2875597680   DEBUG: CurlFile::Open(0xafbcf8f0) https://api.tmdb.org/3/search/tv?api_key=6a5be4999abf74eba1f9a8311294c267&query=Die%20Fosters&language=de&append_to_response=credits,external_ids,images&include_image_language=de,en,null
    2020-05-27 15:29:28.027 T:2875597680   DEBUG: Get: Using "UTF-8" charset for "https://api.tmdb.org/3/search/tv?api_key=6a5be4999abf74eba1f9a8311294c267&query=Die%20Fosters&language=de&append_to_response=credits,external_ids,images&include_image_language=de,en,null"
    2020-05-27 15:29:28.030 T:2875597680   DEBUG: scraper: GetSearchResults returned <results></results>
    2020-05-27 15:29:28.030 T:2875597680   DEBUG: FindMovie: Searching for 'Die Fosters' using The Movie Database scraper (path: '/storage/.kodi/addons/metadata.tvshows.themoviedb.org', content: 'tvshows', version: '3.5.3')
    2020-05-27 15:29:28.031 T:2875597680   DEBUG: scraper: CreateSearchUrl returned <url cache="tmdb-search-Die%20Fosters-de.json">https://api.tmdb.org/3/search/tv?api_key=6a5be4999abf74eba1f9a8311294c267&amp;query=Die%20Fosters&amp;language=de&amp;append_to_response=credits,external_ids,images&amp;include_image_language=de,en,null</url>
    2020-05-27 15:29:28.034 T:2875597680   DEBUG: scraper: GetSearchResults returned <results></results>
    2020-05-27 15:29:28.034 T:2875597680 WARNING: No information found for item '/media/Elements/Serien/Die Fosters/', it won't be added to the library.

    die fosters — The Movie Database (TMDb) <= returns no results
    the fosters — The Movie Database (TMDb) <= shows 3x series

    So you might need to use the English series names for the scraper to match, even if the information the scraper subsequently downloads is the DE translation. Or you need to sign up with TMDB and add/edit the series to ensure the German alternative name is registered and returns results.

    I didn't look into the other items, but it's likely the same root cause.

    Clear the NTP coonfiguration you added (which is not required as we fall back on ntp.org servers if nothing is set) then reboot and run "journalctl | paste" approx 1 min after booting into Kodi and share the URL generated. Kodi logs aren't relevant to the issue.

    LE uses syslinux for 64-bit x86_64 boot environments and grub for 32-bit, so presence of grub might just indicate the device is super low-end and has 32-bit boot firmware. Those devices have always been fairly rare so our experience with them is limited, but historically they were always rather awkward to install onto. You might get further removing the ATA! drive and writing the image directly to the HDD via USB > IDE adaptor. You might also need to experiment to BIOS settings (disable EFI, set legacy, or similar).