Active threads

The most current download images for Helios64 are now all provided with linux 6.18.xx. I downloaded a minimal image and checked the dtb: it would not appear to contain the opp-microvolt patch that made helios64 finally stable. So for the ones who have stability issues again on Helios64, I attached the patched dtb compiled for linux 6.18.18 (and for more recent 6.18.xx too) using the exact same opp-microvolt values as in the previous dtb versions I compiled for linux 6.6 and 6.12. In order to apply it, simply unzip it, copy it into the proper location, update initramfs and reboot: # you may upgrade your linux kernel to 6.18.18 or a more recent one first (from beta.armbian.com/pool/main/l/): wget https://beta.armbian.com/pool/main/l/linux-6.18.18/linux-image-current-rockchip64_26.2.0-trunk.607_arm64__6.18.18-S3318-Dedd0-Pa6b8-C8acb-H444d-HK01ba-Vc222-Bdc65-R448a.deb wget https://beta.armbian.com/pool/main/l/linux-dtb-current-rockchip64/linux-dtb-current-rockchip64_26.2.0-trunk.607_arm64__6.18.18-S3318-Dedd0-Pa6b8-C8acb-H444d-HK01ba-Vc222-Bdc65-R448a.deb wget https://beta.armbian.com/pool/main/l/linux-headers-current-rockchip64/linux-headers-current-rockchip64_26.2.0-trunk.607_arm64__6.18.18-S3318-Dedd0-Pa6b8-C8acb-H444d-HK01ba-Vc222-Bdc65-R448a.deb dpkg -i linux* # install the dtb with the opp-microvolt patch: unzip rk3399-kobol-helios64.dtb-6.18.18-opp.zip cp rk3399-kobol-helios64.dtb-6.18.18-opp /boot/dtb/rockchip/rk3399-kobol-helios64.dtb update-initramfs -u reboot rk3399-kobol-helios64.dtb-6.18.18-opp.zip

Another attempt, again check https://testing.armbian.de/r4s/?C=M&O=D for most recent debs. This time adding an artificial bus scan delay into the r4s dts. Another poke in the dark but perhaps...

See inline comments. Dirty SPI may cause this but without logs from serial console this is just a guess

Is there mainline support for a7a now

I will try downgrading u-boot next once I find the older package somewhere. Kernel does not seem to be the cause given that it has been working fine with both my own build 6.6.122 and 6.6.128 before and rolling back not helping. New device is something I had on my mind for a while. But given the RAM and SSD prices these days, I do not really want to overspend. Not to mention that the SBC landscape has not been that great lately when it comes to compact NAS offerings. HC4 is five years old at this point. Many even recommend N100 but this is a whole different size category.

hi all. any hints to merge olimex imx8 board and compile armbian kernel 6.x and deb12 ?

hello ,my box is mortal t1 2g8rom and motherboard show mortal t2 v2.0 it's broken and i wanna make linux boot what's the most version to be able for my box

I don't know if it's useful, but folks have been attaching external GPUs to low power boards for a while. My personal favorite was sacking and desoldering a USB3 controller to reuse it's PCIE lane: https://mloduchowski.com/raspberry-pi-4-b-pci-express/ Others have run into the same BAR limitation you noted: https://www.jeffgeerling.com/blog/2020/external-gpus-and-raspberry-pi-compute-module-4/ From a practical perspective, I'm not sure how many folks would be interested in discrete GPUs, as I'm not sure these sorts of boards would have the CPU or PCIE lanes to really make use of that extra horsepower. Most would get a dedicated embedded system, or a bespoke NVidia setup. For what it's worth, I ran into an issue where the kernel was too big for u-boot to boot it, and would just throw a synchronous abort and reset. The difference between working and not working was 7 MB.

Good morning I have big problem I have tv box Transpeed-H616_ I update with orange pi But i can't back to old firmware

Hi Armbian_25.5.1_Rpi4b_bookworm_current_6.12.28 broken after last upgrade. I run apt upgrade which installed kernel 6.18.10. It breaks ZFS. Provided ZFS version, 2.3.2, supports kernels up to 6.14. Don't forget a snapshot before "apt upgrade" 🙂 Regards, Chris

what board did you replace it with?

I have a T9 2017 rk3328 box running Ubuntu xcfe many hours for downloading. There are not problems but xcfe displays lunchs himself many times and i have to close 20 or more instances of this application when checking the progress. Box is not crashed by this funny clonning. is it possible to avoid this? p.d. la test trunk

Hi there! I've got 2 of these industrial android boards (s2809-mb-v1.8c) and I've been trying to get armbian running on the. For a while but so far no success. These 2 boards were sold as being tinker boards but I believe that they are EVBs instead. Here are some photos: https://ibb.co/4wTm20s9 https://ibb.co/Z6PfvZCr https://ibb.co/HTFWLKTS I have also managed to find a link to the Chinese seller: https://m.globalsources.com/product/quad-core-board_1195354789f.htm Debug method: UART2 (because they don't have HDMI only LVDS and EDP ports) PMIC: RK808 So far trying to run them on the latest armbian 26 and 25 gets stuck at Starting Kernel. Ive managed to find a version 20 for the miqi board that loads kernel and boots into armbian bullseye but stops before login using a single core only and only 512mb of ram, anything beyond that just never starts the kernel using tinker and tinker-s DTBs. I have also managed to get a full dump of a current android image that is running correctly on one of the board and extracted: loader, kernel, dtb from the partitions. Extracting the images was painful cause none of the rk (linux rkdeveloptool, rkdev and rkandroidtool) methods worked.. only through uboot so that was painful to get 16mb parts from some of the images and join them all. Has anyone ever encountered any of these boards? Maybe anyone has an idea on how to get them up and running? Thanks for your help and sorry if this post is under the incorrect forum.

My ROCK3A has a jumper option to disable SPI clock, so whole SPI will be bypassed and only SD-card works then. I power with fixed 12V (USB-C pigtail). I do not know now what version the board/PCB is. AFAIR from Radxa docs other versions have no such jumper. Maybe you already tried/know all this. Maybe wipe the SPI via rkdevelop. W.r.t. Rockchip SBC's (various brands) I am a bit confused what boot-device prefence/priority is. From schematics I saw it depends on a resistor value, but many boards in the world and endless resistor values possible.

@guy cal Igor just fixed that: https://github.com/armbian/configng/pull/765

Hi all, For whom who are looking for the image to be installed on this box: I have the same mxq box with H3 SoC and I flashed the Tritium H3 (libre) armbian image successfully and playing with it for year. Wifi not working, not sure about Bluetooth because I don't use them at all. Currently it works as my cups printer server for my brother usb printer.

This device is not yet fully compatible with the mainline Linux kernel. Realtek USB 2.5GbE adapters, in particular, are known to have issues when used over USB 3 on these devices. The vendor-provided kernel reportedly offers better tuning for these adapters, though it is still not entirely flawless.

As amazingfate (the Armbian dev for this device) clearly stated on the forum: cellular and camera are not working, only display, touch, wifi, and bluetooth are functional—so it won't replace your phone OS for calls and texts

Can confirm. S905X5M is a different beast than the S905X. If there's interest, I can start another thread with an image and status, once this is somewhat more stable. Currently booting, but not without some debug console interaction on power up. In the meantime, code's up at https://github.com/tparys/build/tree/odroidc5 if anyone wants to go poking

Hello, I hope you don't have any problem. Maybe me and my brother have defective or more unstable helios64 than you. Only thing I can say that Prahal share here the specifics files rk3399-kobol-helios64.dtb-6.XX.xx-L2-hs400-opp in this forum since two years ago my helios64 and my brother's helios64 work stable only with it. I back to 6.12.58 Kernel with rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp file and freeze firmware/kernel with armbian-config.

I am having issues with eMMC detection… The kernel does not detect the eMMC, but apparently U-Boot does. Attached are images.

Hi, I am trying out Armbian 26.2.0-trunk.592 nightly (trixie) on a Radxa Rock PI 4b+ The community supported image boots fine and it is no problem to install Armbian on the on-board eMMC flash, but the installed NVMe SSD on PCIi is no recognised. It looks like the whole PCIe bus is not initialised properly during boot. in the kernel log I see: [ 0.062396] /pcie@f8000000: Fixed dependency cycle(s) with /pcie@f8000000/interrupt-controller [ 2.160749] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 2.160771] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 2.160779] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000 [ 2.869988] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 2.870032] rockchip-pcie f8000000.pcie: probe with driver rockchip-pcie failed with error -110 I have searched for quite a while now but could not really find a solution for this. It seems there have been similar problems reported regarding other SOCs using the same chip and I even see patches being proposed (not sure whether the PR has been merged) though at this moment I cannot really see any solution available to this yet. Did anyone else encounter this and is there any fix or workaround for this? I installed the Homeassistant OS image for this board (maintained here: https://github.com/citruz/haos-rockpi), which does not have this issue and allowed me to install and boot from the NVMe drive without any problem. Is anyone aware of the differences in the upstream linux kernel and the one that Armbian ships w.r.t. patches that could make a difference here? regards, Frederik

Hi Does anyone have any advice on how to get Armbian running on this device. I am comeplety new to Armbian. Is there a generic Allwinner H6 image that I need to modify? Any advice pls? Thanks

Hello, this is my first message here: I want to thank the community for the work done so far, and for allowing to keep functional old devices which would otherwise become (nasty) garbage. Now, I tried to install Armbian on a Wetek Play 2 (Amlogic S905), buit now the box is not booting. I would be grateful if I could get some help, or at least clarification about what happened. Here is what I did so far: Download the image `Armbian_community_26.2.0-trunk.493_Aml-s9xx-box_trixie_current_6.18.13_minimal.img.xz`, and write it on a SD card. Boot from the SD card, by holding the power button when inserting the power cable. The box booted fine. Log in via SSH, and configure the installation. Back-up the full emmc with `dd if=/dev/mmcblk1 of=/mnt/backup/wetek_play2_android_emmc.img bs=4M`. The emmc had the original Android system (with more stuff installed, but I guess the most important part are the first 4 MB...) Run the `/root/install-aml` script. Power-off When powering on again, the box did not boot. I tried to boot from SD by holding the power button, but it did not work. So at this point my questions are: What can I do to recover the situation? What did I made wrong? As additional context, in the past I had also successfully booted LibreELEC from SD, although the last boot before switching to Armbian was to Android. Thanks for your help UPDATE: OK, I think I found the culprit: I overseen the quite important statement "Note: It is not possible to install into emmc on boxes with the s905 cpu". Great.

You may be experiencing the same issue that other people are encountering: https://github.com/tauri-apps/tauri/issues/12787 @Giunti Can you confirm that this is the same issue as the one reported above? Thank you.