RPI 4: Buster, cec-client 4.0.4 segmentation fault #476
Comments
|
I can confirm the same behavior. Is no one maintaining this project anymore? uname -a cec-client --info No matter what I do it seems to complete most commands but exits in a segmentation fault: echo "on 0" | cec-client -s -d 1 |
|
Same issue.. works fine with RPI3, seems like issue is not with CEC library as RPI3 and RPI4 in my case uses same library.. |
|
do you have your monitor in HDMI0 or HDMI1 ? I had the same issue when plugging the monitor / TV into HDMI1, after plugging that into HDMI0 I had no issues since. |
|
Same, after pluggin into HDMI0 and stopped using hdmi to hdmi mini adapter all worked.. |
|
Same problem on all 3 HDMI inputs of Samsung 32K5600AW. On RPi 3B+ and RPi 4 btw: hdmi_force_hotplug=1 added to /boot/config.txt pi@pi:~$ echo 'scan' | cec-client -s -d 1 device #0: TV device #1: Recorder 1 currently active source: unknown (-1) |
|
can you check whether this still happens when using libCEC 6.0.0 |
|
@opdenkamp Sorry for the late response. Only now do I have the machine back for maintenance. I tried libCEC 6.0.2 on RPi 3B+ cat /proc/device-tree/model cec-client --info but now I get autodetect failed echo 'scan' | cec-client -s -d 1 I have no idea if the Segmentation fault is gone |
|
your build doesn't include support for the Pi |
|
Sorry about that! Forgot to include platform. cec-client --info echo 'scan' | cec-client -s -d 1 But the segmentation fault is gone! |
|
Still is seg faulting for me:
libCEC version: 6.0.2, git revision: libcec-6.0.2+1-76551ea, compiled on 2020-08-12 01:05:27 by pi@nickthesickpi on Linux 5.4.51-v7l+ (armv7l), features: P8_USB, DRM, P8_detect, randr, RPi Getting this output: |
|
Actually, after the recompile and fresh boot with the hdmi plug on HDMI0 (labeled next to the port on the PI itself) on the PI, it worked for me. Why would it need a reboot I don't know? |
|
I'm having a similar RPi4 issue on the latest from git (6.0.2).
I see segmentation faults, typically after the command has finished; I can get a scan, and can turn on/off the TV I'm connected to. But execution is very slow and has lots of command timeouts in the debug log. Running on a Pi3B connected to the same TV via the same cable (though the Pi4 has an adapter, I've also tried two different direct micro HDMI->HDMI from Pi4 to TV as well) works flawlessly and almost instantaneously. On my Pi3B turning off the tv with "echo 'standby 0.0.0.0' | cec-client -s" takes about 2 seconds. On the Pi4 it can take 15-30. With no connection on either HDMI port, running "echo 'scan' | cec-client -s" takes over a minute. Here's the output from a scan with no HDMI devices connected: Any thoughts on what I can do to debug further? I've fiddled with most of the hdmi settings in config.txt, rebuilt and rebooted many times. |
|
I happen to have a Pulse Eight USB adapter, and connected that to the Pi4 and inserted it into the HDMI cable path between the Pi4 and the Samsung TV. Running cec-client pointing to the USB adapter works as expected; no segfaults, and commands are as quick as I'd expect. |
|
I have a segfault on a freshly built (via instructions above) libcec Here is the log: |
|
Problem was solved for me when I upgraded from |
uname -a
Linux 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l GNU/Linux
cec-client --info
libCEC version: 4.0.4, compiled on Linux-4.15.0-48-generic ... , features: P8_USB, DRM, P8_detect, randr, RPi, Exynos, AOCEC
Followed these steps to download and compile cec:
apt-get update
apt-get install cmake libudev-dev libxrandr-dev python-dev swig
git clone https://github.com/Pulse-Eight/libcec.git
mkdir libcec/build
cd libcec/build
cmake ..
make -j4
sudo make install
sudo ldconfig
echo "on 0" | cec-client -s -d 2
opening a connection to the CEC adapter...
WARNING: [ 3322] unhandled response received: opcode=0 initiator=e destination=0 response=0
WARNING: [ 17104] unhandled response received: opcode=84 initiator=1 destination=f response=0
WARNING: [ 18635] unhandled response received: opcode=47 initiator=1 destination=0 response=0
WARNING: [ 20165] unhandled response received: opcode=47 initiator=1 destination=0 response=0
WARNING: [ 21695] unhandled response received: opcode=8f initiator=1 destination=0 response=0
WARNING: [ 23228] unhandled response received: opcode=8f initiator=1 destination=0 response=0
WARNING: [ 24759] unhandled response received: opcode=8c initiator=1 destination=0 response=0
WARNING: [ 26289] unhandled response received: opcode=8c initiator=1 destination=0 response=0
WARNING: [ 27819] unhandled response received: opcode=4 initiator=1 destination=0 response=0
Segmentation fault
NOTE:
I tried other commands such as standby, as, pow all produce segmentation fault after completing
echo 'standby 0' | cec-client -s -d 2
echo 'as' | cec-client -s -d 2
echo 'scan' | cec-client -s -d 2
The text was updated successfully, but these errors were encountered: