All Activity

Compiled, flashed, uploaded. I got a running XFCE desktop and a working wifi applet. If you still have different results, I may provide a VPN endpoint and an SSH pubkey to log in to your machine. Here's my upload dir: HTH // Sven-Ola

[UPDATE] Manual Partition Strategy on RK322x (Kingston eMCP) - GPT Signature Error & TOS Anomaly Hi everyone, Following up on my struggle with the "Red LED" issue on this RK3228A box (Kingston eMCP). Since the Multitool wouldn't boot from the SD, I moved to a more aggressive approach using rkdeveloptool on macOS to flash Armbian images and the Multitool components directly to the internal storage. The Loader Struggle (Samsung vs. Kingston) I compiled rkdeveloptool on macOS and tested multiple loaders to initialize the RAM/Flash: • rk322x_loader_v1.10.256.bin • rk322x_loader_v1.11.253.bin • rk322x_loader_v1.10.238_256.bin None of them solved the SD boot issue. Interestingly, they identify my flash as SAMSUNG, even though the physical chip is Kingston: Flash Info: Manufacturer: SAMSUNG, value=00 Flash Size: 7216 MB | Block Size: 512 KB | Page Size: 2 KB Tested Images & Offsets (Direct Flashing via rkdeveloptool) • Armbian Community (6.1.62/Minimal 6.18.7): Tested 0x0 and 0x8000. • LibreELEC (10.0, 11 and 12): Tested 0x0 and 0x8000. • Multitool (v1.11 & Standard): Tested 0x0 and 0x2000. • Educabox (Legacy 4.4.194 / NAND): Tested 0x0. All attempts resulted in "GPT signature wrong", likely because the Secure Boot/Trust OS expects the Android rkparameter structure instead of a standard GPT. When I then changed the GPT table in parameters.txt, it sometimes wouldn't even give me a signal via serial. The Strategy: Manual Image Construction (Partition Replacement) Since full image flashing failed, I followed the "Partition Replacement" strategy to manually construct the layout. I read about it in a post titled long story LINUX on rk3229 rockchip by @fabiobassa: manually constructing the partition layout to satisfy the Bootrom's legacy requirements while injecting Armbian components into specific offsets. The parameter.txt Modification (The Key Step): The root cause of the "GPT signature wrong" error was the mismatch between the Android partition table expected by the device's Secure Boot/Trust OS and the standard GPT layout of Linux images. Original State: The stock parameter.txt defined over 12 Android-specific partitions (cache, recovery, kpanic, metadata, etc.), complicating the boot process. Modified State: I manually edited parameter.txt to consolidate all user partitions into a simplified Linux layout. I removed the Android clutter and defined a single large system partition for the RootFS. New Layout Definition: mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00004000@0x00004000(trust),0x00007800@0x0000A800(resource),0x00006000@0x00012000(kernel),0x00006000@0x00018000(boot),-@0x00028000(system) Component Preparation (Where the files came from) I did not use generic loaders for the boot partition. Instead, I extracted and repackaged each component on macOS to fit this new map: U-Boot (uboot @ 0x2000): I extracted the original bootloader from my device backup using dd to preserve compatibility. Command: dd if=backup_original.img of=uboot_extraido.img skip=8192 count=8192 System/RootFS (system @ 0x28000): I extracted the raw EXT4 Linux partition from the Armbian image. Command: dd if=Armbian...minimal.img of=particao_linux.ext4 skip=8192 count=2269184 Kernel (kernel @ 0x12000): Extracted vmlinuz-6.18.7-rockchip from the Armbian image and wrapped it with Rockchip headers using mkimage. Command: mkimage -A arm -O linux -T kernel -C none -a 0x60408000 -e 0x60408000 -n "Linux" -d vmlinuz... kernel.img Ramdisk (boot @ 0x18000): Extracted uInitrd from Armbian and wrapped it as a ramdisk image. Command: mkimage -A arm -O linux -T ramdisk ... -d uInitrd... boot.img Resource/DTB (resource @ 0xA800): I used the specific Device Tree Blob for this box (rk322x-box.dtb) extracted from the Armbian build and renamed it to resource.img. Afterwards, I tested with resource-linux which was linked in the original discussion, but still did not have success. The Flashing Sequence & Current Anomaly With the files prepared and the partition map redefined, I flashed the components using rkdeveloptool. The Sequence: Initialize: db rk322x_loader_v1.10.238_256.bin Partition Map: prm parameter.txt (Injecting the simplified layout). Flash Images: wl 0x2000 uboot_extraido.img (My extracted U-Boot) wl 0x4000 trust_with_ta_ga4fd2d1.img wl 0xA800 resources-linux.img (The DTB) wl 0x12000 kernel.img wl 0x18000 boot.img wl 0x28000 particao_linux.ext4 (The Armbian RootFS) The Result (The "TOS" Anomaly): The write process returns 100% Success, but the device fails to boot. The serial log (1.5Mbps) reveals a loop with a specific error: GPT 0x63337df8 signature is wrong recovery gpt fail! tag:LOADER error,addr:0x2000 hdr 633377e0 + 0x0:0x20534f54,0x20202020... The Anomaly: The error points to address 0x2000. The header read back is 0x20534f54, which is ASCII for "TOS " (Trust OS). It seems the Bootrom or the initial loader is hardcoded to expect the Trust Image at 0x2000, but my parameter.txt (and the standard Rockchip layout) places U-Boot at 0x2000 and Trust at 0x4000. Even when I flash my extracted U-Boot there, the system seems to be looking for a Trust signature. At this point, I don't know what I'm doing anymore and have spent around 20 hours in this project testing things. Any guidance on how to proceed from more experienced devs such as @fabiobassa, @Harleyyyu and @jock would be greatly appreciated to save my sleepless nights. Thanks for reading.

Hello @Malay! Same for you: cannot reproduce. Can you rebuild with SKIP_ARMBIAN_REPO=yes? This builds a little longer but skips cached stuff. Alternatively, rm -r ./cache from the build dir. To help with this, I will start the following commands on my PC and upload the results later to https://privat-in.de/ (Download section). LG // Sven-Ola

Hello @maxsub, we are talking about git log --oneline -1 which says 613737fab. The post_family_tweaks_bsp__orangepirv2_wifi() from above is exactly what's in there. If you run you should get on the board Can you please elaborate on the "got it"? TIA // Sven-Ola

Was running Ubuntu Noble and mpv-0.37 is from Noble-repo. On Trixie the mpv is version 0.40 (Debian Trixie repo) which somehow does not seem work with the ffmpeg-v4l2request. Are you running Trixie or Bookworn? Is your device Opi5-Plus or RK3588? So far on my Opi5-Plus no luck with 10Bit Hevc or any 10Bit video on mpv with mainline kernel.

I confirm that when building an image with the Edge 6.18 kernel, WiFi does not work. Also, when building an image with the Xfce desktop, the image is approximately 3 GB (it should be more than 4 GB), but it is not there, only the command line works.

Hi everyone, I have rock 5c with PWM fan. I want to control the fan speed manually. Running on Armbian 25.11.1 Noble. Sorry if its obvious I am newbie to this

I was surprised when mine played H265 10 bit. I thought I'd read somewhere v4l2 was limited to 8 bit. Obviously that was incorrect.

I'm very new to Armbian so I could be off track here but I noticed your running MPV version 37. When I ran the instructions for the first time I already had mpv installed (version 40 or something) so it didn't get updated. I ended up uninstalling MPV and running the instructions again. Now I have version 35.1 which fixed the drm_prime errors for me. The version difference could be because you are on 26.2 of Armbian and I'm on 25.05, I haven't got my head around all the different versions of things yet. Maybe try uninstalling MPV and trying the commands again and see what version it gives you.

This video should give you the information you need for setting up a usb debug uart connection:

@Nick A I am not sure whether you can help release some versions of image with ufs supported, as I tried to compile from source with @chainsx git, but not once successful. If you can release the relevant versions of ufs support image? Thanks

Got it! But this DKMS should be loaded by the build: function post_family_tweaks_bsp__orangepirv2_wifi() { display_alert "$BOARD" "Force load bmcdhd wireless" "info" run_host_command_logged mkdir -pv "${destination}"/etc/modules-load.d run_host_command_logged echo "bcmdhd" > "${destination}"/etc/modules-load.d/${BOARD}.conf }

I record a video of the board to see if with this info I don't need to read the outputs via uart. Can't find how to up images. What uart cable I need ? Can you post one from aliexpress. Thanks.

Hu? In difference to Spacemit 6.6.99, the 6.18 kernel has no bcmdhd included. For that reason I put in an adapted version of bcmdhd in a DKMS, installed via a source deb from my repo on codeberg.org/sven-ola. B/c DKMS needs a compiler on the board, the edge image is larger than current image. Code quality of bcmdhd is questionable so it probably never make it into the official Linux tree, but it works (at least on my board with my image). HTH // Sven-Ola

@Nick A Hi Nick, how are you? I have a motherboard identical to the one in the photo you posted, with an AXP313A. I tried the image you recommended, but the Wi-Fi didn't work. Could you give me any advice?

I don't have the usb that you mention. I open the console to clean the fan and I did photos of board but I don' t remember where I place the photos. Give me five minutes to put here photos I need to unmount the box.

Update on NanoPi M4v2 ... I pulled the most recent Armbian build, and manually ran the build for the M4v2, and it fails on kernel patch "general-gpio-driver-no-sleep". See pastebin at https://paste.armbian.com/puvorasuco for failed build. Checking upstream at https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git, it looks like branch 6.18.y already has the subject patch, and was pushed today. Since both the rockchip and rockchip64 families use mainline kernel, I just submitted a PR that kills that patch for both. See https://github.com/armbian/build/pull/9368.

Hi, It seems that the Odroid N2 armbian builds do not support using armbianEnv.txt AT ALL. See this forum entry from 2021: I am facing the same issue with Armbian 26.2.1 Minimal dmesg shows the following: [ 0.000000] Kernel command line: root=UUID=c8906fe5-129c-4388-840c-58c43c541176 rootwait rootfstype=ext4 splash=verbose console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=001c9d62-01 libata.force=noncq usb-storage.quirks= cgroup_enable=memory with the following in /boot/armbianEnv.txt: verbosity=1 console=both overlay_prefix=meson rootdev=UUID=c8906fe5-129c-4388-840c-58c43c541176 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I also tried adding extraargs= but nothing ends up in the command line. The old forum entry does mention editing the boot.ini to manually append it to bootargs, however I am not sure where that is located in the image and how to modify it. I tried both booting with petitboot and without, both show the same issue.

On RV2 with the edge branch WiFi does not work.

Armbian_26.2.1_Rock-3a_trixie_current_6.18.8_minimal.img.xz (ROCK3A) - system has NVME inserted and SATA M.2 E-key adaptor where HDD is connected to - SPI has Armbian legacy U-Boot, but that is skipped as SD-card with new image is inserted - further only power, ethernet and serial console cable connected: 1st boot and user creation all fine - network up, WAN IP shown - NVME is available (but OS is running from SD-card for the test) - SATA is not available as not supported mainline based kernel (and needs adding overlay manually when vendor kernel) - reboot does not reboot (but 'echo 1 > /proc/sys/kernel/sysrq ; echo b > /proc/sysrq-trigger' works) - also poweroff is only shutdown, no powerdown (and HDD keeps also spinning)

At this point you seem to have done everything properly. The next step would be to find the uart connection point on you board and hook up a usb-uart reader so you can see the debug output from uboot to see what is happening.

That is enabling multiboot (what enabled either Armbian or android to boot. I'm going through with you all the basics that you didn't mention in your original post (and that others often forget to do), to eliminate all the basic things. You say "maintain it", but you shouldn't hold that button too long, a few seconds (10 at most is all you need). Holding too long will not work.

Armbian_26.2.1_Bananapi_trixie_current_6.12.68_minimal.img.xz (Bananapi M1) - only power, ethernet and serial console cable connected: 1st boot and user creation all fine - network up, WAN IP shown - then connecting a SATA SSD ('hotplug'), pops up in dmesg, so recognized OK

I follow this instructions The reset button in the case of my box is inside Av connection, I already boot the images with press the button and maintain IT. The result is a screen with HKSERIES screen, I can wait one hour nothing happens only the image. A video to you see that I press the reset multiboot button. Thanks.

some things are happening at the bleeding edge https://lore.kernel.org/u-boot/?q=a733 pay attention to u-boot, the most important thing are dram controller, pmic, mmc/sd etc then of course kernel as well https://lore.kernel.org/linux-sunxi/?q=a733