All Activity

So 25.05 and 25.5 are the same version? That threw me off for a while...

True, it's not critical to compile the ideal kernel into the image as long as I get one that works, I can always update it later from within the image. But I do prefer to do things right the first time, and to be utilizing the version I think I am and intend to be using. Btw, I boot from grub as well. For my Orange PI 5 Plus, The edge kernel is the only one that's actually useful to me because the Vendor kernel has no GPU acceleration at all, the Mainline kernel has no video output to my DVI monitor, and all 3 kernel branches aren't correctly utilizing the ES8388 analog audio, which I need. The audio volume is barely audible even when all volume controls are maxed out. It's been that way in every operating system I've tried (except those with old barebones Vendor Kernels from Orange PI). So ultimately I want to compile the latest (relatively) stable edge kernel myself, so I can modify the source code in an attempt to fix the audio, and of course share the solution when / if I find it. I've already found that the ES8388 and ES8328 are compatible - hence the es8328 modules used in the kernel for the ES8388. And I've narrowed down where the issue most likely is: Directory: sound/soc/codecs Files: es8328.h, es8328.c, es8328-i2c.c

Thank you for letting us know and polish up our next release. I'm sure @Igor will have a look shortly.

Board: ODROID-HC4 Images tested: Armbian_25.5.1_Odroidhc4_bookworm_current_6.12.28_minimal.img Armbian_25.5.1_Odroidhc4_noble_current_6.12.28.img Kernel versions tested: multiple (6.6.x, 6.7.x, 6.12.x) through armbian-config Issues observed: 1. No USB keyboard at boot I have tested with three different USB keyboards (all working fine on Debian/Ubuntu official images). 2. SATA not initialized → NAS functionality is broken Always get: ata1: SATA max UDMA/133 ata1: SATA link down (SStatus 0 SControl 300) ata2: SATA max UDMA/133 ata2: SATA link down (SStatus 0 SControl 300) Disks are never detected. This makes Armbian unusable on HC4 as a NAS (which is the main purpose of the board). 3. Petitboot incompatibility and restore procedure Armbian does not boot correctly with Petitboot (the default bootloader shipped by Hardkernel). The Armbian documentation recommends removing Petitboot, which prevents using other distributions afterwards. The official Armbian forum threads redirect to Hardkernel forum. The tools to restore Petitboot are hosted on ppa.linuxfactory.or.kr, which has been offline for over a week !... This effectively leaves users stuck without a working bootloader or system. Expected behavior SATA disks should be detected and initialized (as with Hardkernel’s Debian/Ubuntu 5.15 LTS images). USB keyboards should work at boot. Armbian should either work with Petitboot, or provide a reliable documented way to restore it. At the moment, Armbian on ODROID-HC4 is unusable as a NAS due to SATA not working and Petitboot being broken. The only working setup is using Hardkernel’s old Debian/Ubuntu images with kernel 5.15. Could you please clarify: Is HC4 still officially supported by Armbian? Do you test your releases ? If yes, which kernel/branch should be used for stable SATA support?... Will there be fixes for USB keyboard and Petitboot compatibility? Thanks a lot !

sorry to hear about your troubles The Tritium H5 is maintained by https://github.com/Tonymac32. Not sure if he is active here in the forum.

My experience is that the edge kernel is stable enough, but if you act like a disk-jockey (playing with disks or SD-cards/images nowadays) you destroy your success potentially every time you try some new image. Instead, pick a distro Debian or Ubuntu when Armbian, and make backups and/or do snapshots of what worked and then install packages variants. You can have vendor, current, edge kernels installed at the same time. A lot faster build maybe because the kernel is already build by some person or some computer before, so you get it fetched from a cache. I have added the beta repo in my sources so I can select between various kernels (and U-Boot variants). You need a bootmanager though, so own extlinux.conf script or wipe standard boot.* files and make sure EFI works, with GRUB or so. The latter works fine if you don't need overlays etc, so more use the SBC as PC then as embedded board to control things via GPIO pins or so. You can also re-install a specific kernel every time, but that does not work when the one you wanted to run does not start the board or crashes it. The OPi5plus I would consider as a PC, I do that for similar boards like ROCK5B and NanoPi-R6C at least. I select kernel via GRUB and have a permanent serial console cable connected, so it also works without HDMI connected. It is mainly the choice between vendor and mainline, that is the state of ARM64 nowadays. Some new boards like RPi5 cannot run mainline yet, so then there is little need to have a bootmanager, then you need the disk-jockey methods.

All I can say about the topic is to give you this link: https://wiki.kobol.io/helios64/pwm/

I've downloaded the latest stable Release of the source code: https://github.com/armbian/build/releases/tag/v25.8.1 When doing a Build, when it allows you to select the kernel branch: [vendor, mainline, edge], the only edge available for selection is the bleeding edge (i.e. latest trunk version). I've downloaded the 25.8.1 source code, and that's the edge version I want to compile. How do you build an image with the latest (relatively) stable edge kernel, as available in Armbian-Config? (i.e. currently v6.16.1-edge at Armbian 25.8.1)? Update #1 When compiling the image with the edge kernel, it downloaded it from the internet and it took roughly an hour to build. When compiling an otherwise identical image with the Vendor kernel, it did not seem to download it from the internet (although I wasn't watching it closely), and it took roughly less than half the time to build the image. The reason I compiled an image with the Vendor kernel is because something broke in the last 24 hours on the internet-supplied edge kernel. It compiled 24 hours ago, a few hours ago it didn't. This wouldn't be an issue if it was compiling the most recent release of v6.16.1-edge (25.8.1), as per my intention, instead of the ultra-latest. I also made some discoveries about version number inconsistencies (independent of the kernel branch selected). Things are confused. In Release 25.8.1, the version is 25.11.0.trunk. In Release 25.5.1, the version is 25.08.0-trunk.

Sorry, I don't have the Android dts, the Android image is erased. I have tried the image from niulinkcloud, The ethernet is working on this image, can we extract dts from this image?

look into understanding what armbian-config does behind the scenes and replicate that. I think that is a better option anyhow. armbian-config is known to royally screw up your system every now and then.

I flashed a fresh image to my uSD card via dd. $ sudo unxz -c Armbian_25.5.1_Tritium-h5_trixie_current_6.12.30_minimal.img.xz | dd of=/dev/sdf bs=1M oflag=direct conv=fsync status=progress iflag=fullblock When I loaded the uSD into my Tritium-H5 all I got was just the red power light, but no activity. Tried a few different power supplies with the same result. I finally figured out that it appeared the bootloader was missing. I used Libre Tech's flash tool to flash their bootloader to my uSD card. Now I was able to get the Tritium-H5 outputting the boot sequesnce on the serial console. However, it stops at: I stumbled through the u-Boot recovery process and after remounting the partition r/w I got dpkg to install linux-u-boot-tritium-h5-current_25.5.1_arm64__2024.01-S866c-P42f9-Hc721-V3ed7-Bb703-R448a.deb However, when I rebooted the Tritium-H5 I was still stuck on the above spoiler. 👆 Am I doing something wrong? How can I get the Tritium-H5 to boot the Armbian image? Thanks!

here is the ouput : @Nick A

@Nick Aalright

Connect using 5037

Hello @Nick A, i'm on my linux virtual machine doing the following command, but i got some problem on it (i have installed every package needed): yes, i got the ip from the ifconfig command on termux 32bit if you are wondering glad you helped me

@Nick AThe possibility of a cold solder joint is very low since both devices (with identical eMCP chips) exhibit the same symptoms. Additionally, SD card read/write functions normally within the Android system. Are there any alternative methods to install the OS onto the eMMC?

Looking at the code, I don't see this being possible as built. Alternative option is scheduling a reboot sufficiently far enough out and hoping the operation has completed by that time.. thoughts?

I'm trying to run the following on edge devices, the remote interface to which does not support a traditional terminal (i.e. no interactivity): armbian-config --cmd ROO001 At the conclusion of this command running, the user is prompted through the UI/TUI to reboot the device. How can I avoid this reboot prompt, and just proceed with the reboot immediately? e.g. the Raspberry Pi OS raspi-config tool allows for the nonint parameter to be passed: raspi-config nonint enable_overlayfs The intent is to automate enabling of the read-only fs. Hardware is various Raspberry Pi and ROCK Pi devices running Armbian. I've already confirmed the command works fine with user input. I just need to understand how to interact with the tool without user input. Thank you

If I run a update after changing kernel to edge it doesn't matter the version, it breaks boot, idk why, but it is installing dtb for kernel 6.16 even with kernel 6.13 or 14 installed, current kernel does not support analog audio out of the box and I managed to get it working a few times, so I'm stuck with edge kernel, did a update then changed to edge kernel and disabled armbian updates until this bug is fixed

Hi. I am not complaining. I just would like to understand why I must deactivate https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu/ if I want watching video on Youtube. If it's needed to disable this repo for watching video. I am ok. But why I can't read video with package from this repo? https://paste.armbian.com/vaxedisuda

What does: ffmpeg -codecs | grep hevc show? Even if it seems to support rkmpp, you can guess that it is broken. So install/get a dedicated external encoder. 2 people in this topic tread show working options. I can't help you any more, you need to do your homework so to say.

@Igor how often does netplan run? how possible might it be to sneak in a sed -i -e 's/PermanentMACAddress/MACAddress/' /run/systemd/network/* networkctl reload in my bootup sequence? will DHCP [on ethEXT1] or carrier up/down events break this?

Hello, Here is the ffmpeg version : gart@orangepi5:~$ ffmpeg ffmpeg version 6.1.1-3ubuntu5+git240504.09cd2a2~noble Copyright (c) 2000-2023 the FFmpeg developers built with gcc 13 (Ubuntu 13.2.0-23ubuntu4) configuration: --prefix=/usr --extra-version='3ubuntu5+git240504.09cd2a2~noble' --toolchain=hardened --libdir=/usr/lib/aarch64-linux-gnu --incdir=/usr/include/aarch64-linux-gnu --arch=arm64 --enable-gpl --disable-stripping --disable-omx --enable-gnutls --enable-libaom --enable-libass --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libharfbuzz --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-openal --enable-opencl --enable-opengl --enable-version3 --enable-rkmpp --enable-rkrga --disable-sndio --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-ladspa --enable-libbluray --enable-libjack --enable-libpulse --enable-librabbitmq --enable-librist --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libx264 --enable-libzmq --enable-libzvbi --enable-lv2 --enable-sdl2 --enable-libplacebo --enable-librav1e --enable-pocketsphinx --enable-librsvg --enable-libjxl --enable-shared libavutil 58. 29.100 / 58. 29.100 libavcodec 60. 31.102 / 60. 31.102 libavformat 60. 16.100 / 60. 16.100 libavdevice 60. 3.100 / 60. 3.100 libavfilter 9. 12.100 / 9. 12.100 libswscale 7. 5.100 / 7. 5.100 libswresample 4. 12.100 / 4. 12.100 libpostproc 57. 3.100 / 57. 3.100 Hyper fast Audio and Video encoder I simply used the ffmpeg in the distro : art@orangepi5:~$ cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=orangepi5 BOARD_NAME="Orange Pi 5" BOARDFAMILY=rockchip-rk3588 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=195b3c7d0 LINUXFAMILY=rk35xx ARCH=arm64 BOOT_SOC=rk3588 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image KERNEL_TARGET=current,edge,vendor KERNEL_TEST_TARGET=vendor,current FORCE_BOOTSCRIPT_UPDATE= FORCE_UBOOT_UPDATE= OVERLAY_DIR="/boot/dtb/rockchip/overlay" VENDOR="Armbian" VENDORCOLOR="247;16;0" VENDORDOCS="https://docs.armbian.com" VENDORURL="https://www.armbian.com" VENDORSUPPORT="https://forum.armbian.com" VENDORBUGS="https://www.armbian.com/bugs" BOOTSCRIPT_FORCE_UPDATE="no" BOOTSCRIPT_DST="boot.cmd" VERSION=25.8.1 REVISION=25.8.1 BR,

@buzz89In oranges zero2 dts it has a 3.3v regulator defined as reg_dcdce. There’s only 5v defined in the vontar dts. You can add this to your dts reg_dcdce: dcdce { regulator-always-on; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-name = "vcc-eth-mmc"; }; https://linux.googlesource.com/linux/kernel/git/bpf/bpf/+/refs/tags/v6.9-rc2/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts you can borrow code off these boards as well https://linux-sunxi.org/index.php?search=RTL8211F&title=Special%3ASearch&go=Go if you can extract your android dts for more clues.

@ARx8X98h has a similar AIC8800D wifi chip. You could probably use the wifi section from x98h dts. I have never had problems with my sdcard. Maybe it’s a bad solder joint?