All Activity

Nice work. We've got the sudo update stuff twice though. Also I think the last image is in the wrong place?

rk3326 and rk3328 are not the same thing, neither is px30. Definitely no chances to run this on those SoCs; I don't know if there are images for boards using px30/rk3326 in armbian.

https://www.armbian.com/olimex-lime-2/ Does the image come with and install non free software on the computer? If so is there documentation showing how to do a fully free software installation of the Armbian_community_25.11.0-trunk.546_Lime2_trixie_current_6.12.58_minimal.img image? Free software is software you can use, share, modify and redistribute. Thank you.

I feed my ROCK5B-16GB with SATA brakeout on E-key and Samsung NVMe on M-key with 12V own soldered USB-C pigtail (from an old car battery in addition if mains power 12V brick is not there). It does not work with USB-C PD (the RPi5 27W nor an HP 45W ), then boot loop. I use the 5V and GND from 40-pin header for feeding the 5V of an 3.5 inch HDD (and it gets its 12V from the mentioned setup). Look at the ROCK5 schematics. It is not a RaspberryPi5 or OrangePi5. It has an own DC/DC stepdown convertor which can take 20V-9V on its USB-C power input connector and so creates an own stable 5V that is used for USB or in my case for some DIY 5V i need. You might dig deep into U-Boot and kernel and see if PD handling does work nowadays with latest, I didn't, I just soldered fixed 12V, much easier for me. Automotive can mean very high spikes and negative dips when engine start, so be aware to protect else your board might die sooner or later.

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

For SBCs without own audio I use networked pulseaudio. I never got it to work in newly installed Jammy and Bookworm, also not in Bookworm upgraded in-place to Trixie. It worked in Buster, BuIlseye and allways worked in Opensuse Tumbleweed. I already had all pipewire user sockets and services disabled and pulseaudio enabled, also de-installed pipewire-pulse as that one is the problem I believe (but is more than a year ago I looked at it). Now it turns out that doing 'pactl load-module module-zeroconf-discover' did add remote audio sinks. GUI based paprefs in Ubuntu/Debian should do it, but that is all grey since years, cannot be selected nor changed. So NanoPi-R6C with Armbian Trixie edge kernel now also plays audio via Armbian Trixie NanoPi-NEO SPDIF enabled with long simple wiring to an amplifier that takes coaxial SPDIF as input. I also had it working analog, but way too much issues with noise etc. 'the long simple wiring' is 1 lead of a low-quality twin analog audio cable, shielding=GND, core=signal.

haha , I have read a lot on PSU, I am currently powering through a USB-C connected to a Anker Block www.amazon.co.uk/dp/B0D59JNQ9F?ref=ppx_yo2ov_dt_b_fed_asin_title This should be overkill, but I am here to learn I was going to start another post as currently this board will run on an Automotive rig which is supplied 13.8V from a fairly good but dumb Bench PSU, which I know i cant feed into it, but I was tempted to ask what the arangement with the USB-C was as could i wire a basic step-down circuit for a stable 5V 5A to connect to the GPIO pins and solve this once and for all. I was tempted to get one of these ordered foor today to eliminate issues, but was looking for somewhere with a list of known good supplies. https://www.amazon.co.uk/iRasptek-Raspberry-Supply-Adapter-（White）-White/dp/B0D12H1N4L?crid=2DR00330ACZG4&dib=eyJ2IjoiMSJ9.yy8NlNRV8fvukOA7JVjC9ng_XPbmDtZarii93lgqL_-ToxBeH4T6raTFYwrTkmXGbv-_trvnbv0rCVrjDbhnz3JY-mW3NRzGmgg9gN_fiEasz3_8Qc6GkhIQJG3FacIhxJIy3WGUyuvKu_5iDOxOj5hveO_RctLLAn33KRTnWT1EwvHQUVfvUzfXO8fi3Y8X0CAK1pjSJNdDU86EaeE1maJK2KtMkd32uxYpUs0TDLE.wLLZXeiEdInd_jsKhSdZfBR7IoK18dfWVdL6iph7Wvs&dib_tag=se&keywords=5v+5a&qid=1763810843&sprefix=5v+5a%2Caps%2C92&sr=8-5

I think @NicoD meant tasksel.

please DO share what steps you took to get it working for the benefit of the next guy.

First tell us how your power supply looks like.

Hiya, I am currently trying to setup some ROCK 5B boards as runners and as I install the latest Ubuntu 24.04 (Noble) from here https://www.armbian.com/rock-5b/ it seems to get to where I configure my user etc, then on the next boot it gets stuck at kernal. So I guess before I go through trial and error , is there a recognised most stable build that can be relaibly flashed people would recommend, I found the Rock provided Debian and KDE Plasma to be very buggy and just kept locking up on me so something with Gnome would be cool for now , but will probably move to headless much further down the line. Amazing community reading the messages so far so thank you for everyone who contributes!

@fabiobassa thank you, it is worth a try.

For rocket support you need at least 25.3. RTFM

@dale as usual shorting pins 6/7 on the well exposed nand

If I remember correctly to actually use the NPU you'd need a 6.18-kernel and a recent Mesa version. Compared to the standard 24.0.x Mesa version in Debian Trixie I though you needed 24.3 or 25.0. But if you actually tried working with it, you should be able tell what you are using.

@王类 here are instructions to build an armbian image with maxio kernel module. It applies to current LTS kernel version 6.12.58. Its mostly cut and paste and uses windows so I hope you can try this! @maka I'll keep working on your suggestions. Many thanks! my_board_df.dtb maxio_install.pdf

debug boot issues: https://debug.armbian.de

taskset is not found in the repository. I have resolved the issue by install xubuntu-desktop package rather than installing xfce4 and xfce4-goodies. Thanks for the help. ref:

Thanks. I got pulseaudio working

I tried Dragon Quest 11S with stripped dxvk 1.11. It failed because the panvk driver does not support Geometry Shader. There's an on-going MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/38401 to support it.

Hi @Scott Ksander, Can you share on which I2C bus the RTC was detected? On my Nanopi Neo3 it was on i2c0, but I see in the meson DTs that RTC is on i2c2. Perhaps you can start with a barebones overlay and add until it starts to work. /dts-v1/; /plugin/; / { fragment@1 { target = <&i2c2>; __overlay__ { #address-cells = <1>; #size-cells = <0>; pcf8563@51 { compatible = "nxp,pcf8563"; reg = <0x51>; status = "okay"; }; }; }; }; Groetjes,

Some more info, I found a lot of DT entries for the PCF8563 in a recent codebase for some of the Amlogic SoCS, but not the C2. What is shown are: HC4 M2 Perhaps you can check if those overlays are compatible with the C2 and experiment a bit? Groetjes,

Thanks. Will give that a look Scott

Hi @Scott Ksander, `i2cdetect` will just detect stuff on the I2C bus, you would not need a DT overlay for the device for that to work. For the kernel to detect the device and load the appropriate kernel module for it, you do have to make sure the device is known in the DT. I'm not sure about your board, but for a PCF8523 (different RTC) my Nanopi Neo3 I had to add or adjust an existing user overlay to make the PFC known to the kernel. /dts-v1/; /plugin/; / { compatible = "rockchip,rk3328"; fragment@1 { target = <&i2c0>; __overlay__ { #address-cells = <1>; #size-cells = <0>; pcf8523@68 { compatible = "nxp,pcf8523"; reg = <0x68>; status = "okay"; }; }; }; }; &rk805 { rk808-rtc { status = "disabled"; }; }; For a DS3231 I also had to add a user overlay that would tell the kernel that it can use the DS3232 driver for a DS3231 device. You most likely already found all the information on this already on the interwebs. You will have to adjust the compatible entry to your board, you might even try without that line completely. Add the file to `/boot/overlay-user/` and then compile and add to `armbianEnv.txt` using `armbian-add-overlay`. Groetjes,

No errors are logged. Overlays are i2cA and i2cB. Module is rtc-pcf8563. No /dev/rtc* is created i2cdetect -y 0 shows 0x51 thanks