Search the Community

Armbian Bookworm 25.8.1. (minimal) Odroid XU4 with 32GB eMMc After lots of searching and trying 2017 Hardkernel solutions and github etc - And this forum suggestions - I could never get get it to boot. I think this is partly because things have changed since 2016/17. I did not have my eMMc on an usb adapter. Just installed, brand new (untouched from China) eMMc and a imaage install on MicroSD of Armbian. The method I believed should work was "armbian-install". But, it had errors while using mkpartimage. I put debug statements in the script and found the particular instance of invoking mkpartimage. Actually the issue is; 2 files are missing from /boot folder. Current SD installation image of Armbian minimal only creates one fdisk (MBR) partition on which /boot is a folder. I tried for ages to create a separate /boot partition. Maybe, since I have now succeeded with an eMMc install, I might try doing a separate root and boot. The 2 missing files are armbianEnv.txt and boot.cmd If one "touch"es armbianEnv.txt then - if it doesn't exist it will be created - if it does then no harm done. If one copies boot.ini to boot.cmd then these two things will satisfy armbian-install. Amrbian-install correctly changes the R/O of mmcblkXboot1 (where X is emmc device number) write the boot stuff and markit back R/O. It also ensures that armbianEnv.txt has got correct entries in it. In summary Install eMMc and Micro SD in XU4 Ensure SD/eMMc switch set to SD and boot armbian from SD Login as root or use sudo touch /boot/armbianEnv.txt cp /boot/boot.ini /boot/boot.cmd armbian-install choose the install and boot from eMMc option shutdown change switch to boot armbian from eMMc boot

Hi. I recently installed an Armbian 25.8.1 noble to an ODROID XU4 with CLOUDSHELL2. All is wonderful, except one thing. I can't make the small TFT work. I enabled the cs2 option in boot.ini, but did not solve the issue. Then it turned out the module loader in modproebe.d lokks as follows: options fbtft_device name=hktft9340 busnum=1 rotate=270 speed=35000000 force32b=1 bgr=1 but actually there is no such module (only hktft32 or hktft35, or ili9340 - none of these worked): /lib/modules/6.6.113-current-odroidxu4/kernel/drivers/staging/fbtft# ls -1 fb_agm1264k-fl.ko fb_bd663474.ko fb_hktft32.ko fb_hktft35.ko fb_hx8340bn.ko fb_hx8347d.ko fb_hx8353d.ko fb_hx8357d.ko fb_ili9163.ko fb_ili9320.ko fb_ili9325.ko fb_ili9340.ko fb_ili9341.ko fb_ili9481.ko fb_ili9486.ko fb_pcd8544.ko fb_ra8875.ko fb_s6d02a1.ko fb_s6d1121.ko fb_ssd1289.ko fb_ssd1305.ko fb_ssd1306.ko fb_ssd1325.ko fb_ssd1331.ko fb_ssd1351.ko fb_st7735r.ko fb_st7789v.ko fbtft.ko fb_tinylcd.ko fb_tls8204.ko fb_uc1611.ko fb_uc1701.ko fb_upd161704.ko How should it be possible getting this hktft9340 module into the kernel? Thank you!

Hi all, I got my hands on an Odroid XU4 and wanted to use it as a replacement for my RPi 3 for all my amateur radio related stuff. Unfortunately all of the AX25 kernelmodules have been left out of official builds. I have a commit ready to add them back, yet I am not sure what the actual process is to submit a PR. As I understood I need to open an issue first yet I cannot figure out which category this fits in. I attached a patch file for current kernel. Thank You, Geoffrey ax25.patch

I recently noticed my ODroid XU4 was reporting weird temperature readings: cat /sys/class/thermal/thermal_zone0/temp -22000 Is this a software issue or maybe hardware failing? Also, I would like to upgrade, is there another board I could just transfer my EMMC to and be up and running? Thanks

A known issue with the Odroid XU4, HC1, and HC2 is that it (uboot?) does not properly park the hard disk heads before/during shutdown or power cycle/off. So, the disk drive is forced to emergency hard retract the heads when power is shutdown/cycled. This is of course a violent action for the HDD and should be avoided. Use this odroid.shutdown script and install into /lib/systemd/system-shutdown/. https://wiki.odroid.com/odroid-xu4/troubleshooting/shutdown_script Recommend adding to armbian for XU4 distros.

Using Armbian_25.8.1_Odroidxu4_noble_current_6.6.102.img I can boot off SD. Then when I run nand-sata-install it sharts and comes up with initramfs prompt. I'll try to fix it there next time, but I'm just using a 3.5" SATA laptop disk with USB controller. .oading, please wait.. .tarting systemd-udevd version 255.4-1ubuntu0.11 .begin: Loading essential drivers ... done. .begin: Running /scripts/init-premount ... done. .begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. .begin: Running /scripts/local-premount ... done. .begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. done. Save up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay=(did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=546a0798-29c9-4f3c-beea-1563d848abd0 does not exist. Dropping to a shell! BusyBox v1.36.1 (Ubuntu 1:1.36.1-6ubuntu3.1) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) _ I had old image Armbian_23.11.1_Odroidxu4_jammy_current_6.1.63.img and it works fine.

Try to upgrade from 25.5.1 but base-files not present in repository. Missed again. @Igor can you fix it?

i've been using armbian for a whole hour now i figure i've mastered this thing :) i loaded Armbian_25.5.1_Odroidxu4_bookworm_current_6.6.88_minimal.img on a sd and fired up an old xu4 according to the instruction the first thing to do is run armbian-config but it hangs because i don't have an interweb connection is there a way around that

Hi guys, this is something that I would like to achieve if feasible. I remember that other OS like "RetroPie Arena" support GPU acceleration, thanks. Any documentation to read? Thanks! 🙏

Hi, I'm trying to run weston on Odroid XU4, but it does not start. Seems something is wrong with GPU drivers. I have installed "Armbian 25.2.1 Bookworm Minimal" image and then installed weston via apt. Then, trying to run the weston fails with error: Date: 2025-04-13 UTC [13:47:44.248] weston 10.0.1 https://wayland.freedesktop.org Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/ Build: 10.0.1 [13:47:44.249] Command line: weston [13:47:44.249] OS: Linux, 6.6.81-current-odroidxu4, #1 SMP PREEMPT Mon Dec 30 15:59:39 UTC 2024, armv7l [13:47:44.249] Flight recorder: enabled [13:47:44.249] Starting with no config file. [13:47:44.250] Output repaint window is 7 ms maximum. [13:47:44.250] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-10/drm-backend.so' [13:47:44.265] initializing drm backend [13:47:44.265] Trying logind launcher... [13:47:44.280] logind: session control granted [13:47:44.290] using /dev/dri/card0 [13:47:44.291] DRM: supports atomic modesetting [13:47:44.291] DRM: supports GBM modifiers [13:47:44.291] DRM: supports picture aspect ratio [13:47:44.291] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-10/gl-renderer.so' MESA-LOADER: failed to open exynos: /usr/lib/dri/exynos_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load driver: exynos MESA-LOADER: failed to open zink: /usr/lib/dri/zink_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load driver: zink MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) failed to load swrast driver [13:47:44.301] failed to initialize egl [13:47:44.302] fatal: failed to create compositor backend Internal warning: debug scope 'drm-backend' has not been destroyed. Runing weston in pixman mode with "weston --use-pixman" succeeds, but I need accelerated weston. Any idea how I can install the missing GPU drivers?

Looking at various Docker images on Docker Hub, I see images for armv6, armv7, and armhf. Which are the right ones to use on an XU4/HC2?

I recently installed:Armbian_25.2.1_Odroidxu4_bookworm_current_6.6.75_minimal.img on my Odroid HC2. Ran the configuration. I'm currently trying to resolve an issue with warm booting and losing the hard drive. I've read this: https://forum.odroid.com/viewtopic.php?f=97&t=44865 on the Odriod forum. And this: https://forum.armbian.com/topic/15611-odroid-hc1-and-kernel-54-soft-reset-makes-the-sata-drive-disappear/ here JMCC said: Just curious if this still applies today with that build of Armbian? Also if the solution of changing the boot.ini is still valid today to fix the soft reset error? Finally as an aside it doesn't look like "hdparm" was installed? Is that possible? If so why? Thanks for all the help.

I've been running Armbian on an Odroid HC1 board for some time now. We've just had a kernel upgrade and it now boots as an XU4 according to the motd. This used to be changeable with armbian-config (I did this regularly on kernel updates). But, with the new armbian-config I can't find a way to do this any more. *edit A bit more info Running SY017 in armbian-config gives an empty list, and I get this error: ls: cannot access '/boot/dtb/overlay/*.dtbo': No such file or directory In fact /boot/dtb/overlay/ does not exist

Hi, hope you're all doing well. I have this Odroid HC2 (XU4 without video output) that was running an old Armbian version. I intended to update to the latest one (o something close to it) but it seems it won't boot with the newer releases. The board seems to power up ok, leds apparently blinking in a normal fashion, but it seems it gets stuck somewhere. It doesn't acquire any IP address. Not having video output leaves me with little to no way of knowing what is failing. No logs seem to be created in the sdcard. I also tried DietPi images, which I believe are based on Armbian but the same thing happens. I does, however, boot the previous Armbian installation and an Ubuntu image I got from somewhere (but it's a desktop version which doesn't seem to include remote ssh access by default). So my guess is that I can mostly rule hardware or sdcard issues. I created "armbianEnv.txt" to include "board_name=hc2 # or xu4, xu3, hc1, hc2" boot.ini didn't show anything suspicious and the UUID in there matches the one of the sdcard I'm using. These are all the images I tried (with Etcher) (in no specific order) : - Armbian_25.2.1_Odroidxu4_bookworm_current_6.6.75_minimal.img - Armbian_25.2.1_Odroidxu4_ubuntu_noble_current_6.6.75_minimal.img - Armbian_24.8.1_Odroidxu4_bookworm_current_6.6.47_minimal.img - DietPi_2025-02-17_OdroidXU4-ARMv7-Bookworm.img - DietPi_2025-02-17_OdroidXU4-ARMv7-Bullseye.img - DietPi_2025-02-17_OdroidXU4-ARMv7-Trixie.img This is the only new image that did boot: - ubuntu-24.04-6.6-minimal-odroid-xu4-20240911.img Any ideas about what could be happening? Also, I couldn't find an older image to try out, i.e. something with a 5.X kernel, is there anywhere I could get one? Thanks in advance. MO

Title says it all. "_amd64" and "_arm64" are in the apt repository "_armhf" is missing.

armbian-bsp-cli-odroidxu4-current is held back because base-files_25.2.2-13ubuntu10-noble_armhf does not exist (again). As before, the fix seems to be wget https://apt.armbian.org/apt/pool/noble-utils/b/base-files/base-files_25.2.2-13ubuntu10-noble_amd64__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb wget https://apt.armbian.org/apt/pool/noble-utils/b/base-files/base-files_25.2.2-13ubuntu10-noble_armhf__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb dpkg-deb -x base-files_25.2.1-13ubuntu10-noble_armhf__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb armhf dpkg-deb -x base-files_25.2.2-13ubuntu10-noble_amd64__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb armhf_new diff -qr armhf armhf_new cp armhf/bin/locale-check armhf_new/bin/locale-check rmdir $(readlink -f armhf_new/lib64) rm armhf_new/lib64 dpkg-deb --control base-files_25.2.2-13ubuntu10-noble_amd64__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb armhf_new/DEBIAN vi armhf_new/DEBIAN/control (replace amd64 by armhf on line 4) grep -nrw armhf_new/DEBIAN -e lib64 (remove all instances of lib64 in files below) vi armhf_new/DEBIAN/postinst vi armhf_new/DEBIAN/postrm vi armhf_new/DEBIAN/preinst md5sum armhf_new/usr/bin/locale-check vi armhf_new/DEBIAN/md5sums (fix md5sum for usr/bin/locale-check) chown -R root:root armhf_new/* sudo dpkg-deb -b armhf_new base-files_25.2.2-13ubuntu10-noble_armhf__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb sudo dpkg -i base-files_25.2.2-13ubuntu10-noble_armhf__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb sudo apt update sudo apt upgrade

Today unattended upgrades ran and installed the following: libtasn1-6 linux-dtb-current-odroidxu4 linux-image-current-odroidxu4 linux-u-boot-odroidxu4-current Afterward, the system automatically rebooted and went into a boot loop. I had a backup I was able to copy to the emmc and get back up and running but it is from October 2024 and I am not really sure what to do. coming here to see if anyone else has experienced the same. I tried to run armbianmonitor -U and it had some weird html. I am pretty good with Linux but everything is self taught. thank you in advance for any help Dan

My hardware: Odroid HC2 Armbian 24.5.1 Bookworm with Linux 6.6.31-current-odroidxu4 : My backup restoration → Has other issues too → But apt upgrade results in various size and hash mismatches. Offtopic: apt upgrade or sudo dpkg --configure -a always crash the system (since summer 2024, troubleshooting without success since christmas 2024) Ruled out HW failure 80-90%. My local apt/dpg cache was corrupted, thus at /var/lib/dpkg/ backed up info/ to info.bak/ and mkdir info/ afresh. And now sudo dpkg --configure -a completed successfully the very first time! But 2025-02-09 ca. 12:00 CET and also later the afternoon apt upgrade results in various size and hash mismatches. Mirror sync in progress? Then decided to flash a fresh image and start fresh (in all cases the SHA checksum matched, and BalenaEtcher checked the flash as identical to the image) Armbian_24.11.1_Odroidxu4_bookworm_current_6.6.60-omv_minimal → Status LED flashes, but SSH never reachable. No idea at what level it fails. Armbian_25.2.1_Odroidxu4_bookworm_current_6.6.75_minimal.img.xz → Status LED flashes, but SSH never reachable. No idea at what level it fails. As recommended by the FAQs "Image does not boot" --> check previous images from archive Armbian_24.11.1_Odroidxu4_bookworm_current_6.6.60_minimal → Boots, SSH works, went through initial setup (root pw, locale, timezone, username, etc). → But apt update ; apt upgrade fails with size and hash mismatches at 2025-02-09 22:30 CET.

Please forgive me if it is a stupid question, but what is preventing us from keeping n previous kernels installed in case an update is broken and does not boot? Fedora does it, Ubuntu does too. In general it should be simpler to boot a previous kernel than to try to pull the SD card and fix it in a second machine.

Hi! I just flashed Armbian 24.11.1 Bookworm Minimal / IOT onto my Odroid HC1 SD-Card. The download page states: "For HC1 and HC2 we provide specially optimized config which has to be applied manually. This results in shorter boot time and lower consumption. Edit /boot/armbianEnv.txt and add: board_name=xu4 # or xu3, xu3, hc1" However there is no /boot/armbianEnv.txt. Should I just run the system as is or do I have to modify something to have it run optimally? Should I just create the file and add line? Thx! Björn

I've flashed: Armbian_25.2.0-trunk.193_Odroidxu4_trixie_current_6.6.65_minimal.img to my eMMC. It boots fine, but after a "armbian-upgrade" it will give a kernel panic upon reboot. I think the new kernel is borked.

I used the Armbian 24.11.1 Bookworm Minimal / IOT Image from https://www.armbian.com/odroid-xu4/. When i checked the boot messages with journalctl -b, then i can see the message -> "system vulnerable" Later i can read the message "Spectre BHB: enabling loop workaround for all CPUs". Is this a fix for the first warning message, or is my system vulnerable? Dec 16 20:32:58 odroidxu4 kernel: smp: Bringing up secondary CPUs ... Dec 16 20:32:58 odroidxu4 kernel: CPU1: thread -1, cpu 1, socket 1, mpidr 80000101 Dec 16 20:32:58 odroidxu4 kernel: CPU2: thread -1, cpu 2, socket 1, mpidr 80000102 Dec 16 20:32:58 odroidxu4 kernel: CPU3: thread -1, cpu 3, socket 1, mpidr 80000103 Dec 16 20:32:58 odroidxu4 kernel: CPU4: thread -1, cpu 0, socket 0, mpidr 80000000 Dec 16 20:32:58 odroidxu4 kernel: CPU4: detected I-Cache line size mismatch, workaround enabled Dec 16 20:32:58 odroidxu4 kernel: CPU4: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable Dec 16 20:32:58 odroidxu4 kernel: CPU4: Spectre BHB: enabling loop workaround for all CPUs Dec 16 20:32:58 odroidxu4 kernel: CPU5: thread -1, cpu 1, socket 0, mpidr 80000001 Dec 16 20:32:58 odroidxu4 kernel: CPU5: detected I-Cache line size mismatch, workaround enabled Dec 16 20:32:58 odroidxu4 kernel: CPU5: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable Dec 16 20:32:58 odroidxu4 kernel: CPU6: thread -1, cpu 2, socket 0, mpidr 80000002 Dec 16 20:32:58 odroidxu4 kernel: CPU6: detected I-Cache line size mismatch, workaround enabled Dec 16 20:32:58 odroidxu4 kernel: CPU6: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable Dec 16 20:32:58 odroidxu4 kernel: CPU7: thread -1, cpu 3, socket 0, mpidr 80000003 Dec 16 20:32:58 odroidxu4 kernel: CPU7: detected I-Cache line size mismatch, workaround enabled Dec 16 20:32:58 odroidxu4 kernel: CPU7: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable Dec 16 20:32:58 odroidxu4 kernel: smp: Brought up 1 node, 8 CPUs Dec 16 20:32:58 odroidxu4 kernel: SMP: Total of 8 processors activated (384.00 BogoMIPS). Dec 16 20:32:58 odroidxu4 kernel: CPU: All CPU(s) started in HYP mode. Dec 16 20:32:58 odroidxu4 kernel: CPU: Virtualization extensions available.

Hello, I have been struggling with this for a while, found some replies on the other communities but I simply cannot get Wireguard up and running on my Odroid HC2 with Armbian. Running... echo "deb http://deb.debian.org/debian/ unstable main" > /etc/apt/sources.list.d/unstable-wireguard.list printf 'Package: *\nPin: release a=unstable\nPin-Priority: 90\n' > /etc/apt/preferences.d/limit-unstable apt update apt install -y linux-headers-odroidxu4 wireguard yields... Loading new wireguard-0.0.20181218 DKMS files... dpkg: warning: version '3.10.106-odroidxu4 4.19.14' has bad syntax: invalid character in revision number Building for 4.19.14-odroidxu4 Module build for kernel 4.19.14-odroidxu4 was skipped since the kernel headers for this kernel does not seem to be installed. Do I really need to compile Wireguard from source? :-(

I recently installed Armbian Jammy on my Hardkernel Odroid-HC1. By monitoring the storage usage through SNMP, I quickly realised that something was filling up the /var/log mountpoint at an alarming rate (40 % usage after three weeks). At a closer inspection, it turned out to be the sysstat logs. Even though sysstat was set (out of the box) to only keep 7 days of history, I could see files that were several weeks old. Having looked into the way that logs are synced to disc (or to the SD card rather), then rotated and synced back every night, it seems that the armbian-ramlog script is rather broken. It will move all of the sysstat logs, then expect the logrotation to rotate/compress/prune them (which it doesn't in the case of sysstat, since pruning is inherent in sysstat and logs aren't structured in the same way that others are). Finally, it will copy the files back (also old ones), thus effectively disabling the pruning mechanism of sysstat. Am I missing something or is this a bug? Seems odd that this issue should have gone unnoticed until now... Also, while looking into this issue, I noticed that the non-rsync armbian-ramlog does not respect sub-directories. For instance, /var/log.hdd/apt/* will get copied back to /var/log.

Hello community! I have performed an update from armbian 11 to 12 and OMV 6 to 7 and completed it successfully so far. Unfortunately just the package armbian-bsp-cli-odroidxu4 was not upgraded due to a missing dependency: +++ The following packages have unmet dependencies: armbian-bsp-cli-odroidxu4-current : Depends: base-files (>= 24.5.1) but 12.4+deb12u6 is to be installed E: Unable to correct problems, you have held broken packages. root@omv:~# sudo apt install 12.4+deb12u6 Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package 12.4+deb12u6 E: Couldn't find any package by glob '12.4+deb12u6' ok, let‘s try: root@omv:~# sudo apt install 12.4+deb12u6-current Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package 12.4+deb12u6-current E: Couldn't find any package by glob '12.4+deb12u6-current' +++ Is this package simply not available in the armbian repository or did I something fundamental wrong?