All Activity

homeassistant ?

Maybe my firmware build can replace Petitboot?

Exactly Since I don't know the build, I can't make any concrete statements about it. It is also not possible under any circumstances, as the access procedures are far too complex to be meaningfully encoded in the MASK-ROM. As firmware devices, only SPI flash, MMC (eMMC, SD card), and USB with a proprietary protocol are available. This is correct. I just quickly built this version out of curiosity. I was just about to provide the binary artifacts when I quickly took a look at the schematic of your device. If I am not misinterpreting the schematic, your device only allows the fixed SPI-MMC-USB sequence and the forced immediate proprietary USB device. This means that you cannot execute the firmware completely from the microSD card, for example, if there is still a valid firmware signature in a device (SPI, eMMC) that is higher up in the priority list. It is therefore essential that you are familiar with the USB recovery procedure (MASK-ROM-MODE), in case something goes wrong during the firmware experiments with the higher prioritized devices (SPI, eMMC).

Hello everyone! I’m new to the forum and recently set up Armbian on my Orange Pi using the latest July 2025 image. I’m working on a user-space application to monitor fuel consumption for IoT projects involving vehicle fleets, like optimizing diesel trucks. I’m thinking of something that could run via armbian-config or as a Python script, pulling data from fuel sensors. So far, my idea is to log consumption data and calculate efficiency based on user input. I’ve tried Grafana, but it lacks a dedicated fuel calculator—kalkulatorpaliwa.com.pl could serve as a starting point for a simple interface. I’m unsure how to approach this on Armbian—should I use Python with Matplotlib, or go for a lighter option like Bash with awk? I’ll share a basic startup script if someone helps me get started! What tools do you recommend for building such apps on Armbian? Has anyone worked on a similar fuel monitoring project with SBCs? What challenges might I face with sensor integration? Looking forward to your suggestions—I plan to start testing this week!

Yes I have the heat sink and a thermal pad: Time CPU load %cpu %sys %usr %nice %io %irq Tcpu C.St. 19:42:28 816 MHz 0.00 0% 0% 0% 0% 0% 0% 51,6 °C 0/4 19:42:33 816 MHz 0.00 0% 0% 0% 0% 0% 0% 50,5 °C 0/4 19:42:38 816 MHz 0.00 0% 0% 0% 0% 0% 0% 52,8 °C 0/4 Armbian 23.02.2 Bullseye with Linux 5.15.93-sunxi Ambient temp is quite hot these days it's like maybe 32°C maybe more

https://wiki.kobol.io/helios64/files/psu/YHY_12V_PSU_Specification.pdf

I was able to get the conflicting versions fixed: now:

Getting into kernel development can be daunting. There are layers upon layers of knowledge to master, but no clear roadmap, especially when it comes to debugging drivers or navigating userspace-kernel issues. View the full article

Does anyone know of a compatible image for the MXQ PRO 4K 5G TV Box with Allwinner H3, model Q44_V4.1_20210120? I've searched a lot and only found images compatible up to version V4.0. Since mine is V4.1, I haven't been able to get a successful boot from the SD card. If anyone has any tips, a working image, or experience with this specific model, I’d really appreciate the help!

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Hi everyone, I’m experiencing a recurring and very specific issue with my TX2 TV Box, with the following specifications: SoC: Rockchip RK3229 RAM: 2GB DDR3 Storage: NAND flash (not eMMC!) Board: Generic TX2 board 🛑 Main Issue The system shuts down abruptly at exactly 29 minutes and 47 seconds of uptime (i monitoring via htop). It always shuts down at this time. It’s not a clean shutdown or reboot — it behaves as if the power was cut off. No meaningful logs appear in journalctl or dmesg, and the shutdown is instantaneous and silent. 🧪 What I’ve Tried: Disabled idle and sleep functions: Masked systemd-logind Set IdleActionSec=0 and HandlePowerKey=ignore Tried different kernel versions: Legacy: Armbian 22.02.0-trunk Focal legacy 4.4.194 Mainline: Armbian Jammy kernel 5.15 Attempted to disable the watchdog: Boot parameter nowatchdog Kernel parameter rcu_cpu_stall_timeout=0 Created a systemd service to periodically write to /dev/watchdog Tried to remove dw_wdt module (modprobe -r), but it either auto-loads or refuses to unload (watchdog did not stop) Tried building a custom kernel with CONFIG_DW_WATCHDOG=n, but the process failed due to gcc-arm-linux-gnueabi toolchain issues. Used config-rk322x to properly set RAM, NAND, and Wi-Fi chip before first boot + update/upgrade. Tried adding sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target ⚠️ Additional Critical Note: The system does not work at all when flashed to eMMC/flash — only boots properly from NAND or SD card. Any image written to internal flash does not boot. Therefore, booting from NAND is required, which may be related to the watchdog being active by default on NAND-based boards. ❓ My Question: Has anyone with a TX2 or RK3229-based NAND board experienced this same issue? Is this a known watchdog timer issue on NAND models? Is there any stable image or device tree overlay known to work for this configuration? Any tips to fully disable the watchdog either via software or kernel patch? Thanks in advance for any help or suggestions!

The defconfigs are also just one piece of the problem here. There are patches getting applied to Sunxi for the Rockchip platform, why? Patches for the Pinephone, why? Last I checked that's not supported in either standard or community. Allwinner on Armbian has also been plagued with Bluetooth issues for years. I would venture to guess this is related to unchecked and unverified patching along with a defconfig that looks like a 5 year old went through and just ticked everything on. You tell me. Who wants to deal with this? Who wants to help fix it? and whom would want to do any work in this muddled up environment.

Could do that. Or you could do a PR and turn on what is now missing from the defconfiigs that is required for your use case. Probably more productive than endlessly complaining. Nothing got intentionally disabled or turned off. They are two new defconfigs that are getting re-worked so everyone with in the community can profit. Not just the OPi crew.

The commit 2a38243de9ff01e079b6ec0c930c00f892e163aa brought lots of unnecessary config changes, DISABLED hundreds lines and at least made owserver failed. You say you just want pwserq and bluetooth work , why did you modified so many TCP/IP network config? Maybe we should rollback to commit d502356d0271f0d5748b67e4b4d998b51e588c6a (tag: v25.8.0-trunk.293) and remove all patches from pyavitz@gmail.com, It is so terriable.

Has anybody had success with Armbian Trixie? I repeated the steps I did for Bookworm, to have HW accelerated H264 1080p in XFCE, X11, with Linux 6.15.4... and I get "Unsupported hwdec: drm" in Trixie: ffmpeg 7.1.1, mpv 0.4.0 mpv log in trixie (with double verbose): For reference, mpv log in Bookworm: I inspected ffmpeg build configuration, and I see that ffmpeg 7.1.1 doesn't have "--enable-libv4l2", while ffmpeg 5.1.6 has that option. I checked with "ffmpeg -codecs|grep h264" In bookworm: In trixie Although, here the ffmpeg manual reads that this is option is only for webcams and videocapture https://www.ffmpeg.org/ffmpeg-devices.html#video4linux2_002c-v4l2

Thanks for your answer 🙂 And Sorry for my Stupidness .... and stupid questions in advance 🙂 with "firmware" you mean the "uboot - loader" mainly right ? at least It should be part of it ? The one I'm used is from the Armbian 25.5.1 image, thats what im copied with the arm-install to the /dev/mtdblock0 So I need a new uboot version for the orange pi 5 (that the chip gets configured properly) with support for my boot device I think this uboot version is lacking at least on nvme support, right ? Usually my plan was not to boot from nvme, but from the extra emmc .... but this had the same result. I have red somewhere that the actual released git branch of uboot has support for the orange pi 5 plus so building a uboot from git would help here ?

OK, PPS has back. good job. But another issue: the 1-Wire device maybe broken , Python3 package w1thermsensor works, but owserver failed . w1thermsensor all Got temperatures of 2 sensors: Sensor 1 (0000051a7f7c) measured temperature: 32.44 celsius Sensor 2 (04146945e5ff) measured temperature: 33.06 celsius owserver: journalctl -xeu owserver 7月 22 14:05:24 opip3 systemd[1]: owserver.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit owserver.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. 7月 22 14:05:24 opip3 systemd[1]: owserver.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit owserver.service has entered the 'failed' state with result 'exit-code'. 7月 22 14:05:25 opip3 systemd[1]: Failed to start owserver.service - Backend server for 1-wire control. ░░ Subject: owserver.service 单元已失败 ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ owserver.service 单元已失败。 ░░ ░░ 结果为“failed”。 7月 22 14:05:25 opip3 systemd[1]: owserver.service: Scheduled restart job, restart counter is at 5. ░░ Subject: Automatic restarting of a unit has been scheduled ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ Automatic restarting of the unit owserver.service has been scheduled, as the result for ░░ the configured Restart= setting for the unit. 7月 22 14:05:25 opip3 systemd[1]: owserver.service: Start request repeated too quickly. 7月 22 14:05:25 opip3 systemd[1]: owserver.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit owserver.service has entered the 'failed' state with result 'exit-code'. 7月 22 14:05:25 opip3 systemd[1]: Failed to start owserver.service - Backend server for 1-wire control. ░░ Subject: owserver.service 单元已失败 ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ owserver.service 单元已失败。 ░░ ░░ 结果为“failed”。

I have an old oDroid M1 that used to have Ubuntu 20 LTS installed on, but after it bricked itself during the install of Ubuntu 22 LTS, I decided to go looking for an alternative OS (it was also really sluggish). I got pointed to Armbian, and since it officially supports the M1, I gave it a go. Unfortunately, the instructions leave much to be desired. This part just doesn't seem to actually work: > Once booted, use armbian-install to write u-boot to MTD (SPI flash). This completely and irrevocably removes Petitboot, replacing it with mainline u-boot. All of the options that appear to be what it means by "write u-boot to MTD (SPI Flash)" don't seem to actually do that, as every time I try, rebooting the oDroid just leads back to this Petiboot screen: I can't seem to do anything from there, and it seems to be the old bootloader that the installation instructions said would be "irrevocably removed", but apparently isn't. I can boot into Armbian if I hold the RCY button while booting up the oDroid, but I believe that's booting in the Armbian that's installed on my SD card (I did the initial setup once). I want to install the system onto the oDroid's storage directly (the eMMC, I think?), so I don't have to hold that button every time I boot. I'm no linux expert (I use PC at home and a Mac at work), so I'm completely at a loss, here. Any help would be greatly appreciated. Here's the options I'm given from armbian-install. I've tried 2, 5, and 6, and none have worked. I don't have a SATA, USB, or NVMe to try the other options with.

Hello! I installed the latest Gnome Noble image from the very top of the Orange Pi 5 page, it has Wayland and generally is working really well - it even is doing higher refresh rate for my monitor and is smooth! HOWEVER the one big thing I noticed right away - my screen never turns off anymore And my Power options are missing such settings? It only gives the option to blank, which still is running my monitor at 100% brightness and a horrible solution Where is the setting to turn my screen off after 5 minutes? NOT blank, but into standby mode Worked on the previous Cinnamon version but that version lacked higher refresh rates and I think was not wayland Thank you!

Maybe you don't need some function, but please don't break it.

Device: Opi5-Plus Armbian Image: Armbian_25.5.1_Orangepi5-plus_noble_vendor_6.1.115_kde-neon_desktop.img.xz Upgraded successfully and reboot up with no issue on Wayland session. Operating System: Ubuntu 24.04 KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.1 Kernel Version: 6.1.115-vendor-rk35xx (64-bit) Graphics Platform: Wayland Processors: 4 × ARM Cortex-A55, 4 × ARM Cortex-A76 Memory: 15.6 GiB of usable RAM Graphics Processor 1: Mali-G610 Graphics Processor 2: Mali-G610 Graphics Processor 3: llvmpipe Product Name: Orange Pi 5 Plus

If it is NAND then you are out of luck as mainline Linux has no support for NAND. If it is eMMC then your dtb would likely need to be modified to support your hardware if it isn't showing up. My guess is that you have NAND.

Do you see all the needed files in the initramfs? Use lsinitramfs -l /boot/initrd... What guide did you use?

Hello, I have a T95 Super with H2+/H3 processor. I've been successful running Armbian in the past on it and even writing to eMMC but am looking for the most updated build I can to burn to the eMMC. I have H3droid running on it after a VERY long install process and many board reburns to fix it. I noticed H3droid has an "Armbian" option in it's rescue menu but there don't seem to be any instructions on how to install with the menu/use it. What is the best new build for this setup? Thank you!

Hello, My pet labubu and I got the most recent onecloud/odroid c1 versions fully working on my horrid former Oriental TV box, the TVPad 4 (previously brought up by user @daniyo). Everything works perfectly, except I want to finish my building by installing to eMMC. None of the recent builds I can find come with an install.sh script, and I cannot see the eMMC (or NAND if it's NAND) in lsblk or any of the installers. Does anyone have any clues or suggestions that can help the poor long suffering Labubu fix this issue? He just wants to watch IPTV and play little games