All Activity

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.

Never heard of that spelling "ip_tables". Anyway should be built in: https://github.com/armbian/build/blob/4e027a40d6d38d5e9072577a7e47b110914a843d/config/kernel/linux-qcs6490-edge.config#L421

When attempting to install microk8s, I noticed that the `ip_tables` module is missing from the provided image (Ubuntu 24.04 (Noble) Minimal / IOT image) on this page: https://www.armbian.com/radxa-dragon-q6a/ Easy way to replicate: ``` sudo modprobe ip_tables modprobe: FATAL: Module ip_tables not found in directory /lib/modules/6.18.0-rc6-edge-qcs6490 ``` Is there another image that has this module are part of the kernel or do I need to build the kernel myself? This seems like a module that should be included for an image that is labeled as `IOT`.

Thanks for the suggestion, but it didn't work for me. Both /var/log/postgresql and /var/log.hdd/postgresql reverted to their pre-intervention ownership and permissions when I rebooted.

I am glad you made the LCD work with a DRM driver Three clarifications: the driver panel-mipi-dbi is provided in the OS image you write in the microSD. The DTS is something you get from this thread, and install it with armbian-add-overlay. Kungfupancake provides a txt or a bin file that defines the configuration sent to the LCD, when the kernel driver starts, and instructions on how to install it. The panel-mipi-dbi driver (the recent versions I tried) does not support X11, and you need 100% Wayland, and 0% X11 See my thread to install rpi-greeter (one of the 2 login managers that work with Wayland), and Labwc:

Those are super cheap maybe a dollar if shipped from Asia and an absolute essential tool for debugging. Get yourself one. http://debug.armbian.de

Hello and thank you for the problem report. What solution did orangepi.org provide for you? As you can see, nobody in the Armbian community was interested to step up and support this board and from what I have heard through the grapevine this is because of the poor support that orangepi.org gives to FOSS projects and communities such as armbian.com. Armbian has already pushed another update for Sunxi64. Maybe you are in luck and the problem is already fixed. If not, we are happy to accept a PR once orangepi.org has published a solution.

@Mohammad Adel here are some links that will help you. Find your Dram settings https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-218660 Find boot.bin and extract dts. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-187672

I find the lack of GRUB via HDMI too problematic, so I put EDK2-UEFI v1.1 in eMMC again. I needed to wipe it completely, just writing the part without partition table normally done for U-Boot kept using the 2025.10 U-boot that was written there. I do not know how that comes. I know EDK2-UEFI v1.1 will divert to SD-card, so I though I use that to test U-Boot again. - blkdiscard SD-card - write U-Boot SPL 2026.01-rc2_armbian-2026.01-rc2-S365a-Pb445-He3cc-V062a-Bbf55-R448a (Dec 03 2025 - 04:31:42 +0000) to it - type reboot After restart and desktop login no HDMI audio. Kernel log showed long series of audio driver related errors - shutdown and pull USB-C powerplug - plug it in again and let it boot - then no audio error and also hear a 'plop' in the monitor that means the audio is enabled/working So it seems something does not reset correctly, so powercycle needed, while HDMI monitor is kept powered and HDMI cable stays connected all the time. What is different now: - kernel 6.18.0-edge-rockchip64 - eMMC contains EDK2-UEFI v1.1 and passes control/boot to SD-card U-Boot But I think it is the powercycle that is the key thing. An interesting new feature of the 2026.01-rc2 U-Boot is that the CPU clock go down to 480 MHz when mainline kernel, was 1GHz. Is not lowering idle power though, is 3 W, is 1.5 W with vendor kernel. Not clear why that is.