# XU4 HDMI CEC issue

**URL:** <https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971>\
**Category:** Troubleshooting\
**Created:** [11 February 2021 14:49 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971 "2021-02-11T14:49:03Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![doomdog](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/d/87869e/32.png) [@doomdog](https://dietpi.com/forum/u/doomdog)\
**Post date:** [11 February 2021 14:49 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/1 "2021-02-11T14:49:03Z")

</div>

Greetings,

Just installed the latest distribution on my XU4. Everything working except CEC:

root@DietPi:~# uname -a  
Linux DietPi 4.14.180+ #1 SMP PREEMPT Tue Oct 13 13:28:54 UTC 2020 armv7l GNU/Linux  
root@DietPi:~# dmesg | grep cec  
root@DietPi:~# dmesg | grep CEC  
root@DietPi:~# ls -al /dev/cec0  
crw-rw---- 1 root video 249, 0 Feb 11 16:38 /dev/cec0  
root@DietPi:~# cec-client -l  
libCEC version: 4.0.4, compiled on Linux-4.9.0-8-armmp-lpae … , features: P8\_USB, DRM, P8\_detect, randr, Exynos, AOCEC  
Found devices: NONE  
root@DietPi:~# cat /etc/debian\_version  
10.8  
root@DietPi:~# grep cec /boot/boot.ini  
setenv cecenable “true” #this one enabled explicitly by me  
if test “${cecenable}” = “false”; then fdt rm /cec@101B0000; fi  
root@DietPi:~#

Needless to say that a RPi on the same cable works…  
Please help me troubleshoot this, I can do any test required, just tell me.

Thanks!

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [11 February 2021 14:59 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/2 "2021-02-11T14:59:09Z")

</div>

Hi,

I guess this is coming from the kernel if I’m not mistaken. As DietPi is not creating kernel, it might be out of our hand. I found this old forum post on Odroid board [https://forum.odroid.com/viewtopic.php?t=19926](https://forum.odroid.com/viewtopic.php?t=19926) . Looks like it should work

MichaIng  
any ideas

---

<div class="post-metadata">

**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\
**Post date:** [11 February 2021 15:35 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/3 "2021-02-11T15:35:46Z")

</div>

It should work with libcec4 package and Linux 4.14 as well: [https://forum.odroid.com/viewtopic.php?p=255259#p255259](https://forum.odroid.com/viewtopic.php?p=255259#p255259)  
The udev rule is to allow world access, however as you’re using root, permissions are not the issue, also 660 root:video actually are reasonable defaults to me.

Which versions of cec packages are installed, actually?

```nohighlight
apt policy libcec4 cec-utils

```

---

<div class="post-metadata">

**Author:** ![doomdog](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/d/87869e/32.png) [@doomdog](https://dietpi.com/forum/u/doomdog)\
**Post date:** [11 February 2021 15:37 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/4 "2021-02-11T15:37:26Z")

</div>

```nohighlight
root@DietPi:~# dpkg -l | grep cec
ii cec-utils 4.0.4+dfsg1-2 armhf USB CEC Adaptor communication Library (utility programs)
ii libcec4:armhf 4.0.4+dfsg1-2 armhf USB CEC Adaptor communication Library (shared library)

```

```nohighlight
root@DietPi:~# apt policy libcec4 cec-utils
libcec4:
  Installed: 4.0.4+dfsg1-2
  Candidate: 4.0.4+dfsg1-2
  Version table:
 *** 4.0.4+dfsg1-2 500
        500 https://deb.debian.org/debian buster/main armhf Packages
        100 /var/lib/dpkg/status
cec-utils:
  Installed: 4.0.4+dfsg1-2
  Candidate: 4.0.4+dfsg1-2
  Version table:
 *** 4.0.4+dfsg1-2 500
        500 https://deb.debian.org/debian buster/main armhf Packages
        100 /var/lib/dpkg/status

```

Also, libcec doesn’t seem to have been compiled with Linux CEC support:

```nohighlight
root@DietPi:~# cec-client -l
libCEC version: 4.0.4, compiled on Linux-4.9.0-8-armmp-lpae ... , features: P8_USB, DRM, P8_detect, randr, Exynos, AOCEC
Found devices: NONE

```

---

<div class="post-metadata">

**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\
**Post date:** [11 February 2021 17:25 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/5 "2021-02-11T17:25:34Z")

</div>

Ah it’s the package from the Debian repository that is installed on Buster. Meveric compiled that exact version for the Stretch images, not sure if there is any difference, but let’s simply try it out:

```nohighlight
cd /tmp
wget https://dietpi.com/meveric/pool/backports/libc/libcec/cec-utils_4.0.4+dfsg1-2~bpo9_armhf.deb
wget https://dietpi.com/meveric/pool/backports/libc/libcec/libcec4_4.0.4+dfsg1-2~bpo9_armhf.deb
dpkg -i libcec4_4.0.4+dfsg1-2~bpo9_armhf.deb cec-utils_4.0.4+dfsg1-2~bpo9_armhf.deb

```

---

<div class="post-metadata">

**Author:** ![doomdog](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/d/87869e/32.png) [@doomdog](https://dietpi.com/forum/u/doomdog)\
**Post date:** [11 February 2021 21:35 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/6 "2021-02-11T21:35:46Z")

</div>

Nope, unfortunately:

root@DietPi:/tmp# dpkg -i libcec4\_4.0.4+dfsg1-2~bpo9\_armhf.deb cec-utils\_4.0.4+dfsg1-2~bpo9\_armhf.deb  
(Reading database … 22559 files and directories currently installed.)  
Preparing to unpack libcec4\_4.0.4+dfsg1-2~bpo9\_armhf.deb …  
Unpacking libcec4:armhf (4.0.4+dfsg1-2~bpo9) over (4.0.4+dfsg1-2~bpo9) …  
Preparing to unpack cec-utils\_4.0.4+dfsg1-2~bpo9\_armhf.deb …  
Unpacking cec-utils (4.0.4+dfsg1-2~bpo9) over (4.0.4+dfsg1-2~bpo9) …  
Setting up libcec4:armhf (4.0.4+dfsg1-2~bpo9) …  
dpkg: dependency problems prevent configuration of cec-utils:  
cec-utils depends on libncurses5 (\>= 6); however:  
Package libncurses5 is not installed.  
cec-utils depends on libtinfo5 (\>= 6); however:  
Package libtinfo5 is not installed.

dpkg: error processing package cec-utils (–install):  
dependency problems - leaving unconfigured  
Processing triggers for libc-bin (2.28-10) …  
Errors were encountered while processing:  
cec-utils

---

<div class="post-metadata">

**Author:** ![doomdog](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/d/87869e/32.png) [@doomdog](https://dietpi.com/forum/u/doomdog)\
**Post date:** [11 February 2021 21:42 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/7 "2021-02-11T21:42:34Z")

</div>

Only downgrading libcec4 and keeping the distro cec-utils results in:  
root@DietPi:~# cec-client -l  
libCEC version: 4.0.4, compiled on Linux-4.14.107+ … , features: P8\_USB, DRM, P8\_detect, randr, Exynos, Linux, AOCEC  
Found devices: 1

device: 1  
com port: Linux  
vendor id: 0000  
product id: 0000  
firmware version: 0  
type: Linux

But it still doesn’t work:

# scan requesting CEC bus information … CEC bus information

device #1: Recorder 1  
address: 1.0.0.0  
active source: no  
vendor: Pulse Eight  
osd string: CECTester  
CEC version: 1.4  
power status: on  
language: eng  
  
  
currently active source: unknown (-1)  
DEBUG: [23262] \<\< Recorder 1 (1) → TV (0): POLL  
TRAFFIC: [23262] \<\< 10  
ERROR: [23262] CLinuxCECAdapterCommunication::Write - ioctl CEC\_TRANSMIT failed - tx\_status=00 errno=64  
TRAFFIC: [23262] \<\< 10  
ERROR: [23262] CLinuxCECAdapterCommunication::Write - ioctl CEC\_TRANSMIT failed - tx\_status=00 errno=64  
DEBUG: [23262] \>\> POLL not sent  
DEBUG: [23262] \<\< requesting active source  
TRAFFIC: [23262] \<\< 1f:85  
ERROR: [23262] CLinuxCECAdapterCommunication::Write - ioctl CEC\_TRANSMIT failed - tx\_status=00 errno=64  
TRAFFIC: [23262] \<\< 1f:85  
ERROR: [23262] CLinuxCECAdapterCommunication::Write - ioctl CEC\_TRANSMIT failed - tx\_status=00 errno=64  
DEBUG: [23262] \<\< requesting active source  
TRAFFIC: [23262] \<\< 1f:85  
ERROR: [23262] CLinuxCECAdapterCommunication::Write - ioctl CEC\_TRANSMIT failed - tx\_status=00 errno=64  
TRAFFIC: [23262] \<\< 1f:85  
ERROR: [23262] CLinuxCECAdapterCommunication::Write - ioctl CEC\_TRANSMIT failed - tx\_status=00 errno=64  
  
  
I have two other HDMI devices on that bus (including, obviously, the TV itself) but they don’t show up.  
I guess it’s caused by that CEC\_TRANSMIT failed error…

---

<div class="post-metadata">

**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\
**Post date:** [12 February 2021 15:13 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/8 "2021-02-12T15:13:19Z")

</div>

apt install ./path/to/package.deb can be used to have dependencies automatically installed.  
It’s not a downgrade, both are version 4.0.4+dfsg1-2, but it’s a different build, probably with other build options or even patches, not sure. I’ll ask Meveric if we get it running.

Not sure whether libcec4 A works with cec-utils B. Could you retry after installing it as well:

```nohighlight
cd /tmp
wget https://dietpi.com/meveric/pool/backports/libc/libcec/cec-utils_4.0.4+dfsg1-2~bpo9_armhf.deb
apt install ./cec-utils_4.0.4+dfsg1-2~bpo9_armhf.deb

```

---

<div class="post-metadata">

**Author:** ![doomdog](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/d/87869e/32.png) [@doomdog](https://dietpi.com/forum/u/doomdog)\
**Post date:** [12 February 2021 23:15 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/9 "2021-02-12T23:15:12Z")

</div>

I did install both libcec4 and cec-utils from the links you specified, using apt install.  
I am still not getting anything in dmesg regarding CEC and cec-client behaves exactly the same, i.e. not transmitting anything.

# CEC bus information

device #1: Recorder 1  
address: 1.0.0.0  
active source: no  
vendor: Pulse Eight  
osd string: CECTester  
CEC version: 1.4  
power status: on  
language: eng  
  
  
currently active source: unknown (-1)  
DEBUG: [14682] \<\< requesting active source  
TRAFFIC: [14682] \<\< 1f:85  
ERROR: [14682] CLinuxCECAdapterCommunication::Write - ioctl CEC\_TRANSMIT failed - tx\_status=00 errno=64  
TRAFFIC: [14682] \<\< 1f:85  
ERROR: [14682] CLinuxCECAdapterCommunication::Write - ioctl CEC\_TRANSMIT failed - tx\_status=00 errno=64  
  
  
I have tested this on 3 (yes, three, don’t ask me why I got so many XU4s 😉 ) different Odroids, and the result is the same.  
I’m now calculating the probability of 3 broken CEC Odroids ending up in my possession…

---

<div class="post-metadata">

**Author:** ![doomdog](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/d/87869e/32.png) [@doomdog](https://dietpi.com/forum/u/doomdog)\
**Post date:** [13 February 2021 00:46 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/10 "2021-02-13T00:46:03Z")

</div>

I’ve now broken down and started trying random images to test CEC and get to the bottom of this.  
I’ve collected and tested these:

Debian-Jessie-1.1.4-20171121-XU3+XU4.img.xz  
Debian-Stretch-1.0\_RC2-20180403-XU3-XU4.img.xz  
ubuntu-18.04.3-4.14-minimal-odroid-xu4-20190910.img.xz  
ubuntu-20.04-5.4-minimal-odroid-xu4-20210112.img.xz  
and, obviously, the latest DietPi.

The only one that has a working CEC (on all 3 XU4s, no less) is Debian Jessie.  
The problem with that one is it’s old and doesn’t offer an easy way to run a new(ish) Kodi.  
Which is why I was putting so much hope in DietPi, with its very nice software and configuration programs.  
Basically, all I want is to have an (easily kept) updated Kodi with a few extras (transmission, samba) on a fast USB3+gigabit XU4, as I grew tired of the Raspberries’ shared USB limitations…

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [13 February 2021 08:57 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/11 "2021-02-13T08:57:42Z")

</div>

Best to my knowledge, on a RPi4 the ethernet interface is not shared anymore and a real gigabit one.

---

<div class="post-metadata">

**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\
**Post date:** [13 February 2021 17:42 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/12 "2021-02-13T17:42:46Z")

</div>

Since the two packages were compiled on/for Stretch, probably some other libraries not not match, causing the issue. I asked Meveric if those were patched or compiled with options different from the regular Debian repo packages, to work with Odroids. If so, we’d need to compile own Odroid-ready packages for Debian Buster.

---

<div class="post-metadata">

**Author:** ![doomdog](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/d/87869e/32.png) [@doomdog](https://dietpi.com/forum/u/doomdog)\
**Post date:** [13 February 2021 21:41 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/13 "2021-02-13T21:41:00Z")

</div>

I’ve compiled the latest libcec6 (which is already patched for kernel CEC framework) directly on the latest DietPi.  
It also throws the same transmit errors as in my previous logs.  
Also, dmesg does not show anything CEC-related, even though the kernel has the support (I checked in /proc/config.gz) and boot.ini has CEC enabled explicitly. It’s almost like the CEC hardware is not there when the system boots. Something is really messing with 4.x kernels on the XU4…

---

<div class="post-metadata">

**Author:** ![tardistardat](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/t/9fc29f/32.png) [@tardistardat](https://dietpi.com/forum/u/tardistardat)\
**Post date:** [20 February 2021 09:32 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/14 "2021-02-20T09:32:30Z")

</div>

I’m having the same issue. Switched from Ubuntu 20.04 LTS to DietPI, because I could not get cec working.  
I have never seen or used cec, so I don’t exactly know what to look for in dmesg. The following returns nothing:

```plaintext
root@DietPi:~# dmesg | grep -i cec

```

Kernel config:

```plaintext
root@DietPi:~# zgrep -i cec /proc/config.gz 
CONFIG_TABLET_USB_ACECAD=m
CONFIG_CEC_CORE=y
CONFIG_CEC_NOTIFIER=y
CONFIG_MEDIA_CEC_SUPPORT=y
# CONFIG_MEDIA_CEC_RC is not set
# USB HDMI CEC adapters
# CONFIG_USB_PULSE8_CEC is not set
# CONFIG_USB_RAINSHADOW_CEC is not set
# CONFIG_VIDEO_VIVID_CEC is not set
CONFIG_CEC_PLATFORM_DRIVERS=y
CONFIG_VIDEO_SAMSUNG_S5P_CEC=y

```

Since we’re debugging, it does not hurt to list what does kernel parameters do. Will include only CEC related parameters:  
CONFIG\_CEC\_CORE=y - [Linux Kernel Driver DataBase: CONFIG\_CEC\_CORE:](https://cateee.net/lkddb/web-lkddb/CEC_CORE.html)  
CONFIG\_CEC\_NOTIFIER=y - [Linux Kernel Driver DataBase: CONFIG\_CEC\_NOTIFIER:](https://cateee.net/lkddb/web-lkddb/CEC_NOTIFIER.html)  
CONFIG\_MEDIA\_CEC\_SUPPORT=y - [Linux Kernel Driver DataBase: CONFIG\_MEDIA\_CEC\_SUPPORT: HDMI CEC drivers](https://cateee.net/lkddb/web-lkddb/MEDIA_CEC_SUPPORT.html)

# CONFIG\_MEDIA\_CEC\_RC is not set - [Linux Kernel Driver DataBase: CONFIG\_MEDIA\_CEC\_RC: HDMI CEC RC integration](https://cateee.net/lkddb/web-lkddb/MEDIA_CEC_RC.html) \<\<-this looks like a potential problem

# CONFIG\_USB\_PULSE8\_CEC is not set - [Linux Kernel Driver DataBase: CONFIG\_USB\_PULSE8\_CEC: Pulse Eight HDMI CEC](https://cateee.net/lkddb/web-lkddb/USB_PULSE8_CEC.html)

# CONFIG\_USB\_RAINSHADOW\_CEC is not set - [Linux Kernel Driver DataBase: CONFIG\_USB\_RAINSHADOW\_CEC: RainShadow Tech HDMI CEC](https://cateee.net/lkddb/web-lkddb/USB_RAINSHADOW_CEC.html)

# CONFIG\_VIDEO\_VIVID\_CEC is not set - [Linux Kernel Driver DataBase: CONFIG\_VIDEO\_VIVID\_CEC: Enable CEC emulation support](https://cateee.net/lkddb/web-lkddb/VIDEO_VIVID_CEC.html)

CONFIG\_CEC\_PLATFORM\_DRIVERS=y - [Linux Kernel Driver DataBase: CONFIG\_CEC\_PLATFORM\_DRIVERS: CEC platform devices](https://cateee.net/lkddb/web-lkddb/CEC_PLATFORM_DRIVERS.html)  
CONFIG\_VIDEO\_SAMSUNG\_S5P\_CEC=y - [Linux Kernel Driver DataBase: CONFIG\_VIDEO\_SAMSUNG\_S5P\_CEC: Samsung S5P CEC driver](https://cateee.net/lkddb/web-lkddb/VIDEO_SAMSUNG_S5P_CEC.html)

From [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868511](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868511) we learn that CEC was included in the mainline kernel starting from 4.10.

So, DietPI kernel is not “far” from when CEC support was included in the kernel:

```plaintext
root@DietPi:~# uname -a
Linux DietPi 4.14.180+ #1 SMP PREEMPT Tue Oct 13 13:28:54 UTC 2020 armv7l GNU/Linux

```

---

<div class="post-metadata">

**Author:** ![tardistardat](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/t/9fc29f/32.png) [@tardistardat](https://dietpi.com/forum/u/tardistardat)\
**Post date:** [20 February 2021 09:38 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/15 "2021-02-20T09:38:21Z")

</div>

Found this debian bug report, seems to be still open: [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872650](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872650)

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [20 February 2021 10:01 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/16 "2021-02-20T10:01:36Z")

</div>

> So, DietPI kernel is not “far” from when CEC support was included in the kernel:

just to avoid a misunderstanding. DietPi is not creating any kernel. The kernel is provided by the base image used. DietPi is not an own OS, it is a set of scripts on top of a Debian based destro/image. The image used depends on the SBC you are using. It could be a Raspberry OS, Armbian, plain Debian or Meveric image.

---

<div class="post-metadata">

**Author:** ![tardistardat](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/t/9fc29f/32.png) [@tardistardat](https://dietpi.com/forum/u/tardistardat)\
**Post date:** [20 February 2021 12:52 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/17 "2021-02-20T12:52:28Z")

</div>

> [@](#):
>
> > So, DietPI kernel is not “far” from when CEC support was included in the kernel:
> 
> […]  
> The kernel is provided by the base image used.  
> […]  
> The image used depends on the SBC you are using. It could be a Raspberry OS, Armbian, plain Debian or Meveric image.

How do I check / know which base image was used? It’s not specified on the download page [DietPi - Lightweight justice for your SBC!](https://dietpi.com/#download)

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [20 February 2021 13:08 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/18 "2021-02-20T13:08:42Z")

</div>

usually it’s part of the header once you login

```nohighlight
 ─────────────────────────────────────────────────────
 DietPi v6.34.3 : 26 APT updates available
 ─────────────────────────────────────────────────────
 - Device model : RPi 4 Model B (armv7l)
 - Uptime : up 3 days, 15 hours, 8 minutes
 - CPU temp : 41'C : 105'F (Optimal temperature)
 - LAN IP : 192.168.0.11 (eth0)
 - Info Text : !!! PRODUCTION SYSTEM !!!
 ─────────────────────────────────────────────────────

 DietPi Team : MichaIng (lead), Daniel Knight (founder), Joulinar (support)
 Image : DietPi Core Team (pre-image: Raspbian Lite)
 Web : https://dietpi.com | https://twitter.com/DietPi_
 Donate : https://dietpi.com/#donate
 DietPi Hosting : Powered by https://myvirtualserver.com

 apt upgrade : Run now to apply 26 available APT package upgrades.

root@DietPiProd:~#

```

In my case it’s RPi OS  
Image : DietPi Core Team (pre-image: Raspbian Lite)

---

<div class="post-metadata">

**Author:** ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)\
**Post date:** [20 February 2021 13:15 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/19 "2021-02-20T13:15:57Z")

</div>

Yeah, “Meveric” is probably a bit short. For Odroids we use Meveric’s images/kernel repository:

- [https://forum.odroid.com/viewtopic.php?t=30552](https://forum.odroid.com/viewtopic.php?t=30552)
- [https://dietpi.com/meveric/](https://dietpi.com/meveric/)

I already forwarded the CEC topic to him and he’s testing it on Debian Buster. The libcec packages from the Debian Buster repositories have Exynos CEC support enabled by default, so likely it’s related to the kernel indeed.

Debian bug reports are likely not helpful here, since it’s not the Debian kernel but Hardkernel’s (Odroid SBC manufacturer) kernel sources, built and packaged by Meveric. But interesting to learn about the options, many thanks for sharing 🙂.

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [20 February 2021 13:17 UTC](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971/20 "2021-02-20T13:17:57Z")

</div>

MichaIng  
Maybe we should create an overview of SBC and show the used base image? Just thinking 🤔

[Next page](https://dietpi.com/forum/t/xu4-hdmi-cec-issue/4971.md?page=2)
