Active threads

This will be fixed soon.

I started from scratch. Installed Armbian_25.2.2_Rpi4b_bookworm_current_6.12.15_minimal.img Having in mind what @eselarm suggested as culprit, I put raspi-firmware on hold root@rpi5b:~# apt-mark hold raspi-firmware then dpkg --remove --force-all libraspberrypi0 armbian-bsp-cli-rpi4b-current apt --fix-broken install apt install armbian-bsp-cli-rpi4b-current everything OK apt upgrade everything OK Reboot root@rpi5b:~# uname -a Linux rpi5b 6.12.31-current-bcm2711 #1 SMP PREEMPT Wed Jun 4 14:00:53 UTC 2025 aarch64 GNU/Linux Tried the same with raspi-firmware unhold and got this . . Setting up raspi-firmware (1:1.20250430-1) ... ERROR: Unsupported kernel version (6.12.15-current-bcm2711) Setting up libraspberrypi0:arm64 (1:2+git20231018~131943+3c97f76-1) ... Setting up libraspberrypi-bin (1:2+git20231018~131943+3c97f76-1) ... Processing triggers for libc-bin (2.36-9+deb12u9) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for initramfs-tools (0.142+deb12u1) ... update-initramfs: Generating /boot/initrd.img-6.12.15-current-bcm2711 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153b-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-3.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for built-in driver r8152 ERROR: Unsupported initramfs version (6.12.15-current-bcm2711) I then did apt-mark hold raspi-firmware apt purge raspi-firmware and apt upgrade went through but the system is not in a good shape. root@rpi5b:~# uname -a Linux rpi5b 6.12.15-current-bcm2711 #1 SMP PREEMPT Wed Feb 19 13:49:50 UTC 2025 aarch64 GNU/Linux The /boot/firmware/initrd.img was not updated. Then I installed Armbian_25.2.4_Rpi4b_bookworm_current_6.12.22_minimal.img First thing after boot: root@rpi4b:~# update-initramfs -u update-initramfs: Generating /boot/initrd.img-6.12.22-current-bcm2711 ERROR: Unsupported initramfs version (6.12.22-current-bcm2711) The same with Armbian_25.5.1_Rpi4b_bookworm_current_6.12.28_minimal.img I don't have anymore a clean 25.2.3 but the homeassistant_minimal.img one has the same problem. No idea how to fix it. raspi-firmware has status optional and the 25.2.2 works OK without it, I think I will go this way hoping somebody with better skills then me will fix it one day. Regards, Chris

Wow, that was fast! But what about ipv6? It works on the community image for opi-PC2 as I mentioned but not here.. Edit. Nvm, I see there is a cmdline.txt file in there.. Thank you for the fast reply!

Welcome to Armbian forums. Most of general questions are answered in: https://docs.armbian.com/ https://docs.armbian.com/User-Guide_Board-Support-Rules/ Remove those you will get answers there ...

@Hqnicolas Thanks for your reply, but i found the workflow run failed, could you please help to re-run the workflow which run successfully before? https://github.com/hqnicolas/ubuntu-rockchip-joshua/actions/runs/13094582628

I finally got time to test my new ili9488 4.0 inch LCD (red, version 2.1)... the graphic display works, but the touch doesn't I see the interrupts number increasing (with watch -n0.1 cat /proc/interrupts , focusing on the line with ads7846) I also see that some people in the arduino community short diode D1, or else the SPI second slave wont work https://github.com/Bodmer/TFT_eSPI/discussions/898 Is anyone here working with a new SPI LCD? How could I see logs specific for the ads7846 kernel driver?

Dont run the entire script at once. Run one section at a time for each step at a time and monitor the output. Example: Run the lines under 1A and monitor the output, Proceed to 1B and monitor. The only changes made to /etc/apt/sources.list are enabling the Debian unstable/experimental repos (which do not require public keys to be manually added. Full disclaimer: This was something I did as an experiment. Full Vulkan support for the Mali g610 is still not officially supported in Debain stable. To be completely honest, I personally rolled back this change by restoring a Timeshift backup taken before the changes. The dependencies installed by Debain Experimental for the latest Mesa version will also break dependencies used by Armbian for firmware updates. Please be smart and remember to make backups before making updates like this. Personally, I'm fine with waiting a few years for Debian to eventually apply compatibility to the stable branch

If the u-boot on the unit supports USB Boot, yes. GXL:BL1:9ac50e:bb16dc;FEAT:ADFD318C:0;POC:3;RCY:0;EMMC:800;NAND:81;SD:800;USB:8;LOOP:1;EMMC:800;NAND:81;SD:800;USB:8;LOOP:2;EMMC:800;NAND:81;SD:800;USB:8;LOOP:3;EMMC:0;READ:0;0.0;CHK:0; The above looks like USB Mode. This Mode is for flashing vendor or custom imgs to the unit via USB. This is for recovery.

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

Forget about it. The problem was the switch at my work desk which seems to be dead. So no physical connection...

Where exactly is it? Can you send me a download link? I have already damaged many units, according to your instructions git clone --depth=1 https://github.com/armbian/build.git cd build ./compile.sh 构建 BOARD=rk3328-heltec BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=no KERNEL_CONFIGURE=yes KERNEL_GIT=shallow RELEASE=bookworm

Thanks for the logs. Do you have tested PCIe extension ? My personal project is to create one NAS with one PCIe-to-SATA add on

I've got Orange Pi 2W board and installed Debian 12 Home Assistant image to it (image link). There is a huge problem with it. Very often there is no bluetooth module appeared in system. I need to reboot system for 10-15 timer to make it work. What can be a reason? I attached 2 boot logs (with good BT appears and no BT appears), I hope it will help to find out the issue. boot_log_bt_good_02.zip boot_log_bt_bad_02.zip

Packages `base-files` 25.* are not not built for Debian Trixie, which prevents upgrades and in my case installing new software. Managed to upgrade my system with some manual labour, but apt.armbian.com/pool/trixie-utils/b/base-files/ Results in errors like: /etc/armbian-image-release:

You are going down the wrong path. You should start here with understanding the Armbian build framework: https://docs.armbian.com/Developer-Guide_Overview

I would suggest you to download clean Debian minimal image and proceed this way: https://docs.armbian.com/User-Guide_Armbian-Software/HomeAutomation/#home-assistant EVCC can be installed this way - official Docker container: https://docs.armbian.com/User-Guide_Armbian-Software/HomeAutomation/#evcc How to deal with EVCC from HA, no idea. This is application level knowledge and I am just an average user of HA. I assume addon will want to connect to the service which runs on some IP address and some port. IMO this part is similar as official HAOS image. Current application images are not yet rebuild with latest stable base, so until then its better going clean Debain + armbian-config way.

update: if disconnect TX from USB-UART adaptor - then there is infinite output that changes every microsecond with more strings: ESC[1;47rESC[46;1H[ 45.827723][ Tible6] [dhd-wlan0] w l_ext_iapsta_evefs.readdy=1 (/system/etcb/init/hw/init.uo sr not foun db^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1Hnt : [S] Link UP with c8::ca:98^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1HESC[1;46rESC[46;1H ESC[1;47rESC[46;1H[ 45.827747][ T6] [dhd-wlan0] wconsole:/ $ ^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1Hl_notify_connect_status : wl_bss_conn.127^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1Hect_done succeeded with c8:ca:98 ^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1HESC[1;46rESC[46;1H ESC[1;47rESC[46;1H[ 45.843270][ T6] [dhd-wlan0] wl_notify_connect_sonso le:/ $ c^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1Htatus : wl_bss_connect_done succeeded127|^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1H with c8:7f:54:e0:ca:98 vndr_oui: 00-90-127|^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1H4C 00-0C-43 00-0C-E7 ^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1HESC[1;46rESC[46;1H ESC[1;47rESC[46;1H[ 45.881840][ T165] type=1400 audit(1699712132.610:14conssole:/ $ ^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1H4): avc: denied { open } for comm="FD655_Demo" path="/sys/class/fd655/fd65console:/ $ ^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1H5_vpause_127|y^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1Hflag" dev="s127fig=|^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1Hysfs" ino=19647 sc[ 82.040633][ T386] read descriptors^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1H[ 82.040698][ T386] read strings^MESC[1;46rESC[46;1H ESC[1;47rESC[46;1H[ 82.043097][ T1] init: processing action (sys.usb.config=adb && sys.usb.configfs=1 && sys.usb.ffs.ready=1) f82.045159][ T1] init: Co mmand 'symlink /coESC[46;159HnESC[46;159HfESC[46;159HiESC[46;159HgESC[46;159H But still no active shell session

just wanted to check if there is plan to have an image for the Rock 3B model? update: just tested the latest image for Rock 3A, and it is working ok. version: Armbian 25.2.1 Bookworm Minimal/IOT Kernel: 6.12.13, Size: 266.4 MB, Release date: Feb 13, 2025 I will run a few docker containers to see if there are any issues.

HDMI audio has been merged into 6.15. Board may need additional device tree nodes to make it work. Analog audio should work already as well bug may also need additional nodes. Collabora sent for Rock5B and 5B+ only upstream. https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md

if NAMESERVER is not set it falls back to default 1.1.1.1 A while ago I made a hack to enforce using whatever hosts nameserver is:https://github.com/armbian/build/blob/e03b1b543cda430fbffcb62c979aecabee42b044/config/templates/config-example.conf.template#L25

hello. Armbian 25.08 for Rockpi 4a executed dtc -O dtb -o rockchip-pwm-gpio.dtbo -b 0 -@ rockchip-pwm-gpio.dts. copied dtbo to /boot/dtb/rockchip/overlays. There is none in /sys/class/pwm/pwmchip1 . /sys/class/pwm/pwmchip0 is available. I can't create the pwmchip1 pwmchip2 folder. Operation not permitted

After the last update/upgrade USB BUS 7 has completely disappeared! So no life at all on the USB-C port. The following packages were upgraded : linux-dtb-edge-rockchip64, armbian-bsp-cli-odroidm2-edge, linux-image-edge-rockchip64, linux-u-boot-odroidm2-edge, armbian-firmware I suspect linux-dtb-edge-rockchip64 is not the M2 specific package and it has over written the dtb. Also I can't seem to install the kernel headers from armbian-config. It appears to go through the motions but nothing is installed. Also where can I find a documentation on what each device overlay (in armbian-config) is for?

@rickg i send you a private message

Interesting, didnt realize that.

Thank you for reporting. If current images have troubles, you can try to use previous ones. There is a link on the download pages or you can find them this way. https://forum.armbian.com/topic/52406-helios-64-fails-to-boot-since-upgrading-to-bookworm/#comment-219614 Which works best for your case, you will need to find on your own. We don't store this information / forum search might help. Similar goes with 3rd party images - most are Armbian based and none is in perfect state, things break apart all the time. By providing logs (if possible) someone might give you hints to workaround the problem, without hardly. As I understand from your report - image boots, but USB port doesn't work to enter password? And also network is down, so you can't login remote. I haven't tested HC4 on last builds, but C4 works just fine. In any case, fixing the problem can take some time - Hardkernel never supported our work, so we don't have active maintainer at stand by. It depends on volunteers that read this forum. When they notice and found time to look into this.