Search the Community

Long story short: I used for about one year an odroid HC4 as NFS server and worked fine. Now I would add a player service for it. It mounts an HDMI port, so I tried to plug in the cable and it worked. I were able to see the video output but with no sound. I found there is no detected hdmi card: # aplay -l **** List of PLAYBACK Hardware Devices **** card 0: ODROIDHC4 [ODROID-HC4], device 0: fe.dai-link-0 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: ODROIDHC4 [ODROID-HC4], device 1: fe.dai-link-1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: ODROIDHC4 [ODROID-HC4], device 2: fe.dai-link-2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 tried again after # alsactl init alsa-lib main.c:1541:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "axg-sound-card" "" "" "" "" Hardware is initialized using a generic method (alsactl -U init provides no error) The modules side looks fine to me (it was the same on 5.10.144, I tried moving to 5.19.10 with no result): # lsmod | grep snd snd_soc_hdmi_codec 24576 1 snd_soc_meson_axg_sound_card 16384 0 snd_soc_meson_card_utils 16384 1 snd_soc_meson_axg_sound_card snd_soc_meson_g12a_tohdmitx 20480 1 snd_soc_meson_codec_glue 16384 1 snd_soc_meson_g12a_tohdmitx snd_soc_meson_axg_tdmout 24576 1 snd_soc_meson_axg_frddr 36864 3 snd_soc_meson_axg_fifo 20480 1 snd_soc_meson_axg_frddr snd_soc_meson_axg_tdm_interface 16384 2 snd_soc_meson_axg_sound_card snd_soc_meson_axg_tdm_formatter 16384 2 snd_soc_meson_axg_tdm_interface,snd_soc_meson_axg_tdmout snd_soc_core 245760 10 snd_soc_meson_axg_tdm_formatter,snd_soc_meson_axg_sound_card,snd_soc_hdmi_codec,snd_soc_meson_g12a_tohdmitx,snd_soc_meson_axg_tdm_interface,snd_soc_meson_axg_fifo,snd_soc_meson_axg_tdmout,snd_soc_meson_axg_frddr,snd_soc_meson_card_utils,snd_soc_meson_codec_glue snd_compress 24576 1 snd_soc_core ac97_bus 16384 1 snd_soc_core snd_pcm_dmaengine 20480 1 snd_soc_core snd_pcm 131072 7 snd_soc_hdmi_codec,snd_compress,snd_soc_meson_axg_tdm_interface,snd_soc_core,snd_soc_meson_axg_fifo,snd_soc_meson_codec_glue,snd_pcm_dmaengine snd_timer 40960 1 snd_pcm snd 90112 5 snd_soc_hdmi_codec,snd_timer,snd_compress,snd_soc_core,snd_pcm soundcore 16384 1 snd I tried digging in dmesg and the only related issue that came out is:p panfrost ffe40000.gpu: error -ENODEV: dev_pm_opp_set_regulators: no regulator (mali) found but I wouldn't say that to be the source of the sound problem. There are errors but I don't feel the solution behind any of them. Do you? Kernel, modules, drive, dtb... where else could the lack of sound come from? Any suggestion?

Hi I was using: Title: Armbian 21.08.5 Odroidhc4 Debian buster legacy Then something bad pushed me to run apt update/upgrade No ZFS anymore. Installed 22.08.2, but, when tried to install kernel headers using armbian-config, result: "grep: invalid max count" message. What is the current correct way to install Armbian with ZFS? Thanks ChrisO

Hello, After a firmware update today I got a problem with Wireguard on my Odroid-hc4. I got that when checking ufw status, sudo ufw status verbose ERROR: problem running iptables: modprobe: FATAL: Module ip_tables not found in directory /lib/modules/5.10.123-meson64 iptables v1.8.7 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. How to fix that? Laurent

Dear All, I am using Jammy with kernel 5.18 on hold, but yesterday I noticed very important updates that were kept back because the kernel is locked, such s: armbian-bsp-cli-odroidhca armbian-firmware linux-dtb-edge-meson64 linux-headers-edge-meson64 linux-image-edge-meson64 linux-u-boot-odroidhc4-edge I wonder if is worth to update or if I had better to stick with my current setup, where my main feature — ZFS — is working. What's your recommendations? Thanks in advance! F.

Is there any way to enable Wake on Lan? As far as I know the Odroid-HC4 Supports WoL but I can't get it to work

I do not have petitboot installed. I ran the Armbian buster with OMV5 for over a year. I decided to make a clean install and booted Armbian bullseye 11. I changed hostname and rebooted (curiously reboot doesn't reboot the hc4, why?). I used armbian-config to install OMV. Installation completed, brought me back to armbian-config and prompted to reboot. I hit reboot (then was forced to power cycle as hc4 won't come back to life after a soft-boot?). Note that I was able to power cycle and get a good boot BEFORE omv installed but not after. At that point Odroid hc4 never comes back online. I've been through this 3 times today. I gave it as long as 30 minutes but doesn't respond even to pings. It does get the blue led blinking denoting successful kernel load. How do I get past this?! (I've tried with and without armbian-config's update upgrade with firmware, the full firmware option etc) Nothing is working. Any and all help is greatly appreciated.

I don't understand why I can't update to 5.19. I just updated to various user-space Debian 11.5 packages, but I can't see any newer kernels. root@odo:/boot# apt policy linux-image-edge-meson64 linux-image-edge-meson64: Installed: 22.05.1 Candidate: 22.05.1 Version table: *** 22.05.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 100 /var/lib/dpkg/status 22.02.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0046 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0045 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0040 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0035 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0034 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0031 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0029 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0027 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0025 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0023 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0021 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.11.0-trunk.115 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.11.0-trunk.108 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.11.0-trunk.101 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages root@odo:/boot# apt policy linux-u-boot-odroidhc4-edge linux-u-boot-odroidhc4-edge: Installed: 22.05.3 Candidate: 22.05.3 Version table: *** 22.05.3 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 100 /var/lib/dpkg/status 22.05.2 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.05.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.08.8 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.08.6 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.08.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages I'm looking at https://mirrors.xtom.de/armbian/pool/main/l/ for example and I can see items such as https://mirrors.xtom.de/armbian/pool/main/l/linux-5.19.5-meson64/. How do I get my apt to see them?

Is there a command to load this splash screen that shows when I open a new session? Also is there a way I can show the storage availability/temperature for the second hard drive? I think the current setting only shows information for the drive on /sda but i need info for drive on /sdb

Hi ! I recently got an Odroid HC4. I am following the guide (https://www.armbian.com/odroid-hc4/) to install Armbian 22.05 Bullseye on it. But I have some problems and I dont know how to do.. So my problems is actually this part : "Create a file in /etc/fancontrol with the following content: INTERVAL=10 DEVPATH=hwmon0=devices/virtual/thermal/thermal_zone0 hwmon2=devices/platform/pwm-fan DEVNAME=hwmon0=cpu_thermal hwmon2=pwmfan FCTEMPS=hwmon2/pwm1=hwmon0/temp1_input FCFANS= hwmon2/pwm1=hwmon2/fan1_input MINTEMP=hwmon2/pwm1=50 MAXTEMP=hwmon2/pwm1=60 MINSTART=hwmon2/pwm1=20 MINSTOP=hwmon2/pwm1=28 MINPWM=hwmon2/pwm1=0 MAXPWM=hwmon2/pwm1=255 followed by: sudo systemctl restart fancontrol" I made this file (see screenshot). Then I run the command, and I got an error : And this I was is shown when I type the command "systemctl status fancontrol;service" :

I see a lot of tutorials online and they all have seems to have different ways of going about making a share and it seems most of them are logged into a user as opposed to root. I'm logged in to root through ssh so that might the the cause of many of my issues I believe. I did a simple apt install samba and it seems to be running fine. I see other tutorials recommending you install "smbclient" and "cifs-utils", is that necessary? Some of the tutorials also say to add user groups and to add settings to the firewall. I'm just using 1 user and don't have any firewalls installed, unless armbian comes with one by default. I think my my service is running fine though. When I run 'sudo systemctl status smbd' it says "active (running)" in green. I can open the sbc on the network and view the shared folders, I cannot access them however. Also the sbc does not show up when I click network on windows explorer, it will however open if i type in the ip/name manually on run or the open bar, not sure if that matters. I did create a new user and gave it a samba password (mouse) I did chown the folder to the user and chmod 777. Here's the what comes up when i ls -al in the root directory where the folder i'm trying to share is located: drwxrwxrwx 3 mouse root 4096 Jun 5 09:25 testfolder Here's my smb.conf [testfolder] comment = Test Folder path = /root/testfolder browseable = yes read only = no writable = yes guest ok = no force user = mouse create mask = 0777 directory mark = 0777 On path I did /root/testfolder instead of /testfolder because I also mounted a hard drive inside that folder. When I tried mapping a drive to fstab using the directory /testfolder , it kept giving me an error about folder not existing or something, but when I typed /root/testfolder , it correctly mounted the drive. I also tried using the /testfolder on the smb config and it doesn't work either. These folders structures are REALLY confusing. When I ls -al in root don't see any folders like mnt var etc I only see the "testfolder" i created and a few folders starting with a period like .bashrc .... Where are the other folders located? in /root/etc ? Here's the error I get when trying to access my folder.

Hi all, we have developed a script to create an SD image for Odroid HC4. With this method you can use Armbian without erase Petitboot partition. https://github.com/TheLillo/generate-image-hc4-armbian

I noticed that TOP an HTOP are in disagreement about many things while my LCD Info panel and TOP are on the same page... TOP OUTPUT top - 23:50:26 up 5:18, 2 users, load average: 1.69, 1.77, 1.72 Tasks: 226 total, 1 running, 225 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.6 us, 0.7 sy, 0.0 ni, 84.5 id, 13.4 wa, 0.1 hi, 0.7 si, 0.0 st MiB Mem : 3785.8 total, 135.1 free, 2551.9 used, 1098.8 buff/cache MiB Swap: 1892.9 total, 1891.4 free, 1.5 used. 1139.1 avail Mem HTOP OUTPUT 1[||||||| 7.9%] Hostname: odroidhc4 2[|||| 4.0%] Tasks: 45, 13 thr; 1 running 3[||| 2.6%] Load average: 1.60 1.65 1.69 4[||| 2.0%] Disk IO: 23.7% read: 0K write: 32K Mem[|||||||||||||||||||673M/3.70G] Network: rx: 5.50MiB/s tx: 115KiB/s (5821/2708 packets) zrm[| 1.16M(5.52M)/1.90G] Uptime: 05:23:36 Swp[| 1.50M/1.85G] Systemd: running (0/353 failed) (0/220 jobs) Who is right?

Ok folks... This very setup was fixed and made working at my job. I tested from the new M$ Terminal while connected to the LAN of my office, extremely satisfied I returned to home and when I connected the HC4 to my router, the "systemd smbd.service" didn't work again (event though at my workplace I rebooted for testing purpose the board several time and Samba had been woking all the time). The Office LAN is most likely managed by a Win Server and is on 192.160.0.X, at home I am connected to a Comcast Cable Router on 10.0.0.X... This the error I get from systemd: × smbd.service - Samba SMB Daemon Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2022-06-08 20:48:33 EDT; 19min ago Docs: man:smbd(8) man:samba(7) man:smb.conf(5) Process: 3650 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) Process: 3655 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE) Main PID: 3655 (code=exited, status=1/FAILURE) Status: "daemon failed to start: reinit_after_fork() failed" Error: 2 (No such file or directory) CPU: 306ms systemd[1]: Starting Samba SMB Daemon... smbd[3655]: [2022/06/08 20:48:33.962189, 0] ../../source3/lib/util.c:482(reinit_after_fork) smbd[3655]: messaging_reinit() failed: NT_STATUS_OBJECT_NAME_NOT_FOUND smbd[3655]: [2022/06/08 20:48:33.962547, 0] ../../lib/util/become_daemon.c:119(exit_daemon) smbd[3655]: exit_daemon: daemon failed to start: reinit_after_fork() failed, error code 2 systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: smbd.service: Failed with result 'exit-code'. odroidhc4 systemd[1]: Failed to start Samba SMB Daemon My setup doesn't change the default "smbd.conf' but it recalls another configuration with: config file = /etc/samba/smb-local.conf I added that line to the very first section of the default "smbd.conf": [global] config file = /etc/samba/smb-local.conf ## Browsing/Identification ### # Change this to the workgroup/NT-domain name your Samba server will part of workgroup = WORKGROUP # server string is the equivalent of the NT Description field server string = %h server (Samba, Ubuntu) All my main configurations go under the "smb-local.conf", this is the setup has been taken from my current "OMSC/RPI2" Samba configuration: [global] # If you require a fully custom smb.conf create smb-local.conf instead of editing smb.conf so your # configuration will not be overwritten by samba upgrades. You can use smb.conf as a template by # copying it to smb-local.conf then removing the config file line below in the new file. If you only # need to add some additional shares see smb-shares.conf below for a simpler way to do this. workgroup = YOUR-HOME-CLOUD security=user follow symlinks = yes wide links = no unix extensions = no lock directory = /var/cache/samba load printers = no printing = bsd printcap name = /dev/null disable spoolss = yes log level = 1 map to guest = bad user usershare template share = automount template ############## read raw = Yes write raw = Yes strict locking = no min receivefile size = 16384 use sendfile = true aio read size = 2048 aio write size = 2048 socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=131072 SO_SNDBUF=131072 ## FreeBSD Changes ntlm auth = yes server max protocol = SMB3_11 server min protocol = NT1 client max protocol = SMB3_11 client min protocol = NT1 [droid] browsable = no read only = yes valid users = droid path = /home/YOUR-HC4-USER comment = Droid Home Directory [automount template] browseable = yes -valid = no valid users = YOUR-HC4-USER path = %P hide files = /$RECYCLE.BIN/System Volume Information/desktop.ini/thumbs.db/ # Add custom shares in smb-shares.conf instead of editing smb.conf so they will not be # overwritten by samba updates. You can only add new shares to smb-shares.conf, not change # the default shares or global options. If you need full control see smb-local.conf above. include = /etc/samba/smb-shares.conf Users are handled by: include = /etc/samba/smb-shares.conf This is an example how my "/etc/samba/smb-shares.conf" is composed and is taken by my documentation, but matches my current setup: [public] comment =Public Storage path = /srv/samba/public valid users = @users force group = users create mask = 0660 directory mask = 0771 read only = no [MyUSER] browsable = yes read only = no valid users = YOUR-HC4-USER, MyUSER path = /srv/samba/MyUSER comment = MyUSER Folder force group = users locking = no create mask = 0765 directory mask = 0765 Of course if I remove from "smbd.conf" this line: config file = /etc/samba/smb-local.conf The systemd service doesn't fail... But with my configuration "testparm -s" doesn't fail either... $ testparm -s Load smb config files from /etc/samba/smb.conf Loaded services file OK. Weak crypto is allowed Server role: ROLE_STANDALONE # Global parameters [global] config file = /etc/samba/smb-local.conf log file = /var/log/samba/log.%m logging = file map to guest = Bad User max log size = 1000 obey pam restrictions = Yes pam password change = Yes panic action = /usr/share/samba/panic-action %d passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . passwd program = /usr/bin/passwd %u server role = standalone server server string = %h server (Samba, Ubuntu) unix password sync = Yes usershare allow guests = Yes idmap config * : backend = tdb [printers] browseable = No comment = All Printers create mask = 0700 path = /var/spool/samba printable = Yes [print$] comment = Printer Drivers path = /var/lib/samba/printers Thanks! 🙏🙏🙏

Dear Friends, I have been testing Armbian 22.04 Current CLI version and 22.01 Edge Jammy CLI and both does not reboot. When I reboot Armbian the LEDs stop to blinking but I can clearly listen the rust-drives spinning, also the LCD is still active. Initially I though it was because the software that handles the LCD but I made a test without it and it was the same. I also thought that was because the spin drives, but when I did the test I made it without the disks as well, therefore I excluded both cases. Since I didn't read anything about it, I think this issue is affecting just me, any idea where I may look to find out what is preventing the board to reboot properly? Thanks in advance! Freezr

So, first of all, pretty much a newbie here. I'm trying to add protonvpn to my HC4. I was able to do it with Ubuntu Mate (from the HC4 webpage) on the same hardware, so I'm pretty sure it's possible on Armbian. To be fair, the ProtonVPN website says that raspbian is not supported (and I assume they meant to say ARM) but I have been able to get it to work on Mate, and the problem on Armbian seems to be the Public Key and nothing else. After installation, the app will start, but won't work, so some successful compiling for ARM seems to be happening. What I did: - Downloaded the deb file for Debian based stable release - Tried GDebi and Apt, but dpkg worked (relatively) better - sudo apt update resulted in: Err:12 https://repo.protonvpn.com/debian unstable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 71EB474019940E11 Reading package lists... Done W: GPG error: https://repo.protonvpn.com/debian unstable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 71EB474019940E11 E: The repository 'https://repo.protonvpn.com/debian unstable InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://repo.protonvpn.com/debian stable InRelease' does not seem to provide it (sources.list entry misspelt?) W: Skipping acquire of configured file 'main/binary-armhf/Packages' as repository 'https://repo.protonvpn.com/debian stable InRelease' does not seem to provide it (sources.list entry misspelt?) - I've tried fixing it using suggestion from https://askubuntu.com/questions/13065/how-do-i-fix-the-gpg-error-no-pubkey being: gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv 71EB474019940E11 gpg --export --armor 71EB474019940E11 | sudo apt-key add - - I retried using a keyserver from MIT and the Public Key file downloaded from the ProtonVPN website (took a few tries to get the syntax right). But every sudo apt update has the same result. Ready to provide more information as needed. Also ready to hear that this is either a bug or a feature.

First off, could someone please help. I did not seem to be able to create this topic without a tag and the only tag it would accept was "solved". Wondering if somebody could remove the "solved" tag and add in "odroidhc4"? I purchased a brand new odroid hc4 board with the intention of installing armbian and then subsequently OMV. My intention was/is to install Armbian on a MicroSD card. On the downloader page I read that in order to clean boot Armbian the incompatible Petit bootloader needs to be removed. I tried the bootloader bypass (preferred) method and that didn't seem to work for me. The board still seemed to go to the petitboot UI. I then tried the Petitboot Console method and ran the following commands as detailed on the download page: # flash_eraseall /dev/mtd0 # flash_eraseall /dev/mtd1 # flash_eraseall /dev/mtd2 # flash_eraseall /dev/mtd3 These all seemed to run/complete without issue. I then rebooted the board and now absolutely nothing happens. It doesn't boot to the Petitboot UI/Console and it doesn't boot to Armbian either.... Does anybody have any suggestions or wisdom that can help resolve this? Thanks 🙂

From time to time, I notice that the HC4 looses its IP address. journalctl then tells me: dhcp4 (eth0): selecting lease failed: -131 But I don't know the reason for it. Sometimes it happens after a reboot. Pulling the ethernet cable off and plugging it in again seems to help and after a few tries, the HC4 is reachable again. I'd be happy to give more information, but I don't know yet how to debug it. I noticed that /var/log (zram) sometimes gets full but I don't know if this is related…

My current HC4-setup consists of 1 SSD and 1 HDD. The SSD contains the most recent Armbian-image (Buster-based) (https://redirect.armbian.com/odroidhc4/Buster_current). Long story short: it won't boot from SSD, and Google tells me it is because Armbian is not compatible with Petiboot. Armbian suggests the following solution: "Important: To be able to boot clean Armbian mainline based u-boot / kernel experiences, you need to remove incompatible Petitboot loader that is shipped with the board. From the Petitboot, go for “Exit to shell” and these commands to remove the Petitboot:" # flash_eraseall /dev/mtd0 # flash_eraseall /dev/mtd1 # flash_eraseall /dev/mtd2 # flash_eraseall /dev/mtd3 "This will make your SPI flash memory empty and would start from SD on next boot." However, it doesn't mention whether this works for booting from an SSD. Does it? And if not, is there a possibility of booting Armbian from an SSD without using an SD-card? Thanks in advance! P.S. I found the following (unresolved) related question: https://www.reddit.com/r/ODroid/comments/moxxhl/uboot_from_sata_on_hc4/

After upgrading to Focal on hc1 I countinously receive cron mails with the following content: /usr/lib/armbian/armbian-truncate-logs: 19: /etc/default/armbian-ramlog: Syntax error: "(" unexpected Similar problem is reported here: https://forum.yunohost.org/t/continuously-receiving-email-about-armbian-log/16549 After checking the code, the problem seams to be, that nowerdays /etc/default/armbian-ramlog contains something like # If USE_RSYNC is true, additional options may be specified for the rsync # commands used to synchronize logs to disk from RAM (XTRA_RSYNC_TO) or from # disk to RAM (XTRA_RSYNC_FROM). These are bash arrays to make specifying # multiple arguments easy even in the presence of whitespace. XTRA_RSYNC_TO=( ## If you use log rotation programs that datestamp their logs (e.g., runit's ## svlogd or daemontools' multilog), deleting log files while synchronizing is ## likely a good idea. # --delete ) When now /usr/lib/armbian/armbian-truncate-logs sources this file, this will always fail because the script is using `#!/bin/sh` which is actually (at least on my system) a link to dash. To fix the problem, in armbian-truncate-logs the first line should be replaced with `#!/bin/bash` and the error disappears. Would be great if this could be fixed. Cheers

Hello, I'm facing a weird issue where a network connection doesn't work after my HC4 is started (after a power off), but then after calling a `reboot` network starts to work. I'm running a fresh install of the latest "Armbian Buster mainline kernel 5.10.y". More details in armbianmonitor's output: http://ix.io/2Rh8 http://ix.io/2Req I've tried playing with /etc/network/interfaces by putting stuff like the following there: allow-hotplug eth0 no-auto-down eth0 auto eth0 iface eth0 inet dhcp also tried static ip but nothing works. What exactly is happening? 1. When I power on my HC4 it awaits for network for a longer while (A start job is running for Raise network interfaces) and then finally boots with no network working. 2. ifconfig shows eth0 and lo interfaces. eth0 has no IP set. I cannot connect to the device from outside not reach network from it. 3. then I run `reboot` (need to connect a screen and a keyboard to the device :/) and the device boots quickly with network up and working Any ideas how to resolve that?

The images where applied with Balena etcher. Petitboot was removed as described. The PSU was included in the bundle (15V 4A). Odroid Ubuntu works fine. The boot process stops at: Booting kernel ... I tried the following Images (none of them works): Armbian Buster - mainline kernel 5.10.y Armbian Focal - mainline kernel 5.10.y What am i missing ? Any help appreciated.

Hi all How can I enable the rtc clock in the Odroid HC4? I know nothing about device tree and overlays, but the Hardkernel Ubuntu image has an overlay to enable: wiki. I didn't find anything similar in the armbian image. Could be related to this this PR for the N2 model? Thanks

I recently upgraded from an Odroid HC2 to and Odroid HC4. I reinstalled the OS following the instructions on armbian.com, flashing onto a MicroSD. After migrating the apps (mostly dockers), I found that restic (backup tool) was generating out of memory errors and bringing the system to a halt in a way the HC2 didn't. This surprised me as it's overall higher specced, and the configuration was otherwise identical. After some troubleshooting, I realised there was no swap drive specified, and that creating a swap eliminated my out of memory errors. I'm not sure if the source of the "problem" is the swapfile here, but it at least stopped the problem occurring.

Hi, is there a way, how to check that image in download section is ok? I have Odroid HC4 with good PSU, both old and new card, flashed by Etcher and Rufus, keyboard plugged in USB, no SATA disks at the moment. I'm able to boot Focal 4.9 kernel (however with some errors after the boot). I've removed Petitboot with flasherase first, I've checked SHA checksum. Edit: File I've downloaded is: Armbian_20.11.6_Odroidhc4_focal_current_5.9.14.img.xz SHA: 9930f984eca2a72b3c22953ee6381c95da528b2a355dd9f429da38d1409f7b1f *Armbian_2 Any ideas what is wrong? Thank you.

Hi guys, I installed the latest Armbian (Buster) release for my Odroid HC4 and - after getting rid of Petitboot as that just wouldn't let me boot the image - it's working great so far. Only big problem I have is that it does not recognize any SATA devices, in neither of the two slots. I tried different HDDs / SSDs that I verified are recognized on a Windows PC and another Ubuntu PC. Did anyone get that working already? I assume the required Kernel drivers for the PCIe-Sata-chip are probably still missing. Many thanks and best regards Daniel