Hi, is the new version(101.10.591.118.76) working for you? For me, the WiFi adapter seems to be turning on but doesn’t show any available networks to connect to.
Maybe Kinhank cheaped out on revision a
And it is only 10/100 mb
Not Gigabit 1000mb
Iam still using 21.3 from Nov 4 2025 ,on My Kinhank, no issues with anything. Of course I’ve always use Ethernet only for connections. Also think iam revision b
Will have to check specs on Ethernet, curious myself now
No, I have used the same box with a 1Gbit connection until Jan or Feb 2026. Later, I switched to WiFi and disconnected the Ethernet cable.
My best guess is that something has physically degraded in either the motherboard or the port itself in these 6-7 months.
I know mine shipped with 100 mb
It´s not easy to analyze network issues if You are not a networkexpert.
sources for wifi from rockchip
101.10.591.118.81 (20260506-3)
clm 2026-01-06
fw 18.35.387.23.311 (gd4f36276) Date=2026-01-30
bcm20260506.zip (4.6 MB)
for CoreELEC NO?
If you are asking me, the Makefile requires some edits to build for CE. Also, certain patches are useful for single-stream RX. I accidentally deleted the Docker container with the patches, so I’ll have to start from scratch.
Hmpf… after month with no issues with CE in EMMC my G1 stopped ssh via ethernet. I found heavy loss of packages… Tried other cable and other router - but the issue stays…
seems that there is a problem with the hardware… I am just not sure, why a few posts before were network drivers posted - is there a chance, that new drivers solve the problem?
Or should I go on with usb2ethernet adapter?
wlan.zip (4.6 MB)
101.10.591.118.81 (20260506-3) and 103.20.56.42(20260506-3) for 4.9 and 5.15 kernels
Blacklist original kernel module
Copy blacklist.conf to /storage/.config/modprobe.d/blacklist.conf
Copy the rest of the files to the /storage directory
Add sh /storage/insmod & to /storage/.config/autostart.sh
like this
#!/bin/sh
sh /storage/insmod &
and make this script executable
chmod +x /storage/.config/autostart.sh
BT firmware
mkdir -p -v /storage/.config/firmware/brcm/
cp BCM4362A2.hcd /storage/.config/firmware/brcm/
iperf3 tests, -R -P1
~780mbps 95% idle
~880mbps 85% idle (without load balancing echo 0 > /sys/wifi/lb/lbrxp) The core 0 should not be used for user processes.
Use the Ugoos X4Q Extra DTB ,it’s in the Device tree folder in CoreELEC.
Then can test ethernet, it will boot on all versions CoreELEC for the Kinhank
Ethernet only works of course
I don’t know how a port can degrade in 6 months 
, let alone ever…
Maybe test.
Just a thought
What is this for ?
Piers 22 5.15 196 kernel
Or still the old 4.9.269 ?
Untested module for 5.15. dhdpci.ko_5.15.zip (1.3 MB)
Everything else is here.
Haven’t visited for a while. What is the latest version version of software (nightly) that I can upgrade to please.
bcm43752a2_pcie_ag (ap6275p) works with 103.20. driver (wifi7 branch). Ofc, there’s no Wi-Fi 7, but this driver still has some extra software optimizations, like work-item aggregation.
[ 11.751623@0]- [dhd] Driver: 103.20.56.42(20260506-3)
[ 11.751623@0]- [dhd] Firmware: wl0: Jan 30 2026 03:32:32 version 18.35.387.23.311 (gd4f36276) FWID 01-9b2e7d85
[ 11.751623@0]- [dhd] CLM: 9.9.24_SS (V15_190709) (2026-01-06 15:32:34
Tested on Linux 4.9 and compiled on 5.15. Kinhank G1 - #1278 by Aloe
Overclocking ddr (for Advanced Users)
Why do this?
AI calculations for Dolby Vision Profile 7 (FEL) show that 2640 MT/s is the realistic minimum, while 2928 MT/s is the sweet spot for smooth playback. In contrast, the stock memory frequency is only 2400 MT/s, whereas S922X devices run at 3216 MT/s.
I have been running my ddr at 2928 MT/s for more than 6 months without any issues.
How to overclock RAM for a single boot
To test the new frequency temporarily, enter the following command in the U-Boot console(uart required):
g12_d2pll 1464
The system will immediately reboot with a new effective frequency of 2928 MT/s (1464*2). (memtester 1500M 3 OK! with 3072)
How to automate overclocking safely
To automate the overclock without the risk of a bootloop, we use a trigger file check.
If the trigger file exists, U-Boot deletes it and reboots with the higher frequency. If the file does not exist, the system proceeds to boot at current frequency (oc or normal). This watchdog mechanism prevents an endless reboot cycle.
U-Boot configuration
Add this logic into your boot chain (for example, inside bcb_cmd):
bcb_cmd=if fatload mmc 0:1 $loadaddr ddr; then fatrm mmc 0:1 /ddr; g12_d2pll $ddr_pll; fi;original bcb_cmd
ddr_pll=1464
CoreELEC / Kodi startup script
Arm the trigger file only after the operating system has booted successfully.
sleep 10
mount -o remount,rw /flash
touch /flash/ddr
How this logic works:
During boot, U-Boot checks whether /flash/ddr exists.
If the file is found, U-Boot immediately deletes it and reboots using the target PLL frequency (ddr_pll=1464).
On the second boot, the file is already gone, so the bootloader skips the command and boots CoreELEC at the overclocked frequency.
Once CoreELEC and Kodi have loaded stably, autostart.sh recreates /flash/ddr for the next reboot.
Hi, what is the difference between these versions 101.10.591.118.81 (20260506-3) and 103.20.56.42(20260506-3)?
Newer codebase, more software optimizations.