Posts by namek

    Thanks HiassofT again.

    Today, I saw this change (CONFIG_INPUT_UINPUT=y) in linux.arm.conf file. at 66bab50e147e2e881f91c0829fd67d372b0305bd · LibreELEC/ · GitHub

    this line was commented out in the source that I could build (the latest master a couple of weeks ago).

    So, I pull the latest master again and tried to build...

    >>> crazycat:target seq 126 >>>

    [263/271] [FAIL] install crazycat:target

    So, I will first fix my build but will try the new build on cubox!


    tools/download did not help. so need to dig in.

    Thanks chewitt and HiassofT

    These are from a fresh reboot.

    systemctl status eventlircd

    wow. disabled!

    And for the output of journalctl -a | pastebinit:

    If I restart kodi and eventlirc after making sure ir-keytable -t detect my remote, I see this error message:

    1. LibreELEC:~ # irw
    2. Cannot connect to socket /run/lirc/lircd: No such file or directory

    Indeed, in /run/lirc, I only see lircd.socket.

    1. LibreELEC:~ # irw -v
    2. irw 0.10.1

    Maybe I need to understand what irw is and how it should be configured.

    I will read here...

    LIRC - Linux Infrared Remote Control

    Hi I am on CuBox-i4 running the image from the latest master (0848005fbf0dedb148df71ed1b137ab2ab2d497e) but tv remote (samsung) is not working...

    I was using an old OpenELEC built by SolidRun on my CuBox-i4P (quad core) and my remote was working fine but when I decided to move on to the latest LiebreELEC master, remote stopped working. So, I followed along the official wiki (Infrared Remotes) and this post (LE9.0 remote configs ir-keytable Amlogic devices) and configured a custom keymap but even with that, irw is not seeing anything...

    I am quite new to all this and spent 3 days to learn up to here. I would love to see LibreELEC 10 working on my CuBox-i...

    When it is working on OpenELEC, the output of ir-keytable and lsmod look like this:

    1. OpenELEC:~ # ir-keytable
    2. Found /sys/class/rc/rc0/ (/dev/input/event4) with:
    3. Driver gpio-rc-recv, table rc-rc6-mce
    4. Supported protocols: unknown other rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp
    5. Enabled protocols: nec rc-6
    6. Name: gpio_ir_recv
    7. bus: 25, vendor/product: 0001:0001, version: 0x0100
    8. Repeat delay = 500 ms, repeat period = 125 ms

    I also see run/lirc/lircd running as service along with eventlircd.service and CEC adaptor was on (Kodi UI System setting -> input).

    In the LibreELEC, the output of ir-keytable look like this:

    And the output of lsmod is like this:

    1. LibreELEC:~ # lsmod
    2. Module Size Used by
    3. coda_vpu 98304 0
    4. imx_vdoa 16384 1 coda_vpu
    5. videobuf2_dma_contig 20480 1 coda_vpu
    6. v4l2_mem2mem 28672 1 coda_vpu
    7. dw_hdmi_ahb_audio 16384 0

    So, I don't see ir_nec_decoder any more... (CEC adaptor is also not there in Kodi UI)

    But I assume this should be ok now that in kernel decoder is doing the work?

    At the beggining, ir-keytable -t was not detecting anything. So, I switch to nec protocol (samsung uses that I believe) and test it by ir-keytable -p nec -t.

    Then I could see scancodes and so I could create my_custom_remote in /storage/.config/rc_keymaps/my_custom_remote and set this up in /storage/.config/rc_maps.cfg as

    1. * * my_custom_remote

    After this, I could see EV_MSC and EV_KEY correctly by ir-keytable -t like below:

    Now that ir-keytable -t is working properly. I should see output from irw command but I see nothing.

    Strangely, I get the response from ir-keytable -t whether or not I stop kodi and eventlircd from systemcntl. So, it looks like kodi is not intercepting remote signals at all, and this explains why irw command show no response at all.