Active threads

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 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?

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?

@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.

@justanothernoob the images with "current" instead of "vendor" in the name have very limited hardware support (no HDMI, no sound, etc). You should peek the "vendor" images. Mind I noted to use the images dated 16th of August or post as otherwise your pcie sata connected drives won't work most of the time. So you should try bookworm_vendor or noble_vendor with xfce,cinnamon,gnome,kde-neon if you want a graphical interface and minimal for serial console/ssh only. You will only get black screen from HDMI with "current" images, that is expected (the HDMI support is not in the linux kernel, only in linux-rockchip kernel, ie vendor as of yet). ie the image you told using https://fi.mirror.armbian.de/incoming/prahal/rock-5-itx/archive/Armbian_25.8.1_Rock-5-itx_bookworm_current_6.12.41_minimal.img.xz is such a linux kernel without HDMI support for rock-5-itx. https://fi.mirror.armbian.de/incoming/prahal/rock-5-itx/archive/Armbian_25.8.1_Rock-5-itx_bookworm_vendor_6.1.115_xfce_desktop.img.xz has HDMI support. you should be able to install form serial console with both vendor and current images. Mind I still need to read about installing RoobiOS on my emmc as sadly my board was shipped with an empty EMMC. So I cannot yet guide you through RoobiOS boot selection.

https://forum.armbian.com/topic/30074-helios64-armbian-2308-bookworm-issues-solved/page/11/#findComment-224260 wow, that's a bummer... how can I check if this happens also to my configuration?

@Piotr s im using the same warpme patches so it’s odd that it doesn’t boot. To show more information on your console screen change your loglevel to 7 in armbianEnv.txt. The file is located at the root directory of your sdcard.

@darcyg @ Hqnicolas 使用了你的rk3576-h96-m9s。dts rk3576-h96-m9s-linux.dtsiarmsom-sige5-rk3576_defconfig 预算Armbian-unofficial_25.11.0-trunk_H96-m9_bookworm_vendor_6.1.115-backported-mesa.img gup可以工作，kodi 4K硬件加速。 1、关机不断电，电源灯亮 2、3.5音频无设备 无输出 3、无wifi蓝牙 4、kodi https://github.com/armsurvivors/kodi-rockchip-deb 硬件共享 https://drive.google.com/drive/folders/1lzLwm9NhxZ_0_mghKG4A0XQ6NNsU9sn-?usp=drive_link

Hi, To my side, below work in root but not with systemd service: # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu #INTERVAL=10 INTERVAL=30 FCTEMPS=/dev/fan-p6/pwm1=/dev/thermal-cpu/temp1_input /dev/fan-p7/pwm1=/dev/thermal-cpu/temp1_input MINTEMP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 MAXTEMP=/dev/fan-p6/pwm1=50 /dev/fan-p7/pwm1=50 MINSTART=/dev/fan-p6/pwm1=20 /dev/fan-p7/pwm1=20 MINSTOP=/dev/fan-p6/pwm1=20 /dev/fan-p7/pwm1=20 MINPWM=20 To my side, below work in root and with systemd service: # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu INTERVAL=10 FCTEMPS=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input MINTEMP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=40 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=40 MAXTEMP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=50 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=50 MINSTART=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=20 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=20 MINSTOP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=20 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=20

At some point we will bump edge to 6.17. These bumps always take time since our patchset on top always needs adjustments. There are 3rd party ppa's for newer mesa. I suggest to use kisak since those are briefly tested. Otherwise go for oibaf which are automated untested, therefore latest mesa packages. In terms of Debian, no clue if there is a similar apt repo for such.

My apologies. I started working on this board again and just spent 3 wasted hours getting angry at the previous wipe eMMC instructions only to realize *I* had the wrong version of RKDevTool. Protip - do not do any hardware development angry, hungry, in a rage, or pressed for time. Wow. Here is the issues with your "erase eMMC" instructions (apparently partly taken from the guide to getting Linux on the T95 Plus): -Config file was loaded, loader, parameters and uboot were written. Board usually does not restart when this is done, restarted once out of my many attempts. -There are no instructions about "wipe_part", what partitions to destroy, or how to do this. Using your version of RKDevTool, no partitions are loaded which then appear in the Download Image window (as I assume they are supposed to). -Flashing the other Miniloader file is met with a Waiting for Device Success prompt, which never completes. These instructions obviously worked the first time I did this several months ago. I don't know what at all could have changed, and I'm pretty frustrated as I'm trying to recover from another OMV system crashing and trying to recover data, so the use was/is pretty urgent, and given this forum, it could be a few days before a replay so my system is now sitting hostage to these instructions.

I'm a bit embarassed to say they are confusing to me. I am going to ask Grok and see if it can help me, thank you

I don't think it's an SD card issue. Performance wise it's about twice the requirement. And if it was a bad block, I doubt the issue would be the same across two different images. As for logs... where? I tried running "sudo dmesg -T --color=always --level=err,warn | more" and nothing about AdGuard came up. I checked the AdGuardHome.yaml file and confirmed bind_host was set to 0.0.0.0 (I also tried setting it to 192.168.0.6... no improvement). The command "sudo netstat -tulnp | grep 3000" said command not found, and "journalctl -u AdGuardHome" came back with no entries.

Thx for your reply. Yes i tried both together. And just one. No difference. # Enable DRM VC4 V3D driver dtoverlay=vc4-kms-v3d # Enable the Touch Display 2 DSI panel dtoverlay=vc4-kms-dsi-ili9881-7inch

OS is stable, errors you are experiencing are likely related to faulty HW component as @eselarm already exposed. And we would most likely notice such anomaly before it gets to you. There are thousands of users and this is the only report of this kind ... Boards are going to the market at high rate, while users support remains more or less the same in past 10 years https://docs.armbian.com/User-Guide_Board-Support-Rules/ Community builds and their upgrades are untested as size of Armbian can only cope with a small selection of boards we call as "standard support", where we have volunteers behind. Community builds are on Debian / Arch images level, but packed with more features. https://github.com/armbian/community?tab=readme-ov-file#purpose-of-this-repository For those - Armbian provides build and hosting infrastructure, place to meet - this forum - while everything else is anyone's problem.

Collabora is heading to Amsterdam with talks, demos, and workshops covering Embedded Linux, KernelCI, Bluetooth & Auracast, mainline video capture for Rockchip, and more. Join us to see our latest open source work in action! View the full article

... straightforward and smooth.

Try this image https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_xfce_desktop.img.xz

Try to upload the old and new driver to an AI with you overlay included. Here it gives some suggestions for what you can try. The power sequence seems to be changed with the new driver and it might be too fast for your display. It suggests to put some parameters in the overlay to delay some parts, with higher chance with the first 3: Under "dsi0_panel: panel@0 {" prepare-delay-ms = <120>; reset-delay-ms = <50>; init-delay-ms = <150>; enable-delay-ms = <50>; disable-delay-ms = <50>; unprepare-delay-ms = <120>;

https://github.com/armbian/build/pull/8517 appears to fix my SFP problems.