Posts by heitbaum

  • WiFi does not come up automatically

    Moving all the reports from GitHub to here.
    - https://github.com/LibreELEC/LibreELEC.tv/issues/7166
    - https://github.com/LibreELEC/LibreELEC.tv/issues/8731
    - https://github.com/LibreELEC/LibreELEC.tv/issues/7353
    - https://github.com/LibreELEC/LibreELEC.tv/issues/10573
    - https://github.com/LibreELEC/LibreELEC.tv/issues/8762
    - https://github.com/LibreELEC/LibreELEC.tv/issues/8760

    Some of the feedback / known issue / suggestions on the issues - please try these first.

    • Disabling fast-transition (FT) in access-point radio properties (this may be resolved in current connman/iwd/drivers, there have been changes in all 3 code bases around this)
    • Not using WPA3 (this may be resolved in current connman/iwd/drivers, there have been changes in all 3 code bases around this)
    • Moving the device closer to the access-point to improve signal strength


    **not recommended** - but has helped some.
    /etc/modprobe.d/iwlwifi-opt.conf
    Add the line "options iwlwifi 11n_disable=1" (without the quotes)


    There is a report that on “unclean restart” connman always returns “invalid”

    LE12.2 (nightly) and LE13 (nightly) both have the most recent iwd and connman. So any testing should be done against these releases. The kernel on 12.2 (nightly (6.16.12)) has diverged from LE13 - which is now 6.17.x on all except RPi, so testing should be performed on LE13 if not RPi.

    As in the issue logs a number of detailed scenarios have been run though, with some success. There seems to be a number of corner cases that cause the issue (including the known ones above) - the interesting observation on https://github.com/LibreELEC/Libr…ment-3395445892 is the DFS and 80. E.g. Does this occur on a simple 20 channel…


    Note - I test using a C9130AXI-Z 802.11ax 2.4 GHz/5 GHz access point at 20 MHz, no FT, no WPA3. Also test against Unifi AC Mesh.

  • [x86-64] LE 12.2 is missing the Broadcom-wl WiFi driver completely

    iwd and connman are synced up to that of LE13.

    Correct there is no b43 in LE12/13. I don’t see the wl driver returning in LE with “patches”, the decision to drop it was only made after the inability to obtain working patches across multiple kernel releases, and lack of support (community) - lots of reading and research done in the PR and issue, with references to the issue.

    The wireless positive with LE12.2/13 is the now available upstreamed rtw88 wireless.

  • Syncthing 2.0.0

    Some change in arguments that I can see. Taking a further look. The addon interface in LE Kodi looks right with a default of 0.0.0.0:8384

  • [RPi3B+] Mounting pCloud Drive

    What does your ldd of your binary show?

    You can use patchelf to update your binary to use the same by doing patchelf --add-rpath '${ORIGIN}/../lib.private' ${ADDON_BUILD}/${PKG_ADDON_ID}/bin/* depending on where you locate your binary. If it is in the backup directory as you have shown. Then patchelf --add-rpath '/storage/.kodi/addons/virtual.system-tools/lib.private' backup/pcloud  if you put your pcloud binary in /storage/.kodi/addons/virtual.system-tools/bin the '${ORIGIN}/../lib.private' would be correct.

  • [RPi] FTPS Broken in LE12

    I can’t see anything in the log either. Suggest checking in on the Kodi forum for the “missing” file / folders now that we have ruled out curl itself (that doesn’t mean it still might not be curl - but it will be the api of curl)

  • [RPi] FTPS Broken in LE12

    I would suggest testing if curl or Kodi/curl api is the issue. Kodi Piers (LE13) is in development presently with curl 8.13.0. If there is an issue it would be the right time to get it fixed at the source.

    From LE - something like -

    curl -k --user myusername:mypassword ftps://ftpserver.mine

    and check that it is showing you the files you expect, they are accessible ….
    - and why / what are the missing files?
    What is the common pattern? E.g. Is it path length…. Is it special characters?

    if a curl issue, then needs to be raised with the curl team (they release approximately every 2 months)

    If a Kodi issue then will need to be raised on the Kodi forum with a reproducible case.

    but first best share debug logs will be required to analyze further with the current LE13 nightlies.

    Also the results of the “locally executed curl”

  • Source archive is never downloaded for custom package - why?

    Typo? PGK_URL