Search the Community

Unable to start docker after update, due to apparmor I used armbian-config's "edit boot-enviroment", added "extraargs=apparmor=0" and after a reboot I still get: docker start portainer Error response from daemon: AppArmor enabled on system but the docker-default profile could not be loaded: running `apparmor_parser apparmor_parser --version` failed with output: error: exec: "apparmor_parser": executable file not found in $PATH Error: failed to start containers: portainer armbianmonitor: https://paste.armbian.com/ebuburoxeh

Hi there, I'd like to understand the best way to handle updates on Armbian… My OS is: odroid ) uname -a Linux odroidxu4 5.4.225-odroidxu4 #22.11.1 SMP PREEMPT Wed Nov 30 10:55:16 UTC 2022 armv7l GNU/Linux odroid ) lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye And APT says: The following packages have been kept back: linux-dtb-current-odroidxu4 linux-headers-current-odroidxu4 linux-image-current-odroidxu4 linux-u-boot-odroidxu4-current The habits tell me to update however the experience taught that I could breaking something, some packages are on hold for a goodreason... What do you recommend? Thanks in advance 🙏 F.

Environment: Armbian on an Odroid-HC2 (Homecloud 2) which uses the odroid-xu4 firmware. Reproduction: After initial installation on the welcome banner "RX today:" always shows a nice value. Install and run some docker containers. This changes /sys/class/net/ . AFAIK it adds so called "virtual network interfaces". From then on the Armbian welcome screen displays like this: Error: Interface "veth•••••••" not found in database. Note: • redacted by me. Analysis: /etc/default/armbian-motd … PRIMARY_INTERFACE="$(ls -1 /sys/class/net/ | grep -v lo | egrep "enp|eth" | head -1)" … The current regular expression falsely matches veth••••••• (created by Docker). $ ls -1 /sys/class/net/ br-•••••••••••• docker0 enx•••••••••••• lo veth••••••• I fixed it for myself by changing PRIMARY_INTERFACE to this: "$(ls -1 /sys/class/net/ | grep -v lo | egrep "^en" | head -1)" Fix Proposal: A developer with proper knowhow of the network interface naming conventions changes the default regular expression / pipe for PRIMARY_INTERFACE so that it safely only matches a real hardware interface for all typical systems, also working fine when using docker or other software which may create virtual network interfaces or other stub like entries there. Notes: This bug was already discussed in a forum thread in a "how to help yourself" manner. This here now is a formal bug report with the inquiry to please fix it. I ran through the bug submission wizard at https://www.armbian.com/bugs/ which eventually led me here.

Hi, A strange error appeared with the last kernel update on an Odroid HC2. From the home in the terminal displays this error under RX totay: RX today: Error: Interface "--oneline" not found in database. The board is hosting an OMV instance under Armbian Bullseye Linux version 5.4.212-odroidxu4. Does anyone have any idea about the origin of this message which does not seem to disrupt the NAS operation. thanks konki

Dear All, I don't have much experience with the eMMC, and I wonder if I can flash this image: Armbian_22.11.1_Odroidxu4_bullseye_current_5.4.225.img.xz directly into the eMMC through Etcher, or do you recommend DD instead? Thanks... 🙏

U-Boot 2017.05-armbian (Nov 30 2022 - 10:45:39 +0000) for ODROID-XU4 CPU: Exynos5422 @ 800 MHz Model: Odroid XU4 based on EXYNOS5422 Board: Odroid XU4 based on EXYNOS5422 Type: xu4 DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1 MMC Device 0 ( SD ): 59.5 GiB Card did not respond to voltage select! mmc_init: -95, time 11 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 ** File not found /boot.ini ** ## Executing script at 43e00000 Wrong image format for "source" command 12548 bytes read in 44 ms (278.3 KiB/s) ## Executing script at 43e00000 111 bytes read in 33 ms (2.9 KiB/s) 6724096 bytes read in 550 ms (11.7 MiB/s) 11217705 bytes read in 881 ms (12.1 MiB/s) 0 bytes read in 45 ms (0 Bytes/s) Found mainline kernel configuration ** File not found /boot/dtb/exynos5422-odroidhc1.dtb ** ** Unrecognized filesystem type ** ** File not found dtb/exynos5422-odroidhc1.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Kernel image @ 0x40008000 [ 0x000000 - 0x669a00 ] ## Loading init Ramdisk from Legacy Image at 42000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11217641 Bytes = 10.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree ** File not found /boot.scr ** ## Executing script at 43e00000 ** Invalid partition 2 ** ## Executing script at 43e00000 ** Invalid partition 2 ** ## Executing script at 43e00000 ** Invalid partition 2 ** ## Executing script at 43e00000 mmc_init: -110, time 120 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... starting USB... USB0: USB EHCI 1.00 USB1: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 USB2: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... cannot reset port 1!? 1 USB Device(s) found scanning bus 2 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found USB device 0: unknown device Waiting for Ethernet connection... done. BOOTP broadcast 1 the boot fails after switching the kernel through armbian-config. Further investigation needed. //Edit 1: the dtb file is missing. ls -la /boot insgesamt 32336 drwxr-xr-x 2 root root 4096 8. Dez 19:03 . drwxr-xr-x 21 root root 4096 12. Jan 2022 .. -rw-r----- 1 root root 111 8. Dez 18:47 armbianEnv.txt -rw-r----- 1 root root 0 29. Dez 2021 armbianEnv.txt.out -rw-r--r-- 1 root root 1536 7. Aug 2019 armbian_first_run.txt.template -rw-r--r-- 1 root root 38518 7. Aug 2019 boot.bmp -rw-r--r-- 1 root root 4882 7. Aug 2019 boot-desktop.png -rw-rw-r-- 1 root root 12548 7. Aug 2019 boot.ini -rw-r----- 1 root root 0 29. Dez 2021 boot.ini.out -rw-r--r-- 1 root root 190980 30. Nov 12:07 config-6.0.9-odroidxu4 lrwxrwxrwx 1 root root 21 6. Dez 18:42 dtb -> dtb-5.4.225-odroidxu4 lrwxrwxrwx 1 root root 22 15. Apr 2020 dtb.old -> dtb-4.14.176-odroidxu4 -rw-r--r-- 1 root root 11217641 8. Dez 19:03 initrd.img-6.0.9-odroidxu4 -rw-r--r-- 1 root root 0 8. Dez 19:03 .next -rw-r--r-- 1 root root 3672734 30. Nov 12:07 System.map-6.0.9-odroidxu4 lrwxrwxrwx 1 root root 23 8. Dez 19:03 uInitrd -> uInitrd-6.0.9-odroidxu4 -rw-r--r-- 1 root root 11217705 8. Dez 19:03 uInitrd-6.0.9-odroidxu4 -rwxr-xr-x 1 root root 6724096 30. Nov 12:07 vmlinuz-6.0.9-odroidxu4 lrwxrwxrwx 1 root root 23 8. Dez 19:03 zImage -> vmlinuz-6.0.9-odroidxu4 It seems that the armbian-config does not install the dtb and because of its enforced reboot, it kills the boot process.

$ systemctl status ● henry State: degraded Jobs: 0 queued Failed: 1 units Since: Sat 2022-12-03 10:19:04 GMT; 24h ago $ systemctl list-units --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● logrotate.service loaded failed failed Rotate log files $ journalctl -u logrotate.service Journal file /var/log/journal/c87d7c4913d949949100f089ec48b092/system.journal is truncated, ignoring file. -- Journal begins at Sun 2022-12-04 00:00:06 GMT, ends at Sun 2022-12-04 10:33:57 GMT. -- Dec 04 00:00:06 henry armbian-ramlog[2714]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2715]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2716]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2717]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2718]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2719]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2720]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2721]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry armbian-ramlog[2722]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8> Dec 04 00:00:06 henry systemd[1]: logrotate.service: Control process exited, code=exited, status=1/FAILURE Dec 04 00:00:06 henry systemd[1]: logrotate.service: Failed with result 'exit-code'. Dec 04 00:00:06 henry systemd[1]: Failed to start Rotate log files. Dec 04 00:00:06 henry systemd[1]: logrotate.service: Consumed 5.879s CPU time.

Hello. I freshly installed bullseye from the other supported variant links for an odroid XU4. When trying to get docker daemon running, it looked like the ip_tables module and br_netfilter modules weren't available in the kernel. I think I have sorted out ip_tables (modprobe doesn't return any problems now), but docker's daemon is still showing a problem when running dockerd (with debug level info in the daemon.json file): Running modprobe bridge br_netfilter failed with message: modprobe: WARNING: Module bridge not found in directory /lib/modules/5.19.10-armmp-lpae When executing systemctl status docker.service ... too see if the daemon is running I get: ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2022-11-20 00:24:34 UTC; 4s ago TriggeredBy: ● docker.socket Docs: https://docs.docker.com Process: 8266 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE) Main PID: 8266 (code=exited, status=1/FAILURE) CPU: 1.868s Nov 20 00:24:34 odroid-bullseye systemd[1]: docker.service: Scheduled restart job, restart counter is at 3. Nov 20 00:24:34 odroid-bullseye systemd[1]: Stopped Docker Application Container Engine. Nov 20 00:24:34 odroid-bullseye systemd[1]: docker.service: Consumed 1.868s CPU time. Nov 20 00:24:34 odroid-bullseye systemd[1]: docker.service: Start request repeated too quickly. Nov 20 00:24:34 odroid-bullseye systemd[1]: docker.service: Failed with result 'exit-code'. Nov 20 00:24:34 odroid-bullseye systemd[1]: Failed to start Docker Application Container Engine.

Is it possible to transfer the entire Armbian system from SD card to HDD? ... it is known that the SD card has a lower endurance than such a HDD dist (write, read etc.) I tried to transfer the system in such a way that I first upgraded the kernel to the newest one on the SD card and then moved the system files to a partition on the HDD: mount /dev/sda1 /mnt time tar --one-file-system -cpf - / | (cd /mnt && tar -xpf -) then knowing the sda1 partition information and ID lsblk -f then knowing the sda1 partition information and ID I changed the UUID / HDD number in two locations nano /boot/boot.ini and nano /etc/fstab after rebooting the system ... surprisingly it works OK, but actually the samba / ftp network (server vsftpd). The update also seems to work OK, i.e. apt update / apt upgrade ... However, there are programs that cause the Armbian system to stop working completely, eg transmission when downloading files to the HDD? ... restarting the system helps, but is it the fault of the transmission program itself copied from the SD card or maybe the Armbian system cannot work properly on the HDD? ... or maybe something else needs to be done to correctly transfer the system from the SD card to the HDD? if I restore the settings and boot from the SD card, Armbian / transmission / download works OK? I haven't checked the option of uninstalling transmission from the system to HDD yet and setting everything up again ... but will it help?

Hi, I was unable to boot the latest flavor of armbian for odroid xu4 (Armbian_22.08.7_Odroidxu4_bullseye_current_5.4.218_minimal.img). My Odroid HC2 card shuts down quickly and no ssh connection is possible. The card stays on if the network cable is physically disconnected but stops immediately when reconnected. The /etc/default/armbian-motd configuration file seems to be at fault? it should contain something like this : PRIMARY_INTERFACE="$(ls -1 /sys/class/net/ | grep -v lo | egrep "enp|eth|enx" | head -1)" maybe not : PRIMARY_INTERFACE="$(ls -1 /sys/class/net/ | grep -v lo | egrep "en|eth ... I finally took an older image file, as I didn't have much more time to work on it (Armbian_22.05.4_Odroidxu4_bullseye_current_5.4.199.img) konki

Hello, I have recently upgraded OMV to version 6 and armbian to bullseye alongside it: https://forum.openmediavault.org/index.php?thread/41361-odroid-hc1-armbian-update-report/ Since the upgrade, I am getting daily emails from armbian-truncate-logs with the following content: I am not sure if this is expected or not, but I was not getting these with OMV 5.

Odroid XU4 / Armbian 22.02 Bullseye USB3 sata drive gets randomly disconnected: (every 8 hours or so when constantly reading / writing) [44676.709229] sd 0:0:0:0: [sda] tag#24 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN [44676.709252] sd 0:0:0:0: [sda] tag#24 CDB: opcode=0x28 28 00 49 a5 1b d8 00 00 08 00 [44681.728962] xhci-hcd xhci-hcd.8.auto: xHCI host not responding to stop endpoint command. [44681.749158] xhci-hcd xhci-hcd.8.auto: xHCI host controller not responding, assume dead [44681.749210] usb 4-1.2: cmd cmplt err -108 [44681.749509] xhci-hcd xhci-hcd.8.auto: HC died; cleaning up [44681.749696] usb 3-1: USB disconnect, device number 2 [44681.751626] sd 0:0:0:0: [sda] tag#20 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD [44681.751666] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 3e a6 aa f0 00 00 08 00 root@btcfn:~# uname -a Linux btcfn 5.4.181-odroidxu4 #22.02.1 SMP PREEMPT Sun Feb 27 08:55:42 UTC 2022 armv7l GNU/Linux USB sata bridge JMicron (the official Hardkernel thingie)

Hey guys! I am running Armbian 22.05.3 on my Odroid XU4. Very happy with it. I just installed linux-image-edge-odroidxu4 (kernel 5.17) and rebooted. Everything hunky dory. However, once I'm on 5.17 I am unable to reboot by using the 'reboot' or 'shutdown -r now' commands, which worked on the default 5.4 kernel. Is this a known issue? Any hints on how to debug or any known workarounds? Thank you

I don't know how to explain this, so I start with my hardware: Two Odroid HC1. I love swapping Kernels, default was 5.4.199 but that was "too old" because I like it bleeding edge. Did upgrade both to 5.17.5 and it works like a charm! Really good performance and some errors from dmesg disappeared too! However the problems did not wait for long: Kernel 5.19.x broke fstrim commands on my SATA drives so I rolled back, everything was good on 5.17.5 again. My logs showed TRIM was supported and running again, cheers! Now to the actual problem at hand and this might be my own doing. I froze the upgrades in armbian-config. Thinking this would prevent upgrading to the new kernel (with the fstrim issues). It did however upgrade again and made both odroids unbootable. After very frustrating loopback device shenanigans with micro sdcard images I had my important data back again. Rolled to some old backups and lost nothing, made new backups and I am happy, though stuck on an "outdated" system as i am not installing updates anymore until I have realized my mistake. A few questions: 1) was freezing the mistake? 2) why is fstrim "broken" on SATA drives in 5.19.x? 3) how to prevent kernel upgrades permanently? 4) will switching to 5.4.x keep me on that branch safely, provided if I take the downgrade pill? What is the best course of action here? How can I force to stay on specific kernel branches and only get security patches? My main goal is working fstrim and being actually able to boot Greetings

Estoy perdido, despues de buscar y buscar soluciones, soy nuevo en este foro. He probado xu4fan, fancontrol, incluso un script que está en este foro, y no puedo iniciar el ventilador con armbian, ni siquiera puedo hacer que el ventilador se mueva. he intentado esto PUNTO_VIAJE_0=25000 PUNTO_VIAJE_1=30000 PUNTO_VIAJE_2=40000 echo $TRIP_POINT_0 > /sys/devices/virtual/thermal/thermal_zone0/trip_point_0_temp$ echo $TRIP_POINT_0 > /sys/devices/virtual/thermal/thermal_zone1/trip_point_0_temp$ echo $TRIP_POINT_0 > /sys/devices/virtual/thermal/thermal_zone2/trip_point_0_temp $ echo $TRIP_POINT_0 > /sys/devices/virtual/thermal/thermal_zone3/trip_point_0_temp$ echo $TRIP_POINT_1 > /sys/devices/virtual/thermal/thermal_zone0/trip_point_1_temp$ echo $TRIP_POINT_1 > /sys/devices/virtual/thermal/thermal_zone1/trip_point_1_temp$ echo $TRIP_POINT_1 > /sys/devices/virtual/thermal/thermal_zone2/trip_point_1_temp $ echo $TRIP_POINT_1 > /sys/devices/virtual/thermal/thermal_zone3/trip_point_1_temp$ echo $TRIP_POINT_2 > /sys/devices/virtual/thermal/thermal_zone0/trip_point_2_temp$ echo $TRIP_POINT_2 > /sys/devices/virtual/thermal/thermal_zone1/trip_point_2_temp$ echo $TRIP_POINT_2 > /sys/devices/virtual/thermal/thermal_zone2/trip_point_2_temp $ echo $TRIP_POINT_2 > /sys/devices/virtual/thermal/thermal_zone3/trip_point_2_temp$ # Velocidad objetivo del ventilador (PWM): 0, 60 180, 240, 255 echo "0 60 180 240 255" > /sys/devices/platform/pwm-fan/hwmon/hwmon0/fan_speed y la respuesta no se puede crear /sys/devices/virtual/thermal/thermal_zone0/trip_point_0_temp$: Permiso denegado he intentado esto https://github.com/lbseale/odroid-fan en teoria se arranca el servicio, pero, se acumula calor, como puedo hacer para que funcione?

At https://www.armbian.com/odroid-xu4/ only CLI version is available. Is there a desktop version?

Hi all, The grey wifi Dongle 5 I bought direct from Odroid seems to have stopped working with recent Debian releases. After much troubleshooting, I downgraded to Buster and it works fine - until I run apt update/upgrade. lsusb info is: Bus 003 Device 010: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter What's also interesting is that post upgrade, the device's name also changes to @_____, and its mac address changes to 00:00:00:00:00:00. The blue wifi light on the dongle won't even flash after upgrade. After apt upgrade: root@odroidxu4:~# iwconfig enx001e06361f54 no wireless extensions. docker0 no wireless extensions. veth099d042 no wireless extensions. @����� unassociated ESSID:"" Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 lo no wireless extensions. veth51d95a5 no wireless extensions. root@odroidxu4:~# ifconfig @�����: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 2312 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Latest that I can get wifi to work (before running apt update) is Armbian_20.11.10_Odroidxu4_buster_current_5.4.91_minimal When it's working, pre upgrade, the info I get is: root@odroidxu4:~# iwconfig veth59fc9ec no wireless extensions. docker0 no wireless extensions. vethfe1f602 no wireless extensions. wlx40a5efd5d9c5 IEEE 802.11AC ESSID:"WiFi-T7JR-5G" Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency:5.18 GHz Access Point: CC:32:E5:0E:8B:AE Bit Rate:867 Mb/s Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:****-****-****-****-****-****-****-**** Security mode:open Power Management:off Link Quality=98/100 Signal level=64/100 Noise level=0/100 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 lo no wireless extensions. enx001e06361f54 no wireless extensions. root@odroidxu4:~# ifconfig docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 inet6 fe80::42:76ff:fea1:e649 prefixlen 64 scopeid 0x20<link> ether 02:42:76:a1:e6:49 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 76 bytes 13510 (13.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enx001e06361f54: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 00:1e:06:36:1f:54 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth59fc9ec: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::701c:e5ff:fe55:5335 prefixlen 64 scopeid 0x20<link> ether 72:1c:e5:55:53:35 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 91 bytes 17422 (17.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethfe1f602: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::dcf7:80ff:fe17:3e4c prefixlen 64 scopeid 0x20<link> ether de:f7:80:17:3e:4c txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 100 bytes 18299 (17.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlx40a5efd5d9c5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 2312 inet 192.168.1.154 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::6a24:4aa4:7bdc:c247 prefixlen 64 scopeid 0x20<link> ether 40:a5:ef:d5:d9:c5 txqueuelen 1000 (Ethernet) RX packets 157 bytes 23355 (22.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 152 bytes 28952 (28.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Please let me know if there's any other information I can provide. Many thanks, appreciate your help.

Hi. I'm Using Armbian 21.05.6 Buster. After some firmware update my Odroid freezes frequently. Trying to fix this issue I found root@nextcloudpi:~# dmesg (cut) [ 18.997342] swapon: swapfile has holes Relevant further information could be: root@nextcloudpi:~# zramctl NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram1 lz4hc 50M 1.2M 168.7K 636K 8 /var/log /dev/zram0 lzo 998M 4K 81B 12K 8 [SWAP] root@nextcloudpi:~# swapon --show NAME TYPE SIZE USED PRIO /dev/zram0 partition 998M 0B 5 root@nextcloudpi:~# swapon --show NAME TYPE SIZE USED PRIO /dev/zram0 partition 998M 0B 5 The only information I found is to recreate swap. But in my case there is no file or partition to recreate - or do I miss something? Has anybody some help for me?

I have a new odroid XU4 that I plan to use for Home Assistant in Docker and run other services in containers. I have loaded a fresh copy of Armbian cli (fully updated) with bluetooth from armbian-config. I installed linux drivers for my usb module (rtl8761a) from the manufacturer and it comes up in "bluetoothctl" as registered and pairable. However "bluetoothd show" gives me a "D-Bus setup failed: Name already in use." I will need dbus to pass device information between my docker containers when I install docker and home assistant so this error is concerning. Any ideas on how I might resolve this error? Thank you armianmonitor url: http://ix.io/48FG

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’m running jammy and (I think) I’d like to upgrade to bullseye. But I can’t find a procedure for doing so. I’m guessing I can’t just dist-upgrade since jammy is Ubuntu and bullseye is Debian? I’ve googled for a procedure and searched this forum as well but I’m not finding a procedure. While searching this forum, I saw lots of topics where people had problems after upgrading to bullseye. Should I even do the upgrade? I don’t have much invested in the jammy install so far. Aside from running through armbian-config and getting all the settings the way I want them, the only things I’ve done are 1) installed Docker and 2) installed docker-compose. The latter was a major pain, though. I kept getting the “file not found” error. It took me hours to get it working and I’m still not exactly sure how I did it. Anyway, if my best course of action is to simply start over with the bullseye image, I can do that.

Hello everyone, I'm wondering if is possible to include in future releases of the Armbian Kernels these options: CONFIG_NETLABEL CONFIG_MPTCP CONFIG_NET_VRF CONFIG_OF_UNITTEST CONFIG_OF_DYNAMIC CONFIG_OF_OVERLAY CONFIG_INET_MPTCP_DIAG CONFIG_MPLS_ROUTING CONFIG_MPLS_IPTUNNEL CONFIG_NLMON CONFIG_NET_VRF CONFIG_GTP CONFIG_GENEVE CONFIG_IPVTAP CONFIG_IFB I'm playing around with my Odroid XU4 and I notice that I'm missing such options and drivers compiled in the Kernel. As an example Debian has these options enabled by default. In my case I created a script that is getting the Armbian Odroid XU4 kernel sources, applying these settings in config and rebuild the kernel.

I've tried nand-sata-install on Armbian_22.05.3_Odroidxu4_jammy_current_5.4.199.img and Armbian_22.05.3_Odroidxu4_focal_current_5.4.199.img. Right at the end of running nand-sata-install there's an error. If I try to install anything after nand-sata-install it will hang or the SSD will go into read only mode. To be safe I tested various SD cards and USB to SATA controllers. sed: can't read /boot/boot.cmd: No such file or directory sed: can't read /boot/boot.cmd: No such file or directory Error while creating U-Boot loader image with mkimage umount: /mnt/nand-sata-install.wwpusQ/bootfs: not mounted.

I tried updating my kernel to self-built 5.4.173 as usual. I got some errors during installation due to low space on /boot, but after removing leftovers of 5.4.168 the installation worked as expected. Something went wrong though, as my HC1 no longer boots. This is shown via UART: All the files seem to be on the SD card: $ ls -l insgesamt 32447 -rw-r--r--. 1 root root 64 8. Jan 16:27 armbianEnv.txt -rw-r--r--. 1 root root 0 6. Sep 2019 armbianEnv.txt.out -rw-r--r--. 1 root root 1536 29. Mai 2018 armbian_first_run.txt.template -rw-r--r--. 1 root root 38518 29. Mai 2018 boot.bmp -rw-r--r--. 1 root root 4882 29. Mai 2018 boot-desktop.png -rw-r--r--. 1 root root 12489 16. Jan 2021 boot.ini -rw-r--r--. 1 root root 0 25. Jun 2019 boot.ini.out -rw-r--r--. 1 root root 169645 22. Jan 10:57 config-5.4.173-odroidxu4 drwxr-xr-x. 3 root root 3072 22. Jan 15:34 dtb-5.4.173-odroidxu4 -rw-r--r--. 1 root root 11220008 22. Jan 15:23 initrd.img-5.4.173-odroidxu4 drwx------. 2 root root 12288 29. Mai 2018 lost+found -rw-r--r--. 1 root root 3194528 22. Jan 10:57 System.map-5.4.173-odroidxu4 lrwxrwxrwx. 1 root root 25 22. Jan 15:23 uInitrd -> uInitrd-5.4.173-odroidxu4 -rw-r--r--. 1 root root 11220072 22. Jan 15:23 uInitrd-5.4.173-odroidxu4 -rwxr-xr-x. 1 root root 7340760 22. Jan 10:57 vmlinuz-5.4.173-odroidxu4 lrwxrwxrwx. 1 root root 25 22. Jan 15:34 zImage -> vmlinuz-5.4.173-odroidxu4 Any ideas where to look?

Hello all! I used the following armbian image to write to an SD (I'm using an old odroid HC1 btw): https://armbian.site-meganet.com/dl/odroidxu4/archive/ I used the bullseye_current image that was there. On the main download page it says that the file for Odroid XU4 is compatible with HC1, HC2 and MC1. https://www.armbian.com/odroid-xu4/ My odroid HC1 boots ok but any attempt to use the built-in ethernet port results in an instant lock-up. Only way I can "get into" the device is with a USB ethernet adapter although even just issuing a command, eg ifconfig enx001e06366b84 192.168.1.99 locks everything up - even the USB ethernet adapter stopped working. I did check with ifconfig to find the relevent ethernet adapters'; names and two are listed. (The enx001e06366b84 name there is what the built-in ethernet adapters' name is btw). Does anyone know why trying to use the inbuilt ethernet should lock the entire device up? ljones