Posts by chewitt

  • startup screen not showing the download progress

    LE executes /storage/.config/autostart.sh at the start of userspace boot long before the network is brought up. As a result the script logic will always return "Internet is not available. Exiting without download." making the script (as-is) pointless.

    The low-skill approach to scheduling the script to run later in the boot sequence is to "(background)&" execution and use a sleep command (10s is normally enough). This will ensure the script works, but Kodi will have already started so there's no point trying to redirect messages to the console TTY for on-screen display alongside the LE boot splash which is quickly overwritten with the Kodi boot splash then home screen; although often that happens quickly so you only see the home screen.

    The better approach is to schedule script execution with a systemd service as this supports dependencies; you can dependen on network-online.target to ensure the network is up and avoid the ping-Google check. If you further depend on kodi.target you can also use kodi-send to show a toaster notification in the Kodi GUI, e.g. "Image Downloading.." and then "Rebooting in 5 seconds" or such before you force reboot to update. Have a look at the example wireguard.service in /storage/.config/system.d/ for something similar to what you need. Beware that systemd does not inherit $PATH so you must use /full/path/to/binary in commands.

  • No options to configure files

    You don't add "files" to Kodi. You add a "source" which defines the base path and type of file (TV or Movies) to be scanned for, and then you scan the source; and the scan adds the files (that match online content libraries or local .nfo files).

    All of that is explained in the Kodi wiki: https://kodi.wiki/view/Settings/Media/Library

    Or you use the "Videos" non-library view which simply shows what's in the filesystem. You still need to add sources though.

  • LibreELEC on RPi4 not announcing hostname to network

    If your internet/wifi router chooses to reuse hostname info obtained from DHCP requests and/or netbios broadcast data and use it to fake a default local DNS zone for lookups to resove against, this will work. If it does not do this (and most routers will not) then DNS will function correctly and the absence of a default lookup zone will mean DNS resolution is not possible and you neeed to use either the IP address, or make changes to the local hosts file on devices you want to connect from, so there is a local name mapping.

  • WiFi Password Problem

    Code
    connmanctl
agent on    <= this is important
scan wifi
services
connect wifi_b827eb3bee66_465249545a21426f782037353630204644_managed_psk
(enter pw)

    I'd guess that you didn't set "agent on" to enable the d-bus agent, so when connmanctl attempts to configure things via d-bus the connmanctl client is "not registered" with d-bus and unable to send the message.

  • Help with Wetek Play 2 sd card boot

    Kodi got a little heavier with time and this is hardware from 2015. Running from eMMC storage will be a little faster, but I would focus more on whether the box is functionally okay with your media before taking that step (although restoring the factory Android image is simple). AMGLX is not perfect and some folks will be better off with legacy images.

    LE11 will not improve anything over LE12 speed-wise and functionally it's a half-step backwards. Your call :)

  • Raspberry 5 cooling fan control

    RaspiOS probably has software tinkering to force the case fan on, and realistically it's more likely to be needed with a desktop OS that generates a lot more CPU activity than LE does. Baseline fan speeds and activation temps are controlled by Linux (defined in device-tree) and we're using the RPi kernel authored by RPi devs to work with their hardware and we assume they know what's needed. From personal experience 100ºF (38ºC) is nothing for an RPi5 board (mine runs with no case, no heatsinks, no fan, at 55ºC with zero issues) so I wouldn't expect a fan to be spinning up until a much higher temperature has been reached.

    In case it's not obvious from the comment. There's no bug to straighten out, so you'll be in for a long wait.

  • No Video through HDMI after Upgrade

    reposting.. https://paste.libreelec.tv/premium-manatee.log

    Code
    ay 08 17:03:51.389390 LibreELEC kodi.sh[1017]: libva info: VA-API version 1.17.0
May 08 17:03:51.389390 LibreELEC kodi.sh[1017]: libva info: Trying to open /usr/lib/dri/iHD_drv_video.so
May 08 17:03:51.732002 LibreELEC kodi.sh[1017]: libva info: Found init function __vaDriverInit_1_17
May 08 17:03:51.733293 LibreELEC kodi.sh[1017]: libva error: /usr/lib/dri/iHD_drv_video.so init failed
May 08 17:03:51.733293 LibreELEC kodi.sh[1017]: libva info: va_openDriver() returns 1
May 08 17:03:51.733293 LibreELEC kodi.sh[1017]: libva info: Trying to open /usr/lib/dri/i965_drv_video.so
May 08 17:03:51.779033 LibreELEC kodi.sh[1017]: libva info: Found init function __vaDriverInit_1_17
May 08 17:03:51.791757 LibreELEC kodi.sh[1017]: libva info: va_openDriver() returns 0

    So it tries iHD and the falls back to i965 ..

    See if adding "video=HDMI-A-1:1280x720M@60" to boot params helps? .. I can see it's trying to use [email protected] and I've seen other issue reports with that weird resolution in recent weeks and despite users blabbing on about it being a native resolution for their old TV, I suspect Linux doesn't like it.