Active threads

Hi, it looks like you or a process is triggering the SysRq key. For example, If I press Alt + PrtSc (SysRq) + h, I see the same message in dmesg. https://en.wikipedia.org/wiki/Magic_SysRq_key

If you follow the instructions earlier in this thread, you can use the Armbian build framework to build an image for aml-s9xx-box with the HA additions, or just use armbian-config to add it. I haven't tested any of those, as I just install the regular docker based HA on my home TV box to run HA.

Not sure what you mean by outdated? Gets updated often or when needed; https://github.com/jwrdegoede/rtl8189ES_linux/tree/rtl8189fs

Welcome to submit PR here: https://github.com/armbian/build/tree/main/config/kernel Best to all those configs:

I think this is handled with overlay "audio" "analogue" or something similar. https://docs.armbian.com/User-Guide_Armbian-Config/System/#device-tree-overlays

Did you figured out what is the reason for this problem with dark pictures?

Checked http://fi.mirror.armbian.de/oldarchive/ ?

I just updated a raspios64 virtual machine with grub-efi and vanilla Debian kernel added: Settings in: /etc/default/raspi-firmware KERNEL=no INITRAMFS=no SKIP_INITRAMFS_GEN=yes Still: update-initramfs: Generating /boot/initrd.img-6.1.0-37-arm64 ERROR: Unsupported initramfs version (6.1.0-37-arm64) So it is not working as I hoped/thought.

Thanks for the reply. I did run each element one at a time and watched to see when and if there were any that reported errors. It's not a big deal though and always worth trying new things to try and get this SOC running as it should do.

It works. On armbian: In /boot/armbianEnv.txt extraargs=ipv6.disable=1 Worked on my orangePi-PC2 at least. On rpiOS: In /boot/firmware/cmdline.txt, add ipv6.disable=1 to your console line, for example: console=serial0,115200 console=tty1 root=PARTUUID=583925ff-02 rootfstype=ext4 fsck.repair=yes ipv6.disable=1 rootwait You can check if it works: $ ls /proc/sys/net/ipv6 ls: cannot access '/proc/sys/net/ipv6': No such file or directory

https://zuckerbude.org/armbian-using-kernel-config/ Once successful tested provide a PR to add the missing module:https://docs.armbian.com/Process_Contribute/

that should be 1500000 (one more zero). Note a lot of uart connectors can't handle this high of a speed. There are many threads in the forums discussing specific ones that are able to reach that speed.

Probably. Only way to really find out is to try: https://www.armbian.com/amlogic-s9xx-tv-box

This will be fixed soon.

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 success now after i fixed some branch missing errors, let me try to test the image

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? update: this LCD does not have a D1 diode, and it looks like this According to this Amazon link, this LCD board should have a flat cable through the "slot hole" near the top right. https://www.amazon.com/Display-Module-ILI9488-480x320-Equipped/dp/B0D92DSCMG

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

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