Posts by chewitt

  • Connection error when building

    Quote from Thursty24

    --2025-03-20 21:25:12-- https://curl.haxx.se/download/curl-8.6.0.tar.xz
    Resolving curl.haxx.se (curl.haxx.se)... 127.0.0.1

    The build device is resolving the download location to 127.0.0.1 (localhost) instead of resolving to a CNAME which has 4x public A records (which are all available). That suggests a DNS issue at your end as the URL resolves fine from here (UAE).

    Quote from Thursty24

    --2025-03-20 21:25:13-- http://sources.libreelec.tv/mirror/curl/curl-8.6.0.tar.xz
    Resolving sources.libreelec.tv (sources.libreelec.tv)... 65.109.172.87
    Connecting to sources.libreelec.tv (sources.libreelec.tv)|65.109.172.87|:80... connected.
    HTTP request sent, awaiting response... 404 Not Found

    It then falls back to our sources mirror, which appears to be down/offline or missing some config at the moment, so that fails too. I'll ping someone internally about that, but it might take time before it's restored.

    It's possible to manually download the file to your local sources folder, but to fool the buildsystem into thinking the file has already been downloaded you'll need to manually create the .url and .sha256 hash files (the format can be cribbed from other downloads).

  • Raspberry Pi 4 as access point.

    Quote from TimboZero

    Can I set this to be an access point (same ssid and password) as my main fibre box to make the Wi-Fi in that room stronger?

    You can create a hotspot with the same name/passphrase as the other network in LE settings, but it will be an independent network, and there is zero configuration beyond name/passphrase (no choosing of IP range, frequency ranges, no config of auth) and it will not act as an extension of the existing wireless network so devices cannot roam between access points, they must disconnect and reconnect. You will also content with the reality of RPi wifi strength generally being a bit rubbish.

    In short, it is an intentionally simple hotspot (as you'd have on a phone) not an access-point or a router. If it works that's great. If it doesn't work there is nothing that can be done and the solution is using a proper AP/router device.

  • [x86-64] No Audio After Upgrading to LE 12.0.2

    The NUC supports both DP and HDMI output, but it was cheaper for Intel to implement the HDMI tranceiver using an LSPCON chip that converts DP to HDMI so both outputs can be handled in a single chip. The GPU still has an HDMI capability which shows up in the kernel (unless you manually disable it in kernel boot params) but this is not wired up to anything.

    NB: It may have worked on LE12 under the DP output too .. maybe?. No harm in staying on the nightly if it works though. Kodi will move to wrap up development on Piers soon and then there'll be an official release to update to.

  • [RPi5] Over-Saturated Coloring

    The media is 4K HDR, so when you start playback the TV is switched from SDR to HDR mode. This means everything is now in HDR mode so the OSD and (if you navigate out of playback) the Desktop will have saturated colours. Some platforms that Kodi supports (Android, Windows) can sometimes tonemap the OSD etc. to normalise the appearance, but on Linux and with low-power ARM SoC devices (as with Android) this is normally done using a dedicated hardware image processor function in the SoC (as doing it on the CPU is too intensive) and RPi boards do not have this capability (and even on devices that have it, software support in the kernel is rarely implemented in upstream Linux). There might be a possibility to improve things a little with shaders, but this is still something to be explored on the Kodi end.

    In short, it's currently working as intended/capable/expected and this is not a bug.

  • USB Dongles for 12.0.2

    Quote from steveski

    If I grab a modern pci-e card is it likely to just work?

    As a general rule PCI cards are better supported in the upstream kernel because there are fewer chipsets and support for new chip families often starts with the PCI variant as this easier to author/upstream code for. However the real answer is /shrug as support depends entirely on the chip on the card, and most vendors have the habit of shipping v1/v2/v3 versions of a card with the chipset changing between versions; hence why we usually abstain from recommending WiFi hardware.

  • [iMac] Fan Control

    The =y option means the module is compiled into the kernel and always loaded (whether it's used or not) and =m (which is more appropriate in this case) means it's compiled as a loadable module and only loaded if matching hardware is probed.

    I'll send an update to include the module in the Generic image kernel config.

  • USB Dongles for 12.0.2

    The dmesg log shows no mention of a USB WiFi device, but it shows there are USB devices being endlessly reset. An educated guess is that too many USB devices are attached to the same internal hub and it cannot supply enough current for all the devices to power up and work properly (modern or cheap WiFi dongles can require a lot of current). An alternative guess is that it has some kind of issue with the USB 3.0 port speed.

    I'd start with removing all other USB devices and see if that helps things to run stable? - If not, see if you can disable USB 3.0 and force the hardware to USB 2.0 in the BIOS/firmware config or perhaps use a USB 2.0 extension cable to force the USB connection down to USB 2.0 speeds.

    In short, the device doesn't show up on the bus correctly so we can't even see what chipset is inside to understand whether drivers are in the LE image. You did say lsusb lists the device, but on a functional level that doesn't actually mean much.