Search the Community
Showing results for 'RTL8189'.
Found 4 results
-
Hello everyone, I have an S96Q+ H616/H313 TV box and I am looking for a working Linux/Armbian or OpenWrt image, or the correct DTB configuration to boot. I am fully ready to test any trial images or boot configurations you send over! **Hardware Details:** - **Device Name:** S96Q+ (Marked as 6K on the plastic shell) - **SoC:** Allwinner H313 / H616 Family (Reported as h313/616 in system apps) - **GPU:** ARM Mali-G31 MP2 - **RAM/Storage:** 4GB RAM / 64GB eMMC - **Physical Ports:** 3x USB ports, 1x Ethernet (RJ45), 1x Headphone jack, 1x DC Power **Networking Setup:** - **Wi-Fi:** Confirmed to be standard Single-band 2.4GHz Wi-Fi only. The exact chip model is unverified from the shell (likely XR829 or RTL8189 based on common configurations). - **Bluetooth:** Broken/Non-functional in original OS (the physical board likely lacks a Bluetooth controller entirely). Please send over any compatible community builds, bootloader setups, or DTB configurations that fit this single-band H616 layout and I will flash them to test! Thank you!
-
As other people have noted, there are issues trying to connect the CB1 to wifi after the first boot. I believe I've narrowed down the cause, but I'm not sure about the right way to fix it permanently. The issue I was experiencing is as follows: 1. Flash latest armbian minimal to sd card 2. Plug into CB1 and turn it on 3. Go through first boot setup and connect to wifi normally 4. Reboot CB1 5. CB1 no longer connects to wifi, wpa_cli says 'CTRL_EVENT_SCAN_FAILED' A temporary solution I found is to mask systemd-networkd, then manually unmask systemd-networkd and start it after booting. This suggests that the problem is that systemd-networkd tries to talk to the RTL8189 before it's ready, and that puts the chip into a bad state. The wireless connection works on the first boot, because the CB1 doesn't try to configure the chip until after it has booted up. If I only mask netplan-wpa-wlan0 (instead of masking networkd) and try to manually bring it up, then I get an empty scan result, rather than CTRL_EVENT_SCAN_FAILED. Is there a way to make systemd-networkd wait until after the driver has loaded before trying to configure the chip? The easiest temporary solution is probably to just add a delay before systemd-networkd starts.
-
On the latest image (25.2.2) of both Server - Noble and Desktop - XFCE - Bookworm, the wireless interfaces show up as expected and connect to wifi. After the first apt upgrade and reboot, the system no longer detects the wireless interface at all. For my armbianmonitor output, there is a mediatek wireless interface plugged into USB, but there is no mention of the rtl8189 in any of the boot or hardware logs. Did something change in the overlay or other pre-kernel bootloader configs which disable the device? I would think if it were merely kernel / driver related, the hardware would still show up, but be unusable until a driver was configured.
-
@Andr1k If I understand correctly the rtl8188 driver is compatible with your rtl8189, so you may try this https://forum.armbian.com/topic/26917-rtl8188fu-driver-install/ https://github.com/sgjava/rtl8188fu/tree/arm Compile and install with (the script expects this way) ./rtl8188fu-arm/scripts/install.sh I am running in my unit with success
