All Activity

I think this is your underlying issue. Focal was dropped from support a year ago (by both Ubuntu and Armbian). So the underlying packages you need are likely no longer in repositories.

Does anyone know if version 22.04 for the raspberry pi4 was disabled by mistake or will no longer have the option to be generated? I'm using git clone --depth=1 --branch=main https://github.com/armbian/build.

Greetings, I've built a custom image for the BPI M4 Zero and have been using a wired USB cable for my config and development work, It's final destination will require wireless. So I started to configure that today and discovered that it does not find any wireless access points. The device exists. 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether ac:6a:a3:3f:9c:65 brd ff:ff:ff:ff:ff:ff There is an overlay loaded (I did not add it, it was part of the image build) overlays=bananapi-m4-sdio-wifi-bt usbhost bananapi-m4-pi-5-6-i2c0 bananapi-m4-pi-7-8-i2c1 I do not see any errors from dmesg, but only these: [ 8.484857] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 8.851537] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [ 8.852261] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Aug 29 2023 01:47:08 version 7.45.265 (28bca26 CY) FWID 01-b677b91b I am not sure where to begin diagnosing this. I almost never use wireless on Linux so I could be overlooking something basic. # iwlist wlan0 scanning wlan0 No scan results # uname -a Linux bananapim4zero 6.13.11-edge-sunxi64 #5 SMP PREEMPT_RT Thu Apr 10 12:42:07 UTC 2025 aarch64 GNU/Linux

@firepowercan you let me know what is difference between Murata and Samsung ones? I don't know what is mine and I tried both but nothing is working for me.

I have been trying to diagnose a QHYCCD camera problem on a N2 running INDI server. Everything appears to work fine but after several minutes the device fails to respond. The device is only supported by QHY on a true USB3 slot. Looking on other forums USB and cable stability are a common problem with these QHY devices so falling onto the wrong USB bus would definitely be a problem. However looking at lsusb I can see the device has dropped onto the wrong USB bus: $ lsusb Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc. USB3.1 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04a9:3217 Canon, Inc. Canon Digital Camera Bus 001 Device 008: ID 1618:0716 QHYCCD QHY715U3G20-20230106 Bus 001 Device 006: ID 1a86:7523 QinHeng Electronics CH340 serial converter Bus 001 Device 005: ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey] Bus 001 Device 004: ID 0483:5740 STMicroelectronics Virtual COM Port Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The QHYCCD is showing up on USB bus 1 (which I'm sure is the USB2 480M) Confirmed here by lsusb -ttv $ lsusb -ttv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M ID 05e3:0620 Genesys Logic, Inc. /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0610 Genesys Logic, Inc. Hub |__ Port 1: Dev 4, If 0, Class=Communications, Driver=cdc_acm, 12M ID 0483:5740 STMicroelectronics Virtual COM Port |__ Port 1: Dev 4, If 1, Class=CDC Data, Driver=cdc_acm, 12M ID 0483:5740 STMicroelectronics Virtual COM Port |__ Port 2: Dev 5, If 0, Class=Vendor Specific Class, Driver=rtl88x2bu, 480M ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey] |__ Port 3: Dev 6, If 0, Class=Vendor Specific Class, Driver=ch341, 12M ID 1a86:7523 QinHeng Electronics CH340 serial converter |__ Port 4: Dev 8, If 0, Class=Vendor Specific Class, Driver=usbfs, 480M ID 1618:0716 |__ Port 2: Dev 2, If 0, Class=Imaging, Driver=usbfs, 480M ID 04a9:3217 Canon, Inc. I'm running the Armbian version of Ubuntu 22.04 with kernel 6.12.22 Linux odroidn2-1 6.12.22-current-meson64 #1 SMP PREEMPT Mon Apr 7 08:08:37 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux. Further : This only occurs if the USB3 device is connected during boot. If the same USB3 device is plugged in well after boot it is correctly detected as a HIGH speed USB device. I'm looking for any ideas on forcing this device to be detected as a high speed USB3 device during boot time. So I don;t have to keep remembering to unplug and plug it back in. Also posted in the Odroid and INDI forums. Walter Zambotti N2 - 22.04 Armbian xfce desktop N2+ - CoreElec KODI

I have a good news : I success to install the different version of Armbian on the eMMC of my OPI5 Plus . The step I follow : install any OS version on the device using the SD card (only way that was working at the beginning to install an OS). It will help to install the other versions in your eMMC use a computer to connect (by SSH) to your device : it will to facilitate the work download the OS version requested from your computer then transfer it on your device (OPI5 Plus for me). You can use filezilla to transfer it or any command line. The file is located on /home (but anywhere should work) for the following step you can use the user manual chapter "Using the dd command to burn the Linux image into eMMC" check that your OS image file is under /home and do : cd /home/ ls you should have at least the file you transfer : Armbian_X.X.X_Orangepi5-X_.img check the node of your eMMC ls /dev/mmcblk*boot0 | cut -c1-12 You should have : /dev/mmcblk1 This node, it is what you will use in the next step . Then use dd command to clear the eMMC, and don't forget to change de node (mmcblk1) if it is different sudo dd bs=1M if=/dev/zero of=/dev/mmcblk1 count=1000 status=progress sudo sync then use the dd command to burn the linux image transfered into the eMMC, Put the correct name of your image after if = Put the correct node name after of = sudo dd bs=1M if=Armbian_X.X.X_Orangepi5-X_.img of=/dev/mmcblk1 status=progress Then pull out your SD card and restart your device : it should start the OS from the eMMC. I success this installations way with 2 versions : - Armbian_24.11.2_Orangepi5-plus_bookworm_current_6.12.0_minimal.img - Armbian_25.2.1_Orangepi5-plus_bookworm_vendor_6.1.99_minimal.img I have no tested with and Orange pi 5 B, but I believe it can work because you have the same process in the user manual Vik

Many thanks Maka! Works like a charm. maxio loads automatically now. No need for modprobe Server listening on 5201 (test #2) ----------------------------------------------------------- Accepted connection from 192.168.0.25, port 45188 [ 5] local 192.168.0.26 port 5201 connected to 192.168.0.25 port 45192 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 111 MBytes 929 Mbits/sec [ 5] 1.00-2.00 sec 112 MBytes 942 Mbits/sec [ 5] 2.00-3.00 sec 112 MBytes 942 Mbits/sec [ 5] 3.00-4.00 sec 112 MBytes 941 Mbits/sec [ 5] 4.00-5.00 sec 112 MBytes 942 Mbits/sec [ 5] 5.00-6.00 sec 112 MBytes 941 Mbits/sec [ 5] 6.00-7.00 sec 112 MBytes 942 Mbits/sec [ 5] 7.00-8.00 sec 112 MBytes 942 Mbits/sec [ 5] 8.00-9.00 sec 112 MBytes 942 Mbits/sec [ 5] 9.00-10.00 sec 112 MBytes 942 Mbits/sec [ 5] 10.00-10.01 sec 1.50 MBytes 913 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.01 sec 1.10 GBytes 940 Mbits/sec receiver ----------------------------------------------------------- Tail of lsmod : maxio 12288 1 dwmac_rk 28672 0 stmmac_platform 20480 1 dwmac_rk stmmac 241664 3 stmmac_platform,dwmac_rk pcs_xpcs 24576 1 stmmac rk817_charger 20480 0 rtc_rk808 16384 1 rockchipdrm 180224 8 dw_hdmi_qp 20480 1 rockchipdrm dw_hdmi 45056 2 dw_hdmi_i2s_audio,rockchipdrm cec 45056 2 dw_hdmi_cec,dw_hdmi dw_mipi_dsi 16384 1 rockchipdrm analogix_dp 40960 1 rockchipdrm drm_display_helper 131072 4 rockchipdrm,dw_hdmi,analogix_dp,dw_hdmi_qp hid_logitech_hidpp 49152 0 hid_logitech_dj 32768 0

I'm coming here again, and I apologize for the insistence, but there was a lot of progress, and I managed to get an image working, and even with the mouse and keyboard working, I just couldn't get it to have a graphical interface. He was always asking for commands. I still tried to install grafic ambient as LXDE ou XFCE I saw with Copilot but it gave errors when installing!! Any suggestions/help you can give please?

duplicated

Hello people, I'm not a debian user so i'm not understand all concepts about apt and how the diferentes branch and dependencies are managed. Can you help me with the following case? (i tried to look for in forums without success, the information that I've found is referenced to another branch noble instead my branch 'focal' but i think it could be similar) i executed the following: sudo apt autoremove what it removed the following package: armbian-bsp-cli-rk322x-box thinking that it could be relevant for my SoC device i tried to install it again: sudo apt install armbian-bsp-cli-rk322x-box > The following packages have unmet dependencies: armbian-bsp-cli-rk322x-box-current : Depends: base-files (>= 25.2.3) but 11ubuntu5.8 is going to be installed E: Unable to correct problems, you have held broken packages. have i broken my system? how could i resolve it ? lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.6 LTS Release: 20.04 Codename: focal if you can help me it would be appreciated. thanks in advance.

Hello people, I'm not a debian user so i'm not understand all concepts about apt and how the diferentes branch and dependencies are managed. Can you help me with the following case? (i tried to look for in forums without success, the information that I've found is referenced to another branch noble instead my branch 'focal' but i think it could be similar) i executed the following: sudo apt autoremove what it removed the following package: armbian-bsp-cli-rk322x-box thinking that it could be relevant for my SoC device i tried to install it again: sudo apt install armbian-bsp-cli-rk322x-box > The following packages have unmet dependencies: armbian-bsp-cli-rk322x-box-current : Depends: base-files (>= 25.2.3) but 11ubuntu5.8 is going to be installed E: Unable to correct problems, you have held broken packages. have i broken my system? how could i resolve it ? lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.6 LTS Release: 20.04 Codename: focal if you can help me it would be appreciated. thanks in advance.

If this is improvement as described, please provide a PR to configs: https://github.com/armbian/build/blob/main/config/kernel/linux-meson64-current.config https://github.com/armbian/build/blob/main/config/kernel/linux-meson64-edge.config Thank you!

I think your driver is already in armbian, but your chip is not identified. To get it working you can identify it in the ethernet node this way: mdio { compatible = "snps,dwmac-mdio"; #address-cells = < 0x01 >; #size-cells = < 0x00 >; ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; ====> compatible = "ethernet-phy-id7b74.4411", "ethernet-phy-ieee802.3-c22";

I haven't identified exactly what module load or trigger causes the network device to appear - waiting for 10 seconds during generator execution doesn't do the trick, so there is something explicit that happens post-initramfs stage that allows wlan0 to be instantiated, and if I understand the comment thread correctly, having the initramfs handle it would be the intended fix. Have to do some testing to figure out which module/firmware/etc. though, so that will have to wait for a few days until I have some time with the system to experiment.

I will get an ili9486 soon, but it is different to yours: it has a red PCB and does not have the serial-to-parallel chip like those made for raspberry.

In case someone else needs MAX0621 support here are the original files sent to me from Maxio Tech and my modified patch file (my_v1_patch.patch) for kernel 6.12.24 Then : sudo modprobe -r dwmac_rk sudo modprobe -a maxio sudo modprobe -a dwmac_rk I made a startup script to do that but there must be a better way? maxio also needs to be selected (M) in kernel config phase of build script (Device Drivers -> Network Device Support -> PHY Deice Support and Infrastructure) Release Note.txt v1_patch.patch maxio.c README my_v1_patch.patch

Armbian Weekly Highlights This summary highlights key updates to the Armbian build repository, including kernel adjustments, tooling fixes, and configuration changes. These contributions reflect ongoing efforts from the community to ensure system stability, compatibility, and enhanced performance across supported platforms. Rockchip: Fixing Broken EDGE Kernel Patch Commit by: @Igor Pecovnik View Commit › Add “Out of Date” Notice to Example Config Author: EvilOlaf View Commit › UFS Devices: Add Sector Size Variable Author: FantasyGmm View Commit › Update prepare-host.sh “This doesn’t feel right. The package exists across all main distros. Probably not needed in every case… but it’s toolchain-related, so worth revisiting if merged.” Author: Werner View Commit › Add New Host Build Dependency for Noble Author: EvilOlaf View Commit › rockchip64: Fix ATF Build & Bump to Latest Author: Werner View Commit › Allwinner: Bump to Latest Author: Igor Pecovnik View Commit › Fix ORAS Tooling Download – Add wget Moved wget to basic dependencies Cleaned up spacing Author: Werner View Commit › ZRAM Service Fix – mkfs Deprecation Author: Igor Pecovnik View Commit › Auto-Sync Board Config Status Author: Igor Pecovnik View Commit › Fix jq Filter Usage in apt-utils Author: Franklyn Tackitt View Commit › AIC Wi-Fi Driver Adjustment for Rockchip Author: Igor Pecovnik View Commit › BananaPi SM1: Fix Patch Naming “Do to my laziness these patches were submitted ugly. My bad.” Author: Patrick Yavitz View Commit › Btrfs Root on Subvolume Support Author: Igor Velkov View Commit › U-Boot v2025 for Sunxi: H616 Fixes, DTS Updates Author: The-going View Commit › Sunxi 6.13 Series Re-export Patches b10d00d Fix EMAC0/MDIO0 (rtl8211F) 61ad7ce Zero2W: Add Missing Nodes c019129 Update to v6.13.11 83d866a Add Sound Support for H616/618 c5fc8be PWM Nodes & Overlays f61dc0c Enable TV Output & Zero2W Patches 481b407 Cedrus V4L2: Add More Formats + DMA Update f2c4d41 Panfrost: Rework Power Domain Patches (v2) c129052 Switch from rkr5 to rkr5.1 Author: Mecid View Commit › Improve Example Config Handling Add BUILD_DESKTOP Automation 1469fda Fix Link & Create Proper Example c93edf5 Copy Example Config at First Start 554580a Remove Deprecated lib.config 1d9c78a Armbian is a community-driven project maintained by a group of dedicated individuals in their limited free time. We provide the platform and tools for collaboration, but fixing every bug is beyond our capacity. Even large, well-funded teams face similar limits. That’s why we rely on the community—not just for reporting issues, but for actively helping to resolve them. file:///tmp/lu1588574hd9ee8.tmp/lu1588574hd9fat_tmp_858a6d92.png View all commits and contribute at github.com/armbian/build file:///tmp/lu1588574hd9ee8.tmp/lu1588574hd9fat_tmp_7111f4e6.png Support Armbian development: Donate Today! The post Armbian Weekly Highlights first appeared on Armbian. View the full article

Yes, I'm aware of that. I wanted to try it because it has a more up-to-date version of Podman, and will likely become stable by the end of the year.

Non-standard docker image can cause rebuild since it is now based on Noble. Thanks for the information, @Werner. That was all useful to know. I removed the attributes you noted and tried building again. (FWIW, removing the DOCKER_ARMBIAN_BASE_IMAGE line using a fresh docker image (no cache)still defaulted to Jammy, not Noble. ) The final image turned out OK, but still required compilation. Is this because the target is Trixie (not Bookworm) which is still unsupported, or is it just not possible now to create a custom image without also compiling a kernel?

I think I figured out the expert=yes switch a few days ago and built a test vendor kernel image. Works splendidly with the exception of an issue with screen not recovering from going to sleep or some such. Thanks for your assistance eselarm and Werner for the sharing of your expertise.

@OP: you need to give more info - what board? - what user space (Ubuntu or Debian, what release)? You said this works on Ubuntu. That was not an SBC? Edit: This issue is known upstream. Ubuntu does not have a delta to Debian and hence should be affected as well. In any case, there is not much Armbian can or is likely going to do.

Please be aware that trixie is as of now still unsupported

Bug in NetPlan / systemd-networkd or bug in Armbian implementation? We have no options to maintain NetPlan or any other similar complex user space component. Armbian uses Ubuntu / Debian packages without changes as we are focused into Kernel space, framework, tools, build automation. If there is a workaround, we can push it somewhere. Like this one: https://github.com/armbian/build/commit/7f32a5853513745ee6aa55b6d3856ac67ec036e2 Forum is just fine. Armbian itself don't have resources to touch any of this, but someone might know something and help you / everyone. I briefly understand what is the problem, but no idea how to solve it.

well.. just to answer your questions.. just because i really think you mishandled or completely misinterpreted what i said.. i didn't undervalued in any way the dedication and good work of everyone on this forum.. for the contrary! it's exactly for all that hard work, that i know that's it's really a lot simpler than it would be if this forum didn't exist! after the work done here, essencially most of the cases, if the chipset is the same it's simply install the right drivers and fly away! i'm saying this forum has done a great job doing our job very very very easy by comparison to what as already been done! now regarding your questions... no support: chipset is nothing more than a computer, and thanks to a lot of good people on this forum and others, if you understand about linux, all the hard work is done for us.. basically we just have to test the versions of armbian that will run on our boxes and make good use of the eyes to physically open the box and check the hardware we have to install the right drivers and put it working as best as possible. varying hardware quality: same answer as above.. varying hardware in general: once again, same answer as above.. no documentation: once again, same answer as above.. You said things for completely different questions than mine.. i simply don't understand why there are a lot of people saying bad things even if it's exactly the same hardware present on the box that exists on some development boards... i always were very close with computers, i know a lot of programming languages and in essence i am addicted to computers and generally everything related to technology.. for someone who knows how to deal with pratically everything i get my hands on in terms of messing with hardware and programming in several degrees, i really don't get it whats so hard just by oppening the 4 screws on the bottom of the boxes, and read the cpu, lan, wifi and Bluetooth and simply installing the basic system and it's drivers.. yes, its as simple as doing that after dealing with the bootloader, and that, with so much shares there are nowadays in the internet i can honestly say i never had any problem with any box i had in my hands.. and basically, there are a lot of boxes, i can say around 90% that have compatible firmwares, being the main and biggest problem for a lot of people, the wifi, the lan and the Bluetooth.. and after you know how to build your drivers, it's really so easy to get things going.. so yeah, in a tech perspective i think it's ridiculous to think that there are boxes impossible to get it working right.. it just takes a bit of work, but for anyone that knows how to deal with linux (and this forum is about armbian, essentially linux) i see all that hate as comparable to someone in a Windows forum putting hate for someone saying they are having difficulties installing a driver on Windows on computers that are not from a bigger brand.. and for the kind of affirmation you made it looks like you think i'm one of those superfans of iptv that sells boxes with servers subscription 😂 but nop, not one of those.. i never wanted anything to do with it, but i sold a lot of android boxes to guys like that, so yeah, i know what you mean 😉 essentially, i had here in my country since 2013, a big website during almost 10 years called lojandroid.com, "loja" from that name is the equivallent to "store". Nowadays everyone knows what a android box is and it's sold even in supermarkets, but during at least in my first 3 years selling them, i can tell you i had sales on several portuguese marketplaces that didn't had another seller with android boxes beside me 😉 As i said before, i always loved messing with hardware, and for several years i sold lots of android boxes with all kind of servers installations, and yes, had a few times customers coming back asking for warranty for heating and freezing installations and/or corrupt installations on the ROM, but if you understand of computers as i think you do, for sure you know on demanding tasks like some uses on home servers, some of the uses sometimes asked too much for too long for the ROM memory or even the sdcards, it's very, very easy to corrupt data on memory, be it ROM, Sdcard or evens USB, ant that happens if it's a big well known cipset and model or not.. when its sdcard installation (the easiest for correcting problems, or simply maintenance) simply had to copy from my backup of the system i had for that model, burn to a new sdcard, and the customer just had to put the sdcard on the box, turn it on and voilá, a new system on a push of a button.. because yes, every model box i sold i made a backup of its original firmware and of mine with my modifications.. And yes, in some demanding tasks its a lot safer to recover just by using a system installed on the sdcards, and usually on that situations its resolved just by replacing a sdcard, a lot easier than trying to recover the internal memory of a chipset, that not always goes the best way.. The brand i sold a lot during the first years, was minix, and i can tell you that the some problems i had with the cheapest, also had with minix.. but the big question there is that 1 minix box price would pay around 3 boxes with the same hardware on white brands.. There will always exist the purists and normal people that know that the world is a lot bigger than the bigger brands.. but for the looks of you affirmations it looks like for example you dont know that for example nowadays the chinese eletric cars are becoming far superior than the most known brands.. Nowadays BYD, Polestar and a lot more brands are superior than the Teslas, but the teslas purists will say that it's not the same.. it's also the same things like Apple people say from the other brands or operating systems.. Nothing against teslas and iphones, in fact i adore teslas and even had two iphones, but in case of the iphone, me being me, i don't like to be locked, i also always messed a lot with the firmwares on my phones, and in Iphones, besides the jailbrake that just leaves it a bit more usable, i never got much to play concerning the things i like to do 😂 in conclusion, i'm not saying bad of the specific chipsets used for armbian! I just dont think that is white or black.. theres really of gray area in between, i for my experience know that the World is really a lot, lot, lot bigger than that, and chipsets simply are nothing more than a computer, and a lot easy to mess on that sense after getting the hang of it.. hope i gave someone a fun reading, and keep cool everyone 😉👍

Interesting effect of changing the ili9488 10cm (4.0 inch) for a 9cm (3.5 inch) LCD, same resolution https://a.aliexpress.com/_mMKRqan https://a.aliexpress.com/_mqk0Qbv (I bought a similar with touch) maybe I need a different spi frequency update: I changed 40 MHz to 60 MHz and my new LCD works perfectly:) update: with 60 Hz, full screen video has a lot of noise and distortion. With 70Hz, there’s only white dots on black background with 50hz, the console shows wrong colors and video is white noise with 30 hz, console text and video are ok… but video looks 10 fps the touch panel in the smaller 9cm LCD does not work. Do not buy it!