Posts by chewitt

  • OpenVPN Config Problem (PIA)

    If you use the default PIA config with the problem CRL certs on LE13 and newer (with new OpenSSL) the problems will exist. If you run LE12 the problem should not exist (as older OpenSSL is used). On LE13 and newer if you remove the problem CRL bits from the default PIA config the problem is worked-around and the config will work. On this topic I think we reached the "You can lead a horse to water, but you can't make it drink" point. The workaround requires 30-seconds' worth of effort. It's up to you though.

    On a deeper technical level WireGuard is quite different to OpenVPN but from a high-level user perspective they achieve the same thing and most commercial services support both. If you want to explore that there are setup instructions in the wiki. I'm going to pass on the opportunity to spoon-feed instructions or debate that further though.

  • How to get EXT4 drive to mount reliably?

    Code
    echo 'options usb-storage quirks=152d:0583:u' > /storage/.config/modprobe.d/usb-storage.conf
reboot

    There are quite a few reports of "device won't mount" on a range of distros for the "JMS583Gen 2 to PCIe Gen3x2 Bridge" adapter so run that ^ over SSH and see if it mounts correctly now?

  • [RPi3B+] WiFi Delayed Connection on LE 12.0.2

    Increase the "wait for network" timeout in LE settings to 30-seconds; it will exit the wait loop earlier if the connection is found/active earlier. Then the network is always up before Kodi starts and time (via NTP) will always be correct. There's no way to make drivers load and probe hardware faster.

    NB: If you need a static address it usually easier to leave devices on DHCP but add a static reservation against the interface MAC in the router so it's always dynamically assigned the same address.

  • [RPi5] Build process to get Kodi

    LE(13) and RPiOS use the same Linux 6.12.y LTS kernel source so you shouldn't need to touch that. All the mesa patches are long upstreamed by Igalia (on behalf of RPi devs) so just use a recent version. Kodi and ffmpeg still requires downstream patches, as you'll find in our repo. The various build options are in the package.mk files, as you found. Beyond that, I've little experience with compiling Kodi outside our buildsystem so I can't really advise.

    popcornmix does RPiOS not have an appropriately patched Kodi (and ffmpeg) version to use out-of-box?

  • How to get EXT4 drive to mount reliably?

    I was originally suspecting a power issue; especially if the drive is being powered from the USB bus, but when power draw is the issue I'd expect to see spurious errors in the log; mount failures or USB errors or .. something to indicate the device probed then trying/failing/trying/failing to mount and then eventually succeeding. Instead the log looks clean, as if the device is probed (once) and then mounts cleanly and correctly (once).

    If the device is USB bus powered, is it a 'single' USB cable or a 'dual' (Y) cable that takes power from multiple USB ports. SSD drives might be small but that doesn't necessarily mean they use little/less power - they can be hungry devices.

    Just for info, please run "lsusb -tv | paste" and "lsmod | paste" when the drive is connected.

  • 8440U , 28W Supported by LibreELEC?

    Benchmarks focus on "Which is fastest?" when the better question(s) are "Which is fast-enough for a good experience?" and "Which is best supported?" so they are not telling the whole story.

    e.g. RK3588 wins all current ARM SoC benchmarks but is only borderline usable due to incomplete software, whereas comparatively slow RPi5 is more than fast-enough and exceptionally well supported. Intel based hardware also scores big numbers but has been a lottery in recent years due to the never-ending drama from by LSPCON chips (and firmware) in the display chain.

    In short: Speed != Value

  • [x86-64] Blank screen when installed, live mode works fine

    XML
    <?xml version="1.0" encoding="utf-8" ?>
<advancedsettings version="1.0">
  <!-- enable debug logging -->
  <loglevel hide="false">1</loglevel>
</advancedsettings>

    First, create /storage/.kodi/userdata/advancedsettings.xml with that ^ content so Kodi is in debug mode for logs.

    Second, run "vainfo | paste" and share the URL.

    Now two things to experiment with:

    a) Force the HDMI connector colourspace profile to Broadcast RGB:

    Code
    systemctl stop kodi
kmstest -c HDMI-A-3 -P "Broadcast RGB=1" < /dev/null
systemctl start kodi

    Any different? - run "pastekodi" and share the URL again.

    b) Force Kodi to use the i965 driver profile:

    Code
    MESA_LOADER_DRIVER_OVERRIDE=i965
LIBVA_DRIVER_NAME=i965

    Create /storage/.config/kodi.conf with that ^ content, then reboot and run "pastekodi" and share the URL again. Also run "vainfo |paste" and share the URL.

    I'm not expecting to acomplish anything .. but we'll have more information to review.

    EDIT: 3rd thing: Do you have a DP to HDMI connector? .. i.e. connect to the DP socket not an HDMI socket. It would be interesting to see if that changes anything. I'm also wondering if the board has native HDMI connectors or internally they are DP with an LSPCON chip providing HDMI .. in which case have you ever updated the BIOS and/or LSPCON firmware?

  • [RPi5] Build process to get Kodi

    Code
    PROJECT=RPi DEVICE=RPi5 ARCH=aarch64 make image

    Or if you really do need to build an image .. start by building the current HEAD commit for either LE12 or master (LE13) branches. It all works. There is no need to muck about with package versions and patches.

  • [x86-64] Blank screen when installed, live mode works fine

    The limited number of resolutions/modes suggests to me that you're hooked up to a monitor? .. which is flagging some warnings about EDID data. Most devices flag some kind of EDID warning, but this is showing unusual ones for primaries/quantization which are related to colour .. and you're reporting weird colours.

    If you connect the device to another HDMI device (ideally a normal TV) is anything different?

  • OpenVPN Config Problem (PIA)

    Quote from Grasshopper

    How does invalid date get updated/corrected in crl?

    It cannot be, hence the problem. The only way to avoid this is not fcuking up your certs with incorrect dates in the first place; then if or when you need to revoke them in the future the revoked certs have valid dates.

    Thus the suggested workaround is to remove/disable the CRL function in the OpenVPN config. It's a bad workaround because CRLs have security purpose, but you have no alternative.