Vodalex

I solved the problems with the updates by completely disabling the kernel and firmware updates.. the board is alive and running great with OpenMediaVault .. All unattended updates were disabled completely. I hope the will be a stable kernel for this device in the future. Running it with 6.6.16 kernel which came with the image..

Updating to the current kernel immediately breaks everything.. Also the copy command of the copying u-boot-helios-4-sd.kwb is not helping in this case.. The device is not booting anymore.. Unpacking linux-image-current-mvebu (25.2.3) over (24.2.1) ... Armbian 'linux-image-current-mvebu' for '6.6.16-current-mvebu': 'postrm' starting. Armbian 'linux-image-current-mvebu' for '6.6.16-current-mvebu': 'postrm' finishing. Setting up libtext-iconv-perl:armhf (1.7-8) ... Setting up linux-image-current-mvebu (25.2.3) ... Armbian 'linux-image-current-mvebu' for '6.6.84-current-mvebu': 'postinst' starting . dkms: autoinstall for kernel 6.6.84-current-mvebu was skipped since the kernel head ers for this kernel do not seem to be installed. update-initramfs: Generating /boot/initrd.img-6.6.84-current-mvebu update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.84-curren t-mvebu Image Name: uInitrd Created: Sat Mar 29 15:48:16 2025 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 14351524 Bytes = 14015.16 KiB = 13.69 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.84-current-mvebu to /boot/u Initrd '/boot/uInitrd' -> 'uInitrd-6.6.84-current-mvebu' update-initramfs: Armbian: done. Remove unused generated file: /boot/initrd.img-6.6.16-current-mvebu Remove unused generated file: /boot/uInitrd-6.6.16-current-mvebu Armbian: update last-installed kernel symlink to 'zImage'... '/boot/zImage' -> 'vmlinuz-6.6.84-current-mvebu' Armbian: Debian compat: linux-update-symlinks install 6.6.84-current-mvebu boot/vml inuz-6.6.84-current-mvebu I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.6.84-current-mvebu I: /initrd.img.old is now a symlink to boot/initrd.img-6.6.84-current-mvebu I: /vmlinuz is now a symlink to boot/vmlinuz-6.6.84-current-mvebu I: /initrd.img is now a symlink to boot/initrd.img-6.6.84-current-mvebu Armbian 'linux-image-current-mvebu' for '6.6.84-current-mvebu': 'postinst' finishin g. Setting up armbian-zsh (25.2.3) ... cp: cannot create directory '/home/download/.oh-my-zsh': No such file or directory cp: cannot create regular file '/home/download/.zshrc': No such file or directory chown: cannot access '/home/download/.oh-my-zsh': No such file or directory chown: cannot access '/home/download/.zshrc': No such file or directory Setting up armbian-config (25.5.0-trunk.5.0206.155506) ... Setting up armbian-bsp-cli-helios4-current (25.2.3) ... Installing new version of config file /usr/lib/armbian/armbian-apt-updates ... Armbian 'armbian-bsp-cli-helios4-current' for '1-PCbbd5-V6a77-H6710-B6e44-R7697': ' postinst' starting. '/boot/boot.cmd' -> '/usr/share/armbian/boot.cmd-1743259697' NOTE: You can find previous bootscript versions in /usr/share/armbian ! Recreating boot script '/usr/share/armbian/boot.cmd' -> '/boot/boot.cmd' update-initramfs: deferring update (trigger activated) Armbian 'armbian-bsp-cli-helios4-current' for '1-PCbbd5-V6a77-H6710-B6e44-R7697': ' postinst' finishing. Setting up armbian-firmware (25.2.3) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for initramfs-tools (0.142+deb12u1) ... update-initramfs: Generating /boot/initrd.img-6.6.84-current-mvebu update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.84-curren t-mvebu Image Name: uInitrd Created: Sat Mar 29 15:48:45 2025 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 14378902 Bytes = 14041.90 KiB = 13.71 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.84-current-mvebu to /boot/u Initrd '/boot/uInitrd' -> 'uInitrd-6.6.84-current-mvebu' update-initramfs: Armbian: done.

This automated installation of the kernel did put the love to the ARM based devices to an end.. Was working solid.. but without display connector it is really diffucuilt to troubleshoot what is wrong with it. After the installation of OMV over the Armbian in the newest version network stops working and I cannot see why.. Time to sell this fine HELIOS4 to someone..

Can anybody help me with this?

Hello all! After upgrading to OMV 7 and Debian 12 my OLED display remains dark. I am using Kobol Helios 4 NAS. Can anyone tell me where the problem is? When i try to execute git clone https://github.com/kobol-io/sys-oled.git cd sys-oled sudo ./install.sh I get the following error message via SSH. Installing luma.oled library error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install. If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv. Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed. If you wish to install a non-Debian packaged Python application, it may be easiest to use pipx install xyz, which will manage a virtual environment for you. Make sure you have pipx installed. See /usr/share/doc/python3.11/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. Installing sys-oled files 'etc/sys-oled.conf' -> '/etc/sys-oled.conf' 'bin/sys-oled' -> '/usr/local/bin/sys-oled' 'share/sys-oled/C&C Red Alert [INET].ttf' -> '/usr/local/share/sys-oled/C&C Red Alert [INET].ttf' 'share/sys-oled/helios4_logo.png' -> '/usr/local/share/sys-oled/helios4_logo.png' 'system/sys-oled.service' -> '/etc/systemd/system/sys-oled.service' Enabling sys-oled at startup Does anyone have an Idea what to do?

Hello guys! I find it very convinient to see the temperature of the NVME drive installed while being logged on via SSH. How can I add the temperature of the drive right under the temperature of the cpu? I added a line: "echo -e "NVMe Drive Temperature: \033[32m$(sudo nvme smart-log /dev/nvme0n1 | grep temperature | sed 's/.*: //;s/ C//')°C\033[0m"" to the file /etc/update-motd.d/10-armbian-header What is the best way to do it?

Hello guys! Just tried another release (community) of armbian for Odroid M1 (Armbian_23.02.0-trunk_Odroidm1_sid_edge_6.1.11.img) Network seems to work fine here but why does the device show random ip instead of using the physical one, printed on the board?

Ok, i will post it there.. Strange that it behaves like that. I wanted to build a NAS with OpenMediaVault using Armbian.

Hello! I have bought Odroid M1 and installed arbian Image Armbian BullseyeCLI it works great but after installing OMV using armbian-config and rebooting the is no network available. If i run ap addr i get for the LAN adapter following: eth0: <BROADCAST.MULTICAST> mtu 1500 qdisc noo state DOWN qlen 1000 How can this be fixed? When I reboot the system it gets stuck on network configuration writing "A start job is running for Wait for Network to be Configured. I wait two minutes and then the system boots without network. The only chance to get network back is to run omv-firstaid and configure it or run following commands in the terminal ip link set dev eth0 up dhclient eth0 This command gives warning: /etc/resolvcon/update.d/libc: Warning: /etc/resolv.conf is not symbolic link to /run/resolvconf/resolv.conf Any help would be highly appreciated.