Hqnicolas

Author: @WINEDS How to Build Armbian with Maxio Ethernet Support for H96 V56 (2025 Model) If you own the H96 V56 (2025 model) TV box and want to run Armbian with full Gigabit Ethernet support, you might have noticed that the stock kernel doesn't always support the Maxio Ethernet chip out of the box. In this guide, we’ll walk through the most accessible method to build a custom Armbian image with the necessary kernel modules using Windows Subsystem for Linux (WSL). Refer to https://docs.armbian.com/Developer-Guide_Build-Preparation/ and note hardware requirements then in a Windows Powershell console select Ubuntu (using down arrow in title bar) and type to update the system: sudo apt update sudo apt upgrade Prerequisites A Windows PC with WSL (Ubuntu) installed. The specific patch file (my_v2_patch.patch) and DTB file (my_board_df.dtb) mentioned in the documentation. Patience (the build process can take a few hours). Step 1: Prepare Your Environment First, ensure your WSL instance has enough resources. Go to your WSL settings (typically via a .wslconfig file or the settings menu) and allocate about 75% of your CPU cores and RAM to ensure the build doesn't crash. Open your Ubuntu terminal in Windows PowerShell and update your system: sudo apt update sudo apt upgrade Step 2: Get the Armbian Build System Clone the official Armbian build repository and enter the directory: git clone [https://github.com/armbian/build](https://github.com/armbian/build) cd build Step 3: Apply the Kernel Patch You need to patch the kernel to support the specific hardware. Create the directory tree for the patch: mkdir -p ./build/userpatches/kernel/archive/rockchip64-6.12 Using Windows File Explorer, copy your my_v2_patch.patch file into this newly created directory (rockchip64-6.12). Step 4: Run the Build Command Now, kick off the compilation process. We will build a Gnome desktop image based on the Noble release. Run the following command (copy and paste this as one line): ./compile.sh build BOARD=h96-tvbox-3566 BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED=browsers DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=yes RELEASE=noble Step 5: Configure the Kernel (Crucial Step) After the build runs for a while, the blue Kernel Configuration menu will appear. This is where you enable the Ethernet driver. Use the arrow keys to navigate to Device Drivers. Select Network device support. Select PHY Device support and Infrastructure. Scroll down to find MAXIO PHYs. Press the Space bar until you see an <M> next to it (this modularizes the feature). Once selected, use the Tab key to select Exit and keep selecting Exit until you leave the configuration menu. Select "Yes" when asked to save the kernel configuration. Step 6: Retrieve Your Image The build will continue (potentially for a few hours). Once finished, your new image file will be located in: output/images Step 7: Post-Installation Setup Flash the image to your SD card/eMMC and boot the device. To get the Ethernet working, you need to update the Device Tree Blob (DTB). Copy the file my_board_df.dtb to /boot/dtb/rockchip/ on the device. Edit the boot environment file: sudo nano /boot/armbianEnv.txt Change the fdtfile line to point to your new DTB: fdtfile=rockchip/my_board_df.dtb Press Ctrl+X, then Y to save. Reboot your H96 V56, and you should now enjoy full Gigabit Ethernet speeds! my_board_df.dtb

That's nice, I don't have this new board BOM, be free to add the variant, I think board variants are included using a .dtso file for armbian i think we cannot include tirth party drivers, but any changes to .dts could be included into a .dtso file that's a way to enable this variant into mainline armbian

this link is private, please change it to public,

You can ask for other users to publish they ROM images, but, the ideal way is to compile your own images, since this is a custom driver, I think it's a safe way to go. You can share some pictures images from the board, so we can confirm your WiFi board and lan chip.

The manufacturer changed the BOM list of materials to lower the product's cost, and now you have a different version with different Wi-Fi and LAN controllers. @WINEDS have some fixes: Files Link Link Link DIffWifiLanCards.zip maxio.c my_rk3566-h96-tvbox3.dtb my_rk3566-h96-tvbox3.dts my_v1_patch.patch README Release Note.txt v1_patch.patch

I came from 4pda to armbian and I came from there already being a prejudiced person. this is just another normal day in the TV box section. Many other users have already encountered similar problems with Chinese boxes. you can solder a better module like @Deoptim

Welcome to TV-Box section, that's the real size of your RAM: 4gb https://github.com/hqnicolas/Rockchip-Library/tree/main/RK356x/rkbin

https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip64-6.18/dt/rk3568-yy3568.dts

Just for fun? for Vendor u-boot I like the ArmSom RK3568 SDK https://github.com/gitacodes/armsom_rk3568_SDK it works fine in all my boards... for mainline U-boot, https://docs.armbian.com/Developer-Guide_Overview/

You need to imagine it as a chip, the entire board; each change to the board alters the description of the "chip" you're referring to. Search for your board model on the forum. I don't own any boards using RK3399, but I believe you can find several users mentioning the board on the forum. for YY3568 board, the factory already have all information https://wiki.youyeetoo.com/en/YY3568/sdCardSystem

Sorry, I didn't take my medicines. where did you find the link between SliTaz and armbian? Do you intend to be the maintainer of this link? you need help writing SliTaz documentation?

Some manufactures change the wifi and lan controllers to keep prices down on new BOM of materials: @WINEDS got experience with thos problems https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/page/16/#comment-210825 https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/#findComment-217289 https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/#findComment-216154

take note that these functions are done by other repos with specificity using the name Armbian, as an example ophub is (ab)using the name Armbian without permission and they do not contribute to the core development process. Rather they trick users into thinking they get support here and therefore (ab)using our resources. everyone in the community has this as the main feature of a TV box

I think this device already have a working linux on SD-card, make a complete documentation of the boot method used by the current ambernic present in the SOC, and how it makes the search for the SD-card your work around will be only inside the rkbin and the u-boot. you will need to match the needs for this rkbin to find armbian, You may need to migrate armbian to mainline uboot or you may need something legacy, only with a debugger connected to the TTL port will it be possible to distinguish link link link I got this folder with some examples: https://github.com/hqnicolas/Rockchip-Library/tree/main/RK356x/rkbin https://github.com/hqnicolas/Rockchip-Library/blob/main/RK356x/rkbin/ABOUT.md also: Ambernic use some custom rkbin and u-boot, please share your research https://github.com/hqnicolas/Rockchip-Library/tree/main/RK356x/u-boot/socfpga https://github.com/hqnicolas/Rockchip-Library/blob/main/RK356x/u-boot/socfpga/rk3568_common.h

For this 16xx displays we need to ask @Jean-Francois Lessard he was in contact with this drivers for a while. these 16xx displays will be included in the mainline 6.18 drivers as tm16xx_i2c make sure to adjust your device according to this repository to benefit from the update https://github.com/jefflessard/tm16xx-display