I've made a new kernel Auxiliary Display Driver for TM16XX and compatible LED controllers. This driver supports various LED controller chips, including TM16XX family, FD6XX family, PT6964, and HBS658. It provides support for both I2C and SPI interfaces.

I wanted it to manage the hardware on the kernel space while having an easy sysfs user space interface. It also aims to reduce the code to maintain by relaying on existing kernel features instead of recoding them. Plus, you can switch to hardware i2c/spi (instead of software gpio) depending on the pins used.

You can use "vfdconf-convert" to convert your existing vfd.conf to its device-tree version.  Or you can use the already converted vfd.conf of https://github.com/arthur-liberman/vfd-configurations that are listed in the device table.

You don't need to manually edit your device tree, the "make" command will apply the device tree source overlay to your dtb.

It comes with a service written as a simple bash script. So it's easily customizable without having to write custom C code.

Instructions and source code at https://github.com/jefflessard/tm16xx-display/

Could you please give it a try and report your feedback? 

Here is the link: https://drive.google.com/file/d/1gVU-iGhoYALZNok6RMkUzWg0BhXTrWCt/view?usp=drive_link

LInux odroidc2 6.12.56-current-meson64 #1 SMP PREEMPT Wed. Oct 29 13:09:02 UTC 2025

Thanks,

Scott

1. git clone --depth=1 --branch=master https://github.com/armbian/build

2. cd build

3. mkdir -p ./output/debs

4. wget -c -O ./output/debs/linux-u-boot-current-odroidc1_23.02.0-trunk_armhf.deb http://apt.armbian.com/pool/main/l/linux-u-boot-odroidc1-current/linux-u-boot-current-odroidc1_21.02.3_armhf.deb

5. ./compile.sh CLEAN_LEVEL= BOARD=odroidc1 BRANCH=current RELEASE=jammy REPOSITORY_INSTALL= BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no KERNEL_ONLY=no COMPRESS_OUTPUTIMAGE=sha,gpg,img

6. ls ./output/images

    

u-boot has not been able to be built for a while now (last supported image was focal and 5.x kernel).

Step 4 copies the last good u-boot to ./output/debs which is created in step 3. Change current in ./output/debs/linux-u-boot-current-odroidc1_23.02.0-trunk_armhf.deb to edge to use edge kernel. Also change build number 23.02.0 to current build number.

Step 5 does build without prompting. Change BRANCH=current to BRANCH=edge to build edge branch. If all goes well you should see image with step 6.

Issues:

• reboot not working.
• Headless, no HDMI.
• No wifi at this point, just wired.
• Current branch with 5.x kernel corrupts SD. I found this build totally unusable.

I'm running debian bullseye on an Odroid C4 since quite some time now and decided it was a good time to upgrade to bookworm.

When I first installed armbian on this board, I remember that I had to install the Odroid HC4 image. If I'm not mistaking, there were no C4 image at the time.

After upgrading my current bullseye firmware with armbian-config ( and by passing the SSD issue described in this armbian forum post by hot plugging it ), I noticed that /boot/armbianEnv.txt had this line:

fdtfile=amlogic/meson-sm1-odroid-hc4.dtb

whereas the amlogic/meson-sm1-odroid-c4.dtb file exists in the /boot/dtb directory.

Despite having read that HC4 and C4 were the same board with few differences, dtdiff shows a lot of settings differ between the dtb of the two boards.

Similarly, I notice that a bunch of *odroidc4 packages are now present in the repository that I don't remember having seen when I first installed armbian.

So before upgrading to bookworm, I was wondering if it would be a good or bad idea to modify the armbianEnv.txt in order to use the C4 dtb, and replace the *odroidhc4 packages by their *odroidc4 equivalents.

Did someone already try these changes ?

Does someone see any issue with applying this changes ?

Will there be other changes to apply in order to fully migrate from the initial HC4 configuration to a possibly more appropriate C4 configuration ?

Thanks for your time and answers.

As repeatedly mentioned, the C2 has usb detect issues.

For us, a main culprit not discussed yet is the default kernel config.

Having both:

CONFIG_USB_EHCI_TT_NEWSCHED=Y

CONFIG_USB_OHCI_HCD=Y

For USB1.1, these should be one or the other, never both.

Mainline has: CONFIG_USB_OHCI_HCD=Y and CONFIG_USB_EHCI_TT_NEWSCHED is not set.

For the OdroidC2, CONFIG_USB_OHCI_HCD=N is proper.
As it has no OHCI and USB2 handles that for us.

Forcing the USB power on state has helped workaround this issue, by keeping the driver tied to the device in the kernel.

Fix is to add a section to the DTB to enable a recently (last year) added kernel driver "meson64-reboot" that is an updated version of the "odroid-reboot" in older kernels.

For Odroid-C2:

- save your existing DTB

- use DTC to convert DTB->DTS

- modify the DTS with the code below

- use DTC to convert DTS->DTB

- reboot (will fail because new DTB not loaded yet)

- POR (will now load the new DTB)

- log-in

- reboot should now work.

Quote

Add the following under the stock "gpio-regulator-tf_io {....}":

 

meson64-reboot {
    compatible = "meson64,reboot";
    sys_reset = <0x84000009>;
    sys_poweroff = <0x84000008>;
    sd-vqsw = <0x39 0x03 0x00>;
    sd-vmmc = <0x23 0x57 0x00>;
};

 For Odroid-HC4:

- save your existing DTB

- use DTC to convert DTB->DTS

- modify the DTS with the code below

- use DTC to convert DTS->DTB

- reboot (will fail because new DTB not loaded yet)

- POR (will now load the new DTB)

- log-in

- reboot should now work.

Quote

Add the following under the stock "gpio-regulator-tf_io {....}":

 

meson64-reboot {
    compatible = "meson64,reboot";
    sys_reset = <0x84000009>;
    sys_poweroff = <0x84000008>;

    sd-vqen = <0x44 0x0e 0x00>;
    sd-vqsw = <0x44 0x06 0x00>;
    sd-vmmc = <0x44 0x03 0x00>;
};

Notes:

- As far as I know, only the Odroid -C4 has an Armbian patch to do the above automatically for each release.

- For others, updates may overwrite the DTB and you'll need to perform this fix again. In theory, DTB changes are fairly rare.

can someone help me, I got an odroid n2 with emmc.

For years I was running buster. Now because of end of updates, I upgraded from buster to bullseye - everything was fine there.

After upgrading to bullseye I tried to update to bookworm. Upgrade itself seemed ok, all packages installed.

I did it like described here

After updating to the "default debian bookworm", I commented in the Armbian repository with bullseye in armbian.list, and it updated this packages

armbian-bsp-cli-odroidn2
armbian-config
armbian-zsh
base-files
linux-dtb-current-meson64
linux-image-current-meson64
linux-u-boot-odroidn2-current

Now, it does not boot any longer. Monitor only shows black, turns on from standby (backlit) and off again. Repeats every 10-30s maybe.

How could I figure out what the issue is?

After upgrading to bullseye, i got this configuration:

# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

# uname -mrs
Linux 5.10.60-meson64 aarch64

# cat /etc/debian_version
11.9

The upgrade output was:

user@odroidn2:/etc/apt# apt full-upgrade
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Paketaktualisierung (Upgrade) wird berechnet… Fertig
Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt:
  armbian-bsp-cli-odroidn2
Verwenden Sie »apt autoremove«, um es zu entfernen.
Die folgenden NEUEN Pakete werden installiert:
  armbian-bsp-cli-odroidn2-current
Die folgenden Pakete werden aktualisiert (Upgrade):
  armbian-bsp-cli-odroidn2 armbian-config armbian-zsh base-files linux-dtb-current-meson64 linux-image-current-meson64 linux-u-boot-odroidn2-current
7 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 57,8 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 36,3 MB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n]
Holen:1 http://apt.armbian.com bookworm/main arm64 base-files arm64 24.2.1-12.4+deb12u5-bookworm [53,1 kB]
Holen:7 http://imola.armbian.com/apt bookworm/main arm64 linux-image-current-meson64 arm64 24.2.1 [44,5 MB]
Holen:4 http://mirrors.xtom.de/armbian bookworm/main arm64 armbian-config all 24.2.1 [136 kB]
Holen:2 http://fi.mirror.armbian.de/apt bookworm/main arm64 armbian-bsp-cli-odroidn2 arm64 24.2.1 [1.288 B]
Holen:3 http://fi.mirror.armbian.de/apt bookworm/main arm64 armbian-bsp-cli-odroidn2-current arm64 24.2.1 [430 kB]
Holen:5 http://fi.mirror.armbian.de/apt bookworm/main arm64 armbian-zsh all 24.2.1 [11,8 MB]
Holen:6 http://fi.mirror.armbian.de/apt bookworm/main arm64 linux-dtb-current-meson64 arm64 24.2.1 [166 kB]
Holen:8 http://fi.mirror.armbian.de/apt bookworm/main arm64 linux-u-boot-odroidn2-current arm64 24.2.1 [761 kB]
Es wurden 57,8 MB in 7 s geholt (8.664 kB/s).
(Lese Datenbank ... 58101 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../base-files_24.2.1-12.4+deb12u5-bookworm_arm64.deb ...
Entpacken von base-files (24.2.1-12.4+deb12u5-bookworm) über (12.4+deb12u5) ...
base-files (24.2.1-12.4+deb12u5-bookworm) wird eingerichtet ...
(Lese Datenbank ... 58101 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../0-armbian-bsp-cli-odroidn2_24.2.1_arm64.deb ...
Entpacken von armbian-bsp-cli-odroidn2 (24.2.1) über (23.02.2) ...
dpkg: Warnung: Altes Verzeichnis »/usr/share/armbian« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer
dpkg: Warnung: Altes Verzeichnis »/usr/local/bin« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer
dpkg: Warnung: Altes Verzeichnis »/usr/local« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer
dpkg: Warnung: Altes Verzeichnis »/usr/lib/chromium-browser« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer
dpkg: Warnung: Altes Verzeichnis »/usr/lib/armbian« kann nicht gelöscht werden: Das Verzeichnis ist nicht leer
Vormals nicht ausgewähltes Paket armbian-bsp-cli-odroidn2-current wird gewählt.
Vorbereitung zum Entpacken von .../1-armbian-bsp-cli-odroidn2-current_24.2.1_arm64.deb ...
Armbian 'armbian-bsp-cli-odroidn2-current' for '1-PC13d1-V2d94-H02fb-Ba537-R6632': 'preinst' starting.
Armbian 'armbian-bsp-cli-odroidn2-current' for '1-PC13d1-V2d94-H02fb-Ba537-R6632': 'preinst' finishing.
Entpacken von armbian-bsp-cli-odroidn2-current (24.2.1) ...
Vorbereitung zum Entpacken von .../2-armbian-config_24.2.1_all.deb ...
Entpacken von armbian-config (24.2.1) über (23.02.2) ...
Vorbereitung zum Entpacken von .../3-armbian-zsh_24.2.1_all.deb ...
Entpacken von armbian-zsh (24.2.1) über (23.02.2) ...
Vorbereitung zum Entpacken von .../4-linux-dtb-current-meson64_24.2.1_arm64.deb ...
Armbian 'linux-dtb-current-meson64' for '6.6.16-current-meson64': 'preinst' starting.
Armbian 'linux-dtb-current-meson64' for '6.6.16-current-meson64': 'preinst' finishing.
Entpacken von linux-dtb-current-meson64 (24.2.1) über (21.08.1) ...
Vorbereitung zum Entpacken von .../5-linux-image-current-meson64_24.2.1_arm64.deb ...
Armbian 'linux-image-current-meson64' for '6.6.16-current-meson64': 'preinst' starting.
Armbian 'linux-image-current-meson64' for '6.6.16-current-meson64': 'preinst' finishing.
Entpacken von linux-image-current-meson64 (24.2.1) über (21.08.1) ...
Vorbereitung zum Entpacken von .../6-linux-u-boot-odroidn2-current_24.2.1_arm64.deb ...
Entpacken von linux-u-boot-odroidn2-current (24.2.1) über (21.08.1) ...
armbian-zsh (24.2.1) wird eingerichtet ...
armbian-config (24.2.1) wird eingerichtet ...
linux-image-current-meson64 (24.2.1) wird eingerichtet ...
Armbian 'linux-image-current-meson64' for '6.6.16-current-meson64': 'postinst' starting.
dkms: autoinstall for kernel 6.6.16-current-meson64 was skipped since the kernel headers for this kernel do not seem to be installed.
update-initramfs: Generating /boot/initrd.img-6.6.16-current-meson64
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.16-current-meson64
Image Name:   uInitrd
Created:      Wed Apr  3 11:54:06 2024
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    16365934 Bytes = 15982.36 KiB = 15.61 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.16-current-meson64 to /boot/uInitrd
'/boot/uInitrd' -> 'uInitrd-6.6.16-current-meson64'
update-initramfs: Armbian: done.
Remove unused generated file: /boot/initrd.img-5.10.60-meson64
Remove unused generated file: /boot/uInitrd-5.10.60-meson64
Armbian: update last-installed kernel symlink to 'Image'...
'/boot/Image' -> 'vmlinuz-6.6.16-current-meson64'
Armbian: Debian compat: linux-update-symlinks install 6.6.16-current-meson64 boot/vmlinuz-6.6.16-current-meson64
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.6.16-current-meson64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.6.16-current-meson64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.6.16-current-meson64
I: /initrd.img is now a symlink to boot/initrd.img-6.6.16-current-meson64
Armbian 'linux-image-current-meson64' for '6.6.16-current-meson64': 'postinst' finishing.
linux-dtb-current-meson64 (24.2.1) wird eingerichtet ...
Armbian 'linux-dtb-current-meson64' for '6.6.16-current-meson64': 'postinst' starting.
Armbian: DTB: symlinking /boot/dtb to /boot/dtb-6.6.16-current-meson64...
'dtb' -> 'dtb-6.6.16-current-meson64'
Armbian 'linux-dtb-current-meson64' for '6.6.16-current-meson64': 'postinst' finishing.
linux-u-boot-odroidn2-current (24.2.1) wird eingerichtet ...
Armbian 'uboot-odroidn2-current' for '2022.10-S4deb-P35fb-H24ab-V33c2-B11a8-R448a': 'postinst' starting.
Armbian 'uboot-odroidn2-current' for '2022.10-S4deb-P35fb-H24ab-V33c2-B11a8-R448a': 'postinst' finishing.
armbian-bsp-cli-odroidn2-current (24.2.1) wird eingerichtet ...
Armbian 'armbian-bsp-cli-odroidn2-current' for '1-PC13d1-V2d94-H02fb-Ba537-R6632': 'postinst' starting.
'/boot/boot.cmd' -> '/usr/share/armbian/boot.cmd-1712138049'
NOTE: You can find previous bootscript versions in /usr/share/armbian !
Recreating boot script
'/usr/share/armbian/boot.cmd' -> '/boot/boot.cmd'
sed: -e Ausdruck #1, Zeichen 76: Nicht beendeter »s«-Befehl
sed: -e Ausdruck #1, Zeichen 47: Nicht beendeter »s«-Befehl
Armbian 'armbian-bsp-cli-odroidn2-current' for '1-PC13d1-V2d94-H02fb-Ba537-R6632': 'postinst' finishing.
Trigger für mandb (2.11.2-2) werden verarbeitet ...
Trigger für cracklib-runtime (2.9.6-5+b1) werden verarbeitet ...
Trigger für initramfs-tools (0.142) werden verarbeitet ...
update-initramfs: Generating /boot/initrd.img-6.6.16-current-meson64
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.6.16-current-meson64
Image Name:   uInitrd
Created:      Wed Apr  3 11:54:31 2024
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    16365968 Bytes = 15982.39 KiB = 15.61 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.6.16-current-meson64 to /boot/uInitrd
'/boot/uInitrd' -> 'uInitrd-6.6.16-current-meson64'
update-initramfs: Armbian: done.
armbian-bsp-cli-odroidn2 (24.2.1) wird eingerichtet ...
user@odroidn2:/etc/apt#

I mounted the emmc on another system and the boot directory looks like this:

drwxr-xr-x  3 root root     4096  3. Apr 14:29 .
drwxrwxrwx 19 root root     4096  3. Apr 11:54 ..
-rw-r--r--  1 root root      161  3. Apr 11:58 armbianEnv.txt
-rw-r--r--  1 root root      161  2. Nov 2021  armbianEnv.txt.old
-rw-r--r--  1 root root     1531 30. Okt 2021  armbian_first_run.txt.template
-rw-r--r--  1 root root    38518 26. Aug 2021  boot.bmp
-rw-r--r--  1 root root     8075  3. Apr 11:54 boot.cmd
-rw-r--r--  1 root root     5579 16. Jun 2023  boot.ini
-rw-r--r--  1 root root     8147  3. Apr 11:54 boot.scr
-rw-r--r--  1 root root   258772 29. Feb 18:56 config-6.6.16-current-meson64
-rwxr-xr-x  1 root root      120  1. Jan 1970  display.bin
lrwxrwxrwx  1 root root       26  3. Apr 11:54 dtb -> dtb-6.6.16-current-meson64
drwxr-xr-x  3 root root     4096  3. Apr 11:53 dtb-6.6.16-current-meson64
-rwxr-xr-x  1 root root      256  1. Jan 1970  edid.bin
lrwxrwxrwx  1 root root       30  3. Apr 11:54 Image -> vmlinuz-6.6.16-current-meson64
-rw-r--r--  1 root root 16365968  3. Apr 11:54 initrd.img-6.6.16-current-meson64
-rw-r--r--  1 root root        0  3. Apr 11:54 .next
-rw-r--r--  1 root root  4424139 29. Feb 18:56 System.map-6.6.16-current-meson64
-rw-r--r--  1 root root 25461312  9. Dez 2021  uImage
lrwxrwxrwx  1 root root       30  3. Apr 11:54 uInitrd -> uInitrd-6.6.16-current-meson64
-rw-r--r--  1 root root 16366032  3. Apr 11:54 uInitrd-6.6.16-current-meson64
-rw-r--r--  1 root root 28346880 29. Feb 18:56 vmlinuz-6.6.16-current-meson64

And now, I'm completely lost!

No clue what to do or where to look.

Any help would be appreciated!
 

Installed latest "Armbian_24.11.1_Odroidc4_noble_current_6.6.60-kisak.img"

...with latest sudo apt update; sudo apt upgrade, rebooted...

Hardware:

- Odroid-C4

- Sabrent USB 3.0 to 2.5-Inch SATA Adapter; Model: EC-SSHD with latest firmware patch,  connected to a Kingston SSD: SA400S37480G

# dmesg -l emerg,alert,crit,err
[    0.879290] meson-drm ff900000.vpu: DSI transceiver device is disabled
[    3.402246] systemd[1]: Failed to start systemd-sysctl.service - Apply Kernel Variables.
[    4.327154] panfrost ffe40000.gpu: error -ENODEV: _opp_set_regulators: no regulator (mali) found
[    4.871183] systemd[1]: Failed to start systemd-sysctl.service - Apply Kernel Variables.
[    5.093021] I/O error, dev sda, sector 2064 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[    5.098203] I/O error, dev sda, sector 2088 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2
[    5.098226] I/O error, dev sda, sector 2120 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 2
[    5.102570] Buffer I/O error on dev sda1, logical block 2, async page read
[    5.111428] Buffer I/O error on dev sda1, logical block 2, async page read

I'm not worried about vpu, or panfrost errors, ..., since I don't care about gpu on this headless (non-desktop) cli mini-server.

# dmesg | grep -i systemd-sysctl
[    3.331877] systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables...
[    3.399999] systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
[    3.400501] systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
[    3.402246] systemd[1]: Failed to start systemd-sysctl.service - Apply Kernel Variables.
[    4.822476] systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables...
[    4.870046] systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
[    4.870601] systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
[    4.871183] systemd[1]: Failed to start systemd-sysctl.service - Apply Kernel Variables.

I checked /etc/sysctl.conf, and everything looks ok, afaik.?
 

# cat /etc/sysctl.conf
#
# /etc/sysctl.conf - Configuration file for setting system variables
# See /etc/sysctl.d/ for additional system variables.
# See sysctl.conf (5) for information.
#

#kernel.domainname = example.com

# Uncomment the following to stop low-level messages on console
#kernel.printk = 3 4 1 3

###################################################################
# Functions previously found in netbase
#

# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
# Turn on Source Address Verification in all interfaces to
# prevent some spoofing attacks
#net.ipv4.conf.default.rp_filter=1
#net.ipv4.conf.all.rp_filter=1

# Uncomment the next line to enable TCP/IP SYN cookies
# See http://lwn.net/Articles/277146/
# Note: This may impact IPv6 TCP sessions too
#net.ipv4.tcp_syncookies=1

# Uncomment the next line to enable packet forwarding for IPv4
#net.ipv4.ip_forward=1

# Uncomment the next line to enable packet forwarding for IPv6
#  Enabling this option disables Stateless Address Autoconfiguration
#  based on Router Advertisements for this host
#net.ipv6.conf.all.forwarding=1


###################################################################
# Additional settings - these settings can improve the network
# security of the host and prevent against some network attacks
# including spoofing attacks and man in the middle attacks through
# redirection. Some network environments, however, require that these
# settings are disabled so review and enable them as needed.
#
# Do not accept ICMP redirects (prevent MITM attacks)
#net.ipv4.conf.all.accept_redirects = 0
#net.ipv4.conf.default.accept_redirects = 0
# _or_
# Accept ICMP redirects only for gateways listed in our default
# gateway list (enabled by default)
# net.ipv4.conf.all.secure_redirects = 1
#
# Do not send ICMP redirects (we are not a router)
#net.ipv4.conf.all.send_redirects = 0
#
# Log Martian Packets
#net.ipv4.conf.all.log_martians = 1
#

###################################################################
# Magic system request Key
# 0=disable, 1=enable all, >1 bitmask of sysrq functions
# See https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html
# for what other values do
#kernel.sysrq=438

Swappiness for zram, see swapon
vm.swappiness=100
# Decrease swap usage to a more reasonable level
#vm.swappiness=30
#
# Improve cache management
#vm.vfs_cache_pressure=50
#
# Improve writing to external media like USB memory sticks
#vm.dirty_bytes=335544320
#vm.dirty_background_bytes=167772160
#

-------------------------------

For the sake of brevity, I'm only running "transmission-daemon" on this successfully -sort of, with everything else being the default Armbian server settings, ...

see:

with:

# cat /etc/udev/rules.d/99-usb-drive.rules
ENV{ID_FS_UUID}=="501ce172-bc60-40db-90b6-9e025d2748bb", ACTION=="add", RUN{program}+="/usr/bin/systemd-mount --type=ext4 --no-block --collect $devnode /media/USB01/"

...so as to mount my USB-SSD-drive upon boot. But that's for another topic,

since the "Failed to start systemd-sysctl.service - Apply Kernel Variables." were there before, and nothing else was changed.

Basically, are the errors in my "dmesg" output above anything to really worry about.?

 My 2TB USB3.0 seagate HD, /dev/sda, is seen fine in "dmesg", as well as "lsblk" and "blkid", but when I add my UUID, ..., in /etc/fstab it fails to mount at boot.
see below line in /etc/fstab for above /dev/sda1 :
 

UUID=<output-of-bklid-for-sda1>   /media/USB01   ext4   defaults   0   1

To test the above /etc/fstab mount I ran:

sudo findmnt --verify

(which completes successfully)
Also, if I run:

sudo mount -a

(it manually automounts /dev/sda1 -> /media/USB01 successfully).

But, whenever i reboot, it does not come up mounted.?

-this is driving me crazy.

Do I also need udisks2 ?, or autofs>, and/or, manually edit udev*?, and/or "systemd-mount" to get this thing to mount on every boot. ?  
 

I am running Armbian v24.11.1 with kernel 6.6.63-current-meson64.

Has anyone ever achieved to enable the external antenna? Any hints appreciated.

Thanks.

Hi there!

I just got my hands on a brand new Odroid C4.

I flashed Armbian Bullseye (tried Buster too as Bullseye is marked unstable) onto an SD card.

The Issue I'm now facing is, after any sort of kernel update the board will not properly soft reboot anymore.

I can restart the freshly installed system (which I generated the ix link with) as many times as I want using /sbin/reboot, but one apt upgrade later the board hangs in limbo when I issue a soft reboot.

I can see the system itself shutting down, the blue light stopping to heartbeat, and then nothing happens anymore, until I replug power, then the board boots up fine.

I have tried to run nand-sata-install as described on the C4's board page (If you face issues with rebooting run this as root) but it does not help, and I'm not even sure whether it even flashes a new U-Boot at all.

Obviously, I have trouble using the board as a server like this, as I'd have to come home and replug it if I ever need to reboot so hopefully this can get fixed 

Should anyone require further data, I can always provide that.

i recently created a game that i would like to install over 905x3 tv box, i would like to protect it from copy.

is there a way to encrypt the whole ROM without the need of any external hardware or password to be entered each reboot ?

tv box launch directly into the game and every possible way to interact with linux is disabled (keyboard, usb, lan) and i only need to encrypt the ROM to make the game more resistent in some extent to copy.

i read about encrypted bootloader but i'm not sure if that is what i need. can i only encrypt the game bin with a key that is protected inside the 905x3 ? (beside cpuid as it seem easy to reverse).

i'm not super good at coding and i would like some help or a step by step guide.

Thank you for the great effort of Armbian having community support of this board.

I have a Waveshare 4inch DSI LCD with touch that I want to use it with Radxa Zero 2 Pro. They have a device tree overlay provided for Raspberry Pi and drivers for different kernels for RPi

And I found a kernel patch that seem to enable DSI here.

**********************************************************************

I am using the latest build of Armbian for radxa-zero2 and it's Linux radxa-zero2 6.6.53-current-meson64

When I

find /lib/modules/$(uname -r) -type f -name '*dsi*'

It shows

/lib/modules/6.6.53-current-meson64/kernel/drivers/gpu/drm/hisilicon/kirin/dw_drm_dsi.ko
/lib/modules/6.6.53-current-meson64/kernel/drivers/gpu/drm/panel/panel-dsi-cm.ko
/lib/modules/6.6.53-current-meson64/kernel/drivers/gpu/drm/bridge/nwl-dsi.ko
/lib/modules/6.6.53-current-meson64/kernel/drivers/gpu/drm/bridge/cadence/cdns-dsi.ko
/lib/modules/6.6.53-current-meson64/kernel/drivers/gpu/drm/bridge/ti-sn65dsi83.ko
/lib/modules/6.6.53-current-meson64/kernel/drivers/mtd/nand/raw/nandsim.ko

When I

zcat /proc/config.gz | grep DSI

It shows

CONFIG_MTD_NAND_NANDSIM=m
CONFIG_DRM_MIPI_DSI=y
CONFIG_DRM_PANEL_DSI_CM=m
CONFIG_DRM_NWL_MIPI_DSI=m
# CONFIG_DRM_SAMSUNG_DSIM is not set
CONFIG_DRM_TI_SN65DSI83=m
# CONFIG_DRM_TI_SN65DSI86 is not set
CONFIG_DRM_CDNS_DSI=m
CONFIG_DRM_CDNS_DSI_J721E=y
CONFIG_DRM_DW_MIPI_DSI=y
CONFIG_DRM_MESON_DW_MIPI_DSI=y

Questions

AFAIK, that means the DSI interface is enabled and what I need to do is to compile a .dtbo device tree overlay based on Waveshare's and then load it into the system? 

And I assume the LCD needs some kind of 'driver' but Waveshare only provides some .ko and .dtso files in their GitHub repo. They have as recent as kernel 

6.6.20, can I use that driver and how?

As for compiling a device tree source DTS into a Device Tree Blog DTB, do I use the traditional way of 

dtc -I dts -O dtb -o output_file.dtb input_file.dts

or using

armbian-add-overlay

(however the documentation says DT overlays are a Work-in-Progress (WIP) feature, present only in certain images.)

Is there a way that I can verify if the DSI interface is functioning at all before I move on to the driver and overlay issue? That way I won't be working with too many uncertainties. I measured some of the pins on the DSI port on the monitor side and they seem to be 'functioning` (as there are pins with voltages and a 3.3v, plus there's  LED on the monitor that is blinking - I didn't go as far as checking if the 3.3v pin is in accordance of the Radxa Zero 2 Pro side for the DSI port, nor I did try to logic analyse other pins)

**********************************************************************

I have tried to compile Armbian and choose ` > Device Drivers > Graphics support > DRM support for MIPI DBI compatible panels > *

I'm reaching out for help with a critical issue I've been facing on my ODROID HC4 server since updating to Armbian_community 24.8.0-trunk.4xx.

I put 4xx because I don't know which version caused the issues. It was yesterday and I just saw updates in my OMV workbench, did the updates and then rebooted and then was unable to access OMV anymore.

I have since upgraded to trunk.500 last night, didn't help, and trunk.501 this morning also didn't fix anything.

Here’s a detailed account of the situation and the troubleshooting steps I've taken so far.

Background:

Device: ODROID HC4

OS: Armbian (latest updates applied)

Purpose: NAS with OpenMediaVault, and Tailscale configured as a subnet router.

Loss of SSH Access:
 

I initially had SSH access to the server, but after executing sudo tailscale down --accept-risk=lose-ssh and rebooting, I completely lost SSH access.

Broken openssh-server Installation

I attempted to reinstall openssh-server, but the installation failed with the message: dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1.

Attempts to fix broken packages with apt-get install -f showed no new issues, but dpkg-reconfigure also fails with errors.

System Services Failures:

Upon trying to resolve the issue, I encountered multiple service failures.

Key services such as nginx, openmediavault, and collectd are not starting, and their status shows errors related to failed starts and missing units.

For example, the nginx service fails with bind() to 0.0.0.0:443 failed (98: Address already in use), and the openmediavault-engined service is not found.

When I open journalctl -xe, I see a lot of errors. the logs seem to go up forever.

First red I see is from odroidhc4 monit [1751]: 'rrdcached' process is not running. Right above that I see in green letters: The unit packagekit.service has successfully entered the 'dead' state. A bit further above that another red one from odroidhc4 monit[1751]: 'collectd' failed to start (exit status 5) -- '/bin/systemctl start collectd': Failed to start colledtd.service: Unit collectd.service not found. Above that some more gray stuff and then the next red one is again about collectd process is not running. Right above that also from odroidhc4 monit[1751]: 'omv-engined' failed to start (exit status 5) -- 'bin/systemctl start openmediavault-engined': Failed to start openmediavault-engined.service: Unit openmediavault-engined.service not found. Next red one up is 'omv-engined' process is not running, and right above that 'nginx' failed to start (exit status 5) -- '/bin/systemctl start nginx': Failed to start nginx.service: Unit nginx.service not found. Then the same thing with php-fpm, 'rrdcached', 'collectd', and keeps on going, but seems to repeat the same errors about rrdcached process is not running and collectd failed to start, omvengined, nginx, php-fpm, rrdcached again

Steps Taken

Checked Network Configuration:

Verified network interface settings with ip a and /etc/netplan/*.yaml. The static IP seems correct, and no Tailscale-related entries appear in the output of ip a or lsof -i :443.

Reviewed System Logs:

Errors related to monit, collectd, nginx, openmediavault-engined, and others were observed in journalctl -xe.

Key errors include failures to start these services and issues with rrdcached and collectd.

Package Management:

Tried sudo apt-get install -f, which showed no issues, but dpkg -l | grep -i broken returned no results.

Request for Assistance

SSH Server Reinstallation:

I need guidance on reinstalling or fixing openssh-server given the current errors.

Service Restoration:

Advice on restoring services like nginx, openmediavault, and collectd, including fixing missing or broken units.

Filesystem and Package Repairs:

Recommendations for handling any remaining package issues.

Any additional troubleshooting steps or insights based on the provided info would be helpful!

I appreciate any help or suggestions you can provide.

Thank you!

I've done 2 clean installs to ensure the problem is reproducable and not something I meddled with.

I spent time on Docker's forums running sample containers I was asked to try, they viewed my settings logs for docker and were at a loss.

The containers go up fine and are running.  They just cannot be accessed even from the host machine e.g. curl http://localhost:8080 fails when running a sample container docker hub forums supplied me with as a 'surefire' test.

---
services:
  test_default_bridge:
    image: nginx:latest
    network_mode: bridge
    ports:
      - 8080:80

Is anyone else having this issue and how do I get it working?

I was running Armbian Bullseye for a while with OMV 6.  I happened to see OMV has gone to v7 and Armbian to bookworm.

I went here to get the SBC/IOT bare version of bookworm:  https://www.armbian.com/odroid-hc4/

Problem 1:  is it said: "You are using an automated version meant only for developers..."

Problem 2:  it did not come with Armbian-config which I had to install manually

Problem 3:  Armbian-config 'softy' refused to install OMV saying it can only be installed on Buster (OMV5) or Bullseye (OMV6)

Finally: https://wiki.omv-extras.org/doku.php?id=omv7:armbian_bookworm_install  states specifically not to use any developer versions of the OS.

Is there a stable version of the OS where it comes with Armbian-config and softy will install OMV-7?   (If so, url's please)

How do I proceed?  For now going back to Bullseye OMV6 

Much thanks in advance.

I tried the steps, but my Mecool KIII pro don't run using default conf

extlinux.conf:

label Armbian_community
  kernel /Image
  initrd /uInitrd
  fdtdir /dtb/amlogic/meson-gxm-mecool-kiii-pro.dtb
  append root=UUID=3bc7a8b8-73ee-4ade-9030-f3fa965fc27e rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles

But I need choose (unofficial)

label Armbian-unofficial
  kernel /Image
  initrd /uInitrd
  fdtdir /dtb/amlogic/meson-gxm-mecool-kiii-pro.dtb

#Insert the correct FDT line for your box's dtb in the extlinux.conf file
#The dtbs for Amlogic s9xx boxes are located in /boot/dtb/amlogic
#For example for a TX3 mini box the FDT line to insert would look like this:
FDT /dtb/amlogic/meson-gxm-mecool-kiii-pro.dtb
append root=UUID=3bc7a8b8-73ee-4ade-9030-f3fa965fc27e rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles

Thx

Current next image kernel:  4.14

Dec. 14 2017:  Functions working for me (N=1 sample size)

• WiFi functioned for me out of the box.
• HDMI (I added this functionality some time ago)
• HDMI Sound (Added as of 1:45 Dec.14, not part of any image/build yet)
• USB
• Ethernet (no long-term stability testing yet)

Jan. 24 2018: small bugfix

• Board now reports 2 GB RAM instead of 1

July 8, 2018:  "Next" kernel (4.17) bugfix

• HDMI audio repaired (in build system, images not built yet)
• DVFS better, but still throwing errors
• [BUG]  No USB on K2. 

1. USB almost never works. Most of the time my very plain USB keyboard won't be detected. There is an error message right at the start of the boot sequence "Failed to get keyboard state from device[...]". I have to shutdown and start multiple times by plugging off the power cable and I also keep trying different USB ports. Some rare times the keyboard will work though, even with the above error message. Even rarely I don’t see the error message at the boot start ( I get a confirmation that the keyboard was detected). This of course while the keyboard is plugged in before connecting the power plug. I found this comment but clearly the problem now is not plugging in the USB cable after booting. Also there is a mention about a note on this requirement in the downloads page, but I wasn’t able to find it?

Then after I managed to setup the basics, I found this recent thread and I would like to know if the suggested fix is the recommended solution. Also I removed the J1 jumper from the board after reading in the official product page that I should remove it to save power in case I don’t use the USB OTG port for power supply (I use a dedicated power cable via the small round connector between the HDMI and the Ethernet ports). Also, would removing or placing the jumper matter for this case?

2. The first time I installed the Armbian image I must have made a mistake and the language got set to my local language, but I prefer English. I tried to change this using 'armbian-config' but it wouldn’t stick. I could see the changes on screen after I made my selection, but if I exited and started the config tool again, it would show the default value again, instead of my previous choice. The only way I could see the changes taking effect was after I followed the instructions here, specifically the BASH script in xinitrc .  

At this point the language issue was fixed but the home folders were not in English, so I figured it wouldn’t take long to try a fresh setup again and so I etched the image again and this time the correct settings were applied. But the issue of not being able to change locale via the tools provided should remain valid.

3. I installed X11vnc to access remotely the same desktop I would have with a monitor connected to the C2. This was the setup I had before with the official Hardkernel images and this was working properly. The issue now is that with a monitor connected I do get via X11vnc the same screen (showing the Armbian Linux penguin), but if I reboot with the monitor disconnected I get a very small window insted, and this time with the xfce wallpaper. I can resize this window with the ratio settings in the control panel, but what I would really like is to have the same desktop, whether a monitor is connected or not, as I had before. I noticed the installation doesn’t create a Xorg.conf file, and I don't want to start tinkering by myself because I need the machine in working condition atm. I found these instructions that involve using a dummy monitor setting, but I am unsure if this would yield the result I’m looking for. If someone is able to provide good directed advice I would prefer that than start changing settings without really knowing if they are going to fix the issue or not.

4. The network connector shows a notification on the top right corner about the wired connection and a button offering the option to not show the notification again, but the button doesn’t do anything and I get the notification again after every boot.

Does the Ubuntu image handle these issues better?

I could maybe post this in 4 separate threads if it would be better to follow up on the discussions? Thanks.

Armbian_21.02.3_Odroidc1_focal_current_5.10.21

how do I find out which number do I need to provide to gpio export command?

Let's say I have physical pin 16, which is labeled by the manufacturer as `GPIOX.5` or `102`.

But that doesn't work with Armbian:

echo 102  > /sys/class/gpio/export

[ 1602.030617] export_store: invalid GPIO 102

How do I know the value to provide for /sys/class/gpio/export?

# cat /sys/kernel/debug/gpio
gpiochip1: GPIOs 413-428, parent: platform/c8100084.pinctrl, aobus-banks:
 gpio-416 (                    |TF_IO               ) out lo
 gpio-417 (                    |usb-hub-reset       ) out hi
 gpio-426 (                    |c1:blue:alive       ) out hi ACTIVE LOW

gpiochip0: GPIOs 429-511, parent: platform/c1109880.pinctrl, cbus-banks:
 gpio-456 (                    |regulator-tflash_vdd) out lo
 gpio-470 (                    |PHY reset           ) out hi ACTIVE LOW
 gpio-482 (                    |cd                  ) in  hi ACTIVE LOW
 gpio-492 (                    |reset               ) out hi ACTIVE LOW

Thanks

I have tested all the bookworm images and they all have the same error.
HDMI debugging not working...
This is the log uart Armbian_23.5.1_Nanopik2-s905_bookworm_current_6.1.30

Regards

npik2-armbian

I broke my /boot on eMMC and my Beelink GT1 is in boot loop.
I can't configure u-boot to boot from the SD card to reinstall it.

Can you help me reconfigure u-boot to boot from the SD card?

Thx

printenv

bootargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.mem_address=0x20000000 ramoops.mem_size=0x100000 ramoops.record_size=0x8000 ramoops.console_size=0x4000 androidboot.selinux=permissive logo=osd1,loaded,0x3f800000,576cvbs hdmimode=720p60hz cvbsmode=576cvbs hdmitx= androidboot.firstboot=0 mac=86:48:d8:49:99:56 androidboot.mac=86:48:d8:49:99:56
bootcmd=run start_autoscript; run storeboot
bootdelay=1
bootmode_check=get_rebootmode; echo reboot_mode=${reboot_mode};if test ${reboot_mode} = factory_reset; then defenv_reserv aml_dt;setenv upgrade_step 2; save;fi;
bootup_offset=0x10ac270
bootup_size=0x5eec36
cmdline_keys=if keyman init 0x1234; then if keyman read usid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.serialno=${usid};fi;if keyman read mac ${loadaddr} str; then setenv bootargs ${bootargs} mac=${mac} androidboot.mac=${mac};fi;if keyman read deviceid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.deviceid=${deviceid};fi;fi;
cvbsmode=576cvbs
display_bpp=24
display_color_bg=0
display_color_fg=0xffff
display_color_index=24
display_height=576
display_layer=osd1
display_width=720
dtb_mem_addr=0x1000000
edid.crcvalue=0x9f290000
ethact=Meson_Ethernet
ethaddr=00:15:18:01:81:31
factory_reset_poweroff_protect=echo wipe_data=${wipe_data}; echo wipe_cache=${wipe_cache};if test ${wipe_data} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; if test ${wipe_cache} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi;
fb_addr=0x3f800000
fb_height=1080
fb_width=1920
fdt_high=0x20000000
filesize=320
firstboot=0
gatewayip=10.18.9.1
hdmimode=720p60hz
hostname=arm_gxbb
identifyWaitTime=750
init_display=hdmitx hpd;osd open;osd clear;vout output ${outputmode};imgread pic logo bootup $loadaddr;bmp display $bootup_offset;bmp scale
initargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.mem_address=0x20000000 ramoops.mem_size=0x100000 ramoops.record_size=0x8000 ramoops.console_size=0x4000 androidboot.selinux=permissive
ipaddr=10.18.9.97
irremote_update=if irkey 0xe31cfb04 0xb748fb04 2500000; then echo read irkey ok!; if itest ${irkey_value} == 0xe31cfb04; then run update;else if itest ${irkey_value} == 0xb748fb04; then run update;\
fi;fi;fi;
loadaddr=1080000
mac=86:48:d8:49:99:56
netmask=255.255.255.0
outputmode=576cvbs
preboot=run factory_reset_poweroff_protect;run upgrade_check;run bootmode_check;run init_display;run storeargs;run upgrade_key;run switch_bootmode;
reboot_mode=cold_boot
recovery_from_flash=if imgread kernel recovery ${loadaddr}; then wipeisb; bootm ${loadaddr}; fi
recovery_from_sdcard=if fatload mmc 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload mmc 0 ${loadaddr} recovery.img; then if fatload mmc 0 ${dtb_mem_addr} dtb.img; then echo sd dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi;
recovery_from_udisk=if fatload usb 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload usb 0 ${loadaddr} recovery.img; then if fatload usb 0 ${dtb_mem_addr} dtb.img; then echo udisk dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi;
saradc_val=0x1
sdc_burning=sdc_burn ${sdcburncfg}
sdcburncfg=aml_sdc_burn.ini
serverip=10.18.9.113
start_autoscript=if mmcinfo; then run start_mmc_autoscript; fi; if usb start; then run start_usb_autoscript; fi; run start_emmc_autoscript
start_emmc_autoscript=if fatload mmc 1 1020000 emmc_autoscript; then autoscr 1020000; fi;
start_mmc_autoscript=if fatload mmc 0 1020000 s905_autoscript; then autoscr 1020000; fi;
start_usb_autoscript=for usbdev in 0 1 2 3; do if fatload usb ${usbdev} 1020000 s905_autoscript; then autoscr 1020000; fi; done
stderr=serial
stdin=serial
stdout=serial
storeargs=setenv bootargs ${initargs} logo=${display_layer},loaded,${fb_addr},${outputmode} hdmimode=${hdmimode} cvbsmode=${cvbsmode} hdmitx=${cecconfig} androidboot.firstboot=${firstboot}; run cmdline_keys;
storeboot=if imgread kernel boot ${loadaddr}; then store dtb read $dtb_mem_addr; bootm ${loadaddr}; fi;run update;
switch_bootmode=get_rebootmode;if test ${reboot_mode} = factory_reset; then run recovery_from_flash;else if test ${reboot_mode} = update; then run update;else if test ${reboot_mode} = cold_boot; then run try_auto_burn; fi;fi;fi;
try_auto_burn=update 700 750;
update=run usb_burning; run sdc_burning; if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;
upgrade_check=echo upgrade_step=${upgrade_step}; if itest ${upgrade_step} == 3; then run init_display; run storeargs; run update;else if itest ${upgrade_step} == 1; then defenv_reserv; setenv upgrade_step 2; saveenv;fi;fi;
upgrade_key=saradc open 0; if saradc get_in_range 0x0 0x50; then echo detect upgrade key; run update;fi;
upgrade_step=2
usb_burning=update 1000
wipe_cache=successful
wipe_data=successful

Hi ,

i buiild a SPDIF connector like shown here:

https://forum.odroid.com/viewtopic.php?t=21477

it uses the J7 SPDIF output which is connected to HDMI.

On coreelec i can clearly see a HDMI soundcard output with aplay -L , i dont see that on armbian....

Is odroid c2 spdif output on armbian working ? why do i not see this soundcard that f.e. libreelec is showing ( i have 2 odroid c2s , one is running coreelec in my living room with HDMI connector working)

im using a little older armbian distro since the latest has ethernet issues on C2 (im using 20.11 , kernel 5.9.10 debian edition )

regards,

Simon

I have installed v4l-utils and cec-utils, but when I use the command cec-ctl there is an error:

Failed to open /dev/cec0 

I know my Samsung tv/hdmi connection is good and the remote works with my raspberry pi 4 with LibreElec, but it seems like this Radxa Zero does not recognize the HDMI/CEC device and its not installed. The Raspi4+LibreELEC works with my TV out of the box. I was going to install CoreELEC on this hardware, but it does not recognize my microSD card so I was hoping I could get it to work with my TV. Any idea where I should start?

The board is Odroid C4, 

SD card Image is download from armbian website

Ubuntu 22.04.3

kernel 6.1.50-current-meson64

Thank you for help

It comes up properly and connects to Wifi and to the attached LAN adapter, so I can access it via SSH on both interfaces.

BUT, when I disconnect the keyboard, it doesn't boot properly anymore and I cannot connect to it.

I attached a monitor to take a look at the startup messages and found that it hangs at starting the hostname service (see screenshot)

How can I get it to boot properly?

I would like to run a 32 bits (armhf) Debian or Ubuntu image on an Odroid C4. Do you know if this is possible, and if it is, can you point me to the right image ?

Cheers,

jf

I have trouble activating i2c on odroid c4. There's a pcf8563 module connected to the board. Also, /dev/i2c-0 /dev/i2c-1 exist. But pcf8563 does not show up when I run i2cdetect. I can rule out hardware issue because both i2c and pcf8563 work well with Hardkernel's Ubuntu image. So far, I've tried the followings but they don't work:

• Adding overlay="i2cA i2cB" to /boot/armbianEnv.txt and reboot.
• Manually editing device tree by changing status under "i2c@1d000" to "okay" and reboot.

Also, I remember that i2c used to work on older versions of Armbian, which come with older version of kernels. But since linux 5.19, i2c no longer works. So I suspect that some changes in kernel may break the i2c functionality.

I've uploaded diagnose info to https://paste.armbian.com/pevijojiwa

Please advise. Thank you.

I try to use GPIO on BananaPi M5 board. But interface doesn't work.

Armbian 23.05.1 Jammy with Linux 6.1.30-meson64.

/boot/armbianEnv.txt:

verbosity=1
console=both
overlay_prefix=meson
fdtfile=amlogic/meson-sm1-bananapi-m5.dtb
rootdev=UUID=d099eb25-cf52-43fb-b826-535b9109637f
rootfstype=ext4
overlays=w1-gpio
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

m5@bananapim5:~$ dmesg | grep w1
[    7.568386] w1-gpio onewire@0: gpio_request (pin) failed
[    7.607814] w1-gpio onewire@0: gpio_request (pin) failed
[    7.620109] w1-gpio onewire@0: gpio_request (pin) failed
[    7.662444] w1-gpio onewire@0: gpio_request (pin) failed
[    7.671512] w1-gpio onewire@0: gpio_request (pin) failed
[    7.677156] w1-gpio onewire@0: gpio_request (pin) failed
[    7.689428] w1-gpio onewire@0: gpio_request (pin) failed
[    7.693341] w1-gpio onewire@0: gpio_request (pin) failed
[    7.711606] w1-gpio onewire@0: gpio_request (pin) failed
[    7.714019] w1-gpio onewire@0: gpio_request (pin) failed
[    7.784669] w1-gpio onewire@0: gpio_request (pin) failed
[    7.836363] w1-gpio onewire@0: gpio_request (pin) failed
[    7.877654] w1-gpio onewire@0: gpio_request (pin) failed
[    7.915447] w1-gpio onewire@0: gpio_request (pin) failed
[    7.975862] w1-gpio onewire@0: gpio_request (pin) failed
[    7.983126] w1-gpio onewire@0: gpio_request (pin) failed
[   18.143361] w1-gpio onewire@0: gpio_request (pin) failed

Have any ideas?

First of all - everything I need works correctly...

However, I have a question about the SD card. During the first installation on the SSD disk, the system hung on the first reboot and you could see from the console that the SD card with UUID=61748c7e-b234-40e8-b6b6-592f845c3699 was being waited for. After the timeout, the only way to fix the "error" was to log into the system via terminal. Long story - only after commenting out the SD card in the fstab on the SSD:

UUID=61748c7e-b234-40e8-b6b6-592f845c3699 /media/mmcboot ext4 defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide 0 0
/media/mmcboot/boot /boot none bind 0 0

the system booted from the SSD as requested.

Since then, the SD card is not mounted and just shows up as:

Disk /dev/mmcblk0: 30.61 MiB, 32096256 bytes, 62688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

at fdisk -l. No UUID etc nothing...

The SD-Card is 32G and is readable on other systems...

Question now - is this normal? Can I live with that? Can it be fixed?

A "curiosity" - after booting from the SSD and updating the kernel to 6.0.13, the update ended up on both the SSD and the unmounted SD card. How - is a mystery to me (;-)

unable to handle kernel paging request at virtual address 000000000002e82e2...

See https://pasteboard.co/NjIo5L6UR0Px.jpg for the complete error message

System diagnosis information is uploaded to https://paste.armbian.com/aqahepelav

https://www.armbian.com/radxa-zero2/

I have a strage problem here with handling large files and I ran out of ideas.

System:

Odroid C4 (running from SD-card)

OS: 5.7.15-meson64 #20.08 SMP PREEMPT

PRETTY_NAME="Debian GNU/Linux 10 (buster)"

Attached to the system are a few USB disks: 

3x 8TB, 1x 4TB, 1x 3TB, 1x 2TB 

All filesystems: ext4 (except the remote NAS filesystem, which is ZFS - see below) 

3 of these disks are encrypted via truecrypt 7.1

On the 3 TB disk (ext4, unencrypted) there is a zipped dd-image of a harddisk.

That file has about 760 GB size

Now I tried to copy this file to a different location.

1st try: rsync to a NAS filer (ZFS, OmniOS, NFSv4) -> The rsync process goes to "D" state after a couple of GB

2nd try: scp to the same NAS -> same result. Copies a couple of gigabytes and then freezes

3rd to 5th try: mounted the NAS via NFSv4 and used rsync, scp and cp to the mountpoint -> same result

6th and 7th try: Tried to copy to a local (truecrypted) 8TB disk using rsync and cp -> same result

All these attemts stopped after transferring a couple of gigabytes and then the involved processes showed "defunct" state.

The transferred size is different every time and is between 40 an 200 GBytes.

What I tried to pinpoint the problem:

Tried to read the big file:

- md5sum <big_imagefile> -> works!

- dd if=<file> of=/dev/null bs=100M -> works!

Tried to write a big file:

- dd if=/dev/zero of=<file_on_8TB_truecrypted_disk> bs=100M count=10000 -> works!

Tried to copy using dd:

- dd if=<the_image_file> of=<file_on_truecrypted_disk> bs=100M -> works! Checksum is ok.

  So I finally managed to copy the file to a different location using dd.

But why is cp, scp and rsync failing?

Additional information:

During the process I did several experiments with the swapspace (disabled, used swapfile on SD-card,  etc) nothing helped.

In the logfiles there is not the smallest hint to a problem.

Also observing the memory during copy using "free" command did not show any unusual state. 

Systemlimits:

root@odroidc4:/var# ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 11363
max locked memory       (kbytes, -l) 65536
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 11363
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited
 

No overclocking or something. Just a plain Armbian installation. No funny "tuning".

I also have the same problem with some other applications.

For example rmlint, for eliminating duplicates, runs for a while (30 minutes?) and then freezes.

After that I connected the USB disk to a different Linux system and rmlint worked fine.

Fun fact: I'm pretty sure I originally copied the long file from a "full size" Linux system via rsync 

to the Odroid a couple of months ago.

Any ideas what the problem could be? 

Thank you!

  Lothar

I have issues with audio - only dummy interface shown - after the system update of ~2year old armbian.

I did not find any solution, so I decided to go for latest build - so I flashed latest image Armbian 23.02 Jammy XFCE to the emmc drive of my odroid C4.

System started ok, but unfortunately no HDMI audio device shown anyway.

I have no idea what to do, my dmesq is full of these lines:

[   13.936415]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[   13.937748]  fe.dai-link-0: ASoC: error at dpcm_fe_dai_prepare on fe.dai-link-0: -22
...
[  935.795034]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[  935.801472]  fe.dai-link-0: ASoC: error at dpcm_fe_dai_prepare on fe.dai-link-0: -22

I believe it is connected - there are some similar issues reported on various distros.   
Only solution, which seems to me would work, was reinstall odroid-base and odroid-alsa packages, however these are not in the armbian repositories.
Would you please help what should I do to resolve such challenge? Or at least where are these packages, please?

I followed official guide (https://docs.armbian.com/User-Guide_Getting-Started), but I always ends up with following:

Gave 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=e614931e-7b37-40f0-8d34-c3ca836004e8 does not exist.  Dropping to a shell!

SD-Card is working fine when other OS is used (such as Ubuntu provided by Hardkernel)

Am I missing something?

• Armbian_21.02.1_Odroidc1_bullseye_current_5.10.12.img.xz
• Armbian_22.08.0-trunk_Odroidc1_jammy_current_5.18.19.img.xz

Results:

Armbian_21.02.1_Odroidc1_bullseye_current_5.10.12.img.xz

Network is recognized and ssh login possible + Serial console output working.

ping gmail.com is working

Armbian_22.08.0-trunk_Odroidc1_jammy_current_5.18.19.img.xz

Network is not recognized and ssh login possible + Serial console output working.

ping gmail.com is not working

What puzzles me is that the kernel has a Watchdog feature which seems to operating fine as witnessed by the console log "watchdog: watchdog0: watchdog did not stop!" meaning that the watchdog driver has been told to disregard attempts to disable it (which is fine in the context that the watchdog is being used to reset the cpu). The problem is, the watchdog never times-out because, i presume, something is still "kicking the dog" (there seems to be a worker thread tasked for this purpose).

As a test I "brutally" caused a watchdog timeout (watchdog_dev.c: watchdog_release()) by:

1) disabling interrupts

2) setting watchdog timeout to 2 secs

3) going into infinite loop

The board now reboots fine and reliably but clearly i've skipped the notification handler mechanism that is meant to be used in the "odroid-reboot.c" solution.

So I guess my question is, are reboots meant to be an elegant hand-off from kernel to uboot, or is the watchdog supposed to be the means to get all registers/pin to their POR state ready for a cold boot?

I'm new here so didn't know where to post, let me know the preferred place or whether it's not appropriate.

I beleave that ODROID-C4 GPIO 40pins supports SDIO bus by SoC GPIO pin configuration.

How can I get such pin configuration, that enables SDIO bus on GPIO 40 pins?

Are there someone who got such configuration?

Thank you .

I have an OdroidC4 with a Hardkernel HDMI Display VU7Aplus.
I installed latest image 22.11 XFCE.

I think the display size via display data channel is not properly handled.
If a lot of text is to be displayed (see pic with the setting of the locale after first login), the lowest lines disappear.
So you have to type in the language/continent/country settings blind, because there is no input prompt to be seen.
Even when the GUI desktop starts, there is the same issue. When you open a terminal window, the lower border of the window
disappears (see pic).

Is there a way to configure the display size manually?

I also did a complete new build (Armbian_23.02.0-trunk_Odroidc4_jammy_current_6.1.11_xfce_desktop) , there is the same problem, as with the stable image from the download area.

Thanks for any help in advance

Andy

[   77.660325] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
[   77.666930] Mem abort info:
[   77.670400]   ESR = 0x86000004
[   77.673801]   EC = 0x21: IABT (current EL), IL = 32 bits
[   77.677915]   SET = 0, FnV = 0
[   77.681367]   EA = 0, S1PTW = 0
[   77.684796] user pgtable: 4k pages, 48-bit VAs, pgdp=000000000f26b000
[   77.690454] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000
[   77.697196] Internal error: Oops: 86000004 [#1] PREEMPT SMP
[   77.702645] Modules linked in: spidev rfkill cpufreq_powersave cpufreq_conservative lz4hc lz4hc_compress lz4 snd_soc_hdmi_codec snd_soc_meson_axg_tdmout snd_soc_meson_axg_sound_card snd_soc_meson_g12a_tohdmitx panfrost snd_soc_meson_card_utils gpu_sched snd_soc_meson_codec_glue snd_soc_meson_axg_frddr snd_soc_meson_axg_fifo meson_gxbb_wdt meson_vdec(C) v4l2_mem2mem ir_nec_decoder videobuf2_dma_contig meson_rng dw_hdmi_i2s_audio videobuf2_memops videobuf2_v4l2 videobuf2_common meson_saradc videodev rc_odroid mc meson_ir rc_core snd_soc_meson_axg_tdm_interface snd_soc_meson_axg_tdm_formatter snd_soc_core ac97_bus snd_pcm_dmaengine snd_pcm snd_timer snd soundcore display_connector zram sch_fq_codel ramoops reed_solomon nfsd efi_pstore auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 meson_gxl reset_meson_audio_arb rtc_meson_vrtc axg_audio sclk_div clk_phase dwmac_generic realtek dwmac_meson8b
[   77.810859] CPU: 2 PID: 3156 Comm: spidev_test Tainted: G         C        5.10.144-meson64 #22.08.2
[   77.819904] Hardware name: Hardkernel ODROID-C4 (DT)
[   77.824823] pstate: a0400009 (NzCv daif +PAN -UAO -TCO BTYPE=--)
[   77.830777] pc : 0x0
[   77.835509] lr : meson_spicc_pow2_determine_rate+0x2c/0x40
[   77.840340] sp : ffff800012eb3920
[   77.845116] x29: ffff800012eb3920 x28: 0000000000000000 
[   77.849906] x27: ffff000001170800 x26: 0000000000000000 
[   77.854808] x25: 0000000000000000 x24: ffff80001134cdf8 
[   77.860069] x23: 0000000000000002 x22: 0000000000000000 
[   77.865331] x21: ffff800012eb3a70 x20: ffff000000d75f00 
[   77.870594] x19: 0000000000000000 x18: 0000000000000000 
[   77.875854] x17: 0000000000000000 x16: 0000000000000000 
[   77.881115] x15: 0000aaaaaf3a3018 x14: 0000000000000000 
[   77.886376] x13: 0000000000000000 x12: 0000000000000000 
[   77.891637] x11: 0000000000000000 x10: 0000000000000054 
[   77.896898] x9 : 0000000000000001 x8 : 0000000000000001 
[   77.902159] x7 : 00000000ffffffbf x6 : 0000000000000000 
[   77.907421] x5 : 0000000000000000 x4 : ffff800012eb39c0 
[   77.912682] x3 : ffff800012eb3d30 x2 : 0000000000000000 
[   77.917943] x1 : ffff800012eb39c0 x0 : ffff00003f9c9e28 
[   77.923206] Call trace:
[   77.927258]  0x0
[   77.931291]  clk_core_determine_round_nolock.part.30+0x20/0x88
[   77.935568]  clk_core_round_rate_nolock+0x80/0x90
[   77.940226]  clk_mux_determine_rate_flags+0xdc/0x208
[   77.945145]  clk_mux_determine_rate+0x14/0x20
[   77.949456]  clk_core_determine_round_nolock.part.30+0x20/0x88
[   77.955234]  clk_core_round_rate_nolock+0x80/0x90
[   77.959889]  clk_core_set_rate_nolock+0x5c/0x1f0
[   77.964460]  clk_set_rate+0x38/0xa8
[   77.968504]  meson_spicc_transfer_one+0x88/0x300
[   77.972483]  spi_transfer_one_message+0x258/0x4c0
[   77.977139]  __spi_pump_messages+0x34c/0x570
[   77.981366]  __spi_sync+0x1e8/0x220
[   77.985297]  spi_sync+0x30/0x58
[   77.989235]  spidev_sync+0x48/0x80 [spidev]
[   77.993146]  spidev_message+0x2e0/0x400 [spidev]
[   77.997026]  spidev_ioctl+0x41c/0x848 [spidev]
[   78.001033]  __arm64_sys_ioctl+0xa8/0xe8
[   78.004914]  el0_svc_common.constprop.4+0x8c/0x180
[   78.009656]  do_el0_svc+0x24/0x90
[   78.013090]  el0_svc+0x14/0x20
[   78.016370]  el0_sync_handler+0x90/0xb8
[   78.019747]  el0_sync+0x160/0x180
[   78.023032] Code: bad PC value
[   78.026046] ---[ end trace b73c9916d0bfd2d6 ]---

This behaviour affects also simple programs like spidev_test from kernel archive.

I checked the hardkernel image (kernel 4.9) and there the problem is not existing.

Any ideas on that?

Thanks in advance, Michael

I just found the problem.

__________________________________________________________________________________________________________________________________________

Hi guys,

i'm running an Odroid C4 with Armbian Jammy.

uname -a
Linux Homeserver 6.0.13-meson64 #22.11.2 SMP PREEMPT Sun Dec 18 16:52:19 CET 2022 aarch64 aarch64 aarch64 GNU/Linux

Everything works fine so far. Today I just bought an external ssd drive "SanDisk Portable SSD 1TB". I can mount and use it, but the speed seams quit slow to me. The packaging of the ssd say "up to 520MB/s" and the USB 3.0 ports should have higher speed than this:

dd if=/dev/zero of=/media/nextcloud/test bs=1M count=1024 conv=fdatasync,notrunc
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 30.7941 s, 34.9 MB/s


echo 3 | sudo tee /proc/sys/vm/drop_caches (clear cached data)


dd if=/media/nextcloud/test of=/dev/null bs=1M count=1024 
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 6.17649 s, 174 MB/s

It is mounted via fstab like this:

UUID=64f28769-a9c1-4011-ad9d-103eceb4bdfc   /media/test   ext4   defaults   0   2

After I attached the drive to the usb port dmesg says:

[504496.115044] usb 2-1.1: new SuperSpeed USB device number 3 using xhci-hcd
[504496.136011] usb 2-1.1: New USB device found, idVendor=0781, idProduct=55bb, bcdDevice=60.04
[504496.136026] usb 2-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[504496.136031] usb 2-1.1: Product: Portable SSD
[504496.136036] usb 2-1.1: Manufacturer: SanDisk
[504496.136040] usb 2-1.1: SerialNumber: 323234384B4C343031363830
[504496.165630] scsi host0: uas
[504496.166400] usbcore: registered new interface driver uas
[504497.026910] scsi 0:0:0:0: Direct-Access     SanDisk  Portable SSD     6004 PQ: 0 ANSI: 6
[504497.040786] sd 0:0:0:0: Attached scsi generic sg0 type 0
[504527.525721] sd 0:0:0:0: [sda] tag#22 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
[504527.525739] sd 0:0:0:0: [sda] tag#22 CDB: opcode=0x9e, sa=0x10 9e 10 00 00 00 00 00 00 00 00 00 00 00 20 00 00
[504527.541708] scsi host0: uas_eh_device_reset_handler start
[504527.621980] usb 2-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
[504527.643980] scsi host0: uas_eh_device_reset_handler success
[504527.649863] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[504527.650022] sd 0:0:0:0: [sda] Write Protect is off
[504527.650031] sd 0:0:0:0: [sda] Mode Sense: 37 00 10 00
[504527.650297] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[504527.650448] sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[504527.650456] sd 0:0:0:0: [sda] Optimal transfer size 1048576 bytes
[504527.670807] sd 0:0:0:0: [sda] Attached SCSI disk

lsusb says driver=uas. Is this about rigth?

lsusb
Bus 002 Device 003: ID 0781:55bb SanDisk Corp. Portable SSD
Bus 002 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub             
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
Bus 001 Device 002: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub             
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
        |__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 3: Dev 4, If 0, Class=Communications, Driver=cdc_acm, 12M
        |__ Port 3: Dev 4, If 1, Class=CDC Data, Driver=cdc_acm, 12M

Has anyone an idea what I did wrong or what am I missing?

I feel like the ssd has USB 2.0 speeds. Could it be a problem with the driver?

For more information see:

https://paste.armbian.com/iyinumakiy
 

With kind regards,

Sebastian

[HDMI:1]
hdmi_group=2
hdmi_mode=87
hdmi_timings=1280 0 8 128 64 390 0 1 3 24 0 0 0 67 0 42009500 8

On the Odroid running Armbian 22.11 Jammy XFCE I tried changing:

/boot/armbianEnv.txt  

adding

display_autodetect=false

hdmimode=1280x390p60hz

I had no joy with this change, it did not modify the display output.  I love how fast and light Odroid is with Armbian, it is really snappy, but I need some help stretching out this display.  Any help pointing me in the right direction would be greatly appreciated, I already threw you $5 to take a look @Igor   https://paypal.com/donate/?hosted_button_id=A2AM5NWLVENF2&source=url

This patches:
https://github.com/armbian/build/blob/master/patch/kernel/archive/meson64-6.0/general-meson-mmc-1-arm64-amlogic-mmc-meson-gx-Add-core-tx-rx-eMMC-SD-SD.patch
https://github.com/armbian/build/blob/master/patch/kernel/archive/meson64-6.0/general-meson-mmc-2-arm64-amlogic-dts-meson-update-meson-axg-device-tree.patch
prevent that.

https://pastebin.com/Cbvd82R8

If I go back to the previous patch:
https://github.com/armbian/build/blob/master/patch/kernel/archive/meson64-6.0/general-meson-gx-mmc-set-core-clock-phase-to-270-degres.patch.disable
Wifi is ok.

Do I have to change something on my dts:

https://pastebin.com/PCa4jTgj

to be able to use the standard patches? Many thanks for the answer.

PS: For running audio I also had to add an asound.state and an axg-sound-card.conf.

Thank's Emanuel

não obteve sucesso

For testing, I'm looking for volunteers who have an Odroid C1  (s805)

I thought it was my micro SD card but I installed Ubuntu onto the same micro SD and the potato booted up fine with a green light and flashing blue light. 

Is this because it is a new update or am I doing something wrong.

https://www.waveshare.com/wiki/3.5inch_RPi_LCD_(A)

Does somebody have this kind of LCD running on a Odroid C2?

Is there a step by step? Because the Waveshare or Odroid Wiki is over my head 😟

I use external CAN-bus controller like MCP2515 via SPI interface. So, i need to enable SPI and CAN-bus peripherals and in kernel. So, could someone explain me how to do that? I know about device tree, but don`t know what to do.

Just give me some guide links about device tree management, any examples, etc.

I have C4 installed sdcard with bullseye from armbian website and all good first steps, change pass etc, update upgrade, no error on console and reboot from console it simple not rebooting, I need to power off all the time. I tried Jammy just for check that is worked so what is wrong with Bullseye?

My armbianmonitor -u is at http://ix.io/4cyZ

i am running an Odroid C2 with the latest Armbian based on debian Bullseye. As disk i am using an 8GB emmc flash drive. For longlive reasons i am thinking about to reduce the read or more important the write access to that drive. I know, that every SD card and also every EMMC flash drive got a certain amount of write access and then its dead...

So i am ask you what can i do to reduce read/write:

- move logs to external usb?

- activate ZRAM?

- disable cache...?

- tmpfs?

I am just at the beginning of this, so kindly let me know if you guys have some well know hints.

Thanks

JM

I install the image with "dd if=./armbian...img bs=8M of=/dev/sde; sync; sync". That makes a bootable EMMC card, but all attempts with the SDHC card it just seems to sit there.

When I attach the R5 to a USB port of my Odroid C2 it is not recognized. lsusb and dmesg do not show it. On my Ubuntu 22.04 PC it does show up.

Looked around and finally found an old post on this forum that mentions a bug with the C2 in recognizing USB devices.

The mentioned workaround is to add a second USB device and reboot the device. I added an USB drive and both are now recognized, initialized and working after a reboot. (When removing one of the devices it again doesn’t stick after a reboot.)

I can not find more information on this. It seems this problem isn't solved?

Regards,

Joost

Hi Folks,

did anybody got a working Armbian image for the Nanopi-K2 EMMC version. The SD Version works great, I'm looking for an EMMC version, or a tutorial on how to convert the SD version into an EMMC Version.

I know that there is an EMMC OÌmage at NanoPi Download page, BUT with this version none of the 4 USB Ports is working, and the Kernel is 3.14. and cannot be updated anymore.

many thanks for any hint

PS: I also try to contact nanopi support but I never get any response from them.

wikrie

Hi there,

I've an odroid C2 device used for home automation and running armbian (uname -a) : Linux odroidc2 4.19.69-meson64 which is running stable with no problem.

Yesterday, I've downloaded a fresh image of latest armbian for odroid C2, named Armbian_21.02.1_Odroidc2_buster_current_5.10.12.img.xz. Put it on a new SD card and booted. It booted correctly but I've NO network. The LAN chip doesnt work at all, altough it appear in the device list

I've theses entries in dmesg:

[    2.217600] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found
[    2.217611] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found
[    2.217694] meson8b-dwmac c9410000.ethernet: PTP uses main clock
[    2.218292] random: fast init done
[    2.218418] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37
[    2.218426] meson8b-dwmac c9410000.ethernet: 	DWMAC1000
[    2.218431] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported
[    2.218435] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported
[    2.218439] meson8b-dwmac c9410000.ethernet: COE Type 2
[    2.218443] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported
[    2.218446] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported
[    2.218538] meson8b-dwmac c9410000.ethernet: Normal descriptors
[    2.218543] meson8b-dwmac c9410000.ethernet: Ring mode enabled
[    2.218547] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer
...
[   10.568311] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
[   10.568329] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[   10.615619] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
[   10.615634] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[   10.716190] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
[   10.716207] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
[   10.735509] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
[   10.735535] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)

the first message I see when I boot (while plug in the power) is:

Net: Could not get PHY for ethernet@c9410000: addr -1

No ethernet found

The device is working with older armbian version but not the latest ?

Could anyone look at it because the image available for download seem's broken and should not be distributed like this.

I've reverted back to my old image (that's why I don't have the full log) and lost my week end on it, trying to sort it out without success. Could this be related to the .dtb ??

Thanks you

https://wiki.odroid.com/odroid-c4/hardware/hardware

Radxa Zero Diagnostic Dump

I have tried latest desktop image but my tv won't show me nothing so i tried latest Focal Cinnamon image and it is the same.

I can log with ssl

Here is my arbianmonitor -u result   http://ix.io/3ZCA
 

I have an C2 and an old VU7 (800x480p60hz) https://wiki.odroid.com/accessory/display/vu_series/vu7/vu7#tab__odroid-c2 that I was hoping to use for a mini kiosk.

Was able to run the older Hard Kernel supplied images with the uboot boot.ini updates suggested above to change disable auto detect, fix the resolution, and set to DVI rather than HDMI mode.

When I loaded the latest Focal image from Armbian when I have the screen switched on then the kernel faults and reboots.

## Flattened Device Tree blob at 04080000
   Booting using the fdt blob at 0x4080000
   Loading Ramdisk to 7b06a000, end 7bf49d63 ... OK
   Loading Device Tree to 000000007aff8000, end 000000007b069fff ... OK

Starting kernel ...

GXBB:BL1:08dafd:0a8993;FEAT:EDFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
TE: 59543
no sdio debug board detected

BL2 Built : 11:44:26, Nov 25 2015.
gxb gfb13a3b-c2 - jcao@wonton

I assume all I should need to do is update the /boot/boot.cmd, run `mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr` and the boot.scr should be updated.

Also set:

setenv disable_vu7 "false"
 

But that variable isn't being used anywhere in the boot.cmd so I don't think it is being applied.

After the last "sudo apt upgrade" my odroid C4 (meson) doesn't  reboot properly anymore.

In the system out there are many lines like:

"Begin: Running /scripts/local-block ... mdadm: No arrays found in config file or automatically done."

and one :

"mdadm: error opening /dev/md?*: No such file or directory

mdadm: No arrays found in config file or automatically /scripts/local-block/mdadm: 58: /scripts/local-block/mdadm: rm: not found"

at the end:

"Gave 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)"

it's stuck in initramfs with "ALERT! UUID=<myUUID> does not exist. Dropping to a shell!"

When I type "exit" the boot process starts and finishes successfully.

screen.pdf

A few odds and ends have come up, the biggest one appears to be the gpio-hog in the C2 device tree somehow not working, causing the USB hub on the board to never be powered on. 

root@odroidc2:/sys/class/gpio# cat /sys/kernel/debug/gpio
gpiochip1: GPIOs 378-496, parent: platform/c8834000.periphs:pinctrl@4b0, periphs-banks:
 gpio-392 (                    |mdio-reset          ) out hi
 gpio-407 (                    |reset               ) out hi
 gpio-422 (                    |cd                  ) in  lo
 gpio-465 (                    |TFLASH_VDD          ) out hi

gpiochip0: GPIOs 497-511, parent: platform/c8100000.bus:pinctrl@14, aobus-banks:
 gpio-500 (                    |TF_IO               ) out lo
 gpio-501 (                    |usb-hub-reset       ) out hi
 gpio-502 (                    |USB_OTG_PWR         ) out hi
 gpio-510 (                    |c2:blue:alive       ) out lo

The hog claims it is there, but I get no power to the port.

The other is the HDMI output becoming extremely fussy about the sort of monitor it's been given.

[update]

On the NanoPi K2 I actually get a crash on boot with my HDMI --> DVI adapter monitor.  With both monitors, if plugged in after boot, desktop displays (on C2 only the pure HDMI monitor will display at all), but a fault occurs:

[  312.393869] WARNING: CPU: 3 PID: 2809 at drivers/gpu/drm/meson/meson_crtc.c:150 meson_crtc_atomic_begin+0x64/0x70 [meson_drm]
[  312.393880] Modules linked in: fuse brcmfmac brcmutil lz4hc cfg80211 lz4hc_compress snd_soc_hdmi_codec rc_cec rfkill snd_soc_simple_card dw_hdmi_cec dw_hdmi_i2s_audio snd_soc_simple_card_utils meson_vdec snd_soc_core snd_pcm_dmaengine videobuf2_dma_contig snd_pcm meson_dw_hdmi videobuf2_memops snd_timer v4l2_mem2mem dw_hdmi snd meson_drm cec videobuf2_v4l2 drm_kms_helper soundcore videobuf2_common drm videodev meson_rng rng_core media drm_panel_orientation_quirks meson_ir rc_core meson_gxbb_wdt pwm_meson scpi_hwmon zram zsmalloc ip_tables x_tables realtek
[  312.394080] CPU: 3 PID: 2809 Comm: Xorg Tainted: G        W         4.19.1-meson64 #2
[  312.394086] Hardware name: friendlyarm,nanopi-k2 (DT)
[  312.394095] pstate: 40000005 (nZcv daif -PAN -UAO)
[  312.394117] pc : meson_crtc_atomic_begin+0x64/0x70 [meson_drm]
[  312.394138] lr : meson_crtc_atomic_begin+0x20/0x70 [meson_drm]
[  312.394144] sp : ffff00000dbb3a00
[  312.394149] x29: ffff00000dbb3a00 x28: 0000000000000000
[  312.394162] x27: ffff80007085e600 x26: ffff80005ce4be00
[  312.394176] x25: ffff8000707cb078 x24: ffff80005ccc5900
[  312.394189] x23: 0000000000000038 x22: 0000000000000000
[  312.394201] x21: 0000000000000000 x20: 0000000000000001
[  312.394214] x19: ffff8000707cb018 x18: 0000000000000000
[  312.394227] x17: 0000000000000000 x16: 0000000000000000
[  312.394239] x15: 0000000000000000 x14: 0000046500000441
[  312.394252] x13: 0000043c00000465 x12: 0000043800000438
[  312.394264] x11: 0000000000000898 x10: 00000804000007d8
[  312.394277] x9 : ffff000008e69888 x8 : ffff000000bea000
[  312.394290] x7 : 0000000000000000 x6 : ffff800070f2d168
[  312.394302] x5 : 0000000000000000 x4 : 0000000000000001
[  312.394315] x3 : 0000000000000000 x2 : 0000000000000000
[  312.394327] x1 : ffff800066ae8000 x0 : 00000000ffffffea
[  312.394340] Call trace:
[  312.394362]  meson_crtc_atomic_begin+0x64/0x70 [meson_drm]
[  312.394461]  drm_atomic_helper_commit_planes+0x70/0x208 [drm_kms_helper]
[  312.394543]  drm_atomic_helper_commit_tail+0x30/0x78 [drm_kms_helper]
[  312.394628]  commit_tail+0x74/0x78 [drm_kms_helper]
[  312.394712]  drm_atomic_helper_commit+0xe8/0x168 [drm_kms_helper]
[  312.394919]  drm_atomic_commit+0x48/0x58 [drm]
[  312.395001]  drm_atomic_helper_set_config+0x84/0xc0 [drm_kms_helper]
[  312.395174]  drm_mode_setcrtc+0x140/0x600 [drm]
[  312.395344]  drm_ioctl_kernel+0x88/0x100 [drm]
[  312.395511]  drm_ioctl+0x1ac/0x3e0 [drm]
[  312.395527]  do_vfs_ioctl+0xb8/0x8e0
[  312.395536]  ksys_ioctl+0x80/0xb8
[  312.395546]  __arm64_sys_ioctl+0x1c/0x28
[  312.395559]  el0_svc_common+0x60/0xe8
[  312.395569]  el0_svc_handler+0x24/0x80
[  312.395578]  el0_svc+0x8/0xc
[  312.395584] ---[ end trace 6dcc4ef2fc3d8888 ]---
[  312.395999] WARNING: CPU: 0 PID: 0 at drivers/gpu/drm/drm_vblank.c:1026 drm_vblank_put+0xa0/0xb8 [drm]
[  312.396019] Modules linked in: fuse brcmfmac brcmutil lz4hc cfg80211 lz4hc_compress snd_soc_hdmi_codec rc_cec rfkill snd_soc_simple_card dw_hdmi_cec dw_hdmi_i2s_audio snd_soc_simple_card_utils meson_vdec snd_soc_core snd_pcm_dmaengine videobuf2_dma_contig snd_pcm meson_dw_hdmi videobuf2_memops snd_timer v4l2_mem2mem dw_hdmi snd meson_drm cec videobuf2_v4l2 drm_kms_helper soundcore videobuf2_common drm videodev meson_rng rng_core media drm_panel_orientation_quirks meson_ir rc_core meson_gxbb_wdt pwm_meson scpi_hwmon zram zsmalloc ip_tables x_tables realtek
[  312.396395] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W         4.19.1-meson64 #2
[  312.396400] Hardware name: friendlyarm,nanopi-k2 (DT)
[  312.396410] pstate: 20000085 (nzCv daIf -PAN -UAO)
[  312.396589] pc : drm_vblank_put+0xa0/0xb8 [drm]
[  312.396762] lr : drm_crtc_vblank_put+0x18/0x20 [drm]
[  312.396768] sp : ffff000008003de0
[  312.396773] x29: ffff000008003de0 x28: 0000000000000001
[  312.396787] x27: ffff000008ceee28 x26: ffff000008ef0c8a
[  312.396817] x25: ffff80007134c000 x24: ffff000008e69000
[  312.396871] x23: 0000000000000020 x22: 0000000000000080
[  312.396897] x21: ffff8000707cb018 x20: ffff000008e69000
[  312.396910] x19: ffff800070f2c218 x18: 0000000000000000
[  312.396922] x17: 0000000000000000 x16: 0000000000000000
[  312.396935] x15: 000000000000684c x14: 0000000000006878
[  312.396947] x13: 0000000000006874 x12: 0000000000006870
[  312.396960] x11: 000000000000686c x10: 0000000000006840
[  312.396972] x9 : 0000000000007498 x8 : 0000000040000000
[  312.396984] x7 : 0000000000210d00 x6 : ffff000008e69888
[  312.396997] x5 : ffff000000ba5a5c x4 : 0000000000000001
[  312.397030] x3 : 0000000000000170 x2 : 0000000000000000
[  312.397074] x1 : ffff800070f2d000 x0 : ffff800070a51800
[  312.397087] Call trace:
[  312.397265]  drm_vblank_put+0xa0/0xb8 [drm]
[  312.397456]  drm_crtc_vblank_put+0x18/0x20 [drm]
[  312.397494]  meson_crtc_irq+0x7c/0x608 [meson_drm]
[  312.397514]  meson_irq+0x20/0x30 [meson_drm]
[  312.397533]  __handle_irq_event_percpu+0x74/0x188
[  312.397559]  handle_irq_event_percpu+0x34/0x88
[  312.397574]  handle_irq_event+0x48/0x78
[  312.397587]  handle_fasteoi_irq+0xa8/0x180
[  312.397597]  generic_handle_irq+0x24/0x38
[  312.397607]  __handle_domain_irq+0x5c/0xb0
[  312.397616]  gic_handle_irq+0x58/0xa8
[  312.397640]  el1_irq+0xb0/0x128
[  312.397665]  arch_cpu_idle+0x10/0x18
[  312.397678]  do_idle+0x1d4/0x298
[  312.397686]  cpu_startup_entry+0x24/0x28
[  312.397699]  rest_init+0xcc/0xd8
[  312.397712]  start_kernel+0x3d4/0x400
[  312.397718] ---[ end trace 6dcc4ef2fc3d8889 ]---

FYI @Neil Armstrong

Trying to boot Armbian on HC4, no picture coming up.

I guess my problem is my old LCD display that im connecting with hdmi-vga connector.

Display and connector are working, i tried with Odroid ubuntu SD-card, but when i ordered i didnt realize its Ubuntu-minimal.

(My internet comes from mobile wifi hotspot, and i have no idea how to install GUI in there. Also Odroid wifi-bluetooth dongle is a pita)

In Ubuntu, to get the monitor working i changed lines in boot.ini and conf.ini, no idea which of those files is the right one.

My working lines in those Odroid Ubuntu 20.04  files are:

setenv display_autodetect "false"
setenv hdmimode "1280x1024p60hz"
setenv voutmode "dvi"

(Also the Odroid wifi dongle needs to be disconnected at boot, otherwise picture is scrambled)

The question is: how to make such settings on Armbian SD-card. What files need to be changed with what text?

according to here 5.13 is latest kernel https://www.armbian.com/odroid-c2/

but when I issue:

sudo apt-get update && sudo apt-get dist-upgrade -y

I'm still on 5.10....

I'm running Armbian from a emmc 16GB card. When I use the web browser the mouse constantly flickers, is there any way to get this to stop? Is there a graphics driver I should have enabled? When I select Additional Hardware Drivers none show up, so maybe there isnt a GPU accelerated driver available. Also switching between desktops feels sluggish. Maybe Im expecting too much performance from a $50 SBC.

Thanks for your help & time in making this distribution. Im just looking to make the best user experience possible.

The latest apt-get upgrade on my board running Focal updated all but two (described below) of the following packages:

armbian-firmware armbian-focal-desktop-xfce armbian-zsh bluez bluez-obexd
libbluetooth3 libnss-myhostname libpam-systemd libsecret-1-0
libsecret-common libsmbclient libsystemd0 libudev1 libwbclient0
linux-dtb-current-meson64 linux-image-current-meson64 linux-libc-dev
linux-u-boot-odroidc4-current python3-samba samba samba-common
samba-common-bin samba-libs smbclient systemdsystemd-sysv udev

This generated a new initramfs and uboot updates so I rebooted afterwards to make sure everything was ok.  Now, the

Light Display Manager has a "failed to start" message and it prompts to see "systemctl status lightdm.service'.

The output from that command is reproduced here: http://ix.io/3qc2 .  (It tries to start the service five times and then gives up

and gives the command-line login only).

When I try to run

$ sudo apt-get update

again, the output now shows that :

armbian-config and linux-focal-root-current-odroidc4

have been kept back.

Any suggestions on how to get that glorious desktop happening again?

I'm trying to get more experience with C, systems programming, drivers, scripting, (also interested in the Berkeley

Software Distributions, have a working Linux From Scratch built [but haven't delved into

https://www.linuxfromscratch.org/blfs/ much yet], have compiled a couple kernels with Gentoo, and have done some

hobbyist work w/ assembly programming).
 

In short, I like this project and want to contribute after improving my skillset more and (also getting more freetime) --  but my system stubbed

its toe on this latest update. should I revert (somehow) to an earlier version of a package?  (I'm not sure which one or ones from that list

of updates goofed the lightdm service up.)

Thanks in advance for any assistance.

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 screen will display for a minute or two before the display will stop and the screen is blank. After 4 minutes the display is back ON.

Armbian_21.02.3_Odroidc4_focal_current_5.10.21_xfce_desktop

Last errors reported;

Mar 11 20:00:00 odroidc4 systemd-udevd[1507]: card1: Worker [1535] failed
Mar 11 20:00:00 odroidc4 systemd-udevd[1507]: Worker [1535] terminated by signal 9 (KILL)
Mar 11 20:00:00 odroidc4 systemd-udevd[1507]: card1: Worker [1535] processing SEQNUM=2984 killed
Mar 11 20:00:00 odroidc4 systemd-udevd[1535]: card1: Spawned process '/usr/local/bin/hdmi-hotplug' [4565] timed out after 2min 59s, killing
Mar 11 19:59:14 odroidc4 systemd[1]: armbian-disable-autologin.service: Succeeded.
Mar 11 19:59:13 odroidc4 systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbu>
Mar 11 19:59:13 odroidc4 systemd[1]: Reloading.
Mar 11 19:59:13 odroidc4 systemctl[5584]: Removed /etc/systemd/system/timers.target.wants/armbian-disable-autologin.timer.
Mar 11 19:59:13 odroidc4 systemd[1]: Started Disable automated desktop login.
Mar 11 19:58:04 odroidc4 systemd[4695]: tracker-store.service: Succeeded.
Mar 11 19:58:04 odroidc4 tracker-store[4871]: OK
Mar 11 19:58:00 odroidc4 systemd-udevd[1507]: card1: Worker [1535] processing SEQNUM=2984 is taking a long time
Mar 11 19:58:00 odroidc4 systemd-udevd[1535]: card1: Spawned process '/usr/local/bin/hdmi-hotplug' [4565] is taking longer than 59s to complete

I am using two Odroid N2 and a new Odroid C4. The N2 installation with OMV5 is using Kernel 4.9.236 actually and the C4 is using the kernel 5.8 used in the latest download image for debian buster. When I try to install newer kernels after the following linux kernel packages the installation gets broken and the odroids are not booting anymore.

There is also no output on hdmi to see what problem could be exist. On Odroid N2 I hear the USB drives starting, stopping, starting and then nothing happens.

All other updates are installing without problems in rebooting. The N2 are using on my test N2 a micro sd card and on my prod n2 a emmc card. The C4 is also using a emmc card.

Can someone help to fix this or are there other persons using these odroids with same problems?

Here are the actually installed packages without problems:

ii  linux-dtb-legacy-meson64          20.08.6                             arm64        Linux DTB, version 4.9.236-meson64
ii  linux-image-legacy-meson64        20.08.6                             arm64        Linux kernel, version 4.9.236-meson64

And here is the output from installing the newer kernel which is actually available

Reading package lists...
Building dependency tree...
Reading state information...
Suggested packages:
  linux-firmware-image-legacy-meson64
The following packages will be upgraded:
  linux-dtb-legacy-meson64 linux-image-legacy-meson64
apt-listchanges: Reading changelogs...
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/21.9 MB of archives.
After this operation, 2632 kB of additional disk space will be used.
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 62535 files and directories currently installed.)
Preparing to unpack .../linux-dtb-legacy-meson64_20.08.13_arm64.deb ...
Unpacking linux-dtb-legacy-meson64 (20.08.13) over (20.08.10) ...
dpkg: warning: unable to delete old directory '/boot/dtb-4.9.236-meson64': Directory not empty
Preparing to unpack .../linux-image-legacy-meson64_20.08.13_arm64.deb ...
update-initramfs: Deleting /boot/initrd.img-4.9.236-meson64
Removing obsolete file uInitrd-4.9.236-meson64
Unpacking linux-image-legacy-meson64 (20.08.13) over (20.08.10) ...
Setting up linux-dtb-legacy-meson64 (20.08.13) ...
Setting up linux-image-legacy-meson64 (20.08.13) ...
update-initramfs: Generating /boot/initrd.img-4.9.238-meson64
update-initramfs: Converting to u-boot format
Fertig ...

I recently uploaded Armbian_20.11_Odroidc4_focal_current 5.9.12_desktop.img.xz onto a new Odroid-C4. Booting up and getting started hasn't been a problem, but I've been interested in driving some brushless motors using a PWM control signal and started looking through the device tree. The C4 is supposed to have a total of 6 PWM outputs, spread over 3 pwmchip devices, which (I believe) should be named pwmchip0, pwmchip4, and pwmchip8. However, upon navigating to /sys/class/pwm, I'm only seeing pwmchip0. This seems a little odd, because if PWM was entirely disabled in the device tree, I wouldn't have expected that any of the chips would have appeared. Not sure if this is a board-level problem, or something I'm missing in the kernel image I downloaded. I'm planning on comparing the stock Odroid image, but the spare uSD card I ordered is taking longer to arrive than expected. I can update when it comes in, but wanted to check either way if this was expected behavior for the Armbian image and if so, there is a simple fix, since I'd prefer sticking with vanilla Armbian over whatever fork the manufacturer puts out is.
 

Thanks for your time, and please let me know if there's any add'l information I can provide to make this easier!

Hey,  I am not able to compile a .ko kernel module : below the error.

1. I think it's fair to say that it may happen on many boards.
2. I guess you supposed that before I had to get the linux-headers on. which required to tune the build config and include the headers during the build for that specific meson64 release at least.  Saying that after rebuilding all I am stuck again on the vdso as i can't build a .ko easily.

I think many people but i let the team taken the decision may be stuck at one point on linux-headers or to compile a .ko module. I would recommend to have DEFAULT parameter YES for the linux-headers as well as all that would be required to compile some .ko module. I remember in the past get stucked on some other boards for similar reasons.

Let us know the decision and how to solve that from a initial build . I also would like to mention that your build is kool. thanks for that. just a few steps to make other customers happy

------------- ERROR in making .KO ------------------------------------------

/src/linux-headers-5.9.16-meson64'
scripts/Makefile.build:418: warning: overriding recipe for target 'modules.order'
Makefile:1400: warning: ignoring old recipe for target 'modules.order'
make[2]: *** No rule to make target 'arch/arm64/kernel/vdso/vdso.lds', needed by 'arch/arm64/kernel/vdso/vdso.so.dbg'.  Stop.
make[1]: *** [arch/arm64/Makefile:193: vdso_prepare] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.9.16-meson64'
make: *** [Makefile:6: all] Error 2

So as we know, the Hardkernel kernel did support powering the device on and off via a GPIO pin. This does not seem to work on Armbian with the mainline kernel. What does work is powering the device on and off with the remote control. So I wonder, what has to be done to enable power on and off vie the GPIO? My approach till now makes it possible to shutdown the device via GPIO interrupt. But then it will not come up again except if I reconnect the power cord or use the remote. I use this user device three overlay btw:

/dts-v1/;
/plugin/;
/{
		fragment@0 {
                target = <&ao_pinctrl>;
                __overlay__ {
                        power_btn_port:power_btn_port {
                                mux {
                                        groups = "GPIOAO_10";
                                        function = "gpio_periphs";
                                        bias-pull-up;
                                        output-high;
                                };
                        };
                };
        };

        fragment@1 {
                target-path = "/";
                __overlay__ {
                        gpio_keys:gpio_keys {
                                compatible = "gpio-keys";
                                power_btn:power_btn {
                                        label = "POWER BUTTON";
                                        linux,code = <116>;
                                        gpios = <&gpio_ao 10 0>; //GPIOAO_10
                                        interrupt-parent = <&gpio_intc>;
                                        interrupts = <10 3>;
                                        wakeup-source;
                                };
                        };
                };
        };
};

I've tried with the default pin as well (GPIOX_4) but with the same result. The hope was that the AO domain would do some magic like with the remote but no dice. Also the 'wakeup-source' seems to be ignored by the system as 'cat /sys/kernel/irq/*/wakeup' prints 'disabled' for all IRQ's.

So, any ideas besides dissembling the remote and some solider works from the power button on the chassis to the IR IC to make it part of the final device? This would be very Frankenstein'ish just have a power button.

Hi,

I'm getting a random packet loss on the ethernet connection. When pinging, about 6-8% pings are lost, the ssh connection sometimes freezes for a moment. 

Things I've tried so far:

• Disabled NetworkManager, added eth0 in /etc/network/interfaces with a static ip4 address
• Disabled EEE for eth0
• Replaced ethernet cable
• Plugged into different switch

None of them made something better. My C1 & C4 with the same Armbian Buster version/release don't have this issue. 

How to investigate deeper in this issue?

Image used Armbian_20.11.10_Odroidc4_focal_current_5.9.14_desktop.img

It works with micro SD (eMMc not inserted)

Not booting with eMMc (SD not inserted),

With SD & eMMC, system boot from SD .. . I tried nand-sata-install -> "Update bootloader" script same problem.

see the attached output error from my monitor

I recently bought a 64 GB eMMC module (chip on orange board) from Ordoid/Hardkernel but u-boot does not recognize the eMMC.

What I did:

• installed the official Armbian_20.11.10_Odroidc2_focal_current_5.9.14.img.xz with Etcher on SD card
• booted successfully from SD card, eMMC is accessible from within Armbian/Ubuntu
• executed nand-sata-install to transfer the system to eMMC, which completed without error messages
• shutdown the system, removed SDcard and restarted it

The serial console displayed the following:

U-Boot 2020.10-armbian (Jan 05 2021 - 01:40:47 +0100) odroid-c2                                                                

Model: Hardkernel ODROID-C2                                                                                                    
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (0:1)                                                                           
DRAM:  2 GiB                                                                                                                   
MMC:   mmc@72000: 0, mmc@74000: 1                                                                                              
In:    serial                                                                                                                  
Out:   serial                                                                                                                  
Err:   serial                                                                                                                  
Net:   eth0: ethernet@c9410000                                                                                                 
Hit any key to stop autoboot:  0                                                                                               
Card did not respond to voltage select!                                                                                        
Card did not respond to voltage select!                                                                                        
MMC Device 2 not found                                                                                                         
no mmc device at slot 2                                                                                                        
starting USB...                                                                                                                
Bus usb@c9100000: USB DWC2                                                                                                     
scanning bus usb@c9100000 for devices... 2 USB Device(s) found                                                                 
       scanning usb for storage devices... 0 Storage Device(s) found                                                           

and then tried to boot via network.

I then flashed the eMMC with the official Odroid image ubuntu-20.04-3.16-minimal-odroid-c2-20200617.img.xz and the system booted up successfully, so the eMMC module is working fine.

Next step was to try the nightly build (Armbian_21.02.0-trunk.80_Odroidc2_focal_current_5.10.10_gnome_desktop.img.xz, with Etcher flashed on SD, then nand-sata-install) and again the eMMC as not visible in u-boot so the system did not come up.

Therefore I set up an Armbian build environment and first tried to use this promising patch for u-boot https://gitlab.denx.de/u-boot/custodians/u-boot-amlogic/-/commit/5ccd5d2cc98224108ae9fb09593a862c9caa5e80 but it seemed not to be suficient.

I then replaced the provided u-boot v2020.10 with the new v2021.01 version and after replacing the kernel and uboot packages with the self compiled ones the eMMC was recognised by u-boot and the system boots from the orange 64GB eMMC module.

U-Boot 2021.01-armbian (Feb 01 2021 - 11:57:23 +0100) odroid-c2

Model: Hardkernel ODROID-C2
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (0:1)
DRAM:  2 GiB
MMC:   mmc@72000: 0, mmc@74000: 1
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0 
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
7136 bytes read in 1 ms (6.8 MiB/s)
## Executing script at 08000000
161 bytes read in 1 ms (157.2 KiB/s)
15703885 bytes read in 342 ms (43.8 MiB/s)
25461248 bytes read in 556 ms (43.7 MiB/s)
38868 bytes read in 2 ms (18.5 MiB/s)
232 bytes read in 1 ms (226.6 KiB/s)
Applying kernel provided DT fixup script (meson-fixup.scr)

The "Card did not respond to voltage select" message is from the missing SD card

Therefore I kindly ask to upgrade the u-boot of Odroid C2 to version 2021.01 in the next release.

Hi,

for the Odrioid C4  eMMC v0.4 modules are available.

like

Can I use these v0.4 modules in my Odroid C2, too? I didn't find any information about the compatibility.

Thanks in advance!

Matt

A few weeks ago, after a firmware-upgrade my C2 bricked. It's blue led didn't flash any more and no serial console was available. Since I had everything setup just right I wanted to recover it using these steps here: https://docs.armbian.com/User-Guide_Recovery/#replacing-boot

Off course I replaced the packages with the ones for the C2. Specifically:

• https://mirrors.dotsrc.org/armbian-apt/pool/main/l/linux-5.9.14-meson64/linux-dtb-current-meson64_20.11.3_arm64.deb
• https://mirrors.dotsrc.org/armbian-apt/pool/main/l/linux-5.9.14-meson64/linux-image-current-meson64_20.11.3_arm64.deb
• https://mirrors.dotsrc.org/armbian-apt/pool/main/l/linux-buster-root-current-odroidc2/linux-buster-root-current-odroidc2_20.11.6_arm64.deb
• https://mirrors.dotsrc.org/armbian-apt/pool/main/a/armbian-firmware/armbian-firmware_20.11.3_all.deb

After following all the steps, I don't seem to have an uInitrd. I don't know if that would help booting up again, but from the symlinks section it's the only file missing after following all the steps:

Does anybody know what went wrong or guide me towards the right steps to recover my C2?

I started to play with lima(mesa mali drivers) on Odroid C2

with ubuntu 19.04 with kernel 5.3. rc6 with lima enabled

I add latest mesa drivers from 

https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers

there are only arm64 packages

But there is problem on amlogic platform with order of dri/card* 

as dri/card0 point to lima

and dri/card1 point to mesa drm driver

but most software don't have options to set it up and they expect drm driver on card0 

so there is problem in weston 5 for example 

https://lists.freedesktop.org/archives/wayland-devel/2018-September/039446.html

but weston 4 and 6(https://packages.debian.org/sid/weston) is working fine

so what is working in my case

I was able to start weston4 like weston --drm-device=card1

then weston-simple-egl

then glmark2-wayland

so good luck with lima and panfrost

it will be nice to test panfrost on odroid xu4

It will be nice to have simple options to enable lima/panfrost on armbian what do you think?

It should be metter of enabling LIMA in kernel configs

and add install mesa from oibaf ppa

I asked him about armhf build be he talk about small amount of users

lima gitlab issues

https://gitlab.freedesktop.org/lima/mesa/issues

Hi,

I recently installed a fresh Armbian and did some tests. I noticed two major problems:

• Video is not accelerated: it is absolutely unusable with kodi
• Bluetooth seems absent (missing from DTB? other reason?)

Please find below execution outputs of some commands:

root@nanopik2-s905:~$ cat /etc/armbian-release 
# PLEASE DO NOT EDIT THIS FILE
BOARD=nanopik2-s905
BOARD_NAME="NanoPi K2"
BOARDFAMILY=meson-gxbb
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=b9814056
DISTRIBUTION_CODENAME=focal
DISTRIBUTION_STATUS=supported
VERSION=20.11.3
LINUXFAMILY=meson64
BRANCH=current
ARCH=arm64
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
root@nanopik2-s905:~$ 
root@nanopik2-s905:~$ hciconfig
root@nanopik2-s905:~$ 
root@nanopik2-s905:~$ rfkill list
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
root@nanopik2-s905:~$ 

Is there any people with same problem on their boards?

Any idea on how to fix bluetooth feature? I read all 7 pages but I did not find anything useful to solve my problem.

Another information, I boot original image from friendlyarm and bluetooth is up and running so my board is physically good.

I tried Armbian_20.11.0-trunk.32_Odroidc2_focal_current_5.9.8.img and Armbian_20.11.0-trunk.32_Odroidc2_buster_current_5.9.8.img and both will not boot after apt upgrade.  Armbian_20.08.22_Odroidc2_focal_current_5.9.6.img will not come up after sudo reboot and has to be power cycled. I believe the latter has been a persistent issue.

With my OPi Zero, I noticed that at random times the ethernet connection somehow gets disabled. The only way to recover is by power cycling. I use the device as Pi-Hole (so when ethernet gets disconnected, I don't have internet anymore), print server and UniFi controller. 

I decided to swap it for my Odroid C2. Odd enough the C2 has the same issue. Maybe someone can help me with this?

When powercycled, the Odroid with the latest Armbian (installed two days ago) is all up and running fine. It can connect to the internet, I can SSH into it. The ethernet led is flashing orange, so the gigabit connection is available. However, at rondom times the ethernet leds are both disabled. At this point, the C2 is still alive, but there's no way to access it without power cycling. I've tried removing the ethernet cable and connecting it again, hoping Armbian would recognize the connection - what happens in this case is that the green led will flash a few times (100Mbit) but the device is still offline.

I've added some information from the log here before rebooting. This information keeps repeating in the log files... Hopefully someone can guide my as how to get the connection stable.

Nov 23 06:00:14 localhost NetworkManager[2219]: <warn>  [1606107614.7172] dhcp4 (eth0): request timed out
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.7183] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.7860] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 6807
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.7863] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.7897] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.7973] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:00:14 localhost NetworkManager[2219]: <warn>  [1606107614.8046] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.8094] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.8358] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.8470] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.8493] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.8571] manager: NetworkManager state is now CONNECTING
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.8619] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.8719] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.8781] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:00:14 localhost NetworkManager[2219]: <info>  [1606107614.9001] dhcp4 (eth0): dhclient started with pid 6869
Nov 23 06:00:59 localhost NetworkManager[2219]: <warn>  [1606107659.7124] dhcp4 (eth0): request timed out
Nov 23 06:00:59 localhost NetworkManager[2219]: <info>  [1606107659.7125] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:00:59 localhost NetworkManager[2219]: <info>  [1606107659.7290] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 6869
Nov 23 06:00:59 localhost NetworkManager[2219]: <info>  [1606107659.7291] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:00:59 localhost NetworkManager[2219]: <info>  [1606107659.7299] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:00:59 localhost NetworkManager[2219]: <info>  [1606107659.7315] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:00:59 localhost NetworkManager[2219]: <warn>  [1606107659.7331] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:00:59 localhost NetworkManager[2219]: <info>  [1606107659.7342] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:05:59 localhost NetworkManager[2219]: <info>  [1606107959.7126] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:05:59 localhost NetworkManager[2219]: <info>  [1606107959.7151] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:05:59 localhost NetworkManager[2219]: <info>  [1606107959.7156] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:05:59 localhost NetworkManager[2219]: <info>  [1606107959.7172] manager: NetworkManager state is now CONNECTING
Nov 23 06:05:59 localhost NetworkManager[2219]: <info>  [1606107959.7183] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:05:59 localhost NetworkManager[2219]: <info>  [1606107959.7206] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:05:59 localhost NetworkManager[2219]: <info>  [1606107959.7219] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:05:59 localhost NetworkManager[2219]: <info>  [1606107959.7275] dhcp4 (eth0): dhclient started with pid 7194
Nov 23 06:06:44 localhost NetworkManager[2219]: <warn>  [1606108004.7119] dhcp4 (eth0): request timed out
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.7132] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.7836] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 7194
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.7846] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.7925] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.8128] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:06:44 localhost NetworkManager[2219]: <warn>  [1606108004.8311] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.8429] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.9060] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.9156] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.9162] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.9176] manager: NetworkManager state is now CONNECTING
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.9186] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.9212] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.9225] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:06:44 localhost NetworkManager[2219]: <info>  [1606108004.9281] dhcp4 (eth0): dhclient started with pid 7256
Nov 23 06:07:29 localhost NetworkManager[2219]: <warn>  [1606108049.7211] dhcp4 (eth0): request timed out
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7213] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7377] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 7256
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7378] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7386] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7403] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:07:29 localhost NetworkManager[2219]: <warn>  [1606108049.7418] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7428] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7488] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7512] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7517] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7532] manager: NetworkManager state is now CONNECTING
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7542] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7565] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7578] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:07:29 localhost NetworkManager[2219]: <info>  [1606108049.7635] dhcp4 (eth0): dhclient started with pid 7295
Nov 23 06:08:14 localhost NetworkManager[2219]: <warn>  [1606108094.7220] dhcp4 (eth0): request timed out
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.7231] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.7931] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 7295
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.7939] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.8019] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.8166] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:08:14 localhost NetworkManager[2219]: <warn>  [1606108094.8238] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.8287] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.8542] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.8653] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.8675] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.8751] manager: NetworkManager state is now CONNECTING
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.8797] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.8897] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.8957] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:08:14 localhost NetworkManager[2219]: <info>  [1606108094.9177] dhcp4 (eth0): dhclient started with pid 7356
Nov 23 06:08:59 localhost NetworkManager[2219]: <warn>  [1606108139.7215] dhcp4 (eth0): request timed out
Nov 23 06:08:59 localhost NetworkManager[2219]: <info>  [1606108139.7217] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:08:59 localhost NetworkManager[2219]: <info>  [1606108139.7543] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 7356
Nov 23 06:08:59 localhost NetworkManager[2219]: <info>  [1606108139.7545] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:08:59 localhost NetworkManager[2219]: <info>  [1606108139.7553] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:08:59 localhost NetworkManager[2219]: <info>  [1606108139.7569] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:08:59 localhost NetworkManager[2219]: <warn>  [1606108139.7584] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:08:59 localhost NetworkManager[2219]: <info>  [1606108139.7594] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:13:59 localhost NetworkManager[2219]: <info>  [1606108439.8093] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:13:59 localhost NetworkManager[2219]: <info>  [1606108439.8375] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:13:59 localhost NetworkManager[2219]: <info>  [1606108439.8435] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:13:59 localhost NetworkManager[2219]: <info>  [1606108439.8632] manager: NetworkManager state is now CONNECTING
Nov 23 06:13:59 localhost NetworkManager[2219]: <info>  [1606108439.8754] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:13:59 localhost NetworkManager[2219]: <info>  [1606108439.8999] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:13:59 localhost NetworkManager[2219]: <info>  [1606108439.9157] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:13:59 localhost NetworkManager[2219]: <info>  [1606108439.9637] dhcp4 (eth0): dhclient started with pid 7732
Nov 23 06:14:45 localhost NetworkManager[2219]: <warn>  [1606108485.7230] dhcp4 (eth0): request timed out
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.7243] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.7939] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 7732
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.7947] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.8028] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.8232] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:14:45 localhost NetworkManager[2219]: <warn>  [1606108485.8414] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.8533] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.9010] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.9035] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.9043] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.9058] manager: NetworkManager state is now CONNECTING
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.9069] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.9092] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.9105] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:14:45 localhost NetworkManager[2219]: <info>  [1606108485.9161] dhcp4 (eth0): dhclient started with pid 7796
Nov 23 06:15:30 localhost NetworkManager[2219]: <warn>  [1606108530.7220] dhcp4 (eth0): request timed out
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.7230] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.7615] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 7796
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.7623] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.7705] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.7924] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:15:30 localhost NetworkManager[2219]: <warn>  [1606108530.8106] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.8219] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.8278] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.8303] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.8308] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.8322] manager: NetworkManager state is now CONNECTING
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.8333] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.8355] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.8370] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:15:30 localhost NetworkManager[2219]: <info>  [1606108530.8426] dhcp4 (eth0): dhclient started with pid 7844
Nov 23 06:16:15 localhost NetworkManager[2219]: <warn>  [1606108575.7225] dhcp4 (eth0): request timed out
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.7235] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.7936] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 7844
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.7944] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.8025] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.8236] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:16:15 localhost NetworkManager[2219]: <warn>  [1606108575.8429] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.8549] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.9177] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.9369] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.9375] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.9390] manager: NetworkManager state is now CONNECTING
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.9400] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.9423] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.9436] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:16:15 localhost NetworkManager[2219]: <info>  [1606108575.9494] dhcp4 (eth0): dhclient started with pid 7907
Nov 23 06:17:00 localhost NetworkManager[2219]: <warn>  [1606108620.7216] dhcp4 (eth0): request timed out
Nov 23 06:17:00 localhost NetworkManager[2219]: <info>  [1606108620.7217] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:17:00 localhost NetworkManager[2219]: <info>  [1606108620.7543] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 7907
Nov 23 06:17:00 localhost NetworkManager[2219]: <info>  [1606108620.7544] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:17:00 localhost NetworkManager[2219]: <info>  [1606108620.7552] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:17:00 localhost NetworkManager[2219]: <info>  [1606108620.7570] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:17:00 localhost NetworkManager[2219]: <warn>  [1606108620.7586] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:17:00 localhost NetworkManager[2219]: <info>  [1606108620.7596] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:22:00 localhost NetworkManager[2219]: <info>  [1606108920.7743] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:22:00 localhost NetworkManager[2219]: <info>  [1606108920.7769] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:22:00 localhost NetworkManager[2219]: <info>  [1606108920.7774] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:22:00 localhost NetworkManager[2219]: <info>  [1606108920.7789] manager: NetworkManager state is now CONNECTING
Nov 23 06:22:00 localhost NetworkManager[2219]: <info>  [1606108920.7800] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:22:00 localhost NetworkManager[2219]: <info>  [1606108920.7823] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:22:00 localhost NetworkManager[2219]: <info>  [1606108920.7836] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:22:00 localhost NetworkManager[2219]: <info>  [1606108920.7894] dhcp4 (eth0): dhclient started with pid 8256
Nov 23 06:22:45 localhost NetworkManager[2219]: <warn>  [1606108965.7229] dhcp4 (eth0): request timed out
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.7242] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.7938] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 8256
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.7946] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.8024] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.8229] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:22:45 localhost NetworkManager[2219]: <warn>  [1606108965.8412] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.8532] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.8650] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.8674] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.8679] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.8694] manager: NetworkManager state is now CONNECTING
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.8705] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.8728] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.8741] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:22:45 localhost NetworkManager[2219]: <info>  [1606108965.8798] dhcp4 (eth0): dhclient started with pid 8289
Nov 23 06:23:30 localhost NetworkManager[2219]: <warn>  [1606109010.7226] dhcp4 (eth0): request timed out
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.7236] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.7925] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 8289
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.7928] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.7969] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.8048] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:23:30 localhost NetworkManager[2219]: <warn>  [1606109010.8117] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.8168] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.8422] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.8533] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.8555] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.8634] manager: NetworkManager state is now CONNECTING
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.8682] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.8782] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.8845] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:23:30 localhost NetworkManager[2219]: <info>  [1606109010.9065] dhcp4 (eth0): dhclient started with pid 8349
Nov 23 06:24:15 localhost NetworkManager[2219]: <warn>  [1606109055.7138] dhcp4 (eth0): request timed out
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.7149] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.7846] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 8349
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.7853] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.7936] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.8141] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:24:15 localhost NetworkManager[2219]: <warn>  [1606109055.8324] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.8444] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.8985] policy: auto-activating connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.9009] device (eth0): Activation: starting connection 'Wired connection 1' (7ab967fe-0741-36ca-8183-0c391be8c3da)
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.9014] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.9029] manager: NetworkManager state is now CONNECTING
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.9039] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.9062] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.9075] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Nov 23 06:24:15 localhost NetworkManager[2219]: <info>  [1606109055.9132] dhcp4 (eth0): dhclient started with pid 8385
Nov 23 06:25:00 localhost NetworkManager[2219]: <warn>  [1606109100.7141] dhcp4 (eth0): request timed out
Nov 23 06:25:00 localhost NetworkManager[2219]: <info>  [1606109100.7143] dhcp4 (eth0): state changed unknown -> timeout
Nov 23 06:25:00 localhost NetworkManager[2219]: <info>  [1606109100.7307] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 8385
Nov 23 06:25:00 localhost NetworkManager[2219]: <info>  [1606109100.7308] dhcp4 (eth0): state changed timeout -> done
Nov 23 06:25:00 localhost NetworkManager[2219]: <info>  [1606109100.7316] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Nov 23 06:25:00 localhost NetworkManager[2219]: <info>  [1606109100.7333] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 23 06:25:00 localhost NetworkManager[2219]: <warn>  [1606109100.7348] device (eth0): Activation: failed for connection 'Wired connection 1'
Nov 23 06:25:00 localhost NetworkManager[2219]: <info>  [1606109100.7359] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Nov 23 11:17:10 localhost kernel: [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Nov 23 11:17:10 localhost kernel: [    0.000000] Linux version 5.9.6-meson64 (root@xeon) (aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 20191025, GNU ld (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 2.33.1.20191209) #20.08.22 SMP PREEMPT Sun Nov 8 12:50:14 CET 2020
Nov 23 11:17:10 localhost kernel: [    0.000000] Machine model: Hardkernel ODROID-C2

I have a second usb network card (chip ax88179) conected to my C4.

It randomly  crashes and I have to rmmod/modprobe to make it work again : can't be done remotely without network...

Looks like this kind of problem is kernel related : any idea ?

 uname -a
Linux gwm 5.8.16-meson64 #20.08.14 SMP PREEMPT Tue Oct 20 22:50:41 CEST 2020 aarch64 GNU/Linux

[34120.524606] ------------[ cut here ]------------
[34120.524659] NETDEV WATCHDOG: enx002427fe2bf8 (ax88179_178a): transmit queue 0 timed out
[34120.525139] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:442 dev_watchdog+0x300/0x308
[34120.525160] Modules linked in: cpufreq_conservative cpufreq_powersave zstd bridge snd_soc_hdmi_codec dw_hdmi_i2s_audio ftdi_sio ax88179_178a usbnet meson_rng ir_nec_decoder meson_dw_hdmi dw_hdmi snd_soc_meson_g12a_tohdmitx reset_meson_audio_arb snd_soc_meson_codec_glue rc_odroid snd_soc_meson_axg_sound_card meson_saradc snd_soc_meson_card_utils meson_ir rc_core snd_soc_meson_axg_frddr snd_soc_meson_axg_fifo snd_soc_meson_axg_tdmout xt_TCPMSS xt_tcpudp meson_vdec(C) meson_drm v4l2_mem2mem videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 drm_kms_helper videobuf2_common cec videodev mc meson_canvas nft_counter snd_soc_meson_axg_tdm_interface snd_soc_meson_axg_tdm_formatter snd_soc_core ac97_bus display_connector snd_pcm_dmaengine snd_pcm drm snd_timer snd drm_panel_orientation_quirks soundcore ch341 usbserial nft_chain_nat zram xt_mark xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink ip_tables x_tables autofs4 spidev rtc_meson_vrtc meson_gxl
[34120.525999]  realtek dwmac_generic dwmac_meson8b
[34120.526096] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G         C        5.8.16-meson64 #20.08.14
[34120.526119] Hardware name: Hardkernel ODROID-C4 (DT)
[34120.526165] pstate: 20400009 (nzCv daif +PAN -UAO BTYPE=--)
[34120.526212] pc : dev_watchdog+0x300/0x308
[34120.526255] lr : dev_watchdog+0x300/0x308
[34120.526278] sp : ffff800010003d90
[34120.526304] x29: ffff800010003d90 x28: ffff0000f20b8680
[34120.526356] x27: 0000000000000004 x26: 0000000000000140
[34120.526406] x25: 00000000ffffffff x24: 0000000000000000
[34120.526455] x23: ffff0000f22883dc x22: ffff0000f2288000
[34120.526504] x21: ffff0000f2288480 x20: ffff8000126b7000
[34120.526551] x19: 0000000000000000 x18: 0000000000000000
[34120.526598] x17: 0000000000000000 x16: 0000000000000000
[34120.526646] x15: ffff8000126d5000 x14: 656d697420302065
[34120.526695] x13: 756575712074696d x12: 736e617274203a29
[34120.526743] x11: 613837315f393731 x10: 3838786128203866
[34120.526791] x9 : 6232656637323432 x8 : 0000000000000000
[34120.526836] x7 : 0000000000000003 x6 : 00000000000001cd
[34120.526881] x5 : 0000000000000001 x4 : 0000000000000000
[34120.526925] x3 : 0000000000000001 x2 : ffff0000f479a1e8
[34120.526972] x1 : 64ee6f6fb4eeb400 x0 : 0000000000000000
[34120.527017] Call trace:
[34120.527075]  dev_watchdog+0x300/0x308
[34120.527134]  call_timer_fn.isra.0+0x24/0x80
[34120.527186]  run_timer_softirq+0x1a0/0x410
[34120.527229]  efi_header_end+0x120/0x25c
[34120.527273]  irq_exit+0xc0/0xe0
[34120.527316]  __handle_domain_irq+0x68/0xc0
[34120.527362]  gic_handle_irq+0x54/0xa8
[34120.527401]  el1_irq+0xb8/0x180
[34120.527446]  arch_cpu_idle+0x14/0x20
[34120.527487]  do_idle+0x210/0x288
[34120.527527]  cpu_startup_entry+0x28/0x70
[34120.527570]  rest_init+0xd8/0xe8
[34120.527619]  arch_call_rest_init+0x10/0x1c
[34120.527664]  start_kernel+0x4f0/0x528
[34120.527692] ---[ end trace 1ba072349341d5ea ]---

I flashed the image Armbian_20.08.1_Odroidc4_buster_current_5.8.5.img on my new odroid c4 without installing the latest updates (see my other post with no boot anymore after kernel update). After this I started via softy installation of omv5. During installation I wondered why my ssh connection was gone without any output.

During installation there is a reboot of the os and the networking is not coming up anymore. I tried to find out and found:

- armbian uses network manager for networking and the default config file is for dhcp

- after omv5 installation network manager seems to be deinstalled and also there is a new empty config file under /etc/networking (which is not used from network manager)

- so I have to repair this manually via direct access to the shell and after reboot network is ok

I didn't see this behavior on my odroids n2 which I installed some month before.

Should I also post this on openmediavault forum because this shouldn't happen. Seems that there is a mismatch in the salt config when using this armbian version and using installation skript via softy.

Dear community,

unfortunately, "armbianmonitor -u" doesn't give me a link anymore, and I'm not sure if uploading works at all. So I cant provide the information

As our deployment date approaches, we try to finalize our Armbian system for North Pacific seafloor... and found some unexpected problems (problems seem alwas to be unexpected):

The TigerVNC has two problems on Armbian, and it would be great if you could verify that issues and maybe problem some helpful ideas:

(1) TigerVNC (tigervnc-common/stable,now 1.9.0) needs the following workaround to start at all:

LD_PRELOAD=/lib/aarch64-linux-gnu/libgcc_s.so.1 vncserver :1 -localhost no

   Seems to be libunwind8 related, and is ugly, but not the main problem.

(2) TigerVNC can be started by crontab "@reboot", but fails to open a desktop. There are messages about dbus problems, the display closes afterwards.

I use Armbian NEXT, with Debian Buster, and kernel is locked to 4.19.90 (due to the various troubles with the new kernel, which seems to be optimzed for video playback but not stable operation).

Any help is appreciated, and if you need more information, please let me know.

So far, Michael

Hi all,

as a small status update on the seafloor business, here are some pictures of the new Odroid C2 based instruments which will be deployed in September/October in the northers Pacific.

Ten modules with different functionality will be deployed, all based on a standard setup of Odroid C2, TRB3sc FPGA based TDC DAQ system, one PADIWA preamp, and a modded mdedia converter serving as a fully configurable mini switch.

One of the modules carries several Hamamatsu mini spectrometers, as well as a camera, to observe bioluminescence.

Another module is targeting at muon tracking with SiPM based readout:

I have some more picture of the more "fancy" PMT based modules, but don't want to flood this forum now with too many pictures.

To all of you: thanks for the support you gave us over the last year, and the discussions on specific topics!

Deployment pictures will follow once the modules are in place on the seafloor, 2600m deep in the Pacific (and operational, hopefully, this time we just have a GbE fiber, no serial port...)

See you, Michael

With our Current moving to 5.7, anyone building it themselves should report anything missing/new/different/wanted here.

I have an application that depends on the Linux HID USB gadget via configfs on the USB OTG port. It works under Raspberry Pi OS (2020-05-27-buster-lite), but I'm having trouble getting it to work under Armbian (Armbian_20.05.2_Odroidc2_buster_current_5.6.15).

Specifically, I'm having trouble getting the configfs module to run.

What I've done so far:

• Removed the J1 jumper as described on the ODROID wiki.
• Recompiled /boot/dtbs/amlogic/meson-gxbb-odroidc2.dtb to set dr_mode = "peripheral"; as described in this ODROID magazine article.

When I run this script with sudo:

#!/usr/bin/env bash

modprobe libcomposite

cd /sys/kernel/config/usb_gadget/
mkdir -p g1
cd g1

echo 0x1d6b > idVendor  # Linux Foundation
echo 0x0104 > idProduct # Multifunction Composite Gadget
echo 0x0100 > bcdDevice # v1.0.0
echo 0x0200 > bcdUSB    # USB2

STRINGS_DIR="strings/0x409"
mkdir -p "$STRINGS_DIR"
echo "6b65796d696d6570690" > "${STRINGS_DIR}/serialnumber"
echo "Linux Foundation" > "${STRINGS_DIR}/manufacturer"
echo "Generic USB Keyboard" > "${STRINGS_DIR}/product"

FUNCTIONS_DIR="functions/hid.usb0"
mkdir -p "$FUNCTIONS_DIR"
echo 1 > "${FUNCTIONS_DIR}/protocol" # Keyboard
echo 1 > "${FUNCTIONS_DIR}/subclass" # Boot interface subclass
echo 8 > "${FUNCTIONS_DIR}/report_length"
# Write the report descriptor
# Source: https://www.kernel.org/doc/html/latest/usb/gadget_hid.html
echo -ne \\x05\\x01\\x09\\x06\\xa1\\x01\\x05\\x07\\x19\\xe0\\x29\\xe7\\x15\\x00\\x25\\x01\\x75\\x01\\x95\\x08\\x81\\x02\\x95\\x01\\x75\\x08\\x81\\x03\\x95\\x05\\x75\\x01\\x05\\x08\\x19\\x01\\x29\\x05\\x91\\x02\\x95\\x01\\x75\\x03\\x91\\x03\\x95\\x06\\x75\\x08\\x15\\x00\\x25\\x65\\x05\\x07\\x19\\x00\\x29\\x65\\x81\\x00\\xc0 > "${FUNCTIONS_DIR}/report_desc"

CONFIG_INDEX=1
CONFIGS_DIR="configs/c.${CONFIG_INDEX}"
mkdir -p "$CONFIGS_DIR"
echo 250 > "${CONFIGS_DIR}/MaxPower"

CONFIGS_STRINGS_DIR="${CONFIGS_DIR}/strings/0x409"
mkdir -p "$CONFIGS_STRINGS_DIR"
echo "Config ${CONFIG_INDEX}: ECM network" > "${CONFIGS_STRINGS_DIR}/configuration"

ln -s "$FUNCTIONS_DIR" "${CONFIGS_DIR}/"
ls /sys/class/udc > UDC

chmod 777 /dev/hidg0

It fails with on the last line with:

chmod: cannot access '/dev/hidg0': No such file or directory

And /sys/class/udc is not a symlink, as it's expected to be:

$ ls /sys/class/udc -l
total 0

Also, when I run dmesg | grep configfs, I get nothing, whereas on RasPiOS I see a message about dwc2 loading the configfs-gadget.

It there anything else I can do to enable the USB HID gadget on Armbian?

My NanoPiK2 is installed with Armbian Focal desktop system.
When I used it normally for a day, I manually shut it down (closed properly). But when I restarted it, it finally displayed and stayed at

 [OK] Reached target Host and Network Name Lookups.

Unable to enter the system.

I tried to insert the SD card into the computer to search for the boot logs, but I couldn’t find it.

How do i solve this problem？THANKS

Hi,

I have question about ports /dev/ttyAML1 and /dev/ttyAML2 (device Odroid C2, Image Buster)

I dont see in dmesg the ports /dev/ttyAML1 and /dev/ttyAML2

[    0.000256] printk: console [tty1] enabled
[    1.877506] c81004c0.serial: ttyAML0 at MMIO 0xc81004c0 (irq = 13, base_baud = 1500000) is a meson_uart
[    1.877549] printk: console [ttyAML0] enabled
[    3.452296] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    3.455230] systemd[1]: Created slice system-getty.slice.
[    4.257715] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device
 

overlays=i2cA i2cB uartA uartB uartC w1-gpio

How should i chnage the meson-gxbb-odroidc2.dtb to working configuration with kernel 5.4.27-meson64 

This is actual configuration:

            serial@84c0 {
                compatible = "amlogic,meson-gx-uart";
                reg = < 0x00 0x84c0 0x00 0x18 >;
                interrupts = < 0x00 0x1a 0x01 >;
                status = "disabled";
                clocks = < 0x0e 0x03 0x1a 0x0e >;
                clock-names = "xtal\0pclk\0baud";
                pinctrl-0 = < 0x0f >;
                pinctrl-names = "default";
                phandle = < 0x47 >;
            };

With kernel 4.19.69 was working with following change in meson-gxbb-odroidc2.dtb

            serial@84c0 {
                compatible = "amlogic,meson-gx-uart";
                reg = < 0x00 0x84c0 0x00 0x18 >;
                interrupts = < 0x00 0x1a 0x01 >;
                status = "disabled";
                clocks = < 0x0d 0x0b 0x1a 0x0d >;
                clock-names = "xtal\0pclk\0baud";
                pinctrl-names = "default";
                pinctrl-0 = < 0x72 >;
                phandle = < 0x43 >;
            };

Thanks for help

Today I installed packages (apt-get upgrade):

   armbian-config armbian-firmware linux-buster-root-current-odroidc2 linux-dtb-current-meson64 linux-image-current-meson64 linux-u-boot-odroidc2-current

and rebooted the system.

Afterwards no more USB devices were found: Active USB Hub, USB Hd, USB mouse, USB memorystick

Regardless if connected via USB Hub or directly.

lsusb doesn't show any devices.

Any hints?

Thanks in advance