All Activity

Managed to edit the MMC by booting from USB, mounting the MMC. The R2S is now up and running, with the mainline armbian. However, the CPU still spins in the kernel and generates a lot of heat. Idle load average is 2.02.

The problem was in the dtb which comes with the Armbian image, added the fix, now it is working as expected. Attaching the fixed dtb file, just replace it with this one and enjoy! Rename the attached file to k3-am67a-beagley-ai.dtb and copy it to your /boot/dtb/ti/ path and reboot. k3-am67a-beagley-ai.dtb_armbian_fixed

I ran into some trouble. I managed to boot the USB and then used armbian-config to flash the image to internal eMMC. However the script copied the USB UUID instead of the MMC UUID so now the MMC won't boot. I need to edit the MMC and change the UUID.

Thanks for the script @sven-ola. I got the R2S booted from USB. I had to tweak a few minor things. Where did you get the Ubuntu boot.cmd? usb start setenv devtype usb setenv devnum 0:1 setenv prefix boot/ setenv fdtfile dtb-6.6.99-legacy-spacemit/spacemit/x1_orangepi-r2s.dtb #setenv fdtfile spacemit/k1-orangepi-rv2.dtb setenv bootargs "console=ttyS0,115200 root=/dev/sda1" ls ${devtype} ${devnum} ${prefix} load ${devtype} ${devnum} ${ramdisk_addr_r} ${prefix}uInitrd load ${devtype} ${devnum} ${kernel_addr_r} ${prefix}Image load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}/${fdtfile} booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}

Wrote a script to change an Armbian desktop system for Spacemit GPU drivers and Chromium (attached). Tested with the two pre-installed Gnome images on my site (see https://privat-in.de/ goto Downloads). Some testing results: Spacemit offers Ubuntu noble and Debian trixie *.deb from their Bianbu site http://archive.spacemit.com/ For us, main diff here is Noble=chromium (Spacemit customized version) and Trixie=chromium-browser-stable (older and not customized). We need Wayland for the GPU, X11 does not work. With lightdm, each Wayland login freezes. Thus use gdm3. With gdm3, Xfce4 exits immediately, Kde-plasma shows drawing errors, Cinnamon works to some extend, e.g has video placing and window sizing problems. So the only useable GUI is Gnome. With Chromium under Gnome we can watch Youtube with 1080p (video / audio sync should stablize after some seconds). When doing this, CPU temperature is up to 75°C from the ususal 65°C, power is 4 Watts from the ususal 3 Watts. Script should work on other Spacemit K1 boards as well. If you miss some package from Bianbu, write a wishlist or make an PR on https://codeberg.org/sven-ola/spacemit-mirror spacemit-gpu-addon.sh

Thanks, gabriel_altoe for your advice. I'm abble to boot from the image you pointed. I have the same board. I success boot with minimal image too from this link: https://github.com/sicXnull/armbian-build/releases/download/v24.8.0-trunk.425/Armbian-unofficial_26.02.0-trunk_X96q-v1-3_bookworm_current_6.12.64_minimal.img.xz

Hello! I'll take the topic a little away from the main direction, but the question will be in the framework of game testing: is running games through the ps2 emulator (aethersx2) a dead end? When you turn on the MALI-610 on aethersx2 (need for speed underground), the video loads well (60fps, 100%), but there is braking on the screensavers, the sound also stutters and the control is noticeably delayed. When switching to Open GL, the screensavers load quickly, the sound does not stutter, the controls are clear without delay, but the video goes with slight drawdowns, the picture and sound twitch, but very rarely (while the video has an average of 55-60 fps with a percentage of 70-90%).I tested everything on the armbian 26 installed on the sd.

@xiboliyadongtu How was it going?

Addon for @maxsub and the bricked R2S: I tested USB boot from u-boot cmdline on my RV2, and it works. Here's how: usb start setenv devtype usb setenv devnum 0:1 setenv prefix boot/ #setenv fdtfile spacemit/x1_orangepi-r2s.dtb setenv fdtfile spacemit/k1-orangepi-rv2.dtb setenv bootargs "console=ttyS0,115200 root=/dev/sda1" ls ${devtype} ${devnum} ${prefix} load ${devtype} ${devnum} ${ramdisk_addr_r} ${prefix}uInitrd load ${devtype} ${devnum} ${kernel_addr_r} ${prefix}Image load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile} booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} In case you have a blank u-boot-env, here's mine attached // HTH printenv.cap

@maxsub You mean the boot.cmd (source for boot.scr) from the Xunlong Ubuntu image for R2S? I'll attach it below // HTH boot.cmd

OK, so that went reasonably fast and produced the 4 kernel debs. The linux-libc-dev-edge-rockchip64 didn't install due to conflict with the (current/stable) linux-libc-dev package - I think this is expected - but the rest of the kernel packages have been succesfully installed and the dkms error seems resolved.

Eh, I can try the 7.0 rc package and see how they behave, as long as it's 6.19 or later is fine. Thanks for the pointers.

No. edge will give you 7.0-rc3 since it was bumped recently. You can try to revert this commit to get 6.19. No guarantee it works, nor any support will be given. https://github.com/armbian/build/pull/9445

If I'm building the .deb file manually, is there a way to build with kernel 6.19 for the OrangePi5 ? Can I use the edge branch (instead of current) for this ? While I don't mind waiting for the package to build, if I can build the bsp/kernel/headers for 6.19 I can give it a try. EDITED for formatting.

Yes, they seem to be missing in repo. As a quick fix I'd suggest to use the build framework to create yourself a set of deb files containing all necessary packages code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh BOARD=orangepi5 BRANCH=current kernel code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } copy the packages from output/debs to your board and use dpkg to install them.

Hello, I have installed the minimal Trixie based image for Orange Pi5 (the image named Armbian_26.2.1_Orangepi5_trixie_current_6.18.8_minimal) and then attempted to build an out-of-tree kernel module. Having installed dkms and build-essentials, plus the kernel headers through armbian-config, I found the headers package hasn't been fully set-up, the build symlink in /lib/modules/<KVER> is missing and dkms complains that the kernel headers for the kernel are not installed. The kernel headers are installed though, but it looks like they're from a previous release (25.11.2 instead of 26.2.1). # dpkg -l | grep rockchip ii linux-dtb-current-rockchip64 26.2.1 arm64 Armbian Linux current DTBs in /boot/dtb-6.18.8-current-rockchip64 ii linux-headers-current-rockchip64 25.11.2 arm64 Armbian Linux current headers 6.12.58-current-rockchip64 ii linux-image-current-rockchip64 26.2.1 arm64 Armbian Linux current kernel image 6.18.8-current-rockchip64 It the headers package still pending packaging ? Shouldn't armbian-config provide an error in this case and not install the old kernel headers ? EDIT: armbianmonitor ouput - https://paste.armbian.com/oliyalebeq

Hello everyone, I'm trying to locate a specific older Armbian build for an RK3318 TV box and hoping someone in the community might have it archived. I'm looking for: Version: Armbian 22.05.1 (or similar from that era) Kernel: Legacy 4.4.213 Base: Debian Buster Desktop: XFCE (or even a CLI version is fine) The original download link from users.armbian.com/balbes150/ is now a 404. I understand this is a very old "Community Maintained" build and that RK3318 support has moved to newer kernels . I'm specifically seeking this kernel version for a project. If anyone has this image file or a similar legacy build (kernel 4.4.x) for the RK3318 stashed away, could you please share it or point me to an alternative source? Any help would be greatly appreciated! Hardware: (e.g., H96 Max RK3318 - please specify your exact box model) Thank you

Thank you. R2S has a built in eMMC and USB. The only way to get a new image is to boot from USB but it seems like I have to manually load the image in u-boot. Is the u-boot script (boot.txt) for the build somewhere in GitHub?

Have you tried all of the gxm dtb files? Per the instructions (https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus)

@maxsub I was not even aware, that boot from USB is a thing. The RV2 boots from SD via extlinux, here is the relevant uboot output. HTH [ 3.458] Retrieving file: /boot/extlinux/extlinux.conf [ 3.490] 1: Armbian-unofficial [ 3.490] Retrieving file: /boot/uInitrd [ 4.772] Retrieving file: /boot/Image [ 5.767] append: root=UUID=c79489b6-9fea-4a53-a334-d91a0f30843a earlycon=sbi console=tty1 console=ttyS0,115200 logleve l=1 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consol es [ 5.785] Retrieving file: /boot/dtb/spacemit/k1-orangepi-rv2.dtb [ 5.838] Uncompressing Kernel Image [ 6.218] Moving Image from 0x10000000 to 0x200000, end=2c90000 [ 6.245] ## Loading init Ramdisk from Legacy Image at 21000000 ... [ 6.248] Image Name: uInitrd [ 6.251] Image Type: RISC-V Linux RAMDisk Image (gzip compressed) [ 6.258] Data Size: 20347839 Bytes = 19.4 MiB [ 6.263] Load Address: 00000000 [ 6.266] Entry Point: 00000000 Verifying Checksum ... OK [ 6.363] ## Flattened Device Tree blob at 31000000 [ 6.365] Booting using the fdt blob at 0x31000000 [ 6.370] Loading Ramdisk to 7ca0b000, end 7dd72bbf ... OK [ 6.391] Loading Device Tree to 000000007c9eb000, end 000000007ca0a097 ... OK Starting kernel ...

i am trying to install armbian on a vorke z6 plus s912 amlogic box. As there is no S912 dtb, i tried using /dtb/amlogic/meson-gxm-t95z-plus.dtb with this iamge: Armbian_26.02.0_amlogic_s912-t95z-plus_trixie_6.18.15_server_2026.03.01.img.gz renamed u-boot-s905x-s912.bin to u-boot.ext After inserting and pressing the reset button, before applying power, i get into the recovery menu What dtb file or image can i use to get armbian running?

Depends on the image you are using. The image for 3 LTS should work for the 3 LTS. The image for the 3 (without lts) will not.

Without uart hard to tell.

I ran into a problem. Flashed the nightly build to the eMMC on the R2S and now it won’t boot from USB. I can see the usb drive in u-boot and kernel.img and dtb. What’s the default address to load the kernel and dtb on these boards? thank you.

I followed the instructions and have OpenGL ES 3 working now. I wasn't able to build Yamagi Quake 2 because of a version issue with one of the packages. I copied a build from the Muse Pi Pro and now I can run it at 1080p, and sometimes it even hits 60fps!