Posts by timd

Quote from timd

Any clues to where the CEC mapping is done? I've got no custom remote changes in ~/.config

Cheers,

Tim

Ok - setting .config/rc_maps.cfg to:

meson-ir        *               cec

seems to have sorted it out.

Ok, this is a bit strange. It seems to be interpreting the CEC remote down button as power off:

21:02:26.878 T:3827299200   DEBUG: PushCecKeypress - received key a6 duration 0
21:02:26.923 T:4097249296   DEBUG: HandleKey: 166 (0xa6, obc89) pressed, action is Up
21:02:27.082 T:3827299200   DEBUG: PushCecKeypress - received key a6 duration 210
21:02:28.084 T:3827299200   DEBUG: PushCecKeypress - received key a6 duration 0
21:02:28.124 T:4097249296   DEBUG: HandleKey: 166 (0xa6, obc89) pressed, action is Up
21:02:28.376 T:3827299200   DEBUG: PushCecKeypress - received key a6 duration 296
21:02:29.157 T:4097249296   DEBUG: LIRC: Update - NEW at 1586110:69 0 KEY_LEFT devinput (KEY_LEFT)
21:02:29.158 T:4097249296   DEBUG: HandleKey: 169 (0xa9, obc86) pressed, action is Left
21:02:29.174 T:3827299200   DEBUG: PushCecKeypress - received key a9 duration 0
21:02:29.187 T:4097249296   DEBUG: HandleKey: 169 (0xa9, obc86) pressed, action is Left
21:02:29.466 T:3827299200   DEBUG: PushCecKeypress - received key a9 duration 292
21:02:29.626 T:3537875840   DEBUG: CWebServer[8080]: request received for /jsonrpc
21:02:30.514 T:3827299200   DEBUG: Previous line repeats 1 times.
21:02:30.515 T:3827299200   DEBUG: PushCecKeypress - received key a7 duration 0
21:02:30.532 T:4097249296   DEBUG: HandleKey: 167 (0xa7, obc88) pressed, action is Down
21:02:30.615 T:4097249296   DEBUG: LIRC: Update - NEW at 1587568:74 0 KEY_POWER devinput (KEY_POWER)
21:02:30.615 T:4097249296   DEBUG: HandleKey: rewind (0xc4) pressed, action is ShutDown()

Any clues to where the CEC mapping is done? I've got no custom remote changes in ~/.config

Cheers,

Tim

Can somebody please point me to some info regarding the CEC issue mentioned in the first post?

I have a Mini M8S II using the gxl_p212_2g device tree. It worked fine up until (and including) v8.90.3, but it crashes on both .4 and .5 as soon as I click a button on the (CEC) remote. It then just shuts down immediately without generating a crash log.

It's perfectly stable until I use the TV/CEC remote (I can control it using Kore fine), so I'm fairly certain it's a CEC issue.

Cheers,

Tim

I've got a couple of boxes - a S905 and a S905x, on both of which I've been running libreelec for some some time without any issues.

I've updated them both from 8.2 releases to 8.90.3, with mixed success - the S905x is working absolutely fine, but I'm having problems with the remote on the S905.

I use CEC on the S905x, but can't on the S905 (it's connected via an av-amp that seems to kill CEC even when configured to pass it through), so use a usb MCE receiver - which has always just worked.

I'm afraid I'm not sure what the important note in the first post is saying - I'm using gxbb_p200_2G1Gbit.dtb - how can I tell whether it has LIRC support?

I've tried following the infrared_remote page in the wiki, but I don't think my receiver is being detected properly. This is from dmesg:

[ 39.220466@3] usb 1-1.3: New USB device found, idVendor=0609, idProduct=031d

[ 39.220472@3] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 39.220476@3] usb 1-1.3: Product: eHome Infrared Transceiver

[ 39.220480@3] usb 1-1.3: Manufacturer: SMK

[ 39.220484@3] usb 1-1.3: SerialNumber: SM006Ygj

I'm getting no other remote-related messages, and

kodi-m18:~ # ir-keytable

/sys/class/rc/: No such file or directory

I can modprobe rc_rc6_mce (which doesn't get loaded automatically), but it doesn't make any difference: nothing else printed in dmesg, no change to the ir-keytable output.

Any pointers?

Thanks,

Tim

Update:

I've gotten rid of the usb mce ir-receiver and have paired my harmony hub via bluetooth instead - a much better solution.