armbian
[Bug]: Armbian-Config RPi4B
What happened?
Hello Armbian Team,
I wanted to report an issue with armbian-config on the Raspberry Pi 4B. It appears that the utility does not recognize or apply custom device tree overlays that are present in /boot/firmware/overlays.
Steps to reproduce: Place a custom overlay .dtbo file in /boot/firmware/overlays. Run armbian-config and attempt to configure hardware that relies on the overlay. The overlay is not listed or applied; armbian-config seems to only consider its pre-defined set of overlays.
Expected behavior: Custom overlays placed in /boot/firmware/overlays should be recognized and selectable in armbian-config, just like the built-in ones.
Observed behavior: Only pre-packaged overlays shipped with Armbian are visible/usable in armbian-config. Manually copying overlays does not allow them to be used through the GUI.
Additional info: Armbian version: Armbian_25.8.1_Rpi4b_noble_current_6.12.41_minimal
Board: Raspberry Pi 4B
Overlay tested: all
This limitation makes it difficult to use Armbian on Pi 4B with non-standard hardware requiring custom overlays. It would be great if armbian-config could either:
Respect all overlays present in /boot/firmware/overlays, or
Provide a clear mechanism to register custom overlays for use in the tool.
Thank you for your attention to this issue.
How to reproduce?
above has info
On which OS are you observing this problem? (for easier diagnosis please provide logs with armbianmonitor -u)
Armbian Ubuntu 24.04 Noble
Code of Conduct
- [x] I agree to follow this project's Code of Conduct
@wizbandit Greetings.
From what I understand, armbian-config is mainly set up to handle overlays included with official Armbian images. Custom overlays added after the build process may not be automatically detected by the tool, though this depends on current implementation details and may change.
If you’d like to see support for more flexible overlay handling, you’re welcome to propose it as a feature request. I’m happy to help with possible solutions.
