Active threads

You can find the dram config options here. https://elixir.bootlin.com/u-boot/v2025.07-rc2/source/arch/arm/mach-sunxi/Kconfig if DRAM_SUN50I_H616 config DRAM_SUNXI_DX_ODT hex "DRAM DX ODT parameter" help DX ODT value from vendor DRAM settings. config DRAM_SUNXI_DX_DRI hex "DRAM DX DRI parameter" help DX DRI value from vendor DRAM settings. config DRAM_SUNXI_CA_DRI hex "DRAM CA DRI parameter" help CA DRI value from vendor DRAM settings. config DRAM_SUNXI_ODT_EN hex "DRAM ODT EN parameter" default 0x1 help ODT EN value from vendor DRAM settings. config DRAM_SUNXI_TPR0 hex "DRAM TPR0 parameter" default 0x0 help TPR0 value from vendor DRAM settings. config DRAM_SUNXI_TPR2 hex "DRAM TPR2 parameter" default 0x0 help TPR2 value from vendor DRAM settings. config DRAM_SUNXI_TPR6 hex "DRAM TPR6 parameter" default 0x3300c080 help TPR6 value from vendor DRAM settings. config DRAM_SUNXI_TPR10 hex "DRAM TPR10 parameter" help TPR10 value from vendor DRAM settings. It tells which features should be configured, like write leveling, read calibration, etc. config DRAM_SUNXI_TPR11 hex "DRAM TPR11 parameter" default 0x0 help TPR11 value from vendor DRAM settings. config DRAM_SUNXI_TPR12 hex "DRAM TPR12 parameter" default 0x0 help TPR12 value from vendor DRAM settings.

I didn't try to replicate the problem in x86... but I compiled the latest labwc 0.9.0, in Orange Pi Zero 3 with Bookworm, and this problem does not show up

after last rolling update wifi has gone... but bluetooth is fine... apt list --upgradable armbian-bsp-cli-bananapim4zero-current/noble 25.8.0-trunk.442 arm64 [upgradable from: 25.8.0-trunk.428] armbian-firmware/noble,noble 25.8.0-trunk.442 all [upgradable from: 25.8.0-trunk.428] .... linux-dtb-current-sunxi64/noble 25.8.0-trunk.442 arm64 [upgradable from: 25.8.0-trunk.428] linux-image-current-sunxi64/noble 25.8.0-trunk.442 arm64 [upgradable from: 25.8.0-trunk.428] how to fix this?

Auy idea why my electron app crashes running on branch edge release noble custom build with below error [2440:0730/102955.112990:ERROR:cert_issuer_source_aia.cc(35)] Error parsing cert retrieved from AIA (as DER): ERROR: Failed parsing Certificate SEQUENCE ERROR: Failed parsing Certificate [2510:0730/102955.113685:ERROR:ssl_client_socket_impl.cc(877)] handshake failed; returned -1, SSL error code 1, net_error -202 [2440:0730/104601.001405:ERROR:network_service_instance_impl.cc(612)] Network service crashed, restarting service. [2440:0730/104601.014376:ERROR:zygote_communication_linux.cc(296)] Failed to send GetTerminationStatus message to zygote [2440:0730/104601.020244:ERROR:zygote_communication_linux.cc(296)] Failed to send GetTerminationStatus message to zygote [2440:0730/104601.041426:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [2440:0730/104601.042506:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [2440:0730/104601.043109:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [2440:0730/104601.043662:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [2440:0730/104601.044196:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [2440:0730/104601.045030:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [2440:0730/104601.046123:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [2440:0730/104601.046765:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [2440:0730/104601.047349:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [2440:0730/104601.047374:FATAL:gpu_data_manager_impl_private.cc(420)] GPU process isn't usable. Goodbye.

Knowing this means your options are to return the case+NVMe back to shop. Or do a cross-check; case with other NVME and NVME in M.2 slot of some other computer. But this is a typical Raspberry problem; storage via USB (SATA or NVME nowadays) easily leads to trouble. Mostly power related, but also many just the chipset in the adaptor. In case of Pi5, you could get an NVMe adaptor board, but also that is not always working out-of-the box. Only if you buy RPi adaptor and RPI NVME it should work out-of-the-box. Or other SBC that has M.2 slot already on the board.

Since about four weeks we encounter out of memory issues when building an Armbian image on GitHub with a customize-image.sh script. We had no big modifications on the build system since then, we have to rebuild from time to time to get the latest version of our application into the image. We already use a more powerful runner (32GB RAM, 8 cores). Our compile call: ./compile.sh \ BOARD=rockpi-4b \ BRANCH=edge \ RELEASE=bookworm \ KERNEL_CONFIGURE=no \ BUILD_MINIMAL=yes \ NETWORKING_STACK="network-manager" \ COMPRESS_OUTPUTIMAGE=xz \ KERNEL_BTF=no \ SHARE_LOG=yes Our build is based on the tag v25.8.0-trunk.260 Any ideas for this? Thanks in advance Florian

Hi @Alex T Indeed the board seems to be dead not getting turned on at all. Even tried to boot with the secondary BIOS but not working. I managed to fit the new board in the older case so its perfectly being utilised.

@amazingfate can tell that. https://github.com/armbian/build/blob/main/config/boards/oneplus-kebab.conf#L3

I've successfully setup Armbian with home assistant preinstalled The image build command is ./compile.sh BOARD="rk3318-box" BRANCH=edge RELEASE=bookworm ENABLE_EXTENSIONS="ha" KERNEL_CONFIGURE="no" BUILD_MINIMAL="yes" I build on edge branch because only kernel after 6.15 can boot on rk3318 tv box, at this time it's 6.16.0rc3 Don't forget to add docker-ce and home assistant extension files to userpatches/extensions folder. After installation you need to cchange internet adapter manager from "Networking" to "Internet Manager" nmcli device set eth0 managed yes This is my prebuild version, use it at your own risk cause everyone on the internet might be the bad guy that want to hack your machine👻 Armbian-unofficial_25.08.0-trunk_Rk3318-box_bookworm_edge_6.16.0-rc3_minimal.img sha file attached Armbian-unofficial_25.08.0-trunk_Rk3318-box_bookworm_edge_6.16.0-rc3-homeassistant_minimal.img.txt Armbian-unofficial_25.08.0-trunk_Rk3318-box_bookworm_edge_6.16.0-rc3-homeassistant_minimal.img.sha

https://docs.armbian.com/Process_Contribute/#adding-a-new-board

Heya, No issue here with a rock 5b plus with rkmppenc v0.15 under kernel 6.1.115 on armbian 25.5.1 using HEVC transcoding: acas@rock-5b-plus:~$ rkmppenc -c hevc --preset best --audio-codec aac --vbr 700 -i ~hts/recordings/foo.ts -o ts.mkv -------------------------------------------------------------------------------- ts.mkv -------------------------------------------------------------------------------- [h264 @ 0xaaab23a61de0] non-existing PPS 0 referenced arm_release_ver: g24p0-00eac0, rk_so_ver: 6 rkmppenc (aarch64) 0.14 (r493) by rigaya, Apr 5 2025 09:08:50 (gcc 13.3.0/Linux) OS: Armbian 25.5.2 noble (6.1.115-vendor-rk35xx) aarch64 CPU: Cortex-A76 aarch64 (4P+4E,8C/8T) Input Info: avmpp: H.264/AVC, 1920x1080, 25/1 fps Output: H.265/HEVC main @ Level auto (main tier) 1920x1080p 1:1 25.000fps (25/1fps) avwriter: hevc, #1:mp2/stereo -> aac/stereo/128kbps, #2:aac_latm/stereo -> aac/stereo/128kbps => matroska Quality: best VBR: 700 kbps Max bitrate: 875 kbps QP: Min: 0, Max: 51 GOP Len: 300 frames CHECKPTS: check_pts(1/1): timestamp of video frame is smaller than previous frame, changing pts: -16 -> 2 (previous pts 0). CHECKPTS: check_pts(2/2): timestamp of video frame is smaller than previous frame, changing pts: -24 -> 4 (previous pts 2). CHECKPTS: check_pts(3/3): timestamp of video frame is smaller than previous frame, changing pts: -8 -> 6 (previous pts 4). ^C.8%] 8506 frames: 496.29 fps, 743 kbps, remain 0:05:37, est out size 624.3MB Encoding aborted. encoded 8917 frames, 489.43 fps, 743.66 kbps, 31.62 MB encode time 0:00:18, CPULoad: 0.0% frame type IDR 30 frame type I 30, avgQP 26.73, total size 1.22 MB frame type P 8887, avgQP 30.84, total size 30.40 MB Finished with error in rkmppenc. From looking at your logs, looks like a Device TRee issue - failed to identify key hardware parameters by the looks of it for some reason - change in boot settings? regards Andrew

Can i get some help,I have Uart adapter and can provide logs

That should be O.K. too.

tl;dr; This "only" difference is huge - modern kernel hw specific code is pretty much written from scratch, feature by feature. Not to mention differences in general areas between kernel 6.1 and 6.12, low level boot loader is also usually different. Further reading: https://docs.armbian.com/User-Guide_FAQ/#why-things-stop-working

Welcome to the forum! Your project sounds really interesting and practical, especially for optimizing fleet fuel usage. For an Armbian-based solution, Python is usually the best starting point. It offers great flexibility, extensive libraries, and good community support. Using Python with libraries like Matplotlib for visualization and Pandas for data handling would make it easier to process sensor data and create useful charts. Plus, Python scripts can easily be integrated into your workflow, whether as standalone scripts or through lightweight web interfaces (Flask or Dash, for example). Bash with awk might be lightweight but can quickly get complicated as your project grows—especially when you need calculations and data visualization. As for sensor integration, make sure to check the compatibility and communication protocol (I2C, SPI, UART) of your fuel sensors with Orange Pi. Sometimes the challenge is not only reading accurate data but also filtering out noise and handling sensor calibration. Regarding dashboards, if Grafana feels too heavy or lacking in fuel-specific functions, you might consider building a custom Python dashboard or integrating with lightweight web frameworks that allow tailored features like a dedicated fuel calculator. Looking forward to seeing your startup script and how your project evolves!

I saw the release of linux kernel 6.16 with initial support for Rockchip RK3528. I hope this update makes more viable to run and configura Armbian on this board 😀

New Linux kernel 6.16 with initial rk3528 support 😁 I hope this helps developing a solid armbian build for this chip and board

PanVK has reached another milestone and will be officially supporting Vulkan 1.4 on V10! We're up-to-date with the latest version and are well caught up for this release. View the full article

Hi, can anyone help me with this TV box? I need to unlock it, but I don't know where to short the cable because the PC won't connect. Rk3228a, zq01-v1.51

Hi and thanks for the reply I have the device running official armbian at my location (already brought it back) and so I'm trying to figure out a way to "simulate" high latency. Any ideas? Otherwise we'll have to wait a few months so I can place it at it's intended location again. As you can imagine, this is something that's taken a LONG time. Many many months and progress is slow.

So I have made some progress. A linux kernel for this device (based on the Berlin chipset family) exists at https://github.com/MarvellEmbeddedProcessors. I',m not sure how this piece adds towards creating a functional armbian install tho.

Hello! Asus Tinkerboard is still perfectly supported by Armbian. Best setup is the current LTS kernel 6.12, you can take an image from the official download page: https://www.armbian.com/tinkerboard/ enjoy!

Thanks c0rnelius, this works.

Thank you for the information I have completed the build dependencies step, for mesa 25.2, in Debian Trixie. However, when I build it, my orange pi zero 3 with 1 GB or RAM, it runs out of memory... even when I make a swap file of 2GB. I keep rebooting the opiz3, and continue the compilation job. Is this normal? In the raspberry forum, they told me that my LCD driver panel-mipi-dbi.ko doesn't work with X11... so I give up on this, and continue my development with labwc/wayland (easily installed in Trixie)

Maybe the mirror isn't good at this time. You can work around by choosing any mirror from this list and add it to your armbian source list: https://docs.armbian.com/Mirrors/