Posts by rdorsch

    I tried https://test.libreelec.tv/12.0/NXP/cubox…06-cubox.img.gz on a cubox-i.

    Initially everything went fine, I downloaded a plugin (ARD aktuell) and played the latest Tagesschau stream. It started to play well, but after moving forth and back in the stream, kodi hang very soon (not the system itself, could still ssh into it).

    I thought I paste the output of dmesg, which reports warnings and bugs, just in case it is useful for anybody.


    Thanks

    Rainer

    [Moderator edit: Log file moved from insecure link to attachment.]

    Would

    iwd: update to 2.6 · LibreELEC/LibreELEC.tv@97e1ced
    log: - https://git.kernel.org/pub/scm/network/wireless/iwd.git/log/
    github.com

    and

    connman: update to 24180d1 (1.41+/2022-04-11) · LibreELEC/LibreELEC.tv@5680288
    log: - https://git.kernel.org/pub/scm/network/connman/connman.git/log/
    github.com

    be enough to apply on LE11?

    And

    PROJECT=Amlogic DEVICE=AMLGX ARCH=aarch64 UBOOT_SYSTEM=box make image

    the right build command?

    I just saw the list of kernel patches for Amlogic. The three digits list is very impressive. That a significant part contains FROMGIT-6.2 or FROMGIT-6.3 gives some hope, that eventually that gets more managable. But there are still many patches remaining. Thanks for all the effort you put into extending the life these devices.

    Thanks for your reply and enjoy the Ironman triathlon :D

    I am most interested in the wifi updates mentioned here

    [BUG] Invalid-key while connecting to wifi - LE11 · Issue #7166 · LibreELEC/LibreELEC.tv
    Describe the bug Hello :) Since upgrading to LireElec 10 (10.0.3) the wifi is really unstable. Every now and then, LibreElec will forget the wifi password and…
    github.com

    Will they also be added to LE11 eventually? Or is it more likely to see Amlogic in LE12 again?

    That's more complex than I thought or I don't know enough to understand it:

    • Both drivers are under the GPL.
    • The Debian driver has these items in modinfo
      • version: v4.1.4_6773.20130222 (entry is missing in kernel 6.1)
      • author: Realtek Semiconductor Corp.
      • description: Realtek Wireless Lan Driver
      • license: GPL
      • staging: Y
      • retpoline: Y
      • intree: Y
      • name: r8188eu
    • The libreelec driver has these items in modinfo
      • license: GPL
      • description: RTL8XXXu USB mac80211 Wireless LAN Driver
      • author: Jes Sorensen <[email protected]>
      • intree: Y
      • name: rtl8xxxu

    What I don't understand:

    • Both drivers are GPL, why are there two drivers and what is the benefit of the rtl8xxxu driver?
    • According to modinfo and the Debian kernel package, the Debian module is from staging:
      rd@h370:/lib/modules/5.10.0-21-amd64$ find -name r8188eu.ko

      ./kernel/drivers/staging/rtl8188eu/r8188eu.ko
      rd@h370:/lib/modules/5.10.0-21-amd64$ dpkg -S /lib/modules/5.10.0-21-amd64/kernel/drivers/staging/rtl8188eu/r8188eu.ko
      linux-image-5.10.0-21-amd64: /lib/modules/5.10.0-21-amd64/kernel/drivers/staging/rtl8188eu/r8188eu.ko
      rd@h370:/lib/modules/5.10.0-21-amd64$

      This rather seems to be that Debian is enabling staging whereas libreelec has just the intree module, correct?

    Interesting, do I get that right that there are two drivers in staging for this USB adapter? A working one from Realtek and a non-working one from Jes Sorensen <[email protected]> ?

    Debian testing (bookworm, upcoming Debian 12) ships a working driver with kernel 6.1:

    On the Debian system FW gets indeed loaded, therefore I copied it to the libreelec system. The license of the driver is GPL on the Debian system, so I assume it is not a vendor driver (which in addition would be very surprising for me, if Debian would ship vendor drivers in its main repo).

    Output of modinfo r8188eu on the Debian system

    debian Pastezone

    In there it is reported that the driver in Debian is also from staging:

    staging: Y

    Sources of this kernel can be found here:

    Folder: 5.10.162-1 | Debian Sources

    Sources of the driver in there

    Folder: rtlwifi | Debian Sources

    Kernel config here:

    https://bokomoko.de/~rd/Debian/config-5.10.0-21-amd64

    I will update that system in the next days to Debian testing, which will come with Kernel 6.1 as well. But I would expect that wifi USB adapter still works flawless there.

    I have a rock64 box with Libreelec 11.0.1.

    I plugged in an usb Wifi adapter

    Bus 004 Device 002: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter

    but it seems that libreelec on the Rock64 device does not recognize the stick:

    rock64:~ # iw list

    rock64:~ #

    Complete dmesg output:

    http://ix.io/4sBb


    The module seems from staging, but since I got it from pine64, I was expecting that it has at least basic Linux support:

    [ 8.281405] r8188eu: module is from the staging directory, the quality is unknown, you have been warned.

    And it is loaded, output of lsmod

    http://ix.io/4sBd

    The USB wifi adapter connects flawless on a Debian stable system on x86. I see there that firmware gets loaded:

    [428204.016092] r8188eu 1-8:1.0: firmware: direct-loading firmware rtlwifi/rtl8188eufw.bin

    I copied the FW from the Debian system to the rock64 box with libreelec 11.0.1

    rd@h370:/lib/firmware$ scp -r rtlwifi root@rock64-wlan:/storage/.config/firmware


    but this did not change anything.

    Does anybody have a suggestion what might have gone wrong?

    Thanks

    Rainer

    With

    Code
    2023-04-03 16:32:16.090 T:908      info <general>: Starting Kodi (20.1 (20.1.0) Git:20.1-Nexus). Platform: Linux ARM 32-bit
    2023-04-03 16:32:16.090 T:908      info <general>: Using Release Kodi x32
    2023-04-03 16:32:16.090 T:908      info <general>: Kodi compiled 2023-04-03 by GCC 12.2.0 for Linux ARM 32-bit version 6.1.19 (393491)
    2023-04-03 16:32:16.091 T:908      info <general>: Running on Amlogic Meson GXBB (S905) WeTek Play 2 with LibreELEC (community): nightly-20230403-bb4c561 11.0, kernel: Linux ARM 64-bit version 6.1.19

    I checked in the openwrt syslog, but did not find any entry there from the connection attempt. For successful connections, I see entries like

    Code
    Mon Apr  3 21:09:54 2023 daemon.info hostapd: wlan0: STA 78:11:dc:ed:a7:e3 IEEE 802.11: associated (aid 5)
    Mon Apr  3 21:09:54 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 78:11:dc:ed:a7:e3
    Mon Apr  3 21:09:54 2023 daemon.info hostapd: wlan0: STA 78:11:dc:ed:a7:e3 WPA: pairwise key handshake completed (RSN)
    Mon Apr  3 21:09:54 2023 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED 78:11:dc:ed:a7:e3

    on the openwrt side. I conclude that the connection process aborts very early.

    I see still the same behavior. I used the box image instead of the wetek-play2, since I still have the Android FW for reference testing on the emmc.

    The double results I cannot deterministically reproduce. I keep an eye if the double results show up again w/o manual iwd run.

    I configured the regdomain and now it seems I can at least see the wireless network.

    I managed to connect to the AP of an Android phone in tethering mode.

    I did not manage to connect to an

    OpenWrt 22.03.3 router, I get invalid key. I use this router since many years with many devices and I do not recall that I ever had an issue that a device did not want to connect.

    dmesg has quite a few entries

    ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel <number>

    (not sure if that is relevant)

    http://ix.io/4swH

    Output of "iw dev wlan0 scan"

    http://ix.io/4swW

    Output of "iwlist wlan0 scanning" looks ok for me:

    and the kodi.log:

    http://ix.io/4swI


    What is very weird: Sometimes all connections show up twice, see

    PXL_20230402_194352852.jpg
    Nextcloud - a safe home for all your data
    nc.d5x.de

    Is that expected?

    Many thanks

    Rainer

    Hi,

    I have trouble getting a wifi connection with the box image on a Wetek Play 2. I don't see any wifi network at all (I do if I boot the stock (Android) firmware on the device). I connected an ethernet cable and iw list at least shows a phy. Is there something I am doing wrong?

    kodi.log:

    http://ix.io/4suB

    dmesg output:


    http://ix.io/4suC

    Any hint or advice is welcome :)

    Many thanks

    Rainer

    I run multiple VLANs for different devices (Wifi, data network, several for home automation, some of them have internet access others not). I have today my xbian box (kodi) in the Wifi VLAN and the data VLAN, i.e. there is a eth0.<vlan1> and eth0.<vlan2>.