Slackware - ARM This forum is for the discussion of Slackware ARM. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
03-26-2024, 08:57 PM
|
#1
|
Member
Registered: Jul 2007
Posts: 762
|
How do I enable CEC on RPi4b?
This may be not entirely Slackware on Aarch64 related, but people here might know.
I want to play with controlling the computer with a TV remote, and it is supposed to be done with the CEC protocol.
It is known that RPi supports CEC, but how do I enable it?
https://www.linuxuprising.com/2019/0...connected.html
Code:
echo 'scan' | cec-client -s -d 1
autodetect FAILED
Code:
cec-ctl -l
Failed to open /dev/cec0: No such file or directory
but,
Code:
raspinfo | grep cec
hdmi_force_cec_address:0=65535
hdmi_force_cec_address:1=65535
So it does know that such a thing as cec exists.
Last edited by Lockywolf; 03-28-2024 at 12:11 AM.
Reason: mark solved
|
|
|
03-27-2024, 01:28 AM
|
#2
|
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 24,200
|
no, rpi itself does not support it, you need to install some software. For example if you use kodi it will automatically detect it and use it, so you will be able to use kodi with your tv remote (without any additional configuration). What do you want to control with your remote?
|
|
1 members found this post helpful.
|
03-28-2024, 12:01 AM
|
#3
|
Member
Registered: Jul 2007
Posts: 762
Original Poster
|
I figured it out.
CEC does not work with dtoverlay dtoverlay=vc4-fkms-v3d-pi4,cma=512, but it does work with dtoverlay=vc4-kms-v3d-pi4,cma=512.
I need to try and see how other features work on it.
|
|
1 members found this post helpful.
|
04-08-2024, 06:40 AM
|
#4
|
Member
Registered: May 2020
Posts: 48
Rep: 
|
Quote:
Originally Posted by pan64
For example if you use kodi it will automatically detect it and use it, so you will be able to use kodi with your tv remote (without any additional configuration).
|
How did you do this? I compiled Kodi, but it does not show CEC adapter
despite of it has been compiled in, see my post https://www.linuxquestions.org/quest...er-4175735804/
.
Quote:
Originally Posted by Lockywolf
I figured it out.
CEC does not work with dtoverlay dtoverlay=vc4-fkms-v3d-pi4,cma=512, but it does work with dtoverlay=vc4-kms-v3d-pi4,cma=512.
I need to try and see how other features work on it.
|
One year ago I posted https://www.linuxquestions.org/quest...6/#post6419247
In this post I described turning your television on and off using cec-ctl. For me cec-ctl -m still doesn't give output when pressing buttons on my remote control of my television.
|
|
|
04-08-2024, 08:43 AM
|
#5
|
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 24,200
|
Quote:
Originally Posted by Johpin
How did you do this?
|
Code:
pan@pi4:~ $ cec-ctl -l
Driver Info:
Driver Name : vc4_hdmi
Adapter Name : vc4-hdmi-0
Capabilities : 0x0000011e
Logical Addresses
Transmit
Passthrough
Remote Control Support
Connector Info
Driver version : 6.6.20
Available Logical Addresses: 1
DRM Connector Info : card 1, connector 32
Physical Address : 3.0.0.0
Logical Address Mask : 0x0000
CEC Version : 2.0
OSD Name : ''
Logical Addresses : 0
but you need to see the device without kodi too
Code:
pan@pi4:~ $ ls -l /dev/cec*
crw-rw---- 1 root video 240, 0 Apr 5 17:59 /dev/cec0
crw-rw---- 1 root video 240, 1 Apr 5 17:59 /dev/cec1
it is detected automatically, I do not do anything. When I start kodi the smart tv will automatically connect to it.
and also you can use it with other software, like cec-client too (that was mentioned in your post too).
Or try libreelec (if that works at all) https://forums.raspberrypi.com/viewtopic.php?t=364971
|
|
|
04-08-2024, 10:58 AM
|
#6
|
Member
Registered: May 2020
Posts: 48
Rep: 
|
Quote:
Originally Posted by pan64
[code]pan@pi4:~ $ cec-ctl -l
but you need to see the device without kodi too
cec-client too (that was mentioned in your post too).
Or try libreelec
|
In my post https://www.linuxquestions.org/quest...6/#post6419247
1. I mentioned seeing the devices, so that's fine.
2. you cannot find the word "cec-client" in this thread, only cec-ctl: cec-client has been deprecated. In this post I have given an example to switch the television on and off.
Libreelec works out of the box and Kodi with CEC on Raspberry Pi OS Bullseye and Bookworm too. My problem is on the Slackware arm platform.
Quote:
Originally Posted by pan64
For example if you use kodi it will automatically detect it and use it
|
Settings -> system -> input -> peripherals does not show a CEC adapter in my case. How did you build Kodi with CEC support on Slackware arm?
|
|
|
10-16-2024, 07:24 AM
|
#7
|
Member
Registered: Jan 2004
Location: EU
Distribution: Debian
Posts: 91
Rep:
|
Quote:
Originally Posted by Lockywolf
I figured it out.
CEC does not work with dtoverlay dtoverlay=vc4-fkms-v3d-pi4,cma=512, but it does work with dtoverlay=vc4-kms-v3d-pi4,cma=512.
I need to try and see how other features work on it.
|
Thank you, I had exactly the same issue after upgrading from Raspbian 11 to 12. HDMI CEC worked fine on 10 and 11, but after upgrade to 12 it stopped working and this change fixed it for me as well.
|
|
|
11-13-2024, 07:48 AM
|
#8
|
LQ Newbie
Registered: Nov 2024
Posts: 1
Rep:
|
Joining this to determine if it will help me with my Bullseye cec-client issue.
I built a dakboard on a Raspberry Pi 3B about 2 years ago. Somehow the SD card got corrupted, so I just put it all aside. I tried reviving the project using the latest dakboard build for raspberry pi, which seems to be on Bullseye.
My previous build had some cronjobs that would turn on the tv and change the input to the dakboard pi at a certain time, which was awesome. Coming into the kitchen in the morning and the board is already showing the agenda, the weather, and a featured "photo of the day" from my google photos.
The latest build on Bullseye does not support the same cec-client that I was using to do this. Perhaps this is the fix found here, but I am new and don't know where to do this dtoverlay fix. Can you explain?
|
|
|
All times are GMT -5. The time now is 09:13 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|