All Activity

Here are fix.

actually did some more digging and i think this describes the same issue that i am seeing with these newer sd cards in uboot spl. https://lore.kernel.org/u-boot/20251031145951.535376-1-c.stoidner@phytec.de/

as far as i am understanding this is running off of the onboard spi-flash/eeprom on the orange pi board unless you're reflashing that on first boot U-Boot SPL board init U-Boot SPL 2017.09-orangepi (Aug 30 2024 - 22:09:16) i've also switched to using mainline uboot v2025.10 for my emmc and sd cards that i'm creating but previously had not been in a situation where i needed to update the spi-flash/eeprom for sd cards or emmc uboot proper to be able to be loaded. I was able to resolve my issue by building mainline uboot spl with a timeout in the mmc probing

T95 Mini H313 EMCP Board V1.0

U-Boot SPL 2025.10_armbian-2025.10-Se50b-P24f2-Hae98-V38b0-Bbf55-R448a (Nov 19 2025 - 09:08:53 +0000) which is in that image, has no btrfs support I saw for example on my NanoPi-R6C using: U-Boot SPL 2026.01-rc2_armbian-2026.01-rc2-S365a-Pb445-He3cc-V062a-Bbf55-R448a (Dec 03 2025 - 04:31:42 +0000) that it has btrfs support, so can load kernel etc directly from the rootfs partition when it is btrfs formatted. You can first write a newer U-Boot in SPI-Flash, then it should work.

Hi, how do you mount the share? It might be that systemd manages the mount in newer systems, then, to umount you have to simply systemctl stop your-share.mount You can check with: systemctl list-units --type=mount --all To see if the mount is systemd managed

``` ❯ sha256sum Armbian_25.11.1_Orangepi5*img 6cb1e6ed97dc41170db8406b056ecbf422f8801261e13b07da4dae3b45a81ab3 Armbian_25.11.1_Orangepi5_noble_vendor_6.1.115_minimal.img 5781fec6fa812fca1f99e79a42b0312bf4403a2a590dec84458dcfbabd28cd13 Armbian_25.11.1_Orangepi5_trixie_vendor_6.1.115_minimal.img ```

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.27W | 0,050A RTL8125B (eth0 or eth1, can even be both): sudo ethtool -s eth0 wol g && sudo systemctl suspend | 5.4V | 0.34W | 0,063A 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

https://zuckerbude.org/armbian-using-kernel-config/

Once this is merged, more recent SoC code can be rebased on top:https://github.com/armbian/build/pull/9049

I am talking about hdmi audio. Analog audio works fine on both kernels. HDMI-Audio doesn't work in 6.16.8 kernel. I'll keep using v25.11.0-trunk.190 with kernel 6.15.4 for now since HDMI works there. I might experiment with those configs later, or perhaps it will get fixed in a future version. Thanks.

Are you sure you can't help me? I just need to add one line to add the module.

You simply need to read the docs, it takes time and maybe some trial-error. Maybe hours, days, weeks or longer. There is no free ride. https://docs.armbian.com/Developer-Guide_Overview/

I'm using compile.sh without any arguments. Can I add the adra module argument to the command? How well will this work? For example, like this: ./compile.sh CONFIGURE_DRM_PANEL_MIPI_DBI=m I tried this, but I got a compilation error saying there was no such argument.

Can you post/do something like this: I use Armbian Trixie on ARM64 computer to do builds. I banned Ubuntu (certainly old Jammy) and also do not use docker.

Thank you very much for your answer. sudo apt install docker.io git clone https://github.com/armbian/build armbian cd armbian/ ./compile.sh In the configurator, I select the custom plate orangepizero3, and then the Trixie release. Then in the configurator, I select device-driver->graphic-support->drm->drm-panel-mipi-dbi-support Then I save the configuration under a custom name. Then exit, exit, exit, and load the configuration. When asked if I wanted to save the new configuration, I selected both options, but the result was always the same: the module wasn't compiled into the kernel.

I am afraid you need to dig deeper than those 'convenience installers'. I never used armbian-install but have been running Armbian from Btrfs for several years. It is easy and low failure risk if just simple SBC with only SD-card like NanoPi-NEO, but you get many options where various modern U-Boot builds / bootloaders can go wrong. Do the math permutation and you will realize. I know Armbian can be booted from single Btrfs formatted partition, but it meant full custom own U-Boot and own partition setup. That also involves whether you use subvolumes or not and whether you set 1 as default, other then the root of the filesystem ( ID <= 5 is that). Also features, I use zstd compression, but I am not 100% if the whole chain does also support it. So you need serial console cable to see/log what is going on and also set kernel loglevel to 7 (in armbianEnv.txt). It would also help if you post sha256sum of image you tested/used. That allows others like myself to quickly check/reproduce in virtual machine or so (I don't have OPi5) and not pick a newer build or so next week when time to help you.

Yeah I am glad that atleast I can get into desktop environment by manually doing a lightdm restart. ls /dev/fb* returns: /dev/fb0 I feel like I've tried everything possible and ended up just making a custom script that restarts lightdm a few seconds after booting, it's not ideal and it bothers me that it isn't working properly but yeah. - I am using adafruit,yx240qv29 - Yes I am using XFCE currently but I've tried Gnome too. - the Slick greeter - Orangepizero3_1.0.2_ubuntu_jammy_server_linux6.1.31 / but have tried MANY others. Also what might be useful for others, just the DTS wasn't enough for things to work, also had to create a config in /etc/X11/xorg.conf.d/ and add these lines: Section "Device" Identifier "ILI9341-Device" Driver "fbdev" Option "fbdev" "/dev/fb0" EndSection However things aren't super stable yet, the screen sometimes will randomly stop working, first I though maybe there is a screensaver or something but that doesn't seem to be the issue. Leaves me to think it's maybe power related and need to use shorter cables and a better 3.3v power supply (currently using the 3.3v from the opiz3). Lastly maybe shortening my jumper wires might make a difference. Previously the screen was all the way glitched as seen in my earlier post, I had shortened the dc, miso, mosi and SCLK jumpers but maybe I should make them even shorter. What makes me think it might be power related is also because sometimes the screen seems to go slightly dimm and then brighten back up, it's subtle but visible. Lastly I might have the depth or spi frequency not dialed in yet.

What are your steps and/or commands? Arguments of compile.sh have changed regularly, so look at that first I would say.

Great job, man! Would it be possible to build the kernel SATA support in the next release? I have the PentaHAT attached to it. It works well with the sunxi kernel eng build but their systems is way too old so I prefer Armbian.

I'm trying to build an abian trixie image with the CONFIG_DRM_PANEL_MIPI_DBI support module enabled in the kernel. However, no matter how many times I build, when checking the modinfo module, panel-mipi-dbi is not found. In the /boot/config(kernel) configuration, the line is commented out: #CONFIG_DRM_PANEL_MIPI_DBI is not set I set M to the panel-mipi-dbi kernel module parameter. I also set Y to the parameter. I also tried adjusting the .config file before running the image build. I used both Docker and non-Docker builds. I'm using Ubuntu 22.04.

I think the confusion here is that `ip_tables` is the module reference and `iptables` is the binary built in reference. Microk8s requires this to be a module and not built in. I am compiling a standard kernel as speak to see if setting the appropriate nettable to `m` from '*` will work.

I got my Orange Pi 5 out of the drawer today and discovered that it would not boot from NVMe after armbian-install if I used btrfs, but it boots fine with ext4. I tried both the Minimal/IOT Ubuntu 24.04 and 25.11.1 Trixie Minimal/IOT images with 6.1.x kernels. (I updated each to 25.11.2 before doing the armbian-install of both the system and the mtd image.) P.S. A minor quibble, but it was annoying that the numbering of the continents/countries during setup and the ordering of the SPI bootloader options during armbian-install were different between the Trixie and Noble images. I had to actually read. 🙈

@Octavio Cuatrochio, you need root privileges to modify any partition at runtime. If you want to modify firmware, get update.zip to your PC, modify it, and flash using android's Settings->About->Local update.

Hello. Im trying to configurate and adapt OrangePI Zero 2W board to a custom extension board with multiple RS485 drivers. For now, im trying to configurate a single secondary UART (UART2) to initialize with muxed Rx\Tx pins and in RS485 (with software driven RTS pin). My current DT overlay is: And it is partially works. Works as UART. Able to send and receive data with muxed Rx\Tx. For RTS... its complicated. Seems RTS(PH4 GPIO) are initialized and acquired by UART2 software, and stay low during initial idling. After im trying to send any data (echo 123 >> /dev/ttyS2), RTS goes HIGH and stuck in this state before reboot. Im have tried to send big blob at 9600 and check the RTS with statserial. But as i see, RTS is 1 (active???) from inital to complete and after, and never changes.