Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Didn't find what you were looking for? Try searching for:

More search options

  • Search By Tags

    Search will match any tag entered
  • Search By Author

Content Type

Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Product Groups

  • Misc
  • Support
  • Legacy Products

Calendars

  • Community Calendar

Find results in

Find results that contain...

Date Created

  • Start

    End

Last Updated

  • Start

    End


Filter by number of...

  • Minimum number of comments

  • Minimum number of replies

  • Minimum number of reviews

  • Minimum number of views

Found 754 results

  1. EDIT: 04.01.2020 - Fixed patches to work with latest armbian sources. (references have changed) Hi everybody, Here is a tutorial to enable the Lemaker 7" Touchscreen on BananaPi Pro with Debian Buster and Mainline-Kernel 5.XX.XX. Kernel: Mainline 5.4.6 / Buster Board: BananaPi Pro WebLinks: • https://forum.armbian.com/topic/1905-enabling-lcd-in-u-boot-kernel-472/ • https://forum.armbian.com/topic/1849-touch-driver-banana-pi/ • http://www.atakansarioglu.com/getting-started-bananapi-linux/ • http://forum.lemaker.org/thread-15482-1-1.html • http://linux-sunxi.org/LCD To make the 7"LCD and the Touchscreen working with BananaPi Pro we need to patch some files and change the kernel config to build the driver for the touchscreen. To do this we need a working setup of the Armbian build tool chain (https://docs.armbian.com/Developer-Guide_Build-Preparation/) /home/<USER>/build/cache/sources/u-boot/v201X.XX/configs/Bananapro_defconfig /home/<USER>/build/cache/sources/u-boot/v201X.XX/arch/arm/dts/sun7i-a20-bananapro.dts /home/<USER>/build/cache/sources/linux-mainline/linux-4.XX.y/arch/arm/boot/dts/sun7i-a20-bananapro.dts 1. U-Boot ( u-boot version that supports the LCD - must be compiled) Start the build process with ./compile.sh CREATE_PATCHES=yes When asked for: [ warn ] Applying existing u-boot patch [ /home/[USER]/build/output/patch/u-boot-sunxi-current.patch ] [ warn ] Make your changes in this directory: [ /home/[USER]/build/cache/sources/u-boot/v201X.XX ] [ warn ] Press <Enter> after you are done [ waiting ] a) edit /home/<USER>/build/cache/sources/u-boot/v201X.XX/configs/Bananapro_defconfig add the following: #7" LVDS LCD CONFIG_VIDEO_LCD_MODE="x:1024,y:600,depth:24,pclk_khz:55000,le:100,ri:170,up:10,lo:15,hs:50,vs:10,sync:3,vmode:0" CONFIG_VIDEO_LCD_PANEL_LVDS=y CONFIG_VIDEO_LCD_POWER="PH12" CONFIG_VIDEO_LCD_BL_EN="PH8" CONFIG_VIDEO_LCD_BL_PWM="PB2" b) edit /home/<user>/build/cache/sources/u-boot/v201X.XX/arch/arm/dts/sun7i-a20-bananapro.dts add after: &i2c2 { ... }; the following: &i2c3 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&i2c3_pins>; edt: edt-ft5x06@38 { compatible = "edt,edt-ft5x06", "edt,edt-ft5206"; reg = <0x38>; pinctrl-names = "default"; pinctrl-0 = <&edt_ft5x06_pins_a &edt_ft5x06_pins_b>; interrupt-parent = <&pio>; interrupts = <7 9 IRQ_TYPE_EDGE_FALLING>; touchscreen-size-x = <1024>; touchscreen-size-y = <600>; }; }; Add these two new sections to the end of the file: &pio { edt_ft5x06_pins_a: ft5@0 { pins = "PH9"; function = "irq"; drive-strength = <20>; bias-pull-up; }; edt_ft5x06_pins_b: ft5@1 { pins = "PH7"; function = "gpio_out"; drive-strength = <20>; bias-pull-up; output-high; }; }; &pwm { pinctrl-names = "default"; pinctrl-0 = <&pwm0_pin>, <&pwm1_pin>; status = "okay"; }; Then save and press <Enter> to continue. 2. Kernel patches - DTB (Device Tree Blob) file that fits to your Kernel and supports pwm When asked for: [ warn ] Applying existing kernel patch [ /home/<USER>/build/output/patch/kernel-sunxi-current.patch ] [ warn ] Make your changes in this directory: [ /home/<USER>/build/cache/sources/linux-mainline/orange-pi-5.XX ] [ warn ] Press <Enter> after you are done [ waiting ] c) edit /home/<USER>/build/cache/sources/linux-mainline/orange-pi-5.XX/arch/arm/boot/dts/sun7i-a20-bananapro.dts add the same lines like section b) Then save and press <Enter> to continue. 3. Compile Touchdriver menuconfig > Device Drivers > Input Device Support > Touchscreens > EDT FocalTech FT5x06 I2C Touchscreen support Exit and save the Kernel configuration. This is the outcome. You probably have a newer version than 19.11.4: Now you can flash the image to a SD-Card or you have to install the new DEBs. dpkg -i linux-u-boot-current-bananapipro_19.11.4_armhf.deb dpkg -i linux-dtb-current-sunxi_19.11.4_armhf.deb dpkg -i linux-image-current-sunxi_19.11.4_armhf.deb reboot The result: The LCD and the touchscreen are working. Attention! There is still the problem with the shutdown. When the patches were made for the LCD, the board did not shut down completely during a shutdown (LCD still had voltage and the red LED on the board did not go out). Workaround: We need to disable the LCD before the shutdown is finished. Therfore we have to create a script in the folder /lib/systemd/system-shutdown e.g. (as root) touch /lib/systemd/system-shutdown/lcd_off.sh chmod +x /lib/systemd/system-shutdown/lcd_off.sh nano /lib/systemd/system-shutdown/lcd_off.sh add these lines: #!/bin/bash # LCD Power PH12 H=8 (8-1)*32+12 = 236 # Backlight enable PH8 H=8 (8-1)*32+8 = 232 # Backlight PWM PB2 B=2 (2-1)*32+2 = 34 if [ ! -d "/sys/class/gpio/gpio34" ] then sudo sh -c 'echo "34" > /sys/class/gpio/export' sudo sh -c 'echo "out" > /sys/class/gpio/gpio34/direction' sudo sh -c 'echo "1" > /sys/class/gpio/gpio34/value' fi if [ ! -d "/sys/class/gpio/gpio232" ] then sudo sh -c 'echo "232" > /sys/class/gpio/export' sudo sh -c 'echo "out" > /sys/class/gpio/gpio232/direction' sudo sh -c 'echo "1" > /sys/class/gpio/gpio232/value' fi if [ ! -d "/sys/class/gpio/gpio236" ] then sudo sh -c 'echo "236" > /sys/class/gpio/export' sudo sh -c 'echo "out" > /sys/class/gpio/gpio236/direction' sudo sh -c 'echo "1" > /sys/class/gpio/gpio236/value' fi # LCD on/off sudo sh -c 'echo "0" > /sys/class/gpio/gpio34/value' sudo sh -c 'echo "0" > /sys/class/gpio/gpio232/value' sudo sh -c 'echo "0" > /sys/class/gpio/gpio236/value' The script will be executed right before the board powers off. Measured power consumption: PowerON (booting / lcd still off) = 0.4A - 0.5A LCD turns on (still booting) = 0.85A - 1.05A Boot process ended (LCD on) = 0.75A Board on, LCD off = 0.35A - 0.45A ( -> LCD needs around 0.4A power ) shutdown -h now = 0.00A 4. Control the Power of the Backlight: The backlight PWM is on PIN CON2 PB2. Following the instructions on http://linux-sunxi.org/GPIO#Accessing_the_GPIO_pins_through_sysfs_with_mainline_kernel http://forum.lemaker.org/thread-10852-1-1.html we have to export GPIO-PIN 34. (position of letter in alphabet - 1) * 32 + pin number position of letter in alphabet: B = 2 pin number: 2 ( 2 - 1 ) * 32 + 2 = 34 echo 34 > /sys/class/gpio/export echo "out" > /sys/class/gpio/gpio34/direction Power on the Backlight: echo "1" > /sys/class/gpio/gpio34/value Power off the Backlight: echo "0" > /sys/class/gpio/gpio34/value Now we could use a switch connected to a GPIO-IN to control the backlight. Steffen
  2. I got something wrong while using armbian 26.11 minimal img。Here‘s the log output from the serial: U-Boot SPL 2026.01-00340-g2549829cc194 (Oct 17 2026 - 12:22:21 +0000) SYSFW ABI: 4.0 (firmware rev 0x000b '11.2.8--v11.02.08 (Fancy Rat)') i2c_probe: pads on bus probably not configured (status=0x10) EEPROM not available at 0x50, trying to read at 0x51 i2c_probe: pads on bus probably not configured (status=0x10) Reading on-board EEPROM at 0x51 failed -121 __omap24_i2c_xfer_msg: pads on bus probably not configured (status=0x10) omap_i2c_xfer: errored out at msg 0: -121 read error from device: 41c86358 register: ?x! __omap24_i2c_xfer_msg: pads on bus probably not configured (status=0x10) omap_i2c_xfer: errored out at msg 0: -121 write error to device: 41c86358 register: ?x! esm_pmic esm: clearing ESM irqs failed: -5 ESM PMIC init failed: -5 Trying to boot from MMC2 __omap24_i2c_xfer_msg: pads on bus probably not configured (status=0x10) omap_i2c_xfer: errored out at msg 0: -121 read error from device: 41c86358 register: ?x! Loading Environment from nowhere... OK lpm will not be functional Cannot find valid LPM address range.. ti_sci system-controller@44083000: Message not acknowledged TIFS lpm save addr fail Starting ATF on ARM64 core... NOTICE: BL31: v2.14.0(release):armbian NOTICE: BL31: Built : 12:19:29, Oct 17 2026 INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: Maximum SPI INTID supported: 991 INFO: SYSFW ABI: 4.0 (firmware rev 0x000b '11.2.8--v11.02.08 (Fancy Rat)') INFO: BL31: Initializing runtime services INFO: BL31: Initializing BL32 I/TC: I/TC: OP-TEE version: f2a7ad063 (gcc version 14.2.0 (Debian 14.2.0-19)) #1 Sat Oct 17 12:20:53 UTC 2026 aarch64 I/TC: WARNING: This OP-TEE configuration might be insecure! I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html I/TC: Primary CPU initializing I/TC: GIC redistributor base address not provided I/TC: Assuming default GIC group status and modifier I/TC: SYSFW ABI: 4.0 (firmware rev 0x000b '11.2.8--v11.02.08 (Fancy Rat)') I/TC: Activated SA2UL device I/TC: Fixing background firewall owner I/TC: Enabled firewalls for SA2UL TRNG device I/TC: EIP76D TRNG initialized I/TC: SA2UL Drivers initialized I/TC: HUK Initialized I/TC: Disabling output console INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x80080000 INFO: SPSR = 0x3c9 U-Boot SPL 2026.01_armbian-2026.01-S2549-P0510-H32aa-V024c-Bb936-R448a (Oct 17 2026 - 12:23:13 +0000) Unable to shutdown MCU R5 core 1, -22 SYSFW ABI: 4.0 (firmware rev 0x000b '11.2.8--v11.02.08 (Fancy Rat)') DM ABI: 3.0 (firmware ver 0x000b 'PSDK.11.02.00.07--v11.02.07' patch_ver: 7) EEPROM not available at 0x50, trying to read at 0x51 ti_i2c_eeprom_am6_parse_record: Ignoring record id 17 Trying to boot from MMC2 U-Boot 2026.01_armbian-2026.01-S2549-P0510-H32aa-V024c-Bb936-R448a (Oct 17 2026 - 12:23:13 +0000) SoC: J721E SR1.1 GP Model: Texas Instruments J721e EVM Board: J721EX-EAIK rev E2 DRAM: 2 GiB (total 4 GiB) __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register optee optee: OP-TEE: revision 4.9 (f2a7ad0638aeff52) Core: 153 devices, 39 uclasses, devicetree: separate Flash: 0 Bytes MMC: mmc@4f80000: 0, mmc@4fb0000: 1 Loading Environment from nowhere... OK In: serial@2800000 Out: serial@2800000 Err: serial@2800000 Net: am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA00101 cpsw_ver: 0x6BA80100 ale_ver: 0x00293904 Ports:1 am65_cpsw_nuss_port ethernet@46000000port@1: RGMII mode without internal TX delay unsupported; please fix your Device Tree eth0: ethernet@46000000port@1 Hit any key to stop autoboot: 0 __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 118 __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 ** Bad device specification mmc 1 ** k3_r5f_rproc r5f@41000000: Core 1 is already in use. No rproc commands work k3_r5f_rproc r5f@41400000: Core 2 is already in use. No rproc commands work __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 ** Bad device specification mmc 1 ** Couldn't find partition mmc 1:2 Can't set block device __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 ** Bad device specification mmc 1 ** Couldn't find partition mmc 1:2 Can't set block device __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 ** Bad device specification mmc 1 ** Couldn't find partition mmc 1:2 Can't set block device __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 ** Bad device specification mmc 1 ** Couldn't find partition mmc 1:2 Can't set block device __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 ** Bad device specification mmc 1 ** Couldn't find partition mmc 1:2 Can't set block device __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 ** Bad device specification mmc 1 ** Couldn't find partition mmc 1:2 Can't set block device __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 75 ** Bad device specification mmc 1 ** Couldn't find partition mmc 1:2 Can't set block device __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 ** Bad device specification mmc 1 ** Couldn't find partition mmc 1:2 Can't set block device __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 ** Bad device specification mmc 1 ** Couldn't find partition mmc 1:2 Can't set block device __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 75 ** Bad device specification mmc 1 ** Couldn't find partition mmc 1:1 Can't set block device WARNING: Initramfs not found, continuing without initramfs __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 ** Bad device specification mmc 1 ** Couldn't find partition mmc 1:2 Can't set block device libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Bad Linux ARM64 Image magic! Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning bootdev 'mmc@4fb0000.bootdev': __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 __omap24_i2c_xfer_msg: error waiting for ACK (status=0x116) omap_i2c_xfer: errored out at msg 0: -121 pca953x gpio@22: Error reading output register Card did not respond to voltage select! : -110 mmc_init: -95, time 76 Scanning bootdev 'mmc@4f80000.bootdev': Card did not respond to voltage select! : -110 mmc_init: -95, time 37 Card did not respond to voltage select! : -110 mmc_init: -95, time 36 Card did not respond to voltage select! : -110 mmc_init: -95, time 36 cdns-usb3-host usb@6400000: DRD version v1 (ID: 0004024e, rev: 00000200) Starting the controller USB XHCI 1.00 Bus usb@6400000: 2 USB Device(s) found Scanning bootdev 'port@1.bootdev': Scanning bootdev 'port@1.bootdev': k3-navss-ringacc ringacc@2b800000: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:235 k3-navss-ringacc ringacc@2b800000: dma-ring-reset-quirk: disabled am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 3 ethernet@46000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT ! am65_cpsw_nuss_port ethernet@46000000port@1: phy_startup failed am65_cpsw_nuss_port ethernet@46000000port@1: am65_cpsw_start end error BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 BOOTP broadcast 4 BOOTP broadcast 5 BOOTP broadcast 6 BOOTP broadcast 7 Retry time exceeded; starting again No more bootdevs --- ----------- ------ -------- ---- ------------------------ ---------------- (0 bootflows, 0 valid) => What should I do?
  3. AAEON BOXER-8741AI is an industrial edge AI box PC built around the NVIDIA Jetson Thor T5000 module, delivering up to 2070 FP4 TFLOPS (sparse) of AI performance and featuring 128GB LPDDR5X memory. Designed for humanoid robotics, autonomous mobile robots (AMRs), and multi-sensor perception workloads, it features two 10GbE and four 5GbE ports, two CAN FD interfaces, RS-232/RS-485, optional GPIO, and four USB 3.2 Gen 2 ports. Expansion options include M.2 slots for NVMe storage, Wi-Fi/Bluetooth, and 4G/5G cellular connectivity. The computer supports 19V to 48V DC input and operates from -20°C to 60°C for industrial applications. AAEON BOXER-8741AI specifications: SoM – NVIDIA Jetson Thor T5000 module CPU – 14-core 64-bit ARM Neoverse-V3AE @ up to 2.6GHz GPU – 2560-core NVIDIA Blackwell GPU with 96 fifth-generation Tensor Cores, Multi-Instance GPU (MIG) support with 10 Texture Processing Clusters (TPCs) VPU Video Decode – 4x 8Kp30 (H.265), 10x 4Kp60 (H.265), 22x 4Kp30 (H.265), [...] The post AAEON BOXER-8741AI industrial Edge AI box PC NVIDIA Jetson Thor T5000 with dual 10GbE and four 5GbE LAN appeared first on CNX Software - Embedded Systems News. View the full article
  4. I've been troubleshooting a little bug all day long, and think I pretty much found it. vcc3v3_pcie20 specifies gpios = <&gpio0 RK_PC5 GPIO_ACTIVE_HIGH>, but the M.2 power switch on the Orange Pi 5 is on GPIO2_A1. The vendor DTS uses gpio2 pin 1. With the mainline value, pcie2x1l2 never links (Phy link never came up / LTSSM 0x3); changing it to <&gpio2 RK_PA1 GPIO_ACTIVE_HIGH> brings up PCIe Gen.2 x1 link up and the NVMe enumerates. This was reproduced on vendor 6.1.115, current 6.18.x, and edge 7.1.8. Workaround that I'm currently using is a little user overlay: mkdir -p /boot/overlay-user cat > /tmp/pcie-m2-power-fix.dts <<'EOF' /dts-v1/; /plugin/; / { compatible = "rockchip,rk3588"; fragment@0 { target = <&vcc3v3_pcie20>; __overlay__ { gpios = <&gpio2 1 0>; }; }; }; EOF dtc -@ -I dts -O dtb -o /boot/overlay-user/pcie-m2-power-fix.dtbo /tmp/pcie-m2-power-fix.dts Hope it helps other people as well, Stefan.
  5. WeAct Studio Logic Analyzer V2 is a low-cost, small WCH CH32H417 board designed to be used as a 16-channel USB 3.0 logic analyzer with up to 200 MHz bandwidth. The company says the board runs three different “apps”: logic analyzer, USB-serial + DAP, or custom firmware developed by the user, all located at different addresses on the flash and selected by simply pressing the button on the board. WeAct Logic Analyzer V2 board specifications: MCU – WCH CH32H417 CPU cores QingKe RISC-V5F up to 400 MHz QingKe RISC-V3F up to 144 MHz GPU – Graphics Processing Hardware Accelerator GPHA Memory – 896KB SRAM Storage – 960KB flash; 304 KB slot for “user app”/custom firmware (slot 2 @ 0x0809E000 in flash) USB – 1x USB 3.0 Type-C port for power, data, and programming Expansion header – 20-pin GPIO header with 16x GPIO, 4x GND pins Logic analyzer features (slot 0 @ [...] The post WeAct Logic Analyzer V2 – A $10 USB 3.0 logic analyzer board compatible with Sigrok/Pulseview (fork) appeared first on CNX Software - Embedded Systems News. View the full article
  6. The log shows the chip id of 0001 vs. 8800 on the 1.5 layout. This is strange, because the marking on the chip itself bears the exact same name. Maybe it contains an other silicon inside. Android log and the DTS file shows an other Wifi driver "seekwcn_sv6160lite". Luckily, retro98boy host a dkms driver , that that might work: https://github.com/retro98boy/swt6621s Furthermore, I found two different GPIOs. PCB v1.7 V1.5 sdio-pwrseq pin gpio1-7 pin gpio1-6 vcc5v0-host-regulator pin gpio4-12 pin gpio4-13 First try if changing the gpio ports and test it with the installed driver: appply this dts overlay file, reboot and and observe a change in the system log. dts-v1/; /plugin/; &{/} { compatible = "rockchip,rk3528"; sdio_pwrseq { reset-gpios = <&gpio1 7 1>; vcc5v0_host: vcc5v0-host-regulator { gpio = <&gpio4 13 0>; }; }; If that does not lead to success, install the new driver on target: #remove old dkms remove -m ea6621q -v 1.0 cd /usr/src git clone https://github.com/retro98boy/swt6621s.git mv seekwave-swt6621s seekwave-swt6621s-1.1.0 dkms add -mseekwave-swt6621s -v 1.1.0 dkms build -mseekwave-swt6621s -v 1.1.0 dkms install -mseekwave-swt6621s -v 1.1.0modify file /etc/modprobe.d/seek.conf: options skw_sdio_lite firmware_dir=seekwave options swt6621s_wifi firmware_dir=seekwave options skwbt firmware_dir=seekwave modyfy file /etc/modules-load.d/seek.conf: hidp rfcomm bnep skw_sdio_lite swt6621s_wifi skwbtApply dts overlay; dts-v1/; /plugin/; &{/} { seekwcn_sv6160lite { compatible = "seekwave,sv6160lite"; dma_type = <0x01>; status = "okay"; phandle = <0x1ca>; }; };reboot board and check: ip link system log | grep SKW not testet from my side. good success
  7. Hi everyone, I have physical access to an Orange Pi 5 Ultra with 16 GB RAM and would like to help with testing and maintenance of this board. Here is my first round of hardware testing on the current/mainline image. I am posting the working features, reproducible problems and remaining gaps separately. This is an initial test report, not a release sign-off. Image and test environmentBoard: Orange Pi 5 Ultra, RK3588, 16 GB RAM. Image: Armbian community 26.11.0-trunk.120, Ubuntu 26.04 Resolute, GNOME/Wayland, booted from microSD. Kernel: 6.18.60-current-rockchip64. Image build commit: c24ea08f8759a37aaa83a101774582c37c18eda6. Kernel, DTB and BSP packages: 26.11.0-trunk.120. Mesa: 26.0.8-1ubuntu0.3. Storage: 64 GB SDXC card using SDR104 at approximately 148.5 MHz; Samsung SSD 980 500 GB on PCIe 3.0 x4; Toshiba MQ04UBF100 1 TB USB hard disk detected at SuperSpeed 5000M. Ethernet: RTL8125B using r8169, linked to a 1 GbE LAN peer. Cooling fan present. PSU model/specification has not yet been recorded. Tests were run on 5–6 November 2026, UTC+8, using remote shell/Python automation and local hands-on cable/desktop checks. A baseline package list and boot log were saved before testing. The desktop updater subsequently updated userspace packages, including libc6 from 2.43-2ubuntu2.3 to 2.43-2ubuntu2.4. The recorded kernel/DTB packages and Mesa version remained as listed above. This should therefore not be treated as a completely untouched-image test for every later result. Additional test utilities were unpacked into a separate test directory. I do not yet have an armbianmonitor -u upload URL from this session. Redacted baseline boot, hardware and package information is included with the test evidence; a formal support report is still incomplete. Completed checksBoot and desktop: SD boot, GNOME/Wayland desktop, HDMI output, USB keyboard and mouse were usable. This covers this desktop image only, not a separate minimal/CLI image. GPU: accelerated OpenGL renderer reported Mali-G610 MC4 (Panfrost). glmark2 output validation passed. Vulkan enumeration with the Panfrost ICD and a 240-frame Wayland vkcube run completed successfully. Three short glmark2 scenes also completed; this was not the full default performance benchmark. RAM: memtester completed one full pass over 2 GiB with exit status 0 in 836.51 seconds. The highest sampled temperature during that test was 53.6°C. This is not exhaustive coverage of all 16 GB. CPU policy: three cpufreq policies were present, with observed peaks of 1.8 / 2.4 / 2.4 GHz during the memory test. The desktop tuning profile and ext4 commit=15 setting were present. A full CPU/VM soak result is still missing, as noted below. RTC: HYM8563 time reads worked. A future, minute-aligned alarm triggered the RTC hardware interrupt at the requested RTC timestamp; its IRQ counter increased from 0 to 1. This was an awake-system alarm test, not a suspend wake-up or battery-backed power-off retention test. Ethernet: TCP receive to the board was approximately 940 Mb/s and transmit from the board approximately 764 Mb/s. A bidirectional run also completed. IPv4, IPv6 and 1500-byte-MTU ping checks passed. The peer was limited to 1 GbE, so 2.5 GbE throughput was not validated. Storage checksfio 3.41 was used for bounded tests. SD and USB file tests used 1 MiB blocks, direct I/O, libaio queue depth 16 and CRC32C write/read verification. The NVMe test used direct, read-only access with a 4 GiB working set for 15 seconds. Rates below are decimal MB/s. Device / scope Write Read Result SD, 2 GiB file 24.75 MB/s 65.81 MB/s CRC32C verification passed USB hard disk, 1 GiB file, first USB 3 port 59.08 MB/s 138.65 MB/s CRC32C verification passed NVMe, read-only Not tested 1403.87 MB/s Read test passed; health queries completed The SD and USB 4 KiB random-read tests also completed. No new storage-related kernel errors were found during this test interval. These tests do not cover the entire capacity of the media. NVMe write verification and the second USB 3 port remain untested. Open finding 1: onboard Wi-Fi interface is missingAt baseline, Ethernet and Bluetooth were present but no WLAN interface or wireless PHY appeared. The installed bcmdhd-sdio-dkms package was built for the running kernel, while the SDIO bus had no enumerated device. The live device tree contained: mmc@fe2d0000 { status = "disabled"; };Observed package/driver state: bcmdhd-sdio-dkms: 101.10.591.52.27-10 bcmdhd-sdio/101.10.591.52.27-10, 6.18.60-current-rockchip64, aarch64: installed iw dev / iw phy: no wireless interface or PHY listed /sys/bus/sdio/devices/: emptyThe vendor board DTS contains SDIO enablement and a Wi-Fi power sequence. Missing board-level SDIO/power-sequence description is a suspect; no proposed fix or overlay has been runtime-tested in this session. Open finding 2: HDMI input self-loop did not lockWith no independent HDMI source available, I connected this board's HDMI OUT to its HDMI IN. A fullscreen colour-bar pattern was generated, and the receiver was given the v4l2-ctl HDMI EDID preset. DRM state confirmed a 1920×1080 at 60 Hz RGB 8 bpc transmitter mode, with a 148.5 MHz TMDS clock. The receiver reported power_present=1, but v4l2-ctl --query-dv-timings failed with “No locks available”. The kernel logged: hdmirx_phy_register_write wait cr write done failed hdmirx_controller_init wait timer base lock failed hdmirx_query_dv_timings: signal is not lockedThe HDMI RX HDMI/DMA IRQ counters stayed at zero while the 5V-detect GPIO IRQ counter increased. Unloading/reloading synopsys_hdmirx and reapplying the test EDID reproduced the same result. The original receiver EDID and monitor connection were restored afterward. This is a reproducible self-loop observation on this setup, not proof that every external HDMI source will fail. Testing with an independent source and checking a clean cold boot remain necessary. Relevant earlier changes include #10172 and the 6.18 patch adjustment #10180. Incomplete and intentionally omitted checksA 15-minute all-CPU plus 4 GiB VM verification run was started, but no final completion record has been collected. The last collected progress line was around 58 seconds. I am not counting this soak as passed. Later, new SSH connections were closed before authentication while the board still answered LAN pings. The cause has not been established, and I am not attributing it to the load test or kernel without further evidence. Bluetooth firmware loading, discovery and three rfkill recovery cycles were observed; pairing and data transfer were not validated. Further Bluetooth testing was intentionally skipped. Actual audio playback/capture, the second USB 3 port, repeated warm/cold boot recovery, RTC power-off retention, other images/kernel branches and additional header/camera interfaces remain outside this completed test set. Maintenance interestI would like to contribute release-image testing and reproducible board reports for the Orange Pi 5 Ultra. In particular, #10673 explicitly noted missing Ultra/Linux 6.18 runtime coverage, and #11157 reported no board hardware testing for the CPU policy changes. The observations above provide some additional runtime evidence, with the limitations stated. I have saved the scripts, package inventories and logs, and can provide specific redacted excerpts. Guidance on the highest-priority follow-up tests and the board-maintainer application process would be appreciated. KingFalse orangepi5-ultra-6.18-first-round-evidence.zip
  8. @CD38 Hi, Unfortunately, the x88pro13 is manufactured by various companies, often featuring different Wi-Fi chips and modified board layouts. I own an older board with an LGX8800 Wi-Fi chip, and have access to a V1.5 board equipped with an EA6521Q chip. Since your image also shows an EA6521Q chip, the driver on https://github.com/joilg/ea6x21-dkms.git should be fine, it is also included in my x88pro image . The PCB layout in the WiFi section differs significantly from that of version 1.5. I assume that the connections for the WiFi control GPIOs have been changed. Due to the modified board layout, it may be necessary to change the GPIO assignments in the dts. I cannot find any specifically assigned GPIOs for the Seekwave driver in your DTS file. They are likely hardcoded into the Android driver. First, check whether the chip is responsive. root@x88pro:~# dmesg | grep SDIO [ 1.726067] mmc2: new UHS-I speed SDR104 SDIO card at address 8800 address 8800 is the Chip ID of the EA6521Q. this is independent of the wifi driver, and controled from sdio_pwrseq , gpio1 6, which is the same in 1.7 dts. If you have access to the Android command line, for example, via ADB, the following commands could be helpful to inpect used Pins adb shell su gpioinfo cat /sys/kernel/debug/gpio cat /sys/kernel/debug/pinctrl/pinctrl-maps dmesg | grep skwyou can change the gpios numbers with dts overlays. Create a DTS overlay file rk3528-skw.dts: dts-v1/; /plugin/; &{/} { compatible = "rockchip,rk3528"; seekwcn_boot { gpio_host_wake = <&gpio1 18 1>; gpio_chip_wake = <&gpio1 17 1>; }; sdio_pwrseq { reset-gpios = <&gpio1 6 1>; };and apply it with: sudo armbian-add-overlay rk3528-skw.dts rebootPlay around with the GPIOs pins. <&gpio1 16 1> are used in some other rockchip boards. view dmesg | grep skw for anny changes on other gpios. please paste the debug Info to pastebin and show the link here with: armbianmonitor -u good luck with the testing johilg
  9. As sort of conclusion, whether wanting grub-efi or not, there is another discovery w.r.t. DS18B20 temperature sensor(s) hooked up to 1-wire. On the Allwinner H3 the default SoC pad/pin is PD14 but that is not wired on the NanoPi-NEO. Via U-Boot scripting, including the fixup.scr and armbianEnv.txt (see boot.cmd how it works) I select PG11. However, extlinux bootmethod that I tend to use besides EFI in KVM, does not support parameter like this. And grub-efi when in KVM needs valid EFI partition which confuses modern U-Boot in a standard configuration. I managed to build a 7.3.3 sunxi kernel+dtbo with that PG11 as default, but it is by hacking the already downloaded sun8i-h3-w1-gpio.dtso file. I made also a patch via kernel-patch first, but I understand now that this patch is against the mainline kernel and not on top of or after the sunxi Armbian overlays for 32-bit. At least it does not work. Maybe I do something wrong w.r.t. Armbian Build, but I think I would need something like 'patch the armbian patch'. Anyway, 1 reason an extra FAT formatted boot partition is used for computers, is that Windows cannot handle Linux filesystems. But I do not use Windows, except a few times per year in a KVM on x86_64 to scan/digitize paper and maybe some unknown old electronics that has no Linux user program. This also means, if kernel crash due to overlay and/or specific HW, extlinux cannot be used to select older kernel ad-hoc. With boot.scr, it would need break autoboot via serial console and then select/load a previous kernel etc via a sequence of u-boot commands, which I once did, but all forgotten now, was in relation to soldered eMMC. For SD-cards, way easier to take out SD-card of-course unless you have glued it which I read once someone did. So I now use this on one of my 24/7 NanoPi-NEO's with just the standard boot.scr+ambianEnv.txt: # gdisk -l /dev/mmcblk0 GPT fdisk (gdisk) version 1.0.10 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/mmcblk0: 62357504 sectors, 29.7 GiB Sector size (logical/physical): 512/512 bytes [...] Partition table holds up to 56 entries Main partition table begins at sector 2 and ends at sector 15 First usable sector is 16, last usable sector is 62357488 Partitions will be aligned on 16-sector boundaries Total free space is 49766385 sectors (23.7 GiB) Number Start (sector) End (sector) Size Code Name 1 532480 13115391 6.0 GiB 8300 Linux filesystem 5 16 8191 4.0 MiB B000 U-Boot boot loader gdisk x l allows sector alignment set to 1 gdisk x s allows resizing partition table I figured out that max 56 partitions is max, so up to sector 16 where the H3/sun8i bootloader starts. The Armbian H3 images rootfs starts at sector 8192. Also nice then to put some protection around that area with a type 0xB000 allocation. This way, it is a bit more convenient to wipe and write u-boot if you hate the dd numbering/arguments. For easy trimming free space (with blkdiscard), I also used to allocate a type 0 partition at the end with high number, but it assumes sub-optimal SD-card internal garbage collection or whatever code is in there. Also good for figuring out if SD-card is counterfeit or so. One normally should not worry about wear-leveling, maybe more about leaving hidden data there. Bigger rootfs is easiest as then fstrim.timer does the job, but old habit of keeping rootfs partition small also plays a role here for me.
  10. Lumissil Microsystems IS31CS9202 and IS32CS9202 are 50 MHz Cortex-M0+ microcontrollers for industrial, consumer, and automotive applications with a serial video bus (SVB), a LumiBus LED controller, and a capacitive touch-key controller. Both chips come with 16KB RAM, 256KB flash, a CAN FD controller, SPI master/slave, I2C master/slave, two enhanced UART interfaces, a quadrature encoder, a 14-bit sigma-delta ADC, a 12-bit SAR ADC, an 8-bit DAC, up to 42 GPIO pins, and more. The only differences are that the IS32CS9202 is designed for automotive applications and benefits from a wider -40°C to 125°C temperature range and AEC-Q100 and ASIL-B qualifications. Lumissil IS31CS9202/IS32CS9202 key features and specifications: CPU – Arm Cortex-M0+ core up to 50MHz Memory – 16KB RAM with ECC 8KB for data memory 8KB for DMA memory Storage 256KB flash with four 1KB IFBs (Information Blocks) with ECC Data flash emulation 1K/ 10K/100K cycles endurance @ 125, 105, 85°C 10 [...] The post Lumissil IS31CS9202/IS32CS9202 Cortex-M0+ MCUs integrate serial video bus (SBV), LumiBus, and capacitive touch-key controller appeared first on CNX Software - Embedded Systems News. View the full article
  11. Follow-up: Ubuntu Resolute Minimal .128 validation (11 November 2026) I have completed another bounded validation run on my Orange Pi 5 Ultra, complementing the earlier Debian results. Image: Armbian_26.11.0-trunk.128_Orangepi5-ultra_resolute_vendor_6.1.172_minimal.img.xz Ubuntu 26.04 Resolute Minimal; kernel 6.1.172-vendor-rk35xx; build commit e5a400a. Hardware: 16 GB RAM, approximately 59.5 GiB SD card, root filesystem on /dev/mmcblk1p1. The imported first-boot preset was consumed successfully. Ethernet, Wi-Fi and automatic NTP synchronization worked. Initial IPv6 NTP queries timed out, then IPv4 fallback synchronized the clock around 52 seconds after boot. Area Result Memory PASS: one locked 2 GiB memtester pass; all 18 checks completed successfully. CPU / VM PASS: approximately 15 minutes, eight CPU workers plus one 4 GiB VM worker with verification; peak 76.7 C. SD storage PASS: 2 GiB CRC32C file verification; write 23.74 MiB/s, verification read 64.23 MiB/s. NVMe PASS: unmounted, raw read-only test at 1,568.35 MiB/s; no host-written sector increase. Network Functional PASS: 12/12 checks; Ethernet and Wi-Fi observations detailed below. RTC PASS: HYM8563 future-minute alarm fired, incremented its interrupt counter, and was cleared. HDMI / keyboard PASS: visible console refresh and USB keyboard Enter response confirmed manually. HDMI audio PASS: 48 kHz S16_LE stereo playback; left and right channels confirmed audible manually. Boot persistence Core PASS: two warm reboots and one cold boot after approximately 30 seconds without power. Stock Bluetooth FAIL: missing rfkill / BlueZ; details below. Ethernet negotiated 1 Gb/s with my router. Separate TCP tests measured approximately 937 Mb/s board RX and 771 Mb/s board TX. Wi-Fi measured approximately 326 Mb/s RX and 373 Mb/s TX. RX means router to board; TX means board to router. These are receiver-reported decimal Mbit/s, not MiB/s. The peer cannot validate 2.5GbE performance. Wi-Fi accumulated 232 additional TX drops during testing, with retransmissions. The iw RX packet count was also inconsistent with kernel interface counters. Similar observations already existed in my Debian .127 evidence; this does not establish a new Ubuntu regression. HDMI controller state was 2560x1440p59.95. Reboot checks confirmed changed boot IDs, the expected SD root, working network, synchronized NTP and an unchanged installed-package set. Test utilities and their libraries came from 61 DEBs in the configured Ubuntu/Armbian repositories, extracted into a separate directory. No test packages were installed into the system. The stock image lacks rfkill and BlueZ clients. ap6611s-bluetooth.service fails at ExecStartPre with 203/EXEC before firmware loading. I did not patch this image, and Bluetooth pairing remains untested. This Ubuntu image was uploaded at 03:24 UTC on 11 November, before dependency-fix PR #11331 merged at 05:26 UTC: https://github.com/armbian/build/pull/11331 This confirms the packaging problem in the older image; it does not validate the merged fix on Ubuntu. I am keeping this result with the existing issue rather than opening a duplicate. Power supply rating: 5 V / 5 A. Two ML307 modules and one 2454 radar remained GPIO powered, with unchanged wiring. Their serial functions and power margin were not tested. No USB storage device was connected this round. Not covered: USB storage/other ports, HDMI input, GPU rendering, codecs, NPU inference, camera/MIPI, eMMC/SPI or NVMe boot, analog audio, mouse interaction, RTC battery retention, full-capacity RAM/media testing, or extended stability. Command execution, evidence collection and log review were AI-assisted. I performed the physical actions and confirmed the display, keyboard and audio observations. This is bounded single-board testing, not full release certification. Selected redacted evidence archive: orangepi5-ultra-ubuntu128-validation-evidence.zip KingFalse orangepi5-ultra-ubuntu128-validation-evidence.zip
  12. This week's work centers on a large-scale kernel CVE backporting program for the 6.1 and 6.12 LTS series, a CPU tuning and frequency framework overhaul, and sustained board, SoC, and vendor-kernel maintenance across the Rockchip, MediaTek, and Allwinner ecosystems. The CVE effort dominates activity, with more than one hundred reviewed backport sets landing across 6.1 and 6.12 covering networking (mac80211, cfg80211, Bluetooth, netfilter, mlx5, stmmac), filesystems (btrfs, f2fs, ext4, smb client, ksmbd), virtualization (KVM SVM/SEV, vhost, virtio), graphics (amdgpu, i915, vc4, msm), and core subsystems (bpf, mm, io_uring). Supporting this is a new fasttrack CI pipeline with per-series sharding, build-time header-change verification, triage records for not-affected verdicts, and tagged releases on each patch set change. The configurations repository has been updated to enable kernel CVE fixes across builds. Platform work introduces a new per-cluster cpufreq and tuning-profile system that replaces cpufrequtils with image-level profiles, exposed through configng. Board additions include the Seeed reComputer Industrial RK3576, Boardcon EM3588, CZ.NIC Turris Omnia, Hardkernel ODROID-U2/U3/X2, and the DshanPi A1 CM5, while Rockchip vendor kernels gain NPU enablement on Orange Pi CM5, ArmSoM CM5-IO and Rock 4D, along with CAN-FD support for the RK3576. MediaTek Filogic boards move to the 6.18 LTS kernel with U-Boot 2026.10, the Anbernic RG DS and RG Vita Pro receive charge-screen and USB fixes, and the UWE5622 wireless driver sees fixes for memory corruption, teardown, and TCP ACK stalls. #Armbian #EmbeddedLinux #Rockchip #KernelSecurity #CVE #MediaTek ChangesCVE-2026-98432: backport fix for pinned / vendor kernel. by @EvilOlaf in armbian/build#11153.github: generate_CODEOWNERS: point family rules at config/sources/families. by @iav in armbian/build#11128Add Boardcon EM3588 board support. by @boardcon-arm in armbian/build#11089add NPU support for orangepi-cm5. by @ECO1AI in armbian/build#11131Add reComputer Industrial RK3576. by @mingzhangqun in armbian/armbian.github.io#526Add RM66 vendor CLI and XFCE images. by @RiPetitor in armbian/armbian.github.io#505Add Seeed Studio reComputer Industrial RK3576 board. by @mingzhangqun in armbian/build#11136Add Seeed Studio reComputer Industrial RK3576 support. by @mingzhangqun in armbian/linux-rockchip#603add support for CSI cameras:. by @ECO1AI in armbian/build#11138Add support for CZ.NIC Turris Omnia (Armada 385). by @BKPepe in armbian/build#11137Add support for Hardkernel ODROID-U2/U3/X2 (Exynos4412). by @BKPepe in armbian/build#11132Add Torder R10D board image and vendor logo. by @JasonYANG170 in armbian/armbian.github.io#529anbernic-rg-ds: show a charge screen instead of booting when a charger is plugged in. by @crackerjacques in armbian/build#11106anbernic-rg-vita-pro: fix USB host and charging on edge 7.3 (sgm41542). by @crackerjacques in armbian/build#11125anbernic-rg-vita-pro: off-charge: port the RG DS charge-screen fixes. by @crackerjacques in armbian/build#11126armsom-cm5-io: add edge kernel with mainline U-Boot. by @gahingwoo in armbian/build#11097armsom-cm5-io: enable the NPU on edge, with the RK3576 NPU series. by @gahingwoo in armbian/build#11162ath10k: add QCA988X hw2.0 firmware. by @BKPepe in armbian/firmware#155attempts: 6.1 batch 1, 38 not affected and 4 failed. by @igorpecovnik in armbian/cve#86attempts: 6.1 batch 2, 31 not affected and 2 failed. by @igorpecovnik in armbian/cve#92attempts: 6.1 batch 5, 21 not affected and 13 failed. by @igorpecovnik in armbian/cve#120attempts: 6.1 batch 6, 9 not affected and 4 failed. by @igorpecovnik in armbian/cve#131attempts: 6.1 batch 7, 2 not affected and 1 failed. by @igorpecovnik in armbian/cve#147attempts: 6.1 batch 8, 4 not affected and 2 failed. by @igorpecovnik in armbian/cve#157attempts: 6.1 batch 9, 3 not affected. by @igorpecovnik in armbian/cve#163attempts: 6.1 batches 3-4, 47 not affected and 7 failed. by @igorpecovnik in armbian/cve#107attempts: 6.12 batch 1, 22 not affected and 3 failed. by @igorpecovnik in armbian/cve#43attempts: 6.12 batch 2, 18 not affected and 2 left out. by @igorpecovnik in armbian/cve#49attempts: 6.12 batch 3, 11 not affected and 3 failed. by @igorpecovnik in armbian/cve#58attempts: 6.12 batches 4-5, 9 not affected and 1 failed. by @igorpecovnik in armbian/cve#79attempts: record triage of failed 6.1 and 6.12 attempts. by @igorpecovnik in armbian/cve#188aw859a: stop advertising park mode in bt_configure_pskey.ini. by @lukaszsobala in armbian/firmware#154board-images: add ODROID-U2, ODROID-U3 and ODROID-X2. by @BKPepe in armbian/armbian.github.io#520board-images: add Turris MOX. by @BKPepe in armbian/armbian.github.io#527board-images: add Turris Omnia and the CZ.NIC logo. by @BKPepe in armbian/armbian.github.io#521board-images: replace blurry ODROID-N2L image. by @BKPepe in armbian/armbian.github.io#525board: firefly-aibox-k3: promote to community supported. by @leoppark94 in armbian/build#11140boards/radxa-dragon-q6a: install EDK2 package once the Armbian repo is on. by @SuperKali in armbian/build#11182boards: add DshanPi A1 CM5 on the Waveshare CM5-to-Pi5-Adapter. by @sckiyo in armbian/build#11096build check: blame a header change, not the patch on the file. by @igorpecovnik in armbian/cve#171build check: compile .c files that include a changed header. by @igorpecovnik in armbian/cve#94build-framework: document TUNING_PROFILE and per-cluster CPU settings. by @igorpecovnik in armbian/documentation#1708build-test: stack new cve/ backports in made order. by @igorpecovnik in armbian/cve#44build-test: test a cve/ series on top of the patch set. by @igorpecovnik in armbian/cve#31build-test: test the cve/ set as the change has it. by @igorpecovnik in armbian/cve#172ci: build-test: start one shard per changed series. by @igorpecovnik in armbian/cve#26ci: bump actions, keep them current with Dependabot. by @igorpecovnik in armbian/cve#25ci: fasttrack: check out the branch tip. by @igorpecovnik in armbian/cve#63ci: fasttrack: free the runner below 40 GB. by @igorpecovnik in armbian/cve#37ci: fasttrack: pass dispatch inputs through env. by @igorpecovnik in armbian/cve#179ci: fasttrack: publish only results of the current cve/ and tool. by @igorpecovnik in armbian/cve#180ci: fasttrack: verify each series in its own job. by @igorpecovnik in armbian/cve#52ci: run the fasttrack unit tests. by @igorpecovnik in armbian/cve#203ci: start fasttrack on a merged backport, fix concurrency. by @igorpecovnik in armbian/cve#51configs: enable kernel CVE fixes. by @igorpecovnik in armbian/ci#105cpufreq, tuning: per-cluster board settings and a tuning profile per image. by @igorpecovnik in armbian/build#11157cpufreq, tuning: replace cpufrequtils and fixed tuning with board settings and profiles. by @igorpecovnik in armbian/build#11156cve --unpatched: resolve each CVE only on the series where it is open. by @igorpecovnik in armbian/cve#178cve: 6.1 backports, af_unix, ipv4, ipv6, neighbour, netlink, codel, skbuff, af_packet, mctp. by @igorpecovnik in armbian/cve#139cve: 6.1 backports, amd display, amdgpu, vc4, i915, altera EDAC. by @igorpecovnik in armbian/cve#153cve: 6.1 backports, amdgpu, amd display, v3d, ALSA, ext4, f2fs, ocfs2. by @igorpecovnik in armbian/cve#118cve: 6.1 backports, amdgpu, virtio-gpu, gud, cirrus, fbdev, ACPI. by @igorpecovnik in armbian/cve#130cve: 6.1 backports, arm64 ioremap_prot. by @igorpecovnik in armbian/cve#105cve: 6.1 backports, arm64 percpu, kprobes, tracing, bpf, keys, ALSA, sd_zbc, EDAC, rtc, HID. by @igorpecovnik in armbian/cve#143cve: 6.1 backports, bcmsysport, mlx5, stmmac, sparx5, mt7915. by @igorpecovnik in armbian/cve#151cve: 6.1 backports, Bluetooth mgmt, ipc mqueue, netlink. by @igorpecovnik in armbian/cve#161cve: 6.1 backports, Bluetooth, sock, seg6, GSO, virtio_net, vsock, flowtable. by @igorpecovnik in armbian/cve#150cve: 6.1 backports, bpf LSM return range. by @igorpecovnik in armbian/cve#85cve: 6.1 backports, bpf, calipso, erofs. by @igorpecovnik in armbian/cve#184cve: 6.1 backports, bpf, perf, sched, reboot, iommu/amd, PCI sysfs. by @igorpecovnik in armbian/cve#126cve: 6.1 backports, cfg80211, ath11k, ath9k_htc. by @igorpecovnik in armbian/cve#145cve: 6.1 backports, cpuset, namespace, btrfs, xfs, power supply, bpf. by @igorpecovnik in armbian/cve#152cve: 6.1 backports, crypto, iommu, amd-pmc, fbcon, usb phy, atomisp. by @igorpecovnik in armbian/cve#99cve: 6.1 backports, dm-raid, iommu, amdkfd, gve, msm, thermal, fman, imx6, i2c. by @igorpecovnik in armbian/cve#84cve: 6.1 backports, f2fs node footer, most core. by @igorpecovnik in armbian/cve#100cve: 6.1 backports, f2fs shutdown, bpf pkt_data, rdma netdev. by @igorpecovnik in armbian/cve#91cve: 6.1 backports, f2fs, btrfs, hfs, ceph, dm, sysfs, ksmbd. by @igorpecovnik in armbian/cve#97cve: 6.1 backports, generic driver_override for 6 buses, x_tables. by @igorpecovnik in armbian/cve#108cve: 6.1 backports, gpio, genirq, imx mailbox, arm_scmi, 8250_of, i3c. by @igorpecovnik in armbian/cve#116cve: 6.1 backports, gtp/tunnels, qdisc, bridge, rtnetlink, wireguard, nf_tables, 8021q, rxrpc, nl80211. by @igorpecovnik in armbian/cve#103cve: 6.1 backports, igmp, ipv6 mcast, udp6, bridge mcast, altnames, rtnetlink. by @igorpecovnik in armbian/cve#123cve: 6.1 backports, kcm, espintcp, xfrm, nf_tables, bpf, wifi. by @igorpecovnik in armbian/cve#98cve: 6.1 backports, KVM SVM, nVMX, SEV, async PF. by @igorpecovnik in armbian/cve#155cve: 6.1 backports, KVM, bpf, perf, page_owner, nx, PCI sysfs. by @igorpecovnik in armbian/cve#115cve: 6.1 backports, lan966x, xprtrdma, irdma, mac80211, iwlwifi, mt7921, Bluetooth ISO, rtl8723bs, af_unix, ksmbd. by @igorpecovnik in armbian/cve#114cve: 6.1 backports, libata, KVM SVM, efa, kprobes, iio, bpf, nx, ksmbd, xfs, ctxfi, rtl8723bs, netfs, coresight, amdkfd, amdgpu. by @igorpecovnik in armbian/cve#104cve: 6.1 backports, mac80211. by @igorpecovnik in armbian/cve#138cve: 6.1 backports, md noio, dm-integrity keyed discard (reworked). by @igorpecovnik in armbian/cve#156cve: 6.1 backports, mlx5e uplink and teardown. by @igorpecovnik in armbian/cve#101cve: 6.1 backports, mm, block, md, ext4, f2fs, btrfs. by @igorpecovnik in armbian/cve#87cve: 6.1 backports, mm, btrfs, io_uring, virtiofs, udmabuf. by @igorpecovnik in armbian/cve#83cve: 6.1 backports, msm, vc4, amdkfd, amdgpu, virtio-gpu. by @igorpecovnik in armbian/cve#141cve: 6.1 backports, mtk_eth_soc, smb client. by @igorpecovnik in armbian/cve#158cve: 6.1 backports, nfsd, btrfs, configfs, ublk. by @igorpecovnik in armbian/cve#125cve: 6.1 backports, nvme, iio, ice1712, usx2y, erdma, vhost-vdpa, mmc hsq. by @igorpecovnik in armbian/cve#127cve: 6.1 backports, own design, needs review: ASoC SOF Intel. by @igorpecovnik in armbian/cve#181cve: 6.1 backports, own design, needs review: bpf trampoline. by @igorpecovnik in armbian/cve#154cve: 6.1 backports, own design, needs review: ima, ipheth, cc2520, vgic, nfsd, io_uring, bpf, ksmbd. by @igorpecovnik in armbian/cve#128cve: 6.1 backports, own design, needs review: inet frags, nvme, md. by @igorpecovnik in armbian/cve#185cve: 6.1 backports, own design, needs review: khugepaged. by @igorpecovnik in armbian/cve#162cve: 6.1 backports, own design, needs review: mac80211, skb defer, bpf, nvme. by @igorpecovnik in armbian/cve#146cve: 6.1 backports, own design, needs review: workqueue disable API. by @igorpecovnik in armbian/cve#197cve: 6.1 backports, own design, reviewed: resctrl, cxl, zram, cec. by @igorpecovnik in armbian/cve#119cve: 6.1 backports, pmbus, atmel-mci, vmbus, nvme, amd-pstate-ut. by @igorpecovnik in armbian/cve#117cve: 6.1 backports, sctp, stmmac, btintel, L2CAP, tipc, xfrm, dsa, vsock. by @igorpecovnik in armbian/cve#124cve: 6.1 backports, smb client and ksmbd. by @igorpecovnik in armbian/cve#88cve: 6.1 backports, smb client, btrfs, hugetlb, damon, ntfs3, io_uring, bootconfig. by @igorpecovnik in armbian/cve#142cve: 6.1 backports, SMB client, f2fs, udf. by @igorpecovnik in armbian/cve#187cve: 6.1 backports, smb client, ksmbd. by @igorpecovnik in armbian/cve#129cve: 6.1 backports, tiny SRCU irq_work, x86-64 copy_user. by @igorpecovnik in armbian/cve#106cve: 6.1 backports, virtio_ring, vdpa, vhost, vduse, KVM, swiotlb. by @igorpecovnik in armbian/cve#140cve: 6.1 backports, vxlan, stmmac, ice, bcmgenet, hci_qca, mtk_eth_soc, macsec, mt7530, gve. by @igorpecovnik in armbian/cve#144cve: 6.1 backports, wifi, mlx5e, amdgpu, drm, hyperv fb, driver core, bpf, riscv. by @igorpecovnik in armbian/cve#89cve: 6.1 backports, zswap. by @igorpecovnik in armbian/cve#90cve: 6.1 fixes from the second review of 357 backports. by @igorpecovnik in armbian/cve#202cve: 6.1 fuse export fix, drop CVE-2026-43115. by @igorpecovnik in armbian/cve#167cve: 6.1, 6.12 backports, own design, needs review: conntrack helper refcount. by @igorpecovnik in armbian/cve#190cve: 6.12 backports, 8021q and netfilter. by @igorpecovnik in armbian/cve#45cve: 6.12 backports, amdgpu, xe, vc4, i915. by @igorpecovnik in armbian/cve#77cve: 6.12 backports, amdkfd, msm, rzv2h watchdog, btrfs, fs. by @igorpecovnik in armbian/cve#69cve: 6.12 backports, arm64 driver, coresight, i3c, iommu. by @igorpecovnik in armbian/cve#47cve: 6.12 backports, arm64, CXL, ctxfi, amdgpu. by @igorpecovnik in armbian/cve#42cve: 6.12 backports, bcmgenet, stmmac, fbnic, hci_qca, erdma. by @igorpecovnik in armbian/cve#67cve: 6.12 backports, block, mm, sched, bpf, KVM. by @igorpecovnik in armbian/cve#40cve: 6.12 backports, Bluetooth and veth. by @igorpecovnik in armbian/cve#41cve: 6.12 backports, bpf trampoline. by @igorpecovnik in armbian/cve#74cve: 6.12 backports, bpf verifier and pci-sysfs. by @igorpecovnik in armbian/cve#59cve: 6.12 backports, bpf, arm64 KVM, powerpc nx. by @igorpecovnik in armbian/cve#46cve: 6.12 backports, bpf, blk-mq, cpuset, namespace, ipc. by @igorpecovnik in armbian/cve#75cve: 6.12 backports, bpf, sched, x86 kprobes, KVM. by @igorpecovnik in armbian/cve#68cve: 6.12 backports, cfg80211 and mac80211. by @igorpecovnik in armbian/cve#71cve: 6.12 backports, ext4, btrfs, smb client, io_uring, xsk. by @igorpecovnik in armbian/cve#54cve: 6.12 backports, f2fs and ksmbd. by @igorpecovnik in armbian/cve#39cve: 6.12 backports, ipv6, neighbour, af_unix, netlink, codel, vsock. by @igorpecovnik in armbian/cve#66cve: 6.12 backports, irdma, nvme, iio, mt76, renesas. by @igorpecovnik in armbian/cve#57cve: 6.12 backports, ksmbd. by @igorpecovnik in armbian/cve#65cve: 6.12 backports, KVM SEV, resctrl, amd-pstate, riscv. by @igorpecovnik in armbian/cve#55cve: 6.12 backports, net core, virtio_net, stmmac, gve, macsec. by @igorpecovnik in armbian/cve#76cve: 6.12 backports, netfs and f2fs. by @igorpecovnik in armbian/cve#50cve: 6.12 backports, nouveau, amdgpu, tas2781, perf. by @igorpecovnik in armbian/cve#48cve: 6.12 backports, serial, nvme, power_supply, gpio, riscv, KVM SEV, regulator. by @igorpecovnik in armbian/cve#78cve: 6.12 backports, smb client. by @igorpecovnik in armbian/cve#70cve: 6.12 backports, smb client and KVM SVM. by @igorpecovnik in armbian/cve#80cve: 6.12 backports, xe, amdgpu, v3d, fbdev. by @igorpecovnik in armbian/cve#56cve: 6.12 fixes from the second review of shipped backports. by @igorpecovnik in armbian/cve#194cve: 6.18 fixes from the second review of shipped backports. by @igorpecovnik in armbian/cve#193cve: add missing mainline follow-ups to 6.1 and 6.12 backports. by @igorpecovnik in armbian/cve#198cve: complete CVE-2026-98180 on 6.1 and 6.12 with the dma-fence name helpers. by @igorpecovnik in armbian/cve#199cve: keep an earlier backport on a partial result. by @igorpecovnik in armbian/cve#174cve: manual backports for 12 CVEs on 6.18 and 7.3. by @igorpecovnik in armbian/cve#24cve: rebase 10 backports on the 6.18 patch set. by @igorpecovnik in armbian/cve#29cve: restore upstream trailers in 7 backports on 6.12. by @igorpecovnik in armbian/cve#61cve: second review of not-affected verdicts, CVE-2026-98718 6.12. by @igorpecovnik in armbian/cve#170d1: follow the Linux 7.3 stable branch. by @khaliforce in armbian/build#11152docs: short README, move how it works to DEVELOPMENT.md. by @igorpecovnik in armbian/cve#28dshanpi-r1: move to U-Boot v2026.07, add mainline DTS and the R1+. by @sckiyo in armbian/build#10892dtoverlays: support a list of overlay prefixes. by @lukaszsobala in armbian/configng#1067eltay-rm66: add PDM microphone overlay. by @RiPetitor in armbian/build#11122eltay-rm66: add PWM fan control. by @RiPetitor in armbian/build#11123eltay-rm66: update U-Boot to v2026.10. by @RiPetitor in armbian/build#11147engine: place a carried mainline pick before its backport set. by @igorpecovnik in armbian/cve#208extensions/ffmpeg-v4l2-request: fix config-phase abort and declare the prebuilt's full runtime. by @Novice-PG in armbian/build#11124fasttrack: no build-test run on the bot's patches PR. by @igorpecovnik in armbian/cve#135fasttrack: only igorpecovnik may run Claude. by @igorpecovnik in armbian/cve#132fasttrack: reject stray .orig and .rej files. by @igorpecovnik in armbian/cve#112fasttrack: run Claude in environment claude. by @igorpecovnik in armbian/cve#133fasttrack: use an absolute work package path. by @igorpecovnik in armbian/cve#23feat(api): attach companion files from file_companion. by @SuperKali in armbian/website#65Featured feed: one dated JSON for website, imager and motd. by @igorpecovnik in armbian/armbian.github.io#208filogic: add edge kernel to BPI-R4. by @igorpecovnik in armbian/build#11173filogic: move BPI-R4 to U-Boot v2026.10, halt on shutdown. by @igorpecovnik in armbian/build#11169filogic: move current kernel to 6.18 LTS for BPI-R4 and BPI-R3 Mini. by @igorpecovnik in armbian/build#11170filogic: remove unused legacy kernel. by @igorpecovnik in armbian/build#11174fingerprint: include attempts.json. by @igorpecovnik in armbian/cve#173followups: list mainline follow-ups the patch sets miss. by @igorpecovnik in armbian/cve#195generate-armbian-images-json: detect companion files generically. by @SuperKali in armbian/armbian.github.io#530genio-7.3: disable ASP FSM parity to fix Ethernet reset loops. by @rbrok in armbian/build#11167git-ref2info: fetch the Makefile from any mirror of the source. by @iav in armbian/build#11172git-ref2info: leave the Makefile version out on unknown git hosts. by @iav in armbian/build#11143Github Action: Add input for userpatch configuration name suffix. by @pykpkg47 in armbian/build#11146Integrate patches from framework directly into 6.1 vendor source. by @EvilOlaf in armbian/linux-rockchip#607integrate patches from the framework directly into 6.12 vendor sources. by @EvilOlaf in armbian/linux-rockchip#606kernel-debs: image: skip dkms hook while headers are unconfigured. by @lukaszsobala in armbian/build#11119kernel: 6.1: zswap: do not allocate from atomic pool. by @igorpecovnik in armbian/build#11171Lenovo y700 gen4 next. by @retro98boy in armbian/build#11104lore: take a stable-list post only when it backports the fix itself. by @igorpecovnik in armbian/cve#200map: key assets on their redi_url. by @SuperKali in armbian/armbian-router#44net: can: rockchip: backport CAN-FD support for rk3576_can + TX queue wedge fix. by @mingzhangqun in armbian/linux-rockchip#610odroidm1: u-boot: enable EFI_RT_VOLATILE_STORE (runtime SetVariable). by @excavador in armbian/build#11148orangepizero3w: update boot0 for 1GB boards. by @JackHuang021 in armbian/build#11142Patch maint: rewrite various patches against upstream or to align properly at least. by @EvilOlaf in armbian/build#11155prune: retire a set whose patches change each other's lines. by @igorpecovnik in armbian/cve#176radxa-nio-12l: patch lk.bin to fix 4-GiB fastboot flashing barrier. by @rbrok in armbian/mtkbin#1radxa-rock-4d: enable the NPU on edge. by @gahingwoo in armbian/build#11163README: add workflow picture. by @igorpecovnik in armbian/cve#113release: tag a release each time the patch set changes. by @igorpecovnik in armbian/cve#33report: a "not affected" verdict does not hold when the set adds the bug. by @igorpecovnik in armbian/cve#192report: list reviewed "not affected" results with their reason. by @igorpecovnik in armbian/cve#34rk35xx vendor: build the PCA953X GPIO expander into the kernel. by @Mkiring in armbian/build#11179rk35xx vendor: drop the unused CANFD_RK3576 fragment symbol. by @mingzhangqun in armbian/build#11176rockchip vendor: drop rkr patches from framework and merge directly into armbian/linux-rockchip. by @EvilOlaf in armbian/build#11159rockchip64-7.3: add Orange Pi 5 Max AP6611S WiFi overlay. by @a1ext in armbian/build#11141rockchip64-7.3: RK3399: make hibernation work (video decoder and GPU). by @iav in armbian/build#11139rockchip64-7.3: rk3528: keep the idle-only pmdomain workaround on RK3528. by @iav in armbian/build#11134rockchip64: helios64: drop two DT patches that contradict the schematic. by @iav in armbian/build#11120rockchip: rk8xx: power off instead of halting on RK3288. by @ohayoyogi in armbian/build#11115rockchip: support a list of overlay prefixes. by @lukaszsobala in armbian/build#11060rootfs, bsp: do not fail when /etc/sysctl.conf is missing. by @igorpecovnik in armbian/build#11164run: a backport carries a fix that is not in the mirror. by @igorpecovnik in armbian/cve#175run: one patch set per series, with reviewed cve/ backports. by @igorpecovnik in armbian/cve#27run: rebuild backports rejected with a mainline pick. by @igorpecovnik in armbian/cve#166run: retry backport sets after a build rejection. by @igorpecovnik in armbian/cve#159series: add LTS 6.12 and 6.1. by @igorpecovnik in armbian/cve#35skill: contribute without the claude CLI, retry stale backports. by @igorpecovnik in armbian/cve#32Spacemit k1 current redux. by @pyavitz in armbian/build#11035tuning_profile: add CPU frequency control per cluster. by @igorpecovnik in armbian/configng#1082u-boot: point the remaining links at u-boot-project.org. by @iav in armbian/build#11121uefi-arm64-6.18: fix HiKey960 USB role-switch endpoint. by @syscl in armbian/build#11181Update dependency oras-project/oras to v1.3.6. by @renovate[bot] in armbian/build#11150UWE5622 fixes: memory corruption, teardown bugs, start-up retry, TCP ACK stall. by @lukaszsobala in armbian/uwe5622#28work package: leave superseded cve/ sets out of the stack. by @igorpecovnik in armbian/cve#177zswap: do not allocate from atomic pool. by @igorpecovnik in armbian/linux-rockchip#611Automatic refresh repository README. by @igorpecovnik in armbian/armbian.github.io#433Automatic refresh repository README. by @igorpecovnik in armbian/build#10245View the full article
  13. Some debug infos collected from Android 13. log.txt pinctrl-handles.txt gpio.txt pinctrl-maps.txt
  14. Continuing the tradition (1, 2) of micro-optimizations for single-board computers that come into my hands. This time I optimized or rather fixed the wake-up function via USB/WoL/WWoL on the Orange Pi 5 Plus. Also got the WiFi adapter RTW8852BE/RTW8852CE working (at least those are the ones I tested). I tested exclusively on the Vendor 6.1.x kernel since the main wake-up features via USB/PCIE/GPIO1-GPIO4 only work in it. I don't currently have the ability to test the new current kernel and I doubt that Power Management will work fully there. Armbian for Orange Pi 5 Plus from the official website, Vendor kernel (kernel 6.1.115-vendor-rk35xx), what does NOT work by default: 1. No WiFi modules that insert into the PCI-E M.2 socket E-Key work - fixed in dts below 2. Wake-up from USB (mouse/keyboard/even Bluetooth dongle) doesn't work - fixed in dts below 3. WoL via Ethernet (on two ports) - fixed in dts below I also conducted power consumption measurements in all these wake-up modes. Let's start with Ethernet ports (WoL won't work by default due to incomplete dts profile). You need to create an overlay file, links I've attached it to this message. To apply this overlay, you need to copy it somewhere on the single-board computer and execute the command: cd <path to rk3588-orangepi-5-plus-Wakeup-GPIO-RTC-USB-WoL-fixes.dts> sudo armbian-add-overlay rk3588-orangepi-5-plus-Wakeup-GPIO-RTC-USB-WoL-fixes.dts Reboot. (if it doesn't boot at all with it or something doesn't work, you can remove these changes from the /boot/overlay-user/ folder) Wake-up Timer Test: sudo sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm" sudo sh -c "echo `date '+%s' -d '+ 1 minutes'` > /sys/class/rtc/rtc0/wakealarm" sudo systemctl suspend (here we set wake-up in 1 minute from current time, you can choose seconds/minutes/hours and so on, maybe even days - haven't tested. Installing a battery on RTC is not necessary, Type-C power is sufficient) Power Consumption: Testing was performed on Imax B6 Evo / OWON HDS242S. Please note, power consumption of m.2 SSD, SD-card, eMMC is not accounted for here (ideally they should be powered off in sleep mode), but USB devices were not used, bare single-board computer was tested, each module will have its own consumption, especially USB-connected devices, add your values to the sleep mode consumption. Wake-up only via GPIO0 (this includes power button), RTC In this power-saving mode only the rk3588-orangepi-5-plus-Wakeup-GPIO0-RTC-only-fixes.dts profile is used, keep this in mind, it's not compatible with other dts, you need to choose only one option. I got these values: sudo shutdown -h now | 5.4V | 0.005W | 0.001A sudo systemctl suspend | 5.4V | 0.14W | 0.027A Wake-up via GPIO0, GPIO1-4, RTC, USB, WoL In this power-saving mode only the rk3588-orangepi-5-plus-Wakeup-GPIO-RTC-USB-WoL-fixes.dts profile is used, keep this in mind, it's not compatible with other dts, you need to choose only one option. sudo systemctl suspend | 5.4V | 0.25W | 0.046A RTL8125B (eth0 or eth1, can even be both): sudo ethtool -s eth0 wol g && sudo systemctl suspend | 5.4V | 0.33W | 0,061A RTW8852BE (external rtw8852be driver (rtw89 doesn't support WWoL for RTW8852BE in vendor 6.1 kernel)): sudo iw phy0 wowlan enable any && sudo systemctl suspend | 5.4V | 0.30W | 0,055A RTW8852CE (built-in rtw89 driver in the build): sudo iw phy0 wowlan enable magic-packet && sudo systemctl suspend | 5.4V | 0.27W | 0,051A (I want to note that the Ethernet ports on Orange Pi 5 Plus in WoL mode don't light up and don't show link activity, you can only find out if the link is working on the router or on the device to which the single-board computer is connected. In magic-packet standby mode the link switches to 10Mbit and for example on the router loses the assigned IP address, you can find out if the device is alive only by ARP scanning on the router itself or by the link light indication on the router itself. The same applies to WWoL (WiFi) - only on the router or device to which the single-board computer is connected can you check in active clients mode or ARP scan for the presence of MAC address) My Armbian build from the official website on Vendor 6.1 kernel where rtw89 (WiFi) modules are already compiled and pre-installed in the kernel has a peculiarity that this driver supports WWoL function only for RTW8852CE - this is a slightly different chip than the official proprietary WiFi module for Orange Pi 5 Plus which uses RTW8852BE. For WWoL to work on RTW8852BE you need to install a third-party driver, for example I recommend from this source. How to use WoL, WWoL: For wired network use ip and ethtool utilities, for wireless network iw. WoL over LAN WWoL over WiFi External Drivers: For RTW8852BE/RTW8852CE and others there are fairly recent drivers (at the time of writing this manual), here's a brief instruction on how to install them on Orange Pi 5 Plus. Issues: File: rk3588-orangepi-5-plus-Wakeup-GPIO-RTC-USB-WoL-fixes.dts File: rk3588-orangepi-5-plus-Wakeup-GPIO0-RTC-only-fixes.dts Original Link 4PDA
  15. I see it is actually a failure for the 7.3.0-rc7-edge-sunxi kernel (with my extra setting CONFIG_EFI=y), just full log from armbian-debug here: https://paste.armbian.com/ucitawavax [ 1.526902] leds-gpio leds: error -EBUSY: Failed to get GPIO '/leds/pwr' [ 1.526958] leds-gpio leds: probe with driver leds-gpio failed with error -16 and already: root@ekker:~# systemctl status armbian-led-state.service * armbian-led-state.service - Armbian leds state Loaded: loaded (/usr/lib/systemd/system/armbian-led-state.service; enabled; preset: enabled) Active: active (exited) since Fri 2026-10-23 14:03:16 UTC; 27min ago Invocation: b071139a57234fb7a65ef3dc88c4534d Process: 376 ExecStart=/usr/lib/armbian/armbian-led-state-restore.sh (code=exited, status=0/SUCCESS) Main PID: 376 (code=exited, status=0/SUCCESS) Mem peak: 1.3M CPU: 485ms Oct 23 14:03:06 ekker systemd[1]: Starting armbian-led-state.service - Armbian leds state... Oct 23 14:03:16 ekker armbian-led-state-restore.sh[376]: warning: /sys/class/leds/nanopi:blue:status/trigger could not be restored Oct 23 14:03:16 ekker armbian-led-state-restore.sh[376]: warning: /sys/class/leds/nanopi:blue:status/invert could not be restored Oct 23 14:03:16 ekker armbian-led-state-restore.sh[376]: warning: /sys/class/leds/nanopi:green:pwr/trigger could not be restored Oct 23 14:03:16 ekker armbian-led-state-restore.sh[376]: warning: /sys/class/leds/nanopi:green:pwr/brightness could not be restored Oct 23 14:03:16 ekker systemd[1]: Finished armbian-led-state.service - Armbian leds state. So seems a matter of a new or wrong path for the leds or pins, where the older Debian kernel does is correct, also the leds config file is correct according to my understanding. Long time ago I disabled blue led of my rock-3a, so remenber a bit. Probably I install current sunxi as well (6.18) and see what that does. EDIT: sorry too fast, this won't work as it has no EFI enabled, so needs then booted via boot.scr or extlinux
  16. Alright, found a boot.cmd tweak in the config for dshanpi-r1, and followed that. Looks like it's working as expected, so no need for duplicate bootscript. Other basic functions appear to be working. SD Card USB HDMI NVME Initial PR submitted to get CSC images working. Now to poke at GPIO headers.
  17. I hit this same issue on Armbian 26.8.3, vendor 6.1.115, Orange Pi 5 8GB. `lsblk` showed no NVMe, `dmesg` stuck at `PCIe Link Fail, LTSSM is 0x3`. **What I tried (didn't work):** - `echo 1 > /sys/bus/pci/rescan` – no effect - The overlay from @atlaste's post targeting `&vcc3v3_pcie20` – **silently failed** because in the vendor 6.1.115 DTB the node label is `vcc3v3_pcie2x1l2`, not `vcc3v3_pcie20`. The `.dtbo` compiles fine but the fixup never resolves, so the overlay is never applied. - Switching to a different PSU (5V/5A RPi 5 charger) – no change **What actually worked (direct DTB patch):** ```bash # Decompile dtc -I dtb -O dts /boot/dtb/rockchip/rk3588s-orangepi-5.dtb -o /tmp/opi5.dts # Find the wrong GPIO line (around line 10720): # gpios = <0x15a 0x15 0x00>; ← gpio0 pin 21 (WRONG) # Find the correct phandle for gpio2 (node gpio@fec30000, around line 7854): # phandle = <0x2ce> # Patch: sed -i 's/gpios = <0x15a 0x15 0x00>/gpios = <0x2ce 0x01 0x00>/' /tmp/opi5.dts # Recompile and replace: dtc -I dts -O dtb -o /tmp/opi5.dtb /tmp/opi5.dts sudo cp /tmp/opi5.dtb /boot/dtb/rockchip/rk3588s-orangepi-5.dtb sudo reboot ``` Verified with `od -A n -t x1 /proc/device-tree/vcc3v3-pcie2x1l2/gpios` → `00 00 02 ce 00 00 00 01 00 00 00 00` (gpio2, pin 1). **Important caveat – Gen4 drives may not work:** After the DTB fix, my **Crucial E100 480GB (PCIe Gen4 x4)** still did NOT enumerate. Swapped to a **Gen3 drive** and it appeared immediately in `lsblk`. The M.2 slot itself was fine (verified with a PCIe-to-SATA adapter). So the full picture: 1. **DTS GPIO bug** – blocks ALL NVMe (Gen2/3/4) → fix as above 2. **Gen4 NVMe drives** – may still fail even after the fix, because RK3588S only does PCIe Gen2 and some Gen4 drives don't negotiate down properly **TL;DR for anyone hitting LTSSM 0x3:** - First: patch the DTB (label is `vcc3v3_pcie2x1l2` in vendor 6.1.115, not `vcc3v3_pcie20`) - If still no luck: try a Gen2/Gen3 drive before blaming the board
  18. Waveshare ESP32-S31-Zero is a small ESP32-S31 development board that follows the form factor of the earlier Waveshare “Zero” boards, such as the ESP32-C6-Zero-B, RA4M1-Zero, and ESP32-S3-Zero, among others. The new tiny board still features a USB-C port for power and programming, as well as eighteen through and castellated holes for GPIO and power signals, but it boasts a more powerful ESP32-S31 dual-core RISC-V MCU clocked at up to 320 MHz, featuring 2.4 GHz WiFi 6, Bluetooth 5.3, and 802.15.4 connectivity, as well as up to 32MB on-chip PSRAM and a 16MB or 32MB SPI flash chip. Since the ESP32-S31 has quite a few extra I/Os, Waveshare also added a 40-pin high-density connector for LCD, touchscreen, SD card, USB 2.0, and extra GPIOs. Waveshare ESP32-S31-Zero specifications: SoC – Espressif Systems ESP32-S31 CPU RISC-V HP (High-performance) RV32IMAFCP CPU @ 320 MHz with FPU, SIMD, etc. RISC-V LP (Low-power) MCU core Memory – [...] The post Waveshare ESP32-S31-Zero – A tiny ESP32-S31 board with up to 32MB PSRAM, 32MB SPI flash appeared first on CNX Software - Embedded Systems News. View the full article
  19. The Main part Is You Buying A Module and Plugging Your Fan Into It. : Here you go — two solid solderless picks: 1. Adafruit MOSFET Driver #5648 (the clean reference — genuine logic-level AO3406, flyback diode already onboard, jumper-friendly header, ~$4): https://www.adafruit.com/product/5648 Also stocked via resellers (Mouser/DigiKey/Pimoroni) if you search "Adafruit 5648." 2. Generic 3.3 V-trigger dual-MOSFET board (cheapest, everywhere, screw terminals — fully solderless; just add a flyback diode across the fan since these usually omit it): https://www.amazon.com/ANMBEST-Trigger-Adjustment-Electronic-Control/dp/B08TW9RB49 If that exact listing has rotated (Amazon ASINs come and go), search "DC 5V-36V MOSFET trigger switch module 3.3V" — you want one whose description explicitly says 3.3 V trigger and, ideally, names the FET (AO3400 / IRLZ44N). For the fan itself, either module handles it with room to spare — a 5 V 40 mm fan pulls well under 0.2 A, and these are rated for amps. Verified straight from your local Armbian build tree — yes. The linux-rockchip64-edge.config (the branch .217 runs) ships all three of the relevant symbols: CONFIG_THERMAL_EMULATION=y ← yes, emul_temp works CONFIG_THERMAL_GOV_BANG_BANG=y ← bonus: the ideal on/off governor is available CONFIG_SENSORS_GPIO_FAN=m ← the fan driver (module) (current also has THERMAL_EMULATION=y, so any edge/current board is covered.) Answer for Pi Claude: Go ahead and use the emul_temp method in Phase A — Compile-verified — exit 0, pull-none pinctrl and all (rockchip,pins = <1 RK_PA4 GPIO &pcfg_pull_none>, trips 75000/10000, active). So the overlay in this post is a real, building artifact, not a sketch. And ha — a real cooking show it is: you're watching me taste-test the sauce (compile it) before it goes to the pass. Here's the plated dish. 👨‍🍳 CPU Cooling: Automatic Fan Control on RK3588 (Orange Pi 5 / 5B) — Armbian / Debian 13 If your Orange Pi 5/5B fan runs flat-out all the time (or not at all), here's how to let the kernel run it — silent at idle, full blast under load — with no daemon and no script. One cheap switch module plus a small device-tree overlay. 1) The hardware — a switch module + your fan You can't drive a fan motor straight off a GPIO pin. A GPIO is a ~few-milliamp logic output; a fan pulls 100–150 mA and would damage the pin. So the GPIO signals a tiny logic-level MOSFET module that switches the fan's 5 V. Two solderless picks: Generic "3.3 V trigger" MOSFET module — screw terminals, ~$1–2, everywhere. Easiest. The listing must say 3.3 V trigger and ideally names the FET (AO3400 / IRLZ44N). These usually omit the flyback diode, so add a 1N5819/1N4001 across the fan. Adafruit #5648 ($4) — cleanest; guaranteed logic-level with the flyback diode onboard. Add its JST-PH 3-pin→female-socket cable ($1.25) for a solderless header tap. 2) Wiring (low-side switch) Fan + → 5V (header pin 2 or 4) Fan − → module output GPIO → module signal / trigger input GND → module GND (common ground is essential) Flyback diode across the fan if your module lacks one (band → +5V side) 3) The overlay — this is what makes it automatic Save as rk3588-gpio-fan.dts. It turns the fan on at 75 °C, off at 65 °C on the big-core sensors (which heat first), safely below the 85 °C throttle. The pull-none pinctrl matches how mainline wires fan GPIOs: /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/pinctrl/rockchip.h> #include <dt-bindings/thermal/thermal.h> / { fan: gpio-fan { compatible = "gpio-fan"; pinctrl-names = "default"; pinctrl-0 = <&fan_en>; gpios = <&gpio1 RK_PA4 GPIO_ACTIVE_HIGH>; /* set to YOUR pin (both here and below) */ gpio-fan,speed-map = <0 0>, <5000 1>; #cooling-cells = <2>; }; }; &pinctrl { fan { fan_en: fan-en { rockchip,pins = <1 RK_PA4 RK_FUNC_GPIO &pcfg_pull_none>; }; }; }; &bigcore0_thermal { polling-delay = <2000>; trips { fan0: fan0 { temperature = <75000>; hysteresis = <10000>; type = "active"; }; }; cooling-maps { m { trip = <&fan0>; cooling-device = <&fan THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; }; }; }; &bigcore2_thermal { polling-delay = <2000>; trips { fan2: fan2 { temperature = <75000>; hysteresis = <10000>; type = "active"; }; }; cooling-maps { m { trip = <&fan2>; cooling-device = <&fan THERMAL_NO_LIMIT THERMAL_NO_LIMIT>; }; }; }; Change both RK_PA4 references to the header pin you actually wired to (GPIO1_A4 is just the example — group A = 0, B = 1, C = 2, D = 3, so GPIO1_D6 = RK_PD6). 4) Install & verify sudo armbian-add-overlay rk3588-gpio-fan.dts sudo reboot # fan registered as a cooling device? (driver is a module; load it if the grep is empty) grep -l gpio-fan /sys/class/thermal/cooling_device*/type || sudo modprobe gpio-fan # watch it react under load: watch -n1 'cat /sys/class/thermal/cooling_device*/cur_state' stress-ng --cpu 8 --timeout 120s cur_state flips to 1 as the die crosses 75 °C and back to 0 below 65 °C. Set-points: 75 on / 65 off (10 °C hysteresis) keeps a 10 °C guard below the 85 °C throttle, so the chip never has to slow down. Thanks to Boardcon (EM3588) for the field-proven numbers from real 24/7 industrial enclosures. Tested on: Orange Pi 5B — Armbian <edge ver> — kernel <uname -r> (This will ship built-in on the new distro — but it works on stock Armbian today.) No sandbagging defcom5-rockchip
  20. Board: HINLINK H68K (community-maintained) Image: Armbian_community_26.11.0-trunk.108_Hinlink-h68k_trixie_current_6.18.57_minimal (kernel 6.18.57-current-rockchip64) What happened? 1. The port labelled eth0 never works. At boot its link LED blinks once and stays dark. mii-tool end1 reports "No MII transceiver present!" and bringing it up logs "Failed to reset the dma". I observed the problem on two separate H68K units. Once that was resolved, I further noticed that... 2. With a good cable, eth0 and eth1 link at 1000 Mbit/s but can't receive. Received frames land in mmc_rx_crc_error (on eth1, all of them), so DHCP never completes. With a cable that negotiates 100 Mbit/s, both ports work. Expected: both 1G ports work at 1000 Mbit/s, as the 2.5G ports (eth2/eth3) do. Root Causes: Both are in patch/kernel/archive/rockchip64-*/dt/rk3568-hinlink-h68k.dts: 1. &i2s1_8ch (RK809 audio) has no pinctrl-0, so it takes the full 8-channel i2s1m0 pin set. That set includes GPIO1_B0, which is gmac1's snps,reset-gpio. Once the i2s driver probes, the eth0 PHY is held in reset: pin 40 (gpio1-8): fe410000.i2s gpio1:40 function i2s1 group i2s1m0-sdo1 2. Both gmacs are rgmii-id (the PHY adds the delays) but also set tx_delay = <0x3c>; rx_delay = <0x2f>;. The rockchip64-6.18 tree carries the WIP patch "dwmac-rk: Allow use of rx/tx delayline for rgmii-id modes", which applies those MAC delays as well, so the delay is applied twice: init for rgmii-id with delay (tx: 0x3c, rx: 0x2f) How to reproduce? Boot the image above on an H68K. Plug a cable into the port labelled eth0: no link. Plug a known-good cable into eth1 with a gigabit partner: it links at 1000 Mbit/s but gets no DHCP lease, and ethtool -S end0 | grep rx_crc climbs. Fix: PR: https://github.com/armbian/build/pull/11251. It restricts i2s1 to the 4 pins the codec uses (same as mainline's rk3568-rock-3a.dts) and drops tx_delay/rx_delay. I tested it on 6.18.57 with an equivalent overlay: both 1G ports pass traffic at 1000 Mbit/s with no CRC errors, and analog audio still plays.
  21. AAEON claims the PICO-PTH4 is the world’s first 2.5-inch Pico-ITX board powered by an Intel Panther Lake processor, such as the Core Ultra 5 325, Core Ultra 7 355, and Core Ultra X7 358H, delivering up to 180 TOPS of AI performance in a 100mm x 72mm form factor. The single board computer ships with up to 32GB of LPDDR5X, supports M.2 M-Key/E-Key and PCIe x4 FPC expansion, and offers dual 2.5GbE, HDMI 2.1 video output, two USB 3.2 Gen 2 ports, and internal connectors for USB 2.0, front panel, RS-232/422/485, GPIO, and SMBus/I2C. AAEON PICO-PTH4 specifications: Panther Lake SoC (one or the other) Intel Core Ultra 5 325 CPU – Octa-core (4P+4LPE) CPU up to 4.5 GHz with 12MB Smart Cache GPU – 4-core Intel Graphics @ 2.45 GHz (40 TOPS) AI accelerator – 47 TOPS Intel AI Boost NPU PBP: 25 Watts Core Ultra 7 355 CPU – [...] The post AAEON PICO-PTH4 Pico-ITX board is powered by an Intel Panther Lake SoC up to the Core Ultra X7 358H appeared first on CNX Software - Embedded Systems News. View the full article
  22. Hi, You made my day! 🙂 I have been struggling with nvme ssd not detected on my new opi5 board rev 1.3.2 too. Many thanks! I confirm the fix is working - detection of nvme only (not booting from nvme automatically): tested with official Armbian v26.8.3 for Orange Pi 5 image + bootloader flashed to SPI booted from sdcard with nvme disk attached running Armbian Linux 6.1.115-vendor-rk35xx Manual method - activate the pin in fw (uboot): Boot 2026.04_armbian-2026.04-S88dc-Pb430-H2ebc-Vccc7-B5da4-R448a (Jul 24 2026 - 14:26:33 +0000) Model: Xunlong Orange Pi 5 SoC: RK3588S DRAM: 8 GiB Core: 726 devices, 33 uclasses, devicetree: separate MMC: mmc@fe2c0000: 0 Loading Environment from nowhere... OK In: serial@feb50000 Out: serial@feb50000 Err: serial@feb50000 Model: Xunlong Orange Pi 5 SoC: RK3588S Net: eth0: ethernet@fe1c0000 Hit any key to stop autoboot: 0 => pci enum pcie_dw_rockchip pcie@fe190000: PCIe-0 Link Fail => gpio set 65 gpio: pin 65 (gpio 65) value is 1 => pci enum => pci BusDevFun VendorId DeviceId Device Class Sub-Class _____________________________________________________________ 00.00.00 0x1d87 0x3588 Bridge device 0x04 01.00.00 0x1c5c 0x1339 Mass storage controller 0x08 > boot ... root@orangepi5:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk1 179:0 0 119.1G 0 disk └─mmcblk1p1 179:1 0 117.9G 0 part /var/log.hdd / zram0 253:0 0 3.9G 0 disk [SWAP] zram1 253:1 0 50M 0 disk /var/log zram2 253:2 0 0B 0 disk nvme0n1 259:0 0 238.5G 0 disk └─nvme0n1p1 259:1 0 238.5G 0 part root@orangepi5:~# with using user dtb root@orangepi5:~# cat > /tmp/pcie-m2-power-fix.dts <<'EOF' /dts-v1/; /plugin/; / { compatible = "rockchip,rk3588"; fragment@0 { target = <&vcc3v3_pcie2x1l2>; __overlay__ { gpios = <&gpio2 1 0>; }; }; }; EOF root@orangepi5:~# root@orangepi5:~# armbian-add-overlay /tmp/pcie-m2-power-fix.dts Compiling the overlay Copying the compiled overlay file to /boot/overlay-user/ Reboot is required to apply the changes root@orangepi5:~# root@orangepi5:~# shutdown -r now ... root@orangepi5:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk1 179:0 0 119.1G 0 disk └─mmcblk1p1 179:1 0 117.9G 0 part /var/log.hdd / zram0 253:0 0 3.9G 0 disk [SWAP] zram1 253:1 0 50M 0 disk /var/log zram2 253:2 0 0B 0 disk nvme0n1 259:0 0 238.5G 0 disk └─nvme0n1p1 259:1 0 238.5G 0 part root@orangepi5:~# EDIT: Tested boot from nvme Transferred system to nvme via armbian-config with uboot in MTD/SPI. But it did not boot automatically because nvme is not detected in u-boot until I manually set the pin (gpio set 65) so this needs to be fixed in u-boot (in the upstream I would say...)
  23. Banana Pi BPI-M8 is a credit card-sized SBC powered by an Allwinner A733 octa-core Cortex-A76/A55 SoC that aims to offer an alternative to the Raspberry Pi 5. The BPI-M8 comes with 4GB LPDDR5, HDMI and MIPI DSI display interfaces, two MIPI CSI camera interfaces, Gigabit Ethernet, on-board WiFi 6 and Bluetooth 5.0, four USB ports, a 16-pin FFC PCIe connector, and the usual 40-pin GPIO header. Two variants are offered: the BPI-M8A with 64GB eMMC flash, and the BPI-M8B with 16MB SPI NOR flash. Banana Pi BPI-M8 specifications: SoC – Allwinner A733 CPU Dual-core Arm Cortex-A76 @ up to 2.00 GHz Hexa-core Arm Cortex-A55 @ up to 1.80 GHz Single-core RISC-V E902 real-time core GPU – Imagination Technologies BXM-4-64 MC1 GPU with support for OpenGL ES 3.2, Vulkan 1.3, and OpenCL 3.0 VPU 4Kp60/8Kp24 H.265/VP9/AVS2 decoding, 4Kp30 H.264 decoding 4Kp30 H.265/H.264 encoding AI accelerator – 3 TOPS NPU Process – 12 [...] The post Banana Pi BPI-M8 – An Allwinner A733 SBC inspired by the Raspberry Pi 5 with PCIe FFC connector, UFS module socket appeared first on CNX Software - Embedded Systems News. View the full article
  24. Confirming the bug, plus a data point: the M.2 power pin differs between Orange Pi 5 PCB revisions. I have two Orange Pi 5 boards: - PCB v1.3.2 (16 GB): NVMe not detected without a fix - PCB v1.2: NVMe works out of the box Both run the same software: Armbian 26.8.3, kernel 6.1.115-vendor-rk35xx (linux-dtb-vendor-rk35xx 26.8.3). The same NVMe drive works in v1.2 and is not detected in v1.3.2. Symptoms on v1.3.2 (no fix): - vendor kernel: "rk-pcie fe190000.pcie: PCIe Link Fail, LTSSM is 0x3", then "failed to initialize host" - current kernel 6.18.43: "Phy link never came up" - U-Boot (Armbian 2026.04 SPI): "pcie_dw_rockchip pcie@fe190000: PCIe-0 Link Fail" Findings: 1. In the stock DTB (vendor), regulator vcc3v3_pcie2x1l2 uses gpios = <... 0x15 ...>, i.e. GPIO0_C5. On v1.2, /sys/kernel/debug/gpio shows: gpiochip0: gpio-21 (vcc3v3-pcie2x1l2) out hi and NVMe works. 2. On v1.3.2, driving GPIO2_A1 instead (as described in this thread) brings the link up. I used this overlay with the vendor kernel: /dts-v1/; /plugin/; / { compatible = "rockchip,rk3588"; fragment@0 { target = <&vcc3v3_pcie2x1l2>; __overlay__ { gpios = <&gpio2 1 0>; }; }; }; Without the overlay the system (rootfs on NVMe) does not boot on v1.3.2; with it, it does. 3. Same story in U-Boot: in the console of the Armbian SPI U-Boot, "gpio set 65; pci enum; nvme scan" makes the NVMe appear. After flashing the SPI bootloader from the official Orange Pi image, U-Boot sees the NVMe and Armbian boots from it. Conclusion: this does not look like a defective board; the M.2 power switch seems to be on GPIO0_C5 on v1.2 and on GPIO2_A1 on v1.3.2. Simply changing the pin to A1 for all Orange Pi 5 boards would likely break v1.2, so the fix probably needs to be per revision (separate overlay/DTB), and the same applies to U-Boot's device tree. Caveats: I only have one board of each revision. I tested the overlay on the vendor kernel only (on mainline the label is vcc3v3_pcie20, I did not test that).
  25. The old blaster isn't coming back on 26.04, and it's worth knowing why before chasing it: "odroid blaster" wasn't a lirc configuration, it was an out-of-tree Hardkernel module (lirc_odroid) built for the 3.10 vendor kernel, and hardware.conf died with lirc 0.10 anyway. There's no modern driver for that path, so the clean way is to rebuild the transmit side on the generic kernel infrastructure. Your LED circuit can stay exactly as it is. Declare a gpio-ir-tx node in a DT overlay on the GPIO behind pin 7 of the 40-pin header (Hardkernel's pinout will give you the GPIOX number), keep driving the LED through the same transistor/resistor from the 5V pin, and the TX side shows up as an extra /dev/lirc device. From there ir-ctl replaces irsend: capture the power code from your LG remote with any IR receiver (a $1 gpio-ir on a spare pin, or the onboard receiver if your image enables it) or pull the LG address/command from irdb, verify the LED blinks with a phone camera, then ir-ctl -S lg:: sends it. If you specifically want lircd and irsend back, modern lirc can sit on top of the same /dev/lirc0 — but for a single SEND_ONCE use case, ir-ctl alone is fewer moving parts. One gotcha: gpio-ir-tx is bit-banged, so a heavily loaded system can stretch the first transmission now and then — a repeat usually fixes it, that's not a config error.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.