Posts by angeltenshi

  • [UNOFFICIAL][LE12][RK3228/RK3229][box] LibreELEC builds

    RK3229 / SSV6051P Wi-Fi working with standalone wpa_supplicant — possible ConnMan/driver compatibility issue

    Hi ilmich,

    First, thank you for your continued work on LibreELEC for RK322X devices.

    I’ve been experimenting with your LibreELEC 12 nightly build on a repurposed RemoteLink appliance and wanted to share my findings regarding the built-in SSV6051P wireless chipset.

    I noticed previous discussions about SSV6051P compatibility problems, including recommendations to use an external USB Wi-Fi adapter. I was able to get the built-in adapter working without replacing the hardware.

    Hardware and software

    • Original device: RemoteLink EQ-RAV200 (ID1720)
    • PCB marking: A7_3229_V6_2 (20170506)
    • SoC: Rockchip RK3229
    • Wireless chipset: SSV6051P (2.4 GHz)
    • LibreELEC: nightly-20260311-1b9970a (RK322X.arm)
    • Installation: eMMC
    • Network: Two Linksys E7350 access points running OpenWrt, broadcasting the same SSID with WPA2/WPA3 mixed-mode security (sae-mixed)

    I’ve attached a photograph of the PCB showing the board revision and SSV6051P chipset for hardware identification.

    Original problem

    The built-in Wi-Fi adapter did not establish a usable wireless connection through LibreELEC’s normal ConnMan interface.

    Because the access points advertise both WPA2-PSK and WPA3-SAE, I suspected a possible compatibility problem involving WPA3 transition mode, ConnMan’s wireless configuration, or the SSV6051P driver.

    I temporarily tested WPA2-only security on an access point but wanted to preserve the original WPA2/WPA3 mixed-mode configuration.

    Successful workaround

    I configured ConnMan to ignore wlan0 using:

    /storage/.config/connman_main.conf

    I then created a custom systemd service, wifi-wpa2.service, to launch wpa_supplicant directly:

    /usr/bin/wpa_supplicant \

    -i wlan0 \

    -c /storage/.config/wpa2-test.conf \

    -D nl80211

    The relevant wireless configuration is:

    network={

    ssid="example-ssid"

    psk="REDACTED"

    key_mgmt=WPA-PSK

    proto=RSN

    pairwise=CCMP

    }

    These parameters explicitly restrict the client to WPA2-PSK authentication using AES-CCMP encryption.

    I also removed the BSSID restriction so the device could associate with either access point.

    Since ConnMan was no longer managing wlan0, I created a separate wifi-dhcp.service using a statically linked BusyBox 1.37 udhcpc client and a custom DHCP script.

    The script handles DHCP lease assignment and renewal, configures the IPv4 address, and installs the default gateway with route metric 500.

    Both services are enabled through systemd.

    Results

    After restoring both access points to their original WPA2/WPA3 mixed-mode configuration:

    • The SSV6051P successfully associates using WPA2-PSK.
    • DHCP successfully obtains the reserved IPv4 address.
    • DNS resolution and Internet connectivity work.
    • SSH access works through the built-in Wi-Fi adapter.
    • A three-packet Internet ping test showed 0% packet loss and approximately 30 ms average latency.
    • The wireless connection successfully survives a reboot.
    • Ethernet is not required.

    The device is now operating successfully over its built-in wireless interface.

    Possible explanation

    I understand that using a USB Wi-Fi adapter would normally still involve ConnMan, but with a different chipset, firmware, and driver.

    These results demonstrate that the SSV6051P hardware and its current driver can establish a functional WPA2 connection under LibreELEC 12, even when the access point advertises WPA2/WPA3 mixed mode.

    This suggests the problem may involve the interaction between ConnMan, wpa_supplicant, and the SSV6051P driver, potentially related to security negotiation or Protected Management Frames (PMF).

    However, I cannot conclusively identify ConnMan as the cause because the workaround changes both connection management and the authentication parameters.

    Questions

    Have you encountered similar behavior with the SSV6051P?

    Do you have an RK322X board equipped with this chipset available for testing?

    Would comparing ConnMan-managed connection logs against the successful standalone wpa_supplicant configuration help identify the underlying problem?

    I would be happy to provide the complete systemd unit files, DHCP script, configuration details, and diagnostic logs if they would be useful.

    Thank you again for your work on these builds.

    Best regards,

    angeltenshi