kris777

After the update/upgrade, all CPUs are now installed nproc 4 This didn't fix my Bluetooth (maybe it's some individual bug in my system?) but since Bluetooth works correctly in the new images for OrangePi 3 LTS, I'm marking this thread as resolved... I'll probably install the latest image soon, although it will be time-consuming. ........................... orangepi3-lts:~# dmesg | grep "CPU" [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: kernel page table isolation forced ON by KASLR [ 0.000000] CPU features: detected: Kernel page table isolation (KPTI) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. [ 0.005157] smp: Bringing up secondary CPUs ... [ 0.007070] Detected VIPT I-cache on CPU1 [ 0.007260] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.009368] Detected VIPT I-cache on CPU2 [ 0.009541] CPU2: Booted secondary processor 0x0000000002 [0x410fd034] [ 0.011117] Detected VIPT I-cache on CPU3 [ 0.011261] CPU3: Booted secondary processor 0x0000000003 [0x410fd034] [ 0.011373] smp: Brought up 1 node, 4 CPUs [ 0.011398] CPU: All CPU(s) started at EL2 [ 0.011443] CPU features: detected: 32-bit EL0 Support [ 0.011449] CPU features: detected: 32-bit EL1 Support [ 0.011458] CPU features: detected: CRC32 instructions [ 0.011470] CPU features: detected: PMUv3 [ 0.260754] ledtrig-cpu: registered to indicate activity on CPUs [ 0.414642] sun50i_cpufreq_nvmem: Using CPU speed bin speed0 [ 0.457342] WARNING: CPU: 3 PID: 71 at drivers/iommu/iommu.c:612 __iommu_probe_device+0x1a8/0x4a0 [ 0.457375] CPU: 3 UID: 0 PID: 71 Comm: kworker/u16:4 Not tainted 6.18.19-current-sunxi64 #2 PREEMPT Ps. I don't know if I announced the CPU solution too early? Maybe there's a problem with the processor clock speed? .............. cat /etc/default/cpufrequtils ENABLE=false MIN_SPEED=480000 MAX_SPEED=1810000 GOVERNOR=performance root@orangepi3-lts:~# cpu Temperature: 40 °C CPU-0 Frequency: 1608 Mhz CPU-1 Frequency: 1608 Mhz CPU-2 Frequency: 1608 Mhz CPU-3 Frequency: 1608 Mhz root@orangepi3-lts:~# cat /etc/default/cpufrequtils ENABLE=false MIN_SPEED=480000 MAX_SPEED=1810000 GOVERNOR=performance root@orangepi3-lts:~# cat /etc/default/cpufrequtils ENABLE=false MIN_SPEED=480000 MAX_SPEED=1810000 GOVERNOR=performance root@orangepi3-lts:~# root@orangepi3-lts:~# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq 1608000 root@orangepi3-lts:~# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor performance performance performance performance ............... shouldn't it be : 1810000 ... ?

I tested the new version (Armbian_26.2.0-trunk.591_Orangepi3-lts_forky_current_6.18.18_minimal) in terms of bloototh and it's OK... but there are errors that rule out this image. Namely, the system lacks 4 working processor cores 🙂 ... only one. Something is wrong at startup because the green LED is on and the red LED is constantly flashing/pulsing. Bringing up secondary CPUs ... [ 5.092655] CPU1: failed to come online [ 5.092666] CPU1: failed in unknown state : 0x0 [ 10.217311] CPU2: failed to come online [ 10.217324] CPU2: failed in unknown state : 0x0 [ 15.341948] CPU3: failed to come online [ 15.341961] CPU3: failed in unknown state : 0x0 [ 15.342047] smp: Brought up 1 node, 1 CPU [ 15.342057] SMP: Total of 1 processors activated. [ 15.342063] CPU: All CPU(s) started at EL2 [ 15.342112] CPU features: detected: 32-bit EL0 Support [ 15.342119] CPU features: detected: 32-bit EL1 Support [ 15.342129] CPU features: detected: CRC32 instructions [ 15.342146] CPU features: detected: PMUv3 [ 15.342193] alternatives: applying system-wide alternatives It's some kind of incompatibility: U-Boot / TF-A / kernel .... Similar errors are found in the version uploaded by: armbian imager (minimal / cli / debian - trixie) more information: https://paste.armbian.com/afokonucej command "poweroff" not working ! ? On version: Ubuntu / minimal (cli) there are the same errors regarding CPU...etc ..................................... dmesg | grep "CPU" [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: kernel page table isolation forced ON by KASLR [ 0.000000] CPU features: detected: Kernel page table isolation (KPTI) [ 0.000000] CPU features: detected: ARM erratum 845719 [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. [ 0.006129] smp: Bringing up secondary CPUs ... [ 5.092344] CPU1: failed to come online [ 5.092356] CPU1: failed in unknown state : 0x0 [ 10.216761] CPU2: failed to come online [ 10.216771] CPU2: failed in unknown state : 0x0 [ 15.341165] CPU3: failed to come online [ 15.341176] CPU3: failed in unknown state : 0x0 [ 15.341242] smp: Brought up 1 node, 1 CPU [ 15.341258] CPU: All CPU(s) started at EL2 [ 15.341291] CPU features: detected: 32-bit EL0 Support [ 15.341297] CPU features: detected: 32-bit EL1 Support [ 15.341309] CPU features: detected: CRC32 instructions [ 16.273971] ledtrig-cpu: registered to indicate activity on CPUs [ 17.351303] sun50i_cpufreq_nvmem: Using CPU speed bin speed0 .........................

That's strange 🙂 ...we have the same kernel. Maybe something's broken in the system? But I haven't messed with Bluetooth in the system. I've only updated the system: apt update /apt upgrade /reboot 🙂 root@orangepi3-lts:~# rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth bluetooth unblocked unblocked 1 wlan phy0 unblocked unblocked .............................. bluetoothctl Waiting to connect to bluetoothd... it keeps reading but shows nothing? ................... bt-device -l ** ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self)) Bail out! ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self)) Aborted ............. Something must have broken in the system, but what and where? Can you give me the exact: Armbian image + version ... Contents of ..../lib/firmware/uwe5622/ also: armbianEnv.txt Output dmesg | grep -i uart i dmesg | grep -i bluetooth Maybe that will help me figure out where the errors are in my system? Or maybe I have Debian and you have Ubuntu? Ps. or, more simply, information from the file: diagnostics.txt command in terminal: ................. ( uname -a cat /etc/os-release ls -lh /lib/firmware/uwe5622/ lsmod | grep -iE "bt|sprd|uwe" dmesg | grep -i uart ls /dev/tty* | grep -i "ttyS\|ttyAMA\|ttyBT" cat /boot/armbianEnv.txt rfkill list hciconfig -a bluetoothctl list hcitool dev bt-device -l dmesg | grep -iE "bluetooth|uwe|sprd|hci" ) > diagnostics.txt .....................

armbianmonitor -u in the link it shows : https://paste.armbian.com/uzudezufit Linux version 6.12.74-current-sunxi64 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #6 SMP Thu Feb 19 15:29:56 UTC 2026

Wi-Fi works → so the problem is only in GPIO / DTB initialization for Bluetooth It worked on the older kernel, but now it doesn't 😞.... Supposedly this is the cause, but is it really? armbianmonitor -u https://paste.armbian.com/uzudezufit

On my Orange Pi 3 LTS I don't use ethernet, only wifi and it works OK... maybe that's why I didn't notice the problem... but here is some information about ethernet on Pi 3 LTS https://forum.armbian.com/topic/19846-orange-pi3-lts/page/11/#comment-226536

I switched to the Armbian version of Debian Trixie and now it's OK

I gave some information ..... Hit:8 http://fi.mirror.armbian.de/beta bookworm InRelease ? 🙂 If this is a bug, meaning the repositories are in beta, then OK... but I don't know if I installed them? Or are they standard in the images/firmware installations, e.g., for the Opi3LTS version? Ps. Has support for my OrangePi3LTS model been completely abandoned? ...because now I don't have the option to install the system to the emmc memory in the :armbian-config options? / nand-sata-install / armbian-install 😞 I think the easiest way would be to switch to the Debian/Triexie version from bookworm because unfortunately bookworm has only bugs and no support for the wifi card now 🙂

This is the hint I got from AI 🙂 I changed the repositories from beta to stable and installed: sudo sed -i 's|beta.armbian.com|apt.armbian.com|g' /etc/apt/sources.list.d/armbian.list and sudo apt download armbian-bsp-cli-orangepi3-lts-current sudo dpkg --install --ignore-depends=base-files armbian-bsp-cli-orangepi3-lts-current_25.8.2_arm64.deb Now it's OK....but is this the right approach?

LC_ALL=C apt update Hit:1 http://security.debian.org bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 https://download.docker.com/linux/debian bookworm InRelease Hit:5 http://deb.debian.org/debian bookworm-backports InRelease Hit:6 https://github.armbian.com/configng stable InRelease Hit:7 https://dtcooper.github.io/raspotify raspotify InRelease Hit:8 http://fi.mirror.armbian.de/beta bookworm InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. root@orangepi3-lts:~# apt list --upgradable Listing... Gotowe armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.439 arm64 [upgradable from: 25.8.0-trunk.49] N: There is 1 additional version. Please use the '-a' switch to see it

I think I messed something up in the system, maybe with the repositories, but I get this message when updating... apt update Stary:1 http://deb.debian.org/debian bookworm InRelease Stary:2 http://security.debian.org bookworm-security InRelease Stary:3 https://download.docker.com/linux/debian bookworm InRelease Stary:4 http://deb.debian.org/debian bookworm-updates InRelease Stary:5 http://deb.debian.org/debian bookworm-backports InRelease Stary:6 https://dtcooper.github.io/raspotify raspotify InRelease Stary:7 https://github.armbian.com/configng stable InRelease Stary:8 http://armbian.lv.auroradev.org/beta bookworm InRelease Czytanie list pakietów... Gotowe Budowanie drzewa zależności... Gotowe Odczyt informacji o stanie... Gotowe 1 package can be upgraded. Run 'apt list --upgradable' to see it. root@orangepi3-lts:~# apt list --upgradable Listing... Gotowe armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.401 arm64 [upgradable from: 25.8.0-trunk.49] N: There is 1 additional version. Please use the '-a' switch to see it root@orangepi3-lts:~# apt list --upgradable -a Listing... Gotowe armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.401 arm64 [upgradable from: 25.8.0-trunk.49] armbian-bsp-cli-orangepi3-lts-current/now 25.8.0-trunk.49 arm64 [installed,upgradable to: 25.11.0-trunk.401] maybe someone has already dealt with this message and error?

I have a question regarding the configuration of the /etc/asound.conf file... are there any changes in the new kernel that prevent this from happening? I've noticed that my USB audio card no longer loses its settings and its position doesn't change. However, to be sure, I tried editing the /etc/asound.conf file... but it turns out to be impossible 🙂 That is, after saving the settings in /etc/asound.conf... ALSA doesn't work! 🙂 Moreover, the blocking for certain selected devices doesn't work either. In my case, the blocking is: HDMI Audio... in the file: /etc/modprobe.d/blacklist.conf blacklist sun9i_hdmi_audio blacklist snd_soc_simple_card Are these changes related to the detection/blocking, etc., of block devices in Linux?

OK...I think it worked in OrangePi3 LTS 🙂 ...first, clean up the remnants: ................................................................. sudo apt purge v4l2loopback-dkms sudo apt autoremove ............................................................... armbian-config then I had to switch to a different kernel: edge:6.15.4-edge-sunxi64 ....then update the system: apt update / upgrade / reboot ! install from GitHub: v4l2loopback and then: cd ~/v4l2loopback .................................................................... VERSION=$(grep -oP 'PACKAGE_VERSION="\K[^"]+' dkms.conf) sudo cp -r . /usr/src/v4l2loopback-$VERSION sudo dkms add -m v4l2loopback -v $VERSION sudo dkms build -m v4l2loopback -v $VERSION sudo dkms install -m v4l2loopback -v $VERSION dkms status sudo modprobe v4l2loopback ls /dev/video* ................................................................... I guess it's OK now: ................................................................ But in my opinion the module is not working properly 😞 I'll be more precise, it works OK... but OrangePi3LTS is a weak device and the option/module: v4l2loopback and the ffmpeg program that transmits/splits the image to two programs (motion/ustreamer) causes high CPU usage... but it works OK, so my problem is solved

I can't build it from GitHub, or rather I've built it but it doesn't work because the kernel headers don't seem to match and it can't be loaded. I guess you have to compile the entire kernel with this module 🙂 ..uppss sudo modprobe v4l2loopback insmod /lib/modules/6.12.35-current-sunxi64/updates/v4l2loopback.ko insmod: ERROR: could not insert module /lib/modules/6.12.35-current-sunxi64/updates/v4l2loopback.ko: Invalid module format

sudo apt install v4l2loopback-dkms Czytanie list pakietów... Gotowe Budowanie drzewa zależności... Gotowe Odczyt informacji o stanie... Gotowe v4l2loopback-dkms is already the newest version (0.12.7-2). 0 aktualizowanych, 0 nowo instalowanych, 0 usuwanych i 8 nieaktualizowanych. root@orangepi3-lts:~# sudo modprobe v4l2loopback modprobe: FATAL: Module v4l2loopback not found in directory /lib/modules/6.12.35-current-sunxi64