no WiFi Adapter after fresh installation. usbcore.autosuspend=-1 fixes it:

  ___      _           _     _    ____ ____  
 / _ \  __| |_ __ ___ (_) __| |  / ___|___ \ 
| | | |/ _` | '__/ _ \| |/ _` | | |     __) |
| |_| | (_| | | | (_) | | (_| | | |___ / __/ 
 \___/ \__,_|_|  \___/|_|\__,_|  \____|_____|
                                             
Welcome to Armbian 24.2.1 Bookworm with Linux 6.6.16-current-meson64

System load:   46%           	Up time:       0 min	
Memory usage:  7% of 1.82G  	IP:	       192.168.25.252
CPU temp:      28°C           	Usage of /:    66% of 3.0G   	

[ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ]

root@odroid:~# cat /boot/armbianEnv.txt 
verbosity=1
console=both
overlay_prefix=meson
rootdev=UUID=1cf10f1a-aa21-4ff0-875d-c59f57c87173
rootfstype=ext4
extraboardargs=fastboot noswap isolcpus=3 usbcore.autosuspend=-1
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

root@odroid:~# lsusb 
Bus 001 Device 007: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 006: ID 7392:7822 Edimax Technology Co., Ltd EW-7612UAn V2 802.11n Wireless Adapter [Realtek RTL8192CU]
Bus 001 Device 005: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Please check when possible.

Thanks in advance,

pbg

i2cdetect -y 0 is seeing the device ID (0x51)  and I have added module rtc-pcf8563 but no joy.  HWCLOCK does not see the device.

Any help would be appreciated.

Scott

I downloaded the Armbian image from here and followed the official install instructions, but the C2 refuses to boot. The red light turns on when powered but nothing more happens, no other lights, no screen, nothing. Coreelec was booting with no issue, so it must be something I'm setting wrong.

Just in case I tried a different SD card and two different images, Bookworm minimal (the one I'm interested in) and Ubuntu Noble XFCE (just to test). Same result. Once I boot I let the C2 on for some minuts, as per the inatructions, no change at all. I am also using usbimager, again as per instructions.

Anyone has any idea what I could try to see if I can boot Armbian in my C2?

Setup

• Yocto branch: Kirkstone (honister back-ports disabled)
• Layers / commits
  • meta-odroid 06f8d2c (last week’s master)
  • poky kirkstone (bitbake 2.2.0)
• Kernel: linux = v5.15 

What I changed so far

Enabled the driver
Added a linux-hardkernel_%.bbappend with:
 

CONFIG_PWM=y
CONFIG_PWM_MESON=y

Patched the Device Tree (added a new layer to patch in yocto using devtool):

From 9f296f4b8f636b12ef8c0a4720cf0d25d9eeb810 Mon Sep 17 00:00:00 2001
From: OpenEmbedded <oe.patch@oe>
Date: Thu, 17 Jul 2025 15:50:18 -0400
Subject: [PATCH] some changes to source for pwm

---
 arch/arm64/boot/dts/amlogic/meson-gx.dtsi          |  2 +-
 .../arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 14 ++++++++++++++
 2 files changed, 15 insertions(+), 1 deletion(-)

diff --git a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
index 32cc9fab4490..f7abfd4746d2 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
+++ b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
@@ -330,7 +330,7 @@ pwm_ab: pwm@8550 {
  compatible = "amlogic,meson-gx-pwm", "amlogic,meson-gxbb-pwm";
  reg = <0x0 0x08550 0x0 0x10>;
  #pwm-cells = <3>;
- status = "disabled";
+ status = "okay";
  };
 
  pwm_cd: pwm@8650 {
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
index 201596247fd9..0f5e52e7096c 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
@@ -416,3 +416,17 @@ &usb0 {
 &usb1 {
  status = "okay";
 };
+
+&pwm_ab {
+  status = "okay";
+  pinctrl-names = "default";
+  pinctrl-0     = <&pwm_a_x_pins>;
+};
+
+&pinctrl {
+   pwm_a_x_pins: pwm_a_x {
+        groups    = "pwm_a_x";
+        functions = "pwm_a_x";
+        bias-pull-disable;
+   };
+};

Symptoms

modprobe pwm-meson dosen't loads, nothing in dmesg. But the file are here : 

root@odroid-c2:~# dmesg | grep pwm                                                                                                   
root@odroid-c2:~# ls /sys/class/pwm*
pwmchip0
root@odroid-c2:~# ls /sys/class/pwm/pwmchip0/
device     export     npwm       power      subsystem  uevent     unexport
root@odroid-c2:~# modprobe pwm-meson 
root@odroid-c2:~# dmesg | grep pwm
root@odroid-c2:~# ls /sys/class/pwm/pwmchip0/
device     export     npwm       power      subsystem  uevent     unexport
root@odroid-c2:~# echo 0 > /sys/class/pwm/pwmchip0/export 
root@odroid-c2:~# ls /sys/class/pwm/pwmchip0/pwm0/
capture     duty_cycle  enable      period      polarity    power       uevent

/sys entries:

/sys/class/pwm/pwmchip0/ 
	├── export 
 	├── npwm
	├── device    
	├── power      
	├── subsystem
	├── uevent     	
	├── unexport
	└── pwm0/ 
		├── freq0 
		├── duty0  
		└── enable0

I run (root):

root@odroid-c2:~# echo 20000000 > /sys/class/pwm/pwmchip0/pwm0/period         
root@odroid-c2:~# echo 1500000 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle         
root@odroid-c2:~# echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable

but nothing happen.

Questions

• Has anyone successfully driven hardware PWM on the C2 with current meta-odroid + Kirkstone?
• Any known quirks with the pinctrl or the pwm-meson driver on kernels ≥ 5.15?
• Sample DTS snippet or working .bbappend would be greatly appreciated!

Thanks in advance.

Krum

I also tested kernel 6.12.13 from debian minimal image, same problem:

Applying kernel provided DT fixup script (meson-fixup.scr)
## Executing script at 32000000
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    17076402 Bytes = 16.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 04080000
   Booting using the fdt blob at 0x4080000
   Loading Ramdisk to 7af01000, end 7bf4a0b2 ... OK
   Loading Device Tree to 000000007ae8e000, end 000000007af00fff ... OK
"Synchronous Abort" handler, esr 0x96000004
elr: 000000000105d0b8 lr : 000000000104cdd0 (reloc)
elr: 000000007dfb90b8 lr : 000000007dfa8dd0
x0 : fbbfe1e3d45df41f x1 : 000000007dfc0438
x2 : 0000000000000010 x3 : 000000007bfa3830
x4 : 0000000000000000 x5 : fbbfe1e3d45df41f
x6 : 0000000001000000 x7 : 0000000000000000
x8 : 0000000000000007 x9 : 0000000000000000
x10: 00000000000001dc x11: 000000007bf4e34c
x12: 00000000000000b0 x13: 000000007bf4e308
x14: 000000007ae8e000 x15: 0000000000000020
x16: 000000007df8f8a8 x17: 0000000000000000
x18: 000000007bf59dd0 x19: 000000007af4f040
x20: 000000007df5cb18 x21: 000000007dfc0438
x22: 0000000000001000 x23: 000000007bf613d0
x24: 000000007dfdd638 x25: 0000000001000000
x26: 0000000000000000 x27: 0000000001000000
x28: 0000000000001000 x29: 000000007bf4e300

Code: eb04005f 54000061 52800000 14000006 (386468a3) 
Resetting CPU ...

I have no idea. Can someone verify?

So for the moment I do not recommend updating to latest 6.12 kernel on Odroid C2.

Installed Armbian_25.2.3_Odroidhc4_bookworm_current_6.12.17-homeassistant_minimal.img
an a HC4 and noticed that USB doesn't work.

lshw shows:

  *-usbhost:0
       product: xHCI Host Controller
       vendor: Linux 6.12.17-current-meson64 xhci-hcd
       physical id: 1
       bus info: usb@1
       logical name: usb1
       version: 6.12
       capabilities: usb-2.00
       configuration: driver=hub slots=2 speed=480Mbit/s
  *-usbhost:1
       product: xHCI Host Controller
       vendor: Linux 6.12.17-current-meson64 xhci-hcd
       physical id: 2
       bus info: usb@2
       logical name: usb2
       version: 6.12
       capabilities: usb-3.00
       configuration: driver=hub slots=1 speed=5000Mbit/s

Nothing in syslog when I connect anything to USB port, just once I saw this:
  kernel: [ 2113.840333] usb usb1-port2: connect-debounce failed

Any idea what could be wrong?

Thanks
Chris

Seems like headers are missing xtables-addons.

During system update it failed and after reboot it stuck. After manualy fixing symlinks for images it booted up, but i couldn't manage to make xt_geoip working again. Tried removing headers and installing them again with armbian-config but still the same

wtminicom.log

after upgrading the Odroid C2 to the current Version on 16.08.2024 the USB-devices do not work at all.

According to the diagnosis information they are recognized during during bootup. But later they are disconnected for an unknown reason.

https://paste.armbian.com/jucovipaxo

lsusb only lists two devices:

Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 

The suggested hack "usbcore.autosuspend=-1" for USB-problems is already activated, but USB doesn't work anyway

Maybe there is a solution for this strange behavior of my C2.

I'm curious, is there any qualitative difference between the dedicated application images and the Minimal image followed by a "normal" manual installation of the given application? For example OpenMediaVault (OMV) which comes with tailored installation instructions for Armbian. IOW, does the dedicated application image "only " take care of the OMV installation for you, or is there more to it which I might miss when installing OMV myself (on top of the minimal image)?

Thanks!

Armbian_24.11.1_Odroidhc4_bookworm_current_6.6.60_minimal.img

Armbian_24.11.1_Odroidhc4_noble_current_6.6.60-kisak.img

Installed those linux-headers:

apt install linux-headers-current-meson64

I tried then to install ZFS module, and it failed:

Setting up zfs-dkms (2.2.5-1~bpo12+1) ...

Loading new zfs-2.2.5 DKMS files...

Building for 6.6.60-current-meson64

Module build for kernel 6.6.60-current-meson64 was skipped since the

kernel headers for this kernel do not seem to be installed.

root@odroidhc4:~# dpkg -l | grep linux-headers

ii linux-headers-current-meson64 24.8.2 arm64 Armbian Linux current headers 6.6.47-current-meson64

The

Armbian_24.8.1_Odroidhc4_bookworm_current_6.6.47_minimal.img

is OK.

Finally I see both SSDs and ZFS works! 🙂

Regards,

Chris

https://wiki.odroid.com/odroid-xu4/application_note/software/headless_setup?s[]=headless#change_resolution_in_xorgconf

I'm guessing the device is different?...

Also what wold be the rest of the xorg.conf settings? The wiki page only shows the part that should be modified.

Thanks.

After I upgraded my ssd install from 23.11.1 to 24.2.1, the board didn't boot.

When starting 24.2.1 from a fresh sd card, usb and disk leds are on, and the board boots. But they don't show in lsusb.

If I reconnect them after the board is booted, the leds stay off (and obviously they don't show in lsusb).

Of course, booting from external ssd stops at some point, because usb is lost during the boot (when connecting a display, the failures start to happen on armbian services).

Had to restore previous release 23.11.1 from backup on my ssd. Everything works again.

hy guys

is it possible to boot the odroid c2 from usb? so i can connect a ssd (M.2 SATA) via usb connector and use this.

thank you

I'm a beginner with all that kernel and modules stuff, so please be kind, if I am asking stupid questions.

My plan is to install a Hifi-Shield on my C2, but so far had no luck:

modprobe: FATAL: Module snd_soc_pcm512x not found in directory /lib/modules/

Found out, that some modules are present under /lib...

e.g.

/lib/modules/5.15.0-105-generic/kernel/sound/soc/codecs/snd-soc-pcm512x.ko (cave:this is example from my ubuntu I'm writing on)

some other modules are in fact missing.

I found similar modules here:

https://github.com/3isenHeiM/HiFi-Shield-Plus/blob/master/sound/soc/aml/m8/snd-soc-odroid-dac.ko

Is it possible to integrate those modules in actual kernel environment and what do I have to do to make them activated (I think, that is what modprobe does!?)

Regards 3MF

I regularly update the C2 I wonder if a recent update has affected the USB port functioning? Any way to troubleshoot?  I tried a few USB flash drives and then lsusb but none are seen.

I tried to retasrt my system, but it doesn't work.

Before i post my question i found this thread:

i can't find a solution in the thread. Does anybody knows, how he fixed it?

I need to restart the system.
Can i disable the user login to the beginn? i need to start without a login choice.

Thank you

Why this doesn't work? My actual problem is that Jack Audio can't use real-time scheduling, but this example should demonstrate that there is a general problem probably. (getting  ERROR: Cannot use real-time scheduling (RR/10) (1: Operation not permitted), ERROR: AcquireSelfRealTime error)

$ uname -a
Linux odroidc2 6.6.16-current-meson64 #1 SMP PREEMPT Mon Feb  5 20:14:39 UTC 2024 aarch64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Armbian 24.2.1 bookworm
Release:        12
Codename:       bookworm

I tried to migrate my odroid C2 form corelec to armbiam bookworm 6.1.6.63... but i'm having some problems with network... i need to fix on switch the limit bandwith at 100mb/s even impossible to have network... 

When it's ok, if i tried to force config with ethtool (network freezes everytime)... and in every case, after some hours.. the network freeze..

So i'm looking for an armbian with a good stability and not too old..

Regards, 

Hi,

I downloaded the jammy xfce image for ODROID C2 today:

MD5SUM

033fbc0babb56db5388b4c707a2fc0ce  Armbian_23.11.1_Odroidc2_jammy_current_6.1.63_xfce_desktop.img.xz

After flashing it onto my SD card with xzcat and dd, I tried to boot with my Odroid C2 ending up with this error message:

ALERT! UUID=75e23441-f5ee-4479-a484-7060ccd898ae does not exist.

So I put the SD back into my PC and checked with gparted: the UUID of the partition that I have on my SD card seems to have exactly the UUID that was not found.

In fact the boot until that error message lastet quite long, so I expect that the timeout is not too small.

Does anyone have an idea?

Thanks!
 

So I found out the hard way that neither jammy nor bullseye builds for odroid c2 actually allow ssh at first boot

My board is headless, but has a wired connection to my lan and always gets assigned the same address. Which file or files do I need to edit to ssh into it without having to do initial setup first, please?

odroidc2 with Armbian 23.02 Jammy XFCE (Armbian_23.02.1_Odroidc2_jammy_current_6.1.14_xfce_desktop.img)

I have an odroidc2 connected to:

1)monitor with built-in speakers via hdmi cable.

2)usb audio adapter (https://ameridroid.com/products/usb-audio-adapter)

3)ethernet cable

4)wireless keyboard dongle

I have issue outputting audio to monitor speaker.

dmesg and syslog output related to hdmi is as follows. Any help is greatly appreciated.

Thanks
 

$ dmesg|grep hdmi
[    0.035220] platform c883a000.hdmi-tx: Fixing up cyclic dependency with d0100000.vpu
[    0.037586] platform hdmi-connector: Fixing up cyclic dependency with c883a000.hdmi-tx
[    1.614016] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
[    1.614532] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver
[    1.614805] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops)


$ sudo cat /var/log/syslog |grep -i hdmi
Apr 25 00:44:37 odroidc2 kernel: [    0.035292] platform c883a000.hdmi-tx: Fixing up cyclic dependency with d0100000.vpu
Apr 25 00:44:37 odroidc2 kernel: [    0.037662] platform hdmi-connector: Fixing up cyclic dependency with c883a000.hdmi-tx
Apr 25 00:44:37 odroidc2 kernel: [    1.614019] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
Apr 25 00:44:37 odroidc2 kernel: [    1.614545] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver
Apr 25 00:44:37 odroidc2 kernel: [    1.614825] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops)
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:5 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:5 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:9 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:9 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:13 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:13 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:16 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:16 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:20 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:20 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:23 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:23 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:26 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:26 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:34 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:39 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:39 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:47 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:47 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:51 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:51 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:55 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:55 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:59 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:59 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:64 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:64 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:68 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:68 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:71 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:71 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:71 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:75 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:75 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:78 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:78 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:81 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:81 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:87 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:87 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:87 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:90 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:90 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:93 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:93 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:93 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:95 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:95 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:104 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:108 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:113 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
<repeated similar lines>
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:409 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 systemd-udevd[801]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:409 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 00:57:50 odroidc2 kernel: [    0.035295] platform c883a000.hdmi-tx: Fixing up cyclic dependency with d0100000.vpu
Apr 25 00:57:50 odroidc2 kernel: [    0.037650] platform hdmi-connector: Fixing up cyclic dependency with c883a000.hdmi-tx
Apr 25 00:57:50 odroidc2 kernel: [    1.613986] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
Apr 25 00:57:50 odroidc2 kernel: [    1.614507] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver
Apr 25 00:57:50 odroidc2 kernel: [    1.614777] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops)
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:5 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:5 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:9 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:9 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:13 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:13 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:16 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:16 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:20 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:20 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:23 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:23 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:26 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:26 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:34 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:39 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:39 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:47 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:47 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:51 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:51 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:55 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:55 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:59 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:59 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:64 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:64 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
<repeated similar lines>
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:93 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 kernel: [    0.035220] platform c883a000.hdmi-tx: Fixing up cyclic dependency with d0100000.vpu
Apr 25 01:50:25 odroidc2 kernel: [    0.037586] platform hdmi-connector: Fixing up cyclic dependency with c883a000.hdmi-tx
Apr 25 01:50:25 odroidc2 kernel: [    1.614016] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
Apr 25 01:50:25 odroidc2 kernel: [    1.614532] meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver
Apr 25 01:50:25 odroidc2 kernel: [    1.614805] meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops)
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:93 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:95 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: message repeated 2 times: [ /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:95 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.]
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:104 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
Apr 25 01:50:25 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:108 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.
<repeated similar lines>
Apr 25 01:50:26 odroidc2 systemd-udevd[802]: /usr/lib/udev/rules.d/60-hdmi2usb-udev.rules:409 ENV key takes '==', '!=', '=', or '+=' operator, assuming '='.

When viewing youtube containing word composed of non-latin characters, it shows a funny symbol for each character.

How do I install the proper language for this?

The odroid-c2 is connected to an HDMI monitor with speakers

I've been manipulating the settings for Pulseaudio and I could not get the audio to output to the monitor speakers. I could hear audio from the USB to audio jack connected to headphones

have available an 16gb hardkernel emmc card on which I had ubuntu 20.04 installed and running. 

But by burning the image with etcher (the same procedure as with the SD image) the odroid is unable to boot. Black screen, solid red led, and nothing else. I waited more than 30 seconds, I tried to disconnect keyboard....I waited more than 30 seconds, I tried to disconnect keyboard

I have repeated the procedure through the SD and it works correctly. When I do it through the emmc, the system does not boot. When I use the SD card, the Emmc card is obviously disconnected, and when I use the emmc, the sd card is disconnected.

I think u-boot has something to do with it

https://redirect.armbian.com/region/EU/odroidc2/Jammy_current_minimal

I apologize to the people mentioned above. I've read the forum a lot and thought they were the right people to respond to. @Igor

Hello all!

I have an ODROID-C2 that I am trying to use with a GPS connected over UART for timing purposes, which requires the use of pps. Based on my searching and reading in this forum, I have determined that for my OS and kernel (Focal, 5.9.14) I should be able to do so by adding overlay=pps-gpio to armbianEnv.txt. What is not clear to me, however, is how to specify which pin to use! 

In this thread I see windysea said:

Quote

Optionally param_pps_* may be used to configure, such as pin.

But I don't know how to use this information! I have found no documentation on param_pps_*, and my attempts at guessing based on information from other threads and resources have failed to work so far. I have been fiddling with this for a few days to no avail now, so any assistance would be greatly appreciated.

Regards,

John