Search the Community

Certainly not a new item but havn't found an Armbian how-to. Hardware: Rockchip rk3588 based hardware with both SDcard slot and eMMC memory. Wish: make a SD card image that, when inserted in the SDcard slot, causes a bootable Armbian OS image to be written to eMMC from that SDcard, followed by boot from eMMC. The bootable image should remain in its most compact form, to limit copy time, and only upon first boot from eMMC be made to use the entire eMMC. Has this been explored already? Ideas on how-to?

Hello everyone I wanted to build Armbian on the AIO-3588Q board. But I did not see that there was a configuration of this board. There was a configuration of the ITX-3588j board and other manufacturers on the same rk3588 platform and tried to build Armbian. In the assembled images in GPT format, only rootfs was stored (it combines rootfs and kernel (boot.img) according to the rockchip documentation). After I built it, I installed it in the rootds partition, it was installed without any errors. But the system does not start. You turn on the power, the fan starts spinning very fast, spins for 5 seconds, the lower LED lights up, and then the fan stops, the light goes out, a second passes and the fan starts spinning again. I tried to get logs through the debug port, nothing was output except Chinese characters mixed with question marks (binary data) I tried to create a custom board profile for building Armbian, but I constantly got errors during the build. Dragged all dts and makefile from source firefly. Also could not understand what is needed to modify uboot so that uboot can run from gpt kernel located in rootfs. Please tell me how to: 1) Get logs from uboot and connect to its command line? 2) How can I build Armbian for AIO-3588Q together with Uboot? Or build Uboot separately, but what is needed for correct parsing of GPT from rootfs? Maybe someone had experience of building for this board

qemu-system-aarch64 -M virt -cpu host -enable-kvm ... only works reliably when 1 CPU core ( -smp 1). When a VM has 2 cores, it randomly worked I experienced. If virt-manager pick 2 equal cores, VM UEFI/BIOS/kernel runs OK, but if a Cortex-A76 and Cortex-A55, all sorts of exceptions are shown or just lockup 2x or 1x 100% usage. In order to still be able to use KVM, start qemu-system-aarch64 as follows: taskset --cpu-list 4-7 qemu-system-aarch64 -M virt -cpu host -enable-kvm -smp 4 ... or taskset --cpu-list 0-3 qemu-system-aarch64 -M virt -cpu host -enable-kvm -smp 4 ... Mainline kernel 6.8.x or later does not have this problem. It can transparently use all 8 cores. Userspace is Debian Bookworm based.

Can I run a YOLOv8 model in RKNN format, developed for Rockchip 3588, on a Rockchip 3588S without any issues?

If I would like to build myself an image with all content present in images posted on web, downloading code at https://github.com/armbian/build and choosing my board, when I build image if I don't change anything I will get what I want? Thanks

Version 20230401 with kernel 6.2 (pancsf-midstream). With HDMI USB support. https://disk.yandex.ru/d/W8pOOhizVjq91A To enable HW acceleration, install the mesa package with the forced overwrite option or an archive to enable acceleration for wayland. To enable wayland acceleration, you need to replace the files in the /usr/lib/aarch64-linux-gnu directory with the contents of the archive (with file replacement). After that, acceleration will work with wayland. X11 and wayland acceleration works the same way on Debian Sid (the images are the same as Ubuntu). After starting the system and initial configuration, replace the files from the archive in the same way and acceleration will work. The results of running in Debian Sid Gnome for x11 and wayland. dpkg -i --force-overwrite mesa_23.0.0-dev-2_arm64.deb After installation and reboot, HW acceleration will work in x11 and wayland. Please note, this is a test version of mesa for the initial evaluation of the work, some of the functions do not work in it and there may be bugs. With x11, the system works more stably, but the test results are lower than in gnome+wayland. deb\archive https://disk.yandex.ru/d/h8c-Y2FfAvx76g

Current kernel: Linux rock-5b 6.1.43-vendor-rk35xx #1 SMP Mon Mar 18 05:06:52 UTC 2024 aarch64 GNU/Linux Symptoms: $ lspci .. 0002:20:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) 0002:21:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) 0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) 0004:41:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) And after a reboot I find with dmesg: # modprobe iwlwifi modprobe: ERROR: could not insert 'iwlwifi': Exec format error root@rock-5b:~# dmesg|grep -E -A 3 -B 3 "intel|iwl" [ 6.285747] input_leds: disagrees about version of symbol module_layout [ 6.288159] joydev: disagrees about version of symbol module_layout [ 6.309378] gpu_sched: disagrees about version of symbol module_layout [ 6.314006] btintel: disagrees about version of symbol module_layout [ 6.314148] btintel: disagrees about version of symbol module_layout [ 6.314693] btintel: disagrees about version of symbol module_layout [ 6.314751] btintel: disagrees about version of symbol module_layout [ 6.368536] iwlwifi: disagrees about version of symbol module_layout [ 6.377085] systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod... [ 6.378547] systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse... [ 6.380075] systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop... [ 6.380564] btintel: disagrees about version of symbol module_layout [ 6.381271] systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/initramfs/fsck-root). [ 6.383701] systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/initramfs/fsck-root). [ 6.384399] dm_mod: disagrees about version of symbol module_layout -- [ 217.993684] [drm:vop2_plane_atomic_check] *ERROR* Invalid size: 64x1->64x1, min size is 4x4 [ 218.001798] [drm:vop2_plane_atomic_check] *ERROR* Invalid size: 64x1->64x1, min size is 4x4 [ 218.009720] [drm:vop2_plane_atomic_check] *ERROR* Invalid size: 64x1->64x1, min size is 4x4 [ 439.786500] iwlwifi: disagrees about version of symbol module_layout [ 445.011474] iwlwifi: disagrees about version of symbol module_layout [ 476.290795] iwlwifi: disagrees about version of symbol module_layout Manually installing the iwlwifi driver yields: # modprobe iwlwifi modprobe: ERROR: could not insert 'iwlwifi': Exec format error Perhaps more people ran into the same problem? Of course I ran into this problem while quickly trying to access some server, only finding that the wifi adapter was not working anymore ("it used to work"). The quick & dirty solution was finding a cable bypassing wifi.

Hi, i have a problem, on my first boot i cant use my Keyboard because Armbian doesnt recognized it. i use Bookworm as an Image

The first version of Armbian images for Station M3 rk3588s (rk3588s-roc-pc) is available. the launch is very simple - download, unpack, burn to an SD card, connect to the device and turn on the power. The system starts automatically. At the first launch, perform the initial setup in the same way as all Armbian-enabled devices. https://disk.yandex.ru/d/-zSW21XKN0pfIA

Hi everyone, I have to make a custom kernel for a RK3568 based device with kernel 4.19.232. Currently running Ubuntu 20.04LTS. I followed this guide https://opensource.rock-chips.com/wiki_Rockchip_Kernel and I tried compiling 4.19 from rockchip source code and made a boot.img with the rk3568-evb1-ddr4-v10.dtb. The device boots but HDMI isn't working correctly, LVDS appears detected but does not show anything and one USB stopped working. Since I am new to all these things, does anyone know of any guides to compile kernels for rockchip ? I am trying to replace the boot.img from the original FW because kernel is inaccessible and iptables is not working. Also, there are some issues with monitors flickering.

Hi! I recently managed to boot Armbian on the QuartzPro64 board (RK3588) from Pine64. I also installed Proxmox, which worked out of the box. This is really amazing to me! To do this, I manually replaced the kernel and DTB file from the Armbian image for the OrangePi5 board, since it's based on the same CPU. Now, I would like to build the image for the QuartzPro64 using the Armbian build script. So far, I've already : added a new .conf file in config/boards (based on orangepi5-plus.conf) added a new .config file in config/kernel added a new entry in the list of branch in config/sources/families/rockchip-rk3588.conf. Megi) # Megi's kernel SKIP_BOOTSPLASH="yes" LINUXFAMILY=rockchip-rk3588 LINUXCONFIG='linux-rockchip-rk3588-'$BRANCH KERNEL_MAJOR_MINOR="6.5" # Major and minor versions of this kernel. KERNELPATCHDIR='rockchip-rk3588-megi' # Empty/nonexisting, so zero patches, hopefully KERNELSOURCE='???' KERNELBRANCH='???' KERNEL_DRIVERS_SKIP+=(driver_rtw88) # This is a custom kernel, while the rtw88 driver patching expects pure mainline ;; As you can see, I would like to build Megi's kernel (https://xff.cz/git/linux/log/?h=orange-pi-6.5). The kernel tree is not available on Github or Gitlab, and is only available using Git bundles. So, to build the kernel, I need to clone torvalds/linux, then apply the Git bundle file from Megi. Does Armbian support this way of fetching the kernel sources? Is there another similar board I could use as inspiration? Thanks!

For my Mekotronics R58 mini PC I downloaded and installed latest Armbian build "bookworm". When I want to execute the suggested scripts to add Mali PPA's for hardware acceleration, I get the error "no release file" for these PPA's. What to do? Wait until it gets solved? Download and install Jammy in stead? Would the PPA's then work without error? Or is there another workaround? Thanks for any pointers! Bas

Are there any other Mekotronics R58 mini users out there? I like this box a lot and Armbian runs great on it, I would very much like to share expereriences with other users and learn from each other. At this point Armbian is downloadable for this board on this site. And it has recent updates too. Some specs: I have the Mekotronics R58 mini plastic version (there is also metal box that has better cooling but same internals) RK3588 8 core Rockchip CPU 4Gb RAM File System transferred to 120Gb SSD with armbian-config Measured it uses 2.1 watt during idle I seem to have everything working except HW acceleration. On the download page it says to execute some PPA scripts (to add repositories) but these fail And everything works rather GREAT very nice silent mini PC Should I wait till subsequent updates will fix HW acceleration? Or run the provided scripts? But alas, these scripts run into errors like below. E: De pakketbron 'https://ppa.launchpadcontent.net/liujianfeng1994/panfork-mesa/ubuntu bookworm Release' heeft geen Release-bestand. N: Bijwerken van de pakketlijst uit een dergelijke pakketbron kan niet veilig gebeuren en is daarom standaard uitgezet. N: Zie de man-pagina apt-secure(8) voor details over het aanmaken van een pakketbron en over de configuratie langs gebruikerskant. E: De pakketbron 'https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu bookworm Release' heeft geen Release-bestand. N: Bijwerken van de pakketlijst uit een dergelijke pakketbron kan niet veilig gebeuren en is daarom standaard uitgezet. N: Zie de man-pagina apt-secure(8) voor details over het aanmaken van een pakketbron en over de configuratie langs gebruikerskant. Do you use R58? Let's help each other! Bas

Hello people, Half a year ago I flashed Armbian to to Mekotronics R58 plastic box, which was then an unofficial version. It's been on the shelf a while. Now I see new Armbian versions for download. I plugged in my device and did an update/upgrade. See Neofetch result below. My question is: is there any reason to completely flash the new version? Or am I already fine? It seems kernal versions are the same! Everything works fine and looks awesome including RealVNC for which I had some work to do. Therefore I am a bit reluctant to ditch the current version. Couple of minor issues I have are can't get Samba working and boot from SSD. Bas rock@r58 ◢🭫◣ -------- ◢◤ ◥◣ OS: Armbian (23.8.1) aarch64 ◢◤ ◥◣ OS Mod: AfterburnerMOD WIP ◢◤ ◥◣ Host: Hugsun RK3588 MINIPC LP4x V1.0 And ◢◤ 🭉🬹🬾 ◥◣ Kernel: 5.10.110-rockchip-rk3588 ◢◤ 🭅█🭐 ◥◣ Uptime: 3 mins ◢◤ ███ ◥◣ Packages: 1952 (dpkg), 24 (flatpak) ◢◤ 🭋███🭀 ◥◣ Shell: bash 5.1.16 ◢█◤ 🭅███🭐 ◥█◣ Resolution: 1920x1080 @ 60.00Hz ◢█◤ 🬏 🭄█████🭏 🬞 ◥█◣ DE: GNOME 42.9 ◢█◤ 🭋▌🭈🭆🭂███████🭍🭑🬽▐🭀 ◥█◣ WM: Mutter ◢█◤ 🭅███████████████🭐 ◥█◣ WM Theme: Adwaita ◢█◤ ███🭞🬎███████🬎🭓███ ◥█◣ Theme: Yaru-dark [GTK2/3] 🭮█◤ 🭒🭡🭘 🭣🮂🮅🭫🮅🮂🭘 🭣🭖🭝 ◥█🭬 Icons: ubuntu-mono-dark [GTK2/3] ◢█ █ █ █◣ Terminal: gnome-terminal ◢██◣ ◢🭡 🭖◣ ◢██◣ CPU: (8) @ 1.800GHz ◢████🭍🭑🬭🬭🬭🬭🬭🬭🭆🭂🭠🭗 🭢🭕🭍🭑🬭🬭🬭🬭🬭🬭🭆🭂████◣ Memory: 1696MiB / 3735MiB

I want to modife the dts file to support my device . But the dts file in source has some other file ,such as: 4 #include <dt-bindings/gpio/gpio.h> 5 #include <dt-bindings/leds/common.h> 6 #include <dt-bindings/pinctrl/rockchip.h> 7 #include <dt-bindings/soc/rockchip,vop2.h> 8 #include "rk3568.dtsi" and than I want to compile this dts file by dtc , has some error: Error: rk3568-hm.dts:4.1-9 syntax error FATAL ERROR: Unable to parse input tree so, how can I do that ? Could I compile the device tree separately? No compile all project or patch? thx u bro

Hello people I would like to share my experience with the Mekotronics R58 mini PC (RK3588 box, in my case with 8Gb RAM and 32Gb EMMC). For a more review like post see NicoD's video review here on the Armbian forum: he just reviewed the new MonkaArmbian on this board. I got the Download links from NicoD, and in the meantime they are also on the official Mekotronics support site. I just want to share my experiences with others. So first I played a bit with Adroid 12, that came with the box. Android is the best supported OS for this box, performance wise. Video and emulated gaming seems to work great also 4K. But I wanted Linux on it, so I installed Debian from Mekotronics site. It works great, at least everything on the board works great: Open Office, Firefox, video playback. But I had some issues installing new software (software like VSCOde, CodeBlocks++, Gimp would not install or it won't run properly). So I eagerly waited for something new and also contacted Mekotronics, but no real luck. Along comes MonkaBlyat the famous dev guy. He produced a personally developed Armbian (not official) that is quite stable. At first I thought performance suffered a bit compared with Mekotronics Debian, but I am glad I did not give up. First I installled Libre Office, it looks a bit crude and boxy and fonts were too smal. I then installed libreoffice-gtk3 BOOM problem solved, I then did a few updates and upgrades from terminal. Changed icon theme and suddenly the desktop transformed into a more Ubuntu like style and everything looks fantastic in dark mode, including LibreOffice, and works as fast as the original Debian from Mekotronics. It's GREAT! Open LibreSheet BOOM one second and you can start typing. Chromium: one second. Gimp: under 2 seconds. VSCode works great. Chromium youtube playback works great. It's so snappy I could really use this as a software development box and daily PC. Few minor issues: if I open the SSD window or the garbagebin window something something hangs and I can't open the screen again. Work-around: option open in new window. Personally I am very pleased to have a working Armbian now, even it it's not offical (yet) and a big thanks to MonkaBlyatt who made it possible! Bought my box for 120EUR and it's a lot more bang for buck than the RPI4 (5 times the performance, way better video, comes with built-in EMMC, wifi, charger and case, completely silent, no fan, yet it doesn't get hot so far). Next step for me is to get it headless with VNC server. Kind regards, Bas

What do I need to do to fix this error? Here is some information: root@orangepi5 ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy root@orangepi5 ~# root@orangepi5 ~# uname -a Linux orangepi5 5.10.110-rockchip-rk3588 #23.02.2 SMP Fri Feb 17 23:59:20 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux root@orangepi5 ~# root@orangepi5 ~# apt install -y bpfcc-tools libbpfcc-dev python3-bpfcc libbpfcc Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: ieee-data libclang-cpp11 libllvm11 python3-netaddr Suggested packages: ipython3 python-netaddr-docs The following NEW packages will be installed: bpfcc-tools ieee-data libbpfcc libbpfcc-dev libclang-cpp11 libllvm11 python3-bpfcc python3-netaddr 0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded. Need to get 30.1 MB of archives. After this operation, 136 MB of additional disk space will be used. Get:1 http://ports.ubuntu.com jammy/universe arm64 libllvm11 arm64 1:11.1.0-6 [17.2 MB] Get:2 http://ports.ubuntu.com jammy/universe arm64 libclang-cpp11 arm64 1:11.1.0-6 [9,149 kB] Get:3 http://ports.ubuntu.com jammy/universe arm64 libbpfcc arm64 0.18.0+ds-2 [599 kB] Get:4 http://ports.ubuntu.com jammy/universe arm64 python3-bpfcc all 0.18.0+ds-2 [34.6 kB] Get:5 http://ports.ubuntu.com jammy/main arm64 ieee-data all 20210605.1 [1,887 kB] Get:6 http://ports.ubuntu.com jammy/main arm64 python3-netaddr all 0.8.0-2 [309 kB] Get:7 http://ports.ubuntu.com jammy/universe arm64 bpfcc-tools all 0.18.0+ds-2 [627 kB] Get:8 http://ports.ubuntu.com jammy/universe arm64 libbpfcc-dev arm64 0.18.0+ds-2 [325 kB] Fetched 30.1 MB in 9s (3,363 kB/s) Selecting previously unselected package libllvm11:arm64. (Reading database ... 97548 files and directories currently installed.) Preparing to unpack .../0-libllvm11_1%3a11.1.0-6_arm64.deb ... Unpacking libllvm11:arm64 (1:11.1.0-6) ... Selecting previously unselected package libclang-cpp11. Preparing to unpack .../1-libclang-cpp11_1%3a11.1.0-6_arm64.deb ... Unpacking libclang-cpp11 (1:11.1.0-6) ... Selecting previously unselected package libbpfcc. Preparing to unpack .../2-libbpfcc_0.18.0+ds-2_arm64.deb ... Unpacking libbpfcc (0.18.0+ds-2) ... Selecting previously unselected package python3-bpfcc. Preparing to unpack .../3-python3-bpfcc_0.18.0+ds-2_all.deb ... Unpacking python3-bpfcc (0.18.0+ds-2) ... Selecting previously unselected package ieee-data. Preparing to unpack .../4-ieee-data_20210605.1_all.deb ... Unpacking ieee-data (20210605.1) ... Selecting previously unselected package python3-netaddr. Preparing to unpack .../5-python3-netaddr_0.8.0-2_all.deb ... Unpacking python3-netaddr (0.8.0-2) ... Selecting previously unselected package bpfcc-tools. Preparing to unpack .../6-bpfcc-tools_0.18.0+ds-2_all.deb ... Unpacking bpfcc-tools (0.18.0+ds-2) ... Selecting previously unselected package libbpfcc-dev. Preparing to unpack .../7-libbpfcc-dev_0.18.0+ds-2_arm64.deb ... Unpacking libbpfcc-dev (0.18.0+ds-2) ... Setting up libllvm11:arm64 (1:11.1.0-6) ... Setting up ieee-data (20210605.1) ... Setting up libclang-cpp11 (1:11.1.0-6) ... Setting up python3-netaddr (0.8.0-2) ... Setting up libbpfcc (0.18.0+ds-2) ... Setting up python3-bpfcc (0.18.0+ds-2) ... Setting up bpfcc-tools (0.18.0+ds-2) ... Setting up libbpfcc-dev (0.18.0+ds-2) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for libc-bin (2.35-0ubuntu3.1) ... root@orangepi5 ~# root@orangepi5 ~# execsnoop-bpfcc create_probe_event: open(/sys/kernel/debug/tracing/kprobe_events): No such file or directory Traceback (most recent call last): File "/usr/sbin/execsnoop-bpfcc", line 229, in <module> b.attach_kprobe(event=execve_fnname, fn_name="syscall__execve") File "/usr/lib/python3/dist-packages/bcc/__init__.py", line 683, in attach_kprobe raise Exception("Failed to attach BPF program %s to kprobe %s" % Exception: Failed to attach BPF program b'syscall__execve' to kprobe b'__arm64_sys_execve' root@orangepi5 ~# root@orangepi5 ~# ls /sys/kernel/debug/tracing available_events buffer_total_size_kb error_log options saved_cmdlines_size set_ftrace_filter set_graph_notrace trace_marker_raw tracing_thresh available_filter_functions current_tracer events per_cpu saved_tgids set_ftrace_notrace timestamp_mode trace_options uprobe_events available_tracers dynamic_events free_buffer printk_formats set_event set_ftrace_notrace_pid trace trace_pipe uprobe_profile buffer_percent dyn_ftrace_total_info instances README set_event_notrace_pid set_ftrace_pid trace_clock tracing_cpumask buffer_size_kb enabled_functions max_graph_depth saved_cmdlines set_event_pid set_graph_function trace_marker tracing_on root@orangepi5 ~# root@orangepi5 ~# ls /sys/kernel/debug/tracing/kprobe_events ls: cannot access '/sys/kernel/debug/tracing/kprobe_events': No such file or directory root@orangepi5 ~#