Search the Community

Hi everyone, I’m working on a custom Armbian build for an RK3588-based board (cm3588-nas) and trying to completely disable the Rockchip crypto driver (rk_crypto2), since it's negatively impacting LUKS (AES-XTS) performance. Despite several attempts, the module continues to register algorithms in /proc/crypto after boot: driver : rk2-sm3 module : rk_crypto2 driver : rk2-sha512 module : rk_crypto2 driver : xts-aes-rk2 module : rk_crypto2 ... ------------------------------------------------------------ What I’ve Tried ------------------------------------------------------------ 1. Kernel Config Override - Added CONFIG_CRYPTO_DEV_ROCKCHIP=n and CONFIG_CRYPTO_DEV_ROCKCHIP2=n to: userpatches/linux-rockchip-rk3588-edge.config - Verified .config has it set to n after build. - Used CLEAN_LEVEL="make,debs,oldcache" in the build command. 2. Blacklisting & Deletion in customize-image.sh echo "blacklist rk_crypto" > /etc/modprobe.d/blacklist-rk_crypto.conf rm -f /lib/modules/*/kernel/drivers/crypto/rockchip/rk_crypto.ko* 3. Post-Boot Verification - lsmod | grep rk_crypto → empty - modinfo rk_crypto → module not found - /proc/crypto still shows rk2-* drivers tied to rk_crypto2 4. Manual Source Removal - Commented out this line in drivers/crypto/rockchip/Makefile: # obj-$(CONFIG_CRYPTO_DEV_ROCKCHIP) += rk_crypto.o - Also removed or disabled its Kconfig entry. ------------------------------------------------------------ System Details ------------------------------------------------------------ Board : cm3588-nas (RK3588) Kernel : rockchip-rk3588 edge (Linux 6.8.x) Builder : Official Armbian compile.sh ------------------------------------------------------------ Goal ------------------------------------------------------------ I want to fully disable the Rockchip crypto engine (rk_crypto2): - It should not load, not build, and not register anything in /proc/crypto. - LUKS should fall back to software crypto (cryptd, aesni, or default fallback). ------------------------------------------------------------ Any help is appreciated. I’d love to hear from anyone who’s successfully disabled rk_crypto2 entirely or has ideas for where the registration is coming from even when the module appears removed. Thanks!

I own a CM3588 NAS board from FriendlyElec. The eMMC drive was factory-installed with the FriendlyElec version of OpenMediaVault, and any other FriendlyElec or Armbian image could be booted from an SD card. After installing the current version of Armbian OpenMediaVault (Debian 12 Bookworm - Armbian Linux v6.1 Build Date: Mar 6, 2025) on eMMC and updating bootloader via armbian-config (option Boot from eMMC + system on eMMC), nothing else can be booted from the SD card except Armbian images. Please, is there a simple way to fix bootloader back to original option of booting FriendlyElec images from SD card without having to erase entire eMMC drive? Boot from SD card does not work even for FriendlyElec automatic eflasher (SD to eMMC) images. I have Windows 11 and RKDevTool 3.30 is quite confusing and too complex software for me. PS. Does the CM3588 NAS board have SPI NOR flash? And how can I upload UEFI 1.1 boot (https://github.com/edk2-porting/edk2-rk3588) to eMMC or to SPI NOR?

Hello, I'm new to Armbian and SoC/ARM devices but I've installed Armbian on the device before, however after tinkering around with RKDevTool and installing FriendlyELEC images on it through USB I'm now unable to boot from SD Card. I've done the "EraseAll" procedure under unbricking method https://wiki.friendlyelec.com/wiki/index.php/CM3588#Windows_Users however it didn't help. I've tried two SD Cards and I have no idea what else I can do. Unfortunately I wasn't able to find anything useful on google. The error is: "Gave up waiting for root file system device." "ALERT! UUID=602525b7-ed9f-43f7-91b0-1dc4e67b44bf does not exist. Dropping to a shell!" When in the initramfs shell I checked blkid and it seems like the SD card is /dev/mmcblk1 PTUUID="8cdc55ae-c576-6f4c-a793-0397a48dccf0". I'm guessing it should work if I change the armbian UUID or is that assumption incorrect? If so how should I go about it? Also it looks like the UUID Armbian is looking for is static which surprised me... I thought it's something randomly generated by the system. I fixed it edit: I booted into debian I got from FriendlyELEC and wrote the Armbian image directly with DD to the SD card and now it works. Before I was writing with Balena Etcher and USB Writer on Windows, tried multiple times, formatted the sd card with diskpart etc., no idea why it didn't work with those but worked with DD, especially since I did it with etcher before and it was ok. I was on a different windows version but I doubt that's the issue?

Hi, I'm trying to setup CM3588Plus NAS 3 x 4tb vp4300 nvme drives OpenMediaVault updated. Drives are setup to RAID5 with ext4. the OS is reporting that ssd temps getting to 63-68C while idling, and likes to creep up to 75C where if I'm correct thermal throttling starts to kick in. the SBC is in open air, no case/enclosure. room temp 21C. How to find the cause and solve it? Amy recommendations setup (change the fs) etc. Thanks a mill.

Hi, I have installed the latest image "Minimal/IOT images with Armbian Linux v6.12" with the mainline Kernel. Many thanks @ColorfulRhino , @amazingfate and many others for their hard work. I have a board with 32GB RAM and 4x NVMe and it is working with HDMI, USB and network. I have installed XFCE on top by my own. Some parts currently not working (what I have seen so far): * second HDMI * HDMI audio * sensor controlled fan speed This seems to be on the roadmap for 2025 for the upstream Kernel. For the fan control I currently use my own overlay and want to share it. /dts-v1/; /plugin/; / { /* our pwm-fan comes with 6 cooling levels (0-5) in relation to 255 <0 50 80 120 160 220> */ /* this overlay use the sensors of big core 0 to control cooling by the fan */ /* add new trips for active cooling */ fragment@0 { target-path = "/thermal-zones/bigcore0-thermal/trips"; __overlay__ { bigcore0-active1 { /* 55 degree with hysteresis of 5 deg */ temperature = <55000>; hysteresis = <5000>; type = "active"; // internal phandles use a small integer to be able to reference phandle = <0x00000001>; }; bigcore0-active2 { /* 60 degree with hysteresis of 2 deg */ temperature = <60000>; hysteresis = <2000>; type = "active"; // internal phandles use a small integer to be able to reference phandle = <0x00000002>; }; }; }; /* add cooling maps to use the new trips by the pwm-fan with level 0-5 */ fragment@1 { target-path = "/thermal-zones/bigcore0-thermal/cooling-maps"; __overlay__ { map1 { trip = <0x00000001>; cooling-device = <0xffffffff 0 1>; }; map2 { trip = <0x00000002>; cooling-device = <0xffffffff 2 5>; }; }; }; /* we need to poll, because in interrupt mode the fan will not stop */ /* alternatively we can use type="passive", a poll interval of 250 ms is already defined for passive */ fragment@2 { target-path = "/thermal-zones/bigcore0-thermal"; __overlay__ { /* for active cooling, in milliseconds */ polling-delay = <2000>; }; }; /* adjust the original fan levels <0 50 80 120 160 220> a bit */ /* the fan starts rotating at 40-45, 45 is sufficient to keep <50°C at normal operation */ fragment@3 { target = <0xffffffff>; __overlay__ { cooling-levels = <0 45 80 120 160 255>; }; }; __fixups__ { fan = "/fragment@1/__overlay__/map1:cooling-device:0", "/fragment@1/__overlay__/map2:cooling-device:0", "/fragment@3:target:0"; }; // to adjust finally the internal references __local_fixups__ { fragment@1 { __overlay__ { map1 { trip = <0x00000000>; }; map2 { trip = <0x00000000>; }; }; }; }; };

Morning all, so I got myself a FriendlyElec CM3588 NAS board for testing and in the end integrating in my homelab. I tried a few Armbian images - FriendlyElec suggests the NanoPi R6S image and I tried the NanoPC T6 image. Both boot but both have some issues, e.g. no USB connectivity and no HDMI out (T6). While not a being developer or SBC specialist, I am a Linux user since 1995 (server)/1996 (desktop) and I am used to some pain, tinkering and problem solving. Is there any kind of "getting started with a new board"- or similar document that I could use as a starting point to tinker with this board? Any hints, advice? Of course I could use the stock Debian/Ubuntu images from FriendlyElec but I grew to like Armbian a little after running it on a bunch of RPis and a Banana Pi... Happy New Year! Stefan