Posts by HiassofT

For 1 and 2 I'm using this:

buttons mapped to KEY_EPG and KEY_HOME in keytable.

In oder to get the EPG working I use the following Lircmap.xml

<lircmap>
    <remote device="devinput">
        <guide>KEY_EPG</guide>
    </remote>
</lircmap>

The linux input events translated by eventlircd will show up as "devinput" lirc events in kodi.

As for 3: that should be doable with mapping a button to KEY_PVR - that should map to <recordedtv> in the default kodi keymap for devinput and will then bring up the window via this entry in the default kodi remote.xml

<recordedtv>ActivateWindow(TVRecordings)</recordedtv>

so long,

Hias

We are only removing the driver for the old xbox USB IR receiver. You'll still be able to use the remote with another IR receiver that's compatible with it - eg the universal GPIO receiver on RPi or most built-in IR receivers eg on Intel NUCs.

lirc_xbox doesn't support configuration via ir-keytable as it is an old lirc-only device driver.

so long,

Hias

That post you mentioned is the right start. Follow the steps outlined there, and if something's not quite clear just ask.

I'm currently putting a guide together which will be posted on the wiki, every feedback from you users is helpful to me.

For me as a dev who's into that stuff it's the other way round, too many things are obvious to me and I might forget mentioning them. Knowing about these things and what's not really obvious to you will help me creating the guide.

so long,

Hias

BTW: It's better to build a simple GPIO IR receiver (eg using a TSOP34138) which you can then use with the "gpio-ir" overlay.

LibreELEC 9.0 will ship without the lirc_xbox driver (it's already removed from current Milhouse builds).

Kernel is moving away from the old lirc drivers to the newer rc-core drivers (with in-kernel decoding support, you don't need userspace lirc for remotes). The lirc_xbox never made it into the upstream kernel, it was only added to OpenELEC (and kept in LibreELEC), and due to the ongoing changes in the kernel we can no longer support it. OpenELEC already removed it, and now we have to do the same as well.

so long,

Hias

The xbox receiver isn't detected by the system at all - the only usb devices listed in dmesg are RPi's ethernet adapter (smsc95xx) and your chicony keyboard.

Check again without the keyboard, or adding an active powered USB hub in between.

so long,

Hias

Please post the journal output and dmesg

dmesg | paste
journalctl -a | paste

so long,

Hias

Your "logitech" file uses DOS-style line-endings (CR LF), change that to unix style (LF only) and it should work.

so long,

Hias

Can you post full logs?

journalctl -a | paste
dmesg | paste

Could be some USB error and the device has fallen off the bus - logs should show that. Or it's some quirk in the ir toy firmware.

so long,

Hias

Quote from avkhid

One more, I had my line-in configured to play on speakers through .sh script and udevrules in old build.

How do I get this to work? Do I need to enable anything else as you advised above?

Add this to the rpi cirrus config script:

# default input gain +8dB
setup_line_in 8

# route line in to mixer 2 of speaker-out. 32 means 0dB gain
set_mixer $speaker_out_signals $line_in_signals 32 2

Adjust the gain settings as you like, but better keep the output gain at 0dB (raw value 32), otherwise you risk clipping.

Some more examples on how to work with the mixer helper functions can be found in the mixer-scripts for raspbian: rpi-cirrus-config/mixer-scripts at master · HiassofT/rpi-cirrus-config · GitHub

so long,

Hias

How did you configure speaker out?

Since version 7.0.3 of my community builds custom configuration is now handled via .config/rpi-cirrus-config.sh. Use the rpi-cirrus-config.sh.sample file from that directory as a template, you only need to un-comment the "playback_to_speakers" line and reboot.

Instead of the old, separate shell-scripts to configure the card helper functions from the /usr/lib/alsa/rpi-cirrus-functions.sh script are now used - this turned out to be more flexible and easier to maintain than the separate scripts.

Also make sure you selected "RPi-Cirrus Analog" as audio output device, "RPi-Cirrus S/PDIF" will only output to S/PDIF and mute all other outputs. "Analog" will output to whatever you have configured in the rpi-cirrus-config.sh script (default is line+headset+spdif out).

so long,

Hias

Could you try with the gpio-ir overlay instead of the lirc-rpi overlay?

Just change your config.txt to contain this:

dtoverlay=gpio-ir,gpio_pin=25

Also disable Lirc in LibreELEC Settings -> Services.

Then follow this guide to configure the remote using ir-keytable: WD TV Live remote

Using irrecord to manually create a lircd.conf file has always been problematic. In your case it created an invalid file - you'd have to remove the 0x00000000 from the keycodes.

Using a remote with a IR standard protocol like rc-5, rc-6 or nec and the in-kernel decoding (which is available if you use gpio-ir) avoids most of these pitfalls.

so long,

Hias

Could you test if this build works: LibreELEC-Generic.x86_64-8.2-devel-20170716140946-r25919-gd1ed5ac36.tar

This is a 8.2 preview build and contains several updates to remote handling.

I've tested this build with an IR reciever, the serial_ir module and couldn't reproduce any of the problems you reported with an rc-5 remote. Both in-kernel decoding (ir-keytable) and userspace lircd worked fine.

so long,

Hias

Thanks a lot for the feedback! I'm glad you are enjoying LE and your card!

so long,

Hias

Could you test if you also see this behaviour with irw (while kodi and eventlircd are running) and with ir-keytable -t (kodi and eventlircd need to be stopped, watch for the KEY_xxx events)?

BTW: You can ignore the lirc_options.conf warning, it is harmless and already fixed in the upcoming 8.2 version.

Instead of running ir-keytable -c -w ... from autostart.sh I'd recommend creating a .config/rc_maps.cfg file with the content * * my_remote - otherwise the udev rule which sets up the keytable (via /etc/rc_maps.cfg, loading the libreelec-combined keymap) could race with your manual ir-keytable setup.

so long,

Hias

No idea what's happening there, that kernel patch should be harmless. Could you post the output of dmesg when this happens?

Have you configured Kodi to use ALSA as well? If yes, disable that (eg select HDMI output in kodi).

Also try with asound.conf removed to disable the softvol plugin.

Another interesting test would be to disable MPD and use only kodi with ALSA output.

so long,

Hias

You have to use setserial /dev/ttyS0 uart unknown - otherwise serial_ir probably won't work (I'm puzzled why loading it seemed to work, I'd expected to see an error).

Also make sure you have disabled lirc in LE settings.

Then, stop kodi and eventlircd

systemctl stop kodi
systemctl stop eventlircd

Now you should be able to test if the IR receiver works:

ir-keytable -p all -t
mode2

The former will print scancodes and decoded keys, the latter will test raw receiption (you should see pulse and space messages printed on the console) - use that if you can't get any output from ir-keytable.

so long,

Hias

I guess you have been using the lirc_serial module before, probably loaded via an autostart.sh script - is that correct?

lirc_serial has been replaced by serial_ir (the latter can be configured via ir-keytable, so you don't have to run userspace lircd - but you still can if you want).

The module parameters are the same as for lirc_serial, so just changing the modprobe line to use serial_ir should be enough to get you going.

If that doesn't work, please post the commands you use to load the driver and the output of ir-keytable.

so long,

Hias

How is this IR receiver connected to your PC,?

Lirc is fully supported and in current testbuilds and in the upcoming 8.2 version it can be configured and used for all devices like on standard Linux installation. In the current 8.0.2 version it's a bit limited as it uses the same configuration methods as older OpenELEC versions.

But, unless you have a really awkward remote I'd recommend configuring the remote via ir-keytable. This already works like on standard Linux installations, only the configuration files (rc_maps.cfg, rc_keymaps) are in the /storage/.config directory instead of /etc.

Read more about ir-keytable configuration in this thread: WD TV Live remote

so long,

Hias