Search the Community

OS running from eMMC: Armbian Debian 12 Bookworm Image Armbian_community_25.5.0-trunk.87_Orangepi3-lts_bookworm_current_6.6.72_minimal apt updated and upgraded Docker-engine installation through armbian-config fails. Here's the log: Get:1 http://security.debian.org bookworm-security InRelease [48.0 kB] Get:2 http://deb.debian.org/debian bookworm InRelease [151 kB] Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB] Get:4 http://deb.debian.org/debian bookworm-backports InRelease [59.4 kB] Ign:5 https://github.armbian.com/configng stable InRelease Get:6 https://download.docker.com/linux/debian bookworm InRelease [43.3 kB] Get:7 http://fi.mirror.armbian.de/beta bookworm InRelease [53.3 kB] Ign:5 https://github.armbian.com/configng stable InRelease Ign:5 https://github.armbian.com/configng stable InRelease Err:5 https://github.armbian.com/configng stable InRelease Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 2606:50c0:8003::153 443] Reading package lists... Done E: Release file for http://security.debian.org/dists/bookworm-security/InRelease is not valid yet (invalid for another 25d 9h 5min 11s). Updates for this repository will not be applied. E: Release file for http://deb.debian.org/debian/dists/bookworm/InRelease is not valid yet (invalid for another 22d 22h 34min 0s). Updates for this repository will not be applied. E: Release file for http://deb.debian.org/debian/dists/bookworm-updates/InRelease is not valid yet (invalid for another 25d 9h 41min 48s). Updates for this repository will not be applied. E: Release file for http://deb.debian.org/debian/dists/bookworm-backports/InRelease is not valid yet (invalid for another 25d 9h 41min 48s). Updates for this repository will not be applied. E: Release file for https://download.docker.com/linux/debian/dists/bookworm/InRelease is not valid yet (invalid for another 11d 0h 1min 59s). Updates for this repository will not be applied. E: Release file for http://beta.armbian.com/dists/bookworm/InRelease is not valid yet (invalid for another 25d 7h 16min 17s). Updates for this repository will not be applied. Reading package lists... Done Building dependency tree... Done Reading state information... Done Package docker-ce is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source Package docker-ce-cli is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'docker-ce' has no installation candidate E: Package 'docker-ce-cli' has no installation candidate E: Unable to locate package containerd.io E: Couldn't find any package by glob 'containerd.io' E: Couldn't find any package by regex 'containerd.io' E: Unable to locate package docker-buildx-plugin E: Unable to locate package docker-compose-plugin Failed to enable unit: Unit file docker.service does not exist. Failed to start docker.service: Unit docker.service not found.

When I check the eMMC from the Disk utility, it shows that it's normal. I can also boot the android distro that came with it normally. Help? 🥲

So I'm trying to connect with a UART cable from my PC to the board (OPI3LTS). Here's what I did so far: In desperation, I double checked every connection, to no avail. My devices are powered separately, so only the RX and TX cable are connected, and they are crossed as they should. Set up permissions: sudo chmod 666 /dev/ttyUSB0 Add user to dialout: sudo adduser <user> dialout Install minicom: Set up minicom with the correct address: /dev/ttyUSB0 Set up the correct baud rate (115200 in this case) Turn off flow control Tried connecting via "screen", minicom and putty, all of them just show me a black CLI I can't write in. Help? 🥲

Good evening! Thats my first post, I have for a year a Orangepi 3 LTS that I used for my kid, he looks that never switch off the unit by software and use the switch all the time, so suddenly the unit dont boot anymore, the SD card partition table was corrupt, so I mounted a new OS in another SD but does not boot, the green light is not coming anymore. So I connected a TTL to USB Serial device for debugging and it shows the following information: U-Boot SPL 2021,10-orangepi (Sep 06 2022 - 18:22:23 +0800) PMU: AXP806 DRAM: 2048 MiB Trying to boot from MMC2 NOTICE: NOTICE NOTICE NOTICE: INFOS NOTICE NOTICE: INFO: INFO: INFO? BL31: BL31: BL31: BL31: v2,2( debug) +a04808c1 Built ¢ 19340326, Jul 13 2022 Detected Allwinner H6 SoC (1728) Found U-Boot DTB at OxcO?ea28, model; OrangePi 3 LTS ARM GICv2 driver initialized PMIC; PMIC: BL31: BL31: BL31: Probing AXP805 AXP805 detected Platform setup done Initializing runtime services cortex_a53; CPU workaround for 855873 was applied Unhandled Exception in EL3, x30 = 0x0000000000107410 x0 = 0x0000000000000002 xd = 0x000000000010F550 x2 = 0x0000000000L0F 000 x3 = 0x0000000000000003 x4 = 0x0000000000110840 x5 = 0x000000000010¢320 x6 = 0x0000000000000001 x? = 0x0000000000000001 x8 = 0x0000000000000000 x9 = 0x000000000000000b x10 = 0x0000000000107190 x11 = 0x000000000000000a x12 = 0x0000000000000002 x13 = 0x00000000016e3600 x14 = 0x1261257500c00008 x15 = 0x01108c0150000508 x16 = 0x00000000000268a8 xl? = 0x00000000001093e4 x18 = 0x0000000000000004 x19 = 0x0000000000110000 x20 = 0x000000000010¢430 x21 = 0x0000000000110860 x22 = 0x0000000000000000 x23 = 0x0000000000000001 x24 = OxOO0OO0O0FFFFFFFF x25 = 0x0000000000000004 x26 = 0x0000000000000004 x2? = 0x0000000000110800 x28 = 0x0000000000000001 x29 = 0x000000000010e4b0 ser_el3 = 0x0000000000000238 sctlr_el3 = 0x0000000030cd183F cptr_el3 = 0x0000000000000000 ter_el3 = 0x0000000080803524 daif = 0x00000000000003c0 mair_el3 = OxO0000000004404FF spsr_el3 = 0x00000000600002cc elr_el3 = 0x000000000010637c ttbro_el3 = 0x0000000000110000 esr_el3 = 0x0000000002000000 far_el3 = 0xe0016ce004006210 spsr_el1 = 0x00000000000001ed elr_elt = 0x4b46367831080083 spsr_abt = 0x000000002a0e5034 spsr_und = 0x0000000004144808 spsr_irg = 0x000000006413060c spsr_fig = 0x000000004215329c sctlr_ell = 0x0000000000c50838 actlr_ell = 0x0000000000000000 cpacr_ell = 0x0000000000000000 esselr_elt = 0x0000000000000000 spell = Oxd53c5800200a0030 esr_elt = 0x000000000160028a ttbro_el1 = 0x180122092468¢203 ttbri_ell = 0x82060b6a44506803 mair_ell = 0x44e048e000098aa4 amair_ell = 0x0000000000000000 ter_elt = 0x0000000000000000 tpidr_ell = 0x0077342201851b64 tpidr_eld = 0x0108cec921e9101de tpidrro_eld = Ox226cc058ae6c0166 par_elt = Ox1b0000F40a066390 mpidr_el1 = 0x0000000080000000 afsr0_ell = 0x0000000000000000 afsri_ell = 0x0000000000000000 contextidr_ell = 0x0000000000000000 vbar_el1 = 0x0000000000000000 cntp_ctl_el0 — = 0x0000000000000002 entp_cval_elO = Ox0b30e1c1057e4981 entvictl_el0 — = 0x0000000000000002 entv_cval_el0 = 0x90cBa5a085b6b490 entketl_ell = 0x0000000000000000 sp_el0 = 0x000000000010e4b0 isr_el1 = 0x0000000000000000 dacr32_e12 = 0x0000000008e41ce9 ifsr32_el2 = 0x0000000000000400 cpuectlr_el1 == 0x0000000000000040 cpumerrsr_ell = 0x0000000000000000 l2merrsr_ell — = 0x0000000000000000 cpuactlr_el1 == 0x00001000090ca000 gicc_hppir = OxO0000000000003FF gicc_ahppir = OxO000OOHOOOOOOSFF gicc_ctlr = 0x00000000000001e9 gicd_ispendr regs (Offsets 0x200-0x278) Offset Value 0x2003 0x0090000000000000 0x2083 0x0090000000000000 0x2103 0x0090000000000000 0x2183 0x0090000000000000 0x2203 0x0090000000000000 0x2283 0x0090000000000000 0x2303 0x0090000000000000 0x2383 0x0090000000000000 0x2403 0x0090000000000000 0x2483 0x0090000000000000 0x2503 0x0090000000000000 0x2583 0x0090000000000000 0x2603 0x0090000000000000 0x2683 0x0090000000000000 Ox2703 0x0090000000000000 Ox2783 0x0000000000000000 I guess I need to flash or upload the firmware onto the H6 chip?

In case anyone wondering, AW859A / 20U5622 Wi-Fi modules (uwe5622 driver) do not support WPA3. GCMP-128/GCMP-256 are not listed as supported in iw output, SAE or WPA-PSK-SHA256 wpa_supplicant key methods are not recognized as valid. # iw phy Wiphy phy0 wiphy index: 0 max # scan SSIDs: 12 max scan IEs length: 2304 bytes max # sched scan SSIDs: 9 max # match sets: 9 RTS threshold: 2353 Retry short limit: 10 Retry long limit: 9 Coverage class: 0 (up to 0m) Device supports RSN-IBSS. Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP-128 (00-0f-ac:4) * WPI-SMS4 (00-14-72:1) * CMAC (00-0f-ac:6) * 00-0f-ac:255 Available Antennas: TX 0x1 RX 0x1 Supported interface modes: * IBSS * managed * AP * P2P-client * P2P-GO * P2P-device … > get_capability pairwise CCMP TKIP > get_capability group CCMP TKIP WEP104 WEP40 > get_capability key_mgmt NONE IEEE8021X WPA-EAP WPA-PSK WPA-EAP-SUITE-B OWE DPP FT-PSK FT-EAP > get_capability proto RSN WPA > get_capability auth_alg OPEN SHARED LEAP > get_capability modes IBSS AP

How do i enable UART 3 in an orange pi 3-LTS. i checked the /boot/armbianEnv.txt file and it has overlay_prefix=sun50i-h6. i then did a sudo armbian-config > System > Kernel > SYS210 Manage device tree overlays > enabled sun50i-h6-uart3 > reboot. after all that i am still only seeing ttys0 when i do a dmesg | grep tty

Hi there, I have this device left over from a previous project, and now I want to repurpose it for a forked version of PiKVM that is meant for alternate SBC such as the OrangePi. I spent the last 2 days adjusting various build settings and compiling. After installing, the kvmd service would complain about the UDC driver missing. Also executing ls /sys/class/udc/ would return nothing, seemingly indicating that OTG is not possible. Just last night I came across the file "sun50i-h6-orangepi-3-lts.dts" in which there is a comment containing the following: /* * This board doesn't have a controllable VBUS even though it * does have an ID pin. Using it as anything but a USB host is * unsafe. */ My question is if I either use an adaptor that disconnects the +5v ping, or tape over the +5v pin on the USB connector itself, I would be able to set dr_mode to otg and not risk damaging anything on either the pi itself or the server I plan to plug it into?

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/

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.

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'

Recently I tried to connect CAN bus adapter to my Orange Pi 3 LTS board and it happened that there is not so much information about it, it is outdated or related to other boards. So, after I spent a few days in trials and errors below is my recipe. 1. Connect a CAN interface board. Orange Pi pins are not 5V tolerant, so I decided to use a dedicated 2-channel board from Waveshare: https://www.waveshare.com/2-ch-can-hat.htm (only one channel for the start). You can modify a cheap board from AliExpress though; there are instructions in the Internet. I used the PL10 pin of Orange Pi 3 LTS board as INT pin. Actually first I tried to use the PD21 pin but it seems that this pin cannot generate interrupts for some reason and it took a few days to find the solution. Also note that in the overlay this pin bank is set as 0 (as if it would set for the PA10 pin). I have no idea why it should be set this way, maybe someone would explain. 2. Activate the SPI interface in the device tree (it is disabled by default). So, first decompile the device tree: mentioning that you are using the 3LTS board, you need the /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dtb file. Decompile it with the following command: dtc -I dtb -O dts -o sun50i-h6-orangepi-3-lts.dts sun50i-h6-orangepi-3-lts.dtb . Edit the dts file a little: in the resulting text file sun8i-h3-orangepi-pc.dts find section named like spi@5011000 and change the status field value from “disabled” to “okay”. Then compile the dts file back to dtb: dtc -I dts -O dtb -o sun50i-h6-orangepi-3-lts.dtb sun50i-h6-orangepi-3-lts.dts . 3. Add an overlay file for the MCP25251 interface. Compile the attached overlay file sun50i-h6-spi-mcp2515.dts: dtc –I dts –O dtb –o sun50i-h6-spi-mcp2515.dtbo sun50i-h6- spi-mcp2515.dts . Copy the resulted .dtbo file into the /boot/overlay-user folder and add into the /boot/orangepiEnv.txt string user_overlays=sun50i-h6-spi-mcp2515 . 4. Install CAN tools: sudo apt-get install can-utils . 5. Restart your board. 6. Make sure that the CAN interface is initialized; run the following command: dmesg | grep spi||mcp . You will see a line like this: mcp251x spi1.0 can0: MCP2515 successfully initialized. 7. Activate the CAN bus; run the following command: ip link set can0 up type can bitrate 500000 . 8. Make sure that the CAN bus is active; run the following command: ip –det link show can0 . You should see that the bus has UP state now. Hope this helps and sorry if I missed something. sun50i-h6-spi-mcp2515.dts

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.

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 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?