Search the Community

Flash 25.2.0 (The Latest Built Dec 01) to a SD card and boot a Orange Pi 3 LTS, Ethernet lost after sudo reboot the board. It did not even come back after physically power off and on. Have anyone experienced the same problem? The same board worked very well with Debian Bullseyes (downloaded from http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-pi-3-LTS.html). I googled and found Orange Pi 3B has similar problem. https://www.reddit.com/r/OrangePI/comments/1aojmn3/orange_pi_3b_ethernet_doesnt_work/

Does anyone use an infrared remote control with the Lirc / rc6 / mce program..and have a verified configuration? I can't configure the above to work on Orange pi 3 lts But I want the Lirc program and not the ir-keytable 🙂

I have a question for more experienced users. Quite a long time ago I built an internet radio based on OrangePi Lite + DAC I think in the I2S interface with the module: PCM5102 ... PCM5102 DAC Decoder I2S -Aliexpress unfortunately the board broke down. I have another model, the aforementioned Pi 3 lts but it seems to be less supported. Can I connect the above-mentioned PCM5102 module to this model? Or maybe buy some other supported model that will work just as well as Pi lite with this DAC model or another? Ps. it would be nice if it had the ability to upload Armbian firmware to emmc flash memory I installed Armbian/Ubuntu on Pi3lts but I get some errors when trying to update Get:1 http://beta.armbian.com noble/noble-desktop arm64 chromium arm64 9:126.0.6478.182-1~deb12u1+narmbian1 [75,5 MB] Err:1 http://beta.armbian.com noble/noble-desktop arm64 chromium arm64 9:126.0.6478.182-1~deb12u1+narmbian1 File has unexpected size (75534134 != 75534200). Mirror sync in progress? [IP: 130.185.239.75 80] Hashes of expected file: - SHA512:a7e5830c81b8e490ebc775bc96bb333cdd1f77c5fc63eebda4f4af3afa7b93ea3fa12bc77a3f01897406b0fec5fb6086955c50fa2948eddce193339dcafafa77 - SHA256:bb3b81a3d587729e06ff1ce01c1f381ce80b6862cdcc0fe71ffb3ee72ce9e1bf - SHA1:0e8312f23cef970db12a45203aa9af1dadf40a8d [weak] - MD5Sum:b25df98ff45f7a20eb89c1ad27cb0390 [weak] - Filesize:75534200 [weak] E: Failed to fetch http://armbian.tnahosting.net/beta/pool/noble-desktop/c/chromium/chromium_126.0.6478.182-1~deb12u1+narmbian1_arm64.deb File has unexpected size (75534134 != 75534200). Mirror sync in progress? [IP: 130.185.239.75 80] Hashes of expected file: - SHA512:a7e5830c81b8e490ebc775bc96bb333cdd1f77c5fc63eebda4f4af3afa7b93ea3fa12bc77a3f01897406b0fec5fb6086955c50fa2948eddce193339dcafafa77 - SHA256:bb3b81a3d587729e06ff1ce01c1f381ce80b6862cdcc0fe71ffb3ee72ce9e1bf - SHA1:0e8312f23cef970db12a45203aa9af1dadf40a8d [weak] - MD5Sum:b25df98ff45f7a20eb89c1ad27cb0390 [weak] - Filesize:75534200 [weak] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? OK ...I removed chromium from the system...now the upgrade has been done but I had another problem with the reboot option which didn't always work? And also restarting the Pi-3 LTS after the poweroff option from the button on the case for 2 seconds. I switched to FW from the Orange PI provider: Orangepi3-lts_3.0.8_debian_bullseye_server_linux5.16.17 and now it's OK? ...I switched to the original FW supplied by the OrangePi manufacturer, version: Orangepi3-lts_3.0.8_debian_bullseye_server_linux5.16.17 .... and it's OK

Hello, I'm a lay user, I don't know much about Armbian and networks - On my network I have a router whose default DNS is set to point to an OrangePI 3 lts with Armbian 23.02, where I installed AdGuard (v0.107.52) and created my rules to filter advertisements through URLs that I access through the web browser of any device. It works almost 100% as I would like - I use a NO-IP DDNS on the router to access the surveillance DVR and I can see the cameras fine on my smartphone. However, when there is a power outage and then it comes back on, there is often some kind of synchronization failure between the router and the OrangePI to access the cameras. So I need to restart the Orangepi to be able to view them remotely again. I believe it could be something related to the free and dynamic DDNS, or because I needed to disable the router's DHCP and transfer this function to the OrangePI (so that the network device logs could work correctly through AdGuard). I would like to know: 1) Is there a way to program the OrangePI to restart itself every X hours? What program do I need to install (with a tutorial if possible) and how can I configure a script for this? I tried to find something within armbian-config, I searched on Google, but I couldn't find exactly what I was looking for. So I want to test if this would solve my problem. 2) What is the easiest way to access the OrangePI system files from Windows? Is it via FTP? I use PuTTY for remote access, but I don't know much more about it. Thank you

just downloaded orange-pi-3-lts's latest debian bookworm available on your website I found out that apt sources includes a reference to a beta repository didn't expect that and I'd rather prefer to avoid beta... what's better: just comment out the beta updates or build a custom image not containing betas?

I'm testing different firmware versions for OrangePi 3 LTS a bit and I have to mention that version: Armbian_community_24.11.0-trunk.202_Orangepi3-lts_noble_current_6.6.44_gnome-kisak_desktop.img It has a flaw that can cause some trouble for beginners, i.e. after installing, the system automatically goes to the suspend option after 15 minutes 🙂 Disabling the suspend option completely helps, but it then prevents you from using the suspend option by clicking the button on the board 🙂 This is probably an error related to both battery and mains power supply. https://discussion.fedoraproject.org/t/gnome-suspends-after-15-minutes-of-user-inactivity-even-on-ac-power/79801 but unfortunately this is not it 😞

When I attempt to run the Sudo apt update command I am receiving an error message about the Repository not being signed. See attached photograph

With Armbian 22 (kernel 5.15 and bullseye/jammy) the Orange PI 3 LTS worked great including WiFi, ETH, Bluetooth. Partly thanks to @Ukhellfire and @going. Downloadable here: https://xogium.performanceservers.nl/archive/orangepi3-lts/archive/ Below is what I find the status is for the new Armbian 23 images provided for here : https://www.armbian.com/orangepi3-lts/ Branch current: Main downloads Armbian 23 with kernel 6.1 bookworm: It boots, but every 3rd or 4th keystroke is ignored. No ETH, no WiFi. Armbian 23 with kernel 6.1 jammy: It boots, keystrokes are OK, ETH is OK, but WiFi doesn't work. Branch edge: Rolling release downloads Armbian 23 with kernel 6.4 bookworm: Doesn't boot, no board lights come on. Armbian 23 with kernel 6.4 lunar: Doesn't boot, no board lights come on. Branch edge: When I build myself There doesn't seem to be any selection to make edge boot regardless of kernel (5.15, 6.1 or 6.4) or bookworm/bullseye. Branch current: When I build myself I found a way to get a good build of Armbian 23: use branch current with legacy kernel 5.15: 1) Checkout the last current commit: https://github.com/armbian/build/commit/6af50cfcdd46661038fd30c71548362012df6438 2) Edit config/boards/orangepi3-lts.csc and add support for legacy kernel: KERNEL_TARGET="legacy,current,edge" 3) Build legacy bullseye: ./compile.sh build BOARD=orangepi3-lts BRANCH=legacy RELEASE=bullseye @Igor I can send free Orange PI 3 LTS boards to US based Armbian contributors if it can improve community support of this board.

Hello, sorry for the dumb questions incoming, thanks for your time. Lately I spent a lot of time searching for a working image to run Kodi with wifi/ethernet/bluetooh on this board. Does anybody managed to play videos on Kodi on this SBC ? If yes, what armbian image should I choose for this purpose ? Do I have to build the image myself ? Tested LibreElec for this but no wifi because the drivers are out-of-the-tree, not in mainline Kernel. Read about my problem in many posts but didn't find what I was searching for... Not even sure if this SBC can be used as a linux media player. Any tip/link/guide/wiki on how to successfully install kodi/hardware acceleration/video decoding/needed drivers for this board will be much appreciated.

I've had an Orange Pi 3 LTS for a couple of months now. I bought it for use as a home theater tv box. I thought I'd use the official orange pi ubuntu release, but it turned out to be really outdated and broken. So I have been trying to get Armbian to work. After a lot of troubleshooting and time spent reading docs and forums, I can't get the thing to play video properly. It plays but is terrible quality and stutters constantly. I've determined that panfrost is working. In orangepi-config, under Hardware, it says the GPU is enabled. But when I run glmark2 I get a score of 100 or less no matter what I do. I've tried old builds of armbian for the pi 3 lts and they either wouldn't boot, don't have working wifi, or have the same video issue. I've tried running the build script myself but it has either failed or not produced a bootable build. I would love to learn more about Armbian and SBCs and actually get this thing to work for video, but it is incredibly overwhelming. Is this even worth my time to try to get working? I keep thinking there's just one setting I need to change, one driver I need to install, or something I'm missing, but I can't find it. Should I just buy a different board? If so, which one in a similar price range would actually do what I'm looking for? Thanks folks.

Hi @ertugrul and @afaulkner420. I was trying to create a bootable drive for the orangepi 3 lts and it always fails in validation in balenaEtcher. I tried even with that and it does not seems to work. The non-desktop versions worked however. I didn't see any error messages during the flashing and everything else seemed to work well. Thanks, Ashish

Have a nice day! Could you tell me how to build a linux-tools package for my OS? Best regards.

Hi! Is the Orange Pi3 image suitable for the Orange Pi3 LTs? Or where to find it?

Hello. Sorry for my english. I have OrangePi3 LTS and BTT TFT35 SPI v2.1 with ili9488. I am trying to connect display to orangepi via SPI, but I dont have ili9488 driver in fbtft folder. When I am building fbtft with ili9488 from github https://github.com/Snitro/fbtft-ili9488, I am getting error. What did I wrong? uname -a : Linux orangepi3-lts 6.6.31-current-sunxi64 FBTFT Build error: root@orangepi3-lts:/lib/modules/6.6.31-current-sunxi64/build/drivers/video/fbdev# make -C /lib/modules/`uname -r`/build M=$PWD modules make: Entering directory '/usr/src/linux-headers-6.6.31-current-sunxi64' CC [M] /lib/modules/6.6.31-current-sunxi64/build/drivers/video/fbdev/fbtft-ili9488/fbtft-core.o /lib/modules/6.6.31-current-sunxi64/build/drivers/video/fbdev/fbtft-ili9488/fbtft-core.c: In function ‘fbtft_framebuffer_alloc’: /lib/modules/6.6.31-current-sunxi64/build/drivers/video/fbdev/fbtft-ili9488/fbtft-core.c:694:36: error: ‘FBINFO_FLAG_DEFAULT’ undeclared (first use in this function); did you mean ‘FAULT_FLAG_DEFAULT’? 694 | info->flags = FBINFO_FLAG_DEFAULT | FBINFO_VIRTFB; | ^~~~~~~~~~~~~~~~~~~ | FAULT_FLAG_DEFAULT /lib/modules/6.6.31-current-sunxi64/build/drivers/video/fbdev/fbtft-ili9488/fbtft-core.c:694:36: note: each undeclared identifier is reported only once for each function it appears in make[3]: *** [scripts/Makefile.build:243: /lib/modules/6.6.31-current-sunxi64/build/drivers/video/fbdev/fbtft-ili9488/fbtft-core.o] Error 1 make[2]: *** [scripts/Makefile.build:480: /lib/modules/6.6.31-current-sunxi64/build/drivers/video/fbdev/fbtft-ili9488] Error 2 make[1]: *** [/usr/src/linux-headers-6.6.31-current-sunxi64/Makefile:1915: /lib/modules/6.6.31-current-sunxi64/build/drivers/video/fbdev] Error 2 make: *** [Makefile:234: __sub-make] Error 2 make: Leaving directory '/usr/src/linux-headers-6.6.31-current-sunxi64'

Hi I've got both left and right channels working of my analog audio jack. The quality is quite good as long as Master audio isn't set above volume 15 - 20 or so. Toggling DAC or DAC-Reversed in Alsamixer will enable or disable the physical left and right physical speakers of ear buds. However! On both channels, the left and right software signals are mixed. So if I use "aplay stereo-file.wav", I hear left+right mixed through my separate left ear. Listening to my right earbud, same story: I hear left+right audio mixed. Please help, I can't even find any snd_ module flags to mess with. I've no pulseaudio installed on this latest stable server edition of Armbian (Armbian_23.8.3_Orangepi3-lts_jammy_current_6.1.53_minimal.img). Armbianmonitor txt/gzip output is attached. root@oranger:/etc/modprobe.d# lsmod | grep -i snd snd_soc_hdmi_codec 20480 1 snd_soc_ac200 32768 1 snd_soc_simple_card 20480 0 snd_soc_simple_card_utils 24576 1 snd_soc_simple_card root@oranger:/etc/modprobe.d# modinfo snd_soc_ac200 filename: /lib/modules/6.6.16-current-sunxi64/kernel/sound/soc/codecs/snd-soc-ac200.ko license: GPL author: Jernej Skrabec <jernej.skrabec@gmail.com> description: X-Powers AC200 Codec Driver alias: of:N*T*Cx-powers,ac200-codecC* alias: of:N*T*Cx-powers,ac200-codec depends: intree: Y name: snd_soc_ac200 vermagic: 6.6.16-current-sunxi64 SMP mod_unload aarch64 root@oranger:/etc/modprobe.d# uname -a Linux oranger 6.6.16-current-sunxi64 #2 SMP Fri Feb 23 08:25:28 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux armbianmonitor-output.txt.gz

I disabled Armbian kernel upgrades to stay at Armbian 23.11.1 until Armbian 24 stabilizes. Yesterday I unfroze the kernel upgrades to upgrade to 24.2.1. I run: apt update apt upgrade apt dist-upgrade Apt update says All packages are up to date. shows nothing. What did I miss?

I have a orange pi3 lts. I tried to install either minimal ether gnome version. Wireless is configured and working . I tried to execute command sudo systemctl enable ssh and reboot but sshd is down always and screen show always desktop orange PI without any network connection. I tried to use also u armbian-config but ssh is always down and network is down . Any attempts is not working . In addition thr desktop interface is the same in minimal and gnome version .... very strange

After an "apt upgrade", the kernel was switched to "Linux 6.6.16-current-sunxi64" (Armbian 24.2.1 Jammy). On the WiFi side, no problem, but for Ethernet, it no longer seems to detect the link. So I downgraded to "Linux 6.1.77-legacy-sunxi64" with armbian-config. After this, the Ethernet works again. Do you have any idea where this could come from? And if this can be fixed in future versions?

I updated my system to the newest kernel and lost all WiFi. What is the deal???

As the title says. I can not get PWM to work. I can type gpio mode 2 pwm and no error. But when I try to access it from Klipper (3D Printer Software and Firmware) it won't work. However if I use gpio 3, in software, gpio 4 turns on. Please help me out here. Thanks, Kevin

Hello, I have Orange Pi 3 LTS with Armbian 22.*.1 5.15.80-sunxi64. It have been working well for about a year, but after upgrading to 23.8.16.1.47-current-sunxi64 network interfaces stop working at all. I can't downgrade kernel with arbian-config because it need internet access. Here is output from armbianmonitor: armbianmonitor.txt Could you please guide me how to solve this issue?

Hello everyone, I encountered an issue while using SPI with my Orange Pi 3 LTS, and now I'm going to share some solutions. Perhaps the Armbian Team can assist me in resolving the final problem. These tests were conducted on Armbian 23.02.2 Bullseye with Linux 5.15.93-sunxi64. The initial step I took to ensure the appearance of `spidev` on the Orange Pi 3 LTS was to include these configurations in `/boot/armbianEnv.txt`. overlays=spi-spidev1 param_spidev_spi_bus=0 param_spidev_spi_cs=0 Note: If `spi-spidev` and `spi-spidev1` are added together, it will not work, and the `spidev` will not appear when using the `ls /dev/sp*` command. After performing the above steps, I executed the `sudo reboot` command, and `/dev/spidev1.0` appeared. root@orangepi3-lts:~/wiringOP# ls /dev/sp* /dev/spidev1.0 However, this alone was insufficient to ensure proper functionality of SPI. I attempted to send a message to an ATMega 168p using a Python script that utilizes the `spidev` library. The script is below: import spidev spi = spidev.SpiDev() spi.open(1, 0) spi.max_speed_hz=10000 payload = [0x0c, 0x00] spi.xfer(payload) print(*payload[1:]) The ATMega 168p occasionally received the message, and sometimes it did not. I suspected that the issue might be related to the MISO or MOSI connections. To investigate further, I directly connected the MISO pin of the Orange Pi 3 LTS to its MOSI pin, testing whether I would receive an echo in the script provided earlier. Indeed, I received the echo successfully. Considering the observations so far, my remaining suspicion lies with the CS (Chip Select) line. If the CS line is not functioning properly, it may fail to select the specific device, resulting in issues with the request/response process (similar to what I experienced). Hence, I proceeded to install wiringOp, on my device. This allowed me to read all the GPIOs of my Orange Pi 3 LTS and check for any anomalies. After successfully building it, I ran the command `gpio readall` and observed the following output: root@orangepi3-lts:~/wiringOP# gpio readall +------+-----+----------+------+---+ OPi 3 +---+------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | | | 3.3V | | | 1 || 2 | | | 5V | | | | 122 | 0 | SDA.0 | OFF | 0 | 3 || 4 | | | 5V | | | | 121 | 1 | SCL.0 | OFF | 0 | 5 || 6 | | | GND | | | | 118 | 2 | PWM.0 | OFF | 0 | 7 || 8 | 0 | OFF | PL02 | 3 | 354 | | | | GND | | | 9 || 10 | 0 | OFF | PL03 | 4 | 355 | | 120 | 5 | RXD.3 | OFF | 0 | 11 || 12 | 0 | OFF | PD18 | 6 | 114 | | 119 | 7 | TXD.3 | OFF | 0 | 13 || 14 | | | GND | | | | 362 | 8 | PL10 | OFF | 0 | 15 || 16 | 0 | OFF | PD15 | 9 | 111 | | | | 3.3V | | | 17 || 18 | 0 | OFF | PD16 | 10 | 112 | | 229 | 11 | MOSI.1 | ALT2 | 0 | 19 || 20 | | | GND | | | | 230 | 12 | MISO.1 | ALT2 | 0 | 21 || 22 | 0 | OFF | PD21 | 13 | 117 | | 228 | 14 | SCLK.1 | ALT2 | 0 | 23 || 24 | 0 | OFF | CE.1 | 15 | 227 | | | | GND | | | 25 || 26 | 0 | OFF | PL08 | 16 | 360 | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+ OPi 3 +---+------+----------+-----+------+ I noticed that the CS pin (GPIO 227) is currently set to `OFF` and needs to be configured as `ALT2` along with `MOSI.1`, `MISO.1`, and `SCLK.1` . This information gave me a clear direction on how to solve my problem. To investigate further, I began checking the device tree configuration using the following commands: `sudo armbian-config` -> `System` -> `Dtc`: ... spi1-pins { pins = "PH4\0PH5\0PH6"; function = "spi1"; phandle = <0x2b>; }; spi1-cs-pin { pins = "PH3"; function = "spi1"; phandle = <0x2c>; }; ... spi@5011000 { compatible = "allwinner,sun50i-h6-spi\0allwinner,sun8i-h3-spi"; reg = <0x5011000 0x1000>; interrupts = <0x00 0x0b 0x04>; clocks = <0x04 0x53 0x04 0x51>; clock-names = "ahb\0mod"; dmas = <0x2a 0x17 0x2a 0x17>; dma-names = "rx\0tx"; pinctrl-names = "default"; pinctrl-0 = <0x2b 0x2c>; resets = <0x04 0x20>; status = "disabled"; #address-cells = <0x01>; #size-cells = <0x00>; phandle = <0x72>; }; ... Upon examining the pinout diagram, I realized that the Orange Pi 3 LTS utilizes SPI1, and all the SPI pins (H3, H4, H5, H6) were correctly configured in the device tree. This led me to speculate that the issue might not be in the device tree itself but rather in the `spi-spidev1 overlay`. To investigate further, I decompiled the `sun50i-h6-spi-spidev1.dtbo` file located at `/boot/dtb/allwinner/overlay/` into a `.dts` file using the command `dtc -I dtb -O dts sun50i-h6-spi-spidev1.dtbo -o sun50i-h6-sp i-spidev1.dts`. Next, I edited the `pinctrl-0` section of the `sun50i-h6-spi-spidev1.dts` file, adding the addresses `0x2b` and `0x2c` (similar to what was done in spi@5011000). /dts-v1/; / { compatible = "allwinner,sun8i-h3-spi"; fragment@0 { target-path = "/aliases"; __overlay__ { spi1 = "/soc/spi@5011000"; }; }; fragment@1 { target = <0xffffffff>; __overlay__ { pinctrl-names = "default"; pinctrl-0 = <0x2b 0x2c>; status = "okay"; #address-cells = <0x01>; #size-cells = <0x00>; spidev@0 { compatible = "armbian,spi-dev"; reg = <0x00>; spi-max-frequency = <0xf4240>; }; }; }; __fixups__ { spi1 = "/fragment@1:target:0"; spi1_pins = "/fragment@1/__overlay__:pinctrl-0:0"; }; }; Compiled the modified `sun50i-h6-spi-spidev1.dts` file into a `.dtbo` using the command `dtc -O dtb -I dts sun50i-h6-spi-spidev1.dts -o sun50i-h6-spi-spidev1.dtbo`. Then, I rebooted the Orange Pi 3 LTS. After the reboot, I ran the `gpio readall` command again to check the GPIO pin status: root@orangepi3-lts:~# gpio readall +------+-----+----------+------+---+ OPi 3 +---+------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | | | 3.3V | | | 1 || 2 | | | 5V | | | | 122 | 0 | SDA.0 | OFF | 0 | 3 || 4 | | | 5V | | | | 121 | 1 | SCL.0 | OFF | 0 | 5 || 6 | | | GND | | | | 118 | 2 | PWM.0 | OFF | 0 | 7 || 8 | 0 | OFF | PL02 | 3 | 354 | | | | GND | | | 9 || 10 | 0 | OFF | PL03 | 4 | 355 | | 120 | 5 | RXD.3 | OFF | 0 | 11 || 12 | 0 | OFF | PD18 | 6 | 114 | | 119 | 7 | TXD.3 | OFF | 0 | 13 || 14 | | | GND | | | | 362 | 8 | PL10 | OFF | 0 | 15 || 16 | 0 | OFF | PD15 | 9 | 111 | | | | 3.3V | | | 17 || 18 | 0 | OFF | PD16 | 10 | 112 | | 229 | 11 | MOSI.1 | ALT2 | 0 | 19 || 20 | | | GND | | | | 230 | 12 | MISO.1 | ALT2 | 0 | 21 || 22 | 0 | OFF | PD21 | 13 | 117 | | 228 | 14 | SCLK.1 | ALT2 | 0 | 23 || 24 | 0 | ALT2 | CE.1 | 15 | 227 | | | | GND | | | 25 || 26 | 0 | OFF | PL08 | 16 | 360 | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+ OPi 3 +---+------+----------+-----+------+ The SPI functionality is now operational, but this solution is not definitive. To address the underlying issue, I need assistance as device trees, kernels, and other aspects of Linux are not within my area of expertise. It seems that the problem with the CS pin is related to an error during the boot process, resulting in an incorrect address assignment. Well, I hope this information proves helpful to others who are experiencing the same issue as I did. Remember: English is not my first language, so there may be some errors.

I use Armbian_23.5.1_Orangepi3-lts_bookworm_current_6.1.30. I'm trying to download in armbian-config kernel headers, but linux-headers-5.15.93-sunxi64 are downloaded. How to download kernel headers 6.1.30.?

Hello! How to turn off Wi-Fi and Bluetooth devices to reduce power consumption? armbianmonitor -U -> result in attachment. Thank you. armbian-hardware-monitor.log

My Orange Pi 3 LTS with Armbian 23.11.1 Jammy with Linux 6.1.63-current-sunxi64 is showing high load, but low CPU. The SBC crashed overnight. When I run htop, the following lines show state D: root lscpu root /bin/bash /usr/lib/armbian/armbian-hardware-optimization start root grep -q \<ondemand\> /sys/devices/cpu/cpu0/cpufreq/scaling_available_governors load average: 4.00, 4.00, 4.00 System load: 100% CPU usage: less than 1% sar -u 5 Linux 6.1.63-current-sunxi64 (hostname) 12/31/2023 _aarch64_ (4 CPU) 03:41:54 PM CPU %user %nice %system %iowait %steal %idle 03:41:59 PM all 0.50 0.00 0.35 0.00 0.00 99.15 I'm up to date with software (sudo apt update && sudo apt upgrade -y). I am unable to kill -9 the offending processes. When I try to reboot, I get locked out of ssh, but SBC does not reboot, and keeps replying to pings. I have to end up pulling the plug to get it to reboot. After plugging it back in, it starts out without the problem, but the problem resurfaces shortly thereafter. My other three OPI3LTS with Armbian 23.11.1 Jammy with Linux 6.1.63-current-sunxi64 are not having this issue. Thank you for your assistance, and Happy New Year!