Posts by HiassofT

I'm regularly building on Debian Stretch and so far didn't have any problems with RPi or Generic builds.

Just kicked off clean RPi2 and Generic master builds over night and they worked fine - didn't check for warnings though.

bcus the snippet you posted just shows some warnings but not an actual error - hard to tell what failed with your build.

so long,

Hias

Could you test with the latest beta (8.1.2) and follow the steps in the troubleshooting section of this wiki page:

infrared_remotes [LibreELEC]

so long,

Hias

Thanks for reporting back!

We'll include the fix in LE 8.2 [8.2] linux (rpi): sync spinelplus patch with default by HiassofT · Pull Request #2052 · LibreELEC/LibreELEC.tv · GitHub

so long,

Hias

Could you test if this build works:

LibreELEC-RPi2.arm-8.2-devel-20171002114845-r26129-gc1dcaf7699.tar

so long,

Hias

Lirc now uses a different startup method (the same as used by upstream lirc, instead of the rather custom way OpenELEC and LibreELEC used before).

It's puzzling why your autostart.sh script even worked with LE 8.0.2 (IMO it should already have failed there), but I certainly won't work with LE 8.1.

so long,

Hias

Thanks for the link to the kodi / openelec wiki page, now I know where the autostart.sh instructions were coming from. I think I'll have to add a section to the LE wiki page to not do that.

About your issue: The main problem is that your lircd.conf file contains now invalid key codes (Media, PlayPause, com2d etc). Only standard linux keycodes will work (those starting with KEY_). In early lirc days you could use any key/button code you'd like but this quickly led to a mess (everyone used slightly different spellings or names for the same buttons). Now this is restricted to the well defined standard codes.

You can get a list of all supported keycodes with the following command:

irrecord -l

Then change your lircd.conf file to use these codes (eg KEY_PLAYPAUSE instead of PlayPause).

so long,

Hias

What kind of IR receiver and remote are you using?

If you use a simple IR receiver connected to a GPIO use the "gpio-ir" overlay instead of lirc-rpi in config.txt - see the wiki page for details.

Also, if you don't use an original Microsoft MCE remote post details about it and your current lircd.conf file.

so long,

Hias

Details about remote configuration are in the wiki: infrared_remotes [LibreELEC]

MCE remotes should work out of the box without any configuration, make sure lirc is disabled in LE settings.

Also make sure you use the latest LE 8.1.x version, there were reports that eventlircd on LE 8.0.x didn't pick up all remote events and thus some keys (eg OK) didn't work.

so long,

Hias

Quote from tojnk

To load the custom lircd.conf I use an autostart.sh file:

Code

killall lircd
ir-keytable -p lirc
lircd --device=/dev/lirc0 /storage/.config/lircd.conf

Don't do that.

Remove autostart.sh and make sure Lirc is enabled in LibreELEC settings. You may also have to disable ir-keytable auto-configuration (via ": > /storage/.config/rc_maps.cfg").

Another alternative is to keep lirc disabled and create a custom rc_keymap (yes, you can enable multiple protocols and have multiple remote codes in it). See the wiki for details:

infrared_remotes [LibreELEC]

so long,

Hias

You'll need to add this patch for 8.0 (it's only in 8.2 and master trees, cherry-pick should work fine):

dvb-apps: fix compilation with current perl versions · LibreELEC/LibreELEC.tv@6bb3d95 · GitHub

so long,

Hias

We don't know anything about this Orange Pi build, it was not created by us. Only the creator of this build can answer your questions.

so long,

Hias

Those PCM5102 DAC boards derive their frequency from the BCK pin which is driven by the RPi - in contrast to other boards with on-board crystals / PLLs that generate and drive the I2S BCK.

Make sure you've wired up the board correctly and the SCL is connected to ground. You can also test with the DAC board disconnected - you won't hear anything but you can test if mpd, aplay, ... lock up.

I did some tests with this PCM5102 DAC board pHAT DAC - Pimoroni on a RPi2 running LE 8.1.1 using MPD, aplay and speaker-test and everything worked as expected, neither of these locked up.

Please try to find a minimal setup (stock LE installation with only dtoverlay=hifiberry-dac in config.txt and all peripherals removed that aren't strictly needed) and post steps how to reproduce it.

BTW: Also check if you can trigger the issue with speaker-test (and various rate/format parameters, if needed), this would make it easier for me to reproduce it locally.

so long,

Hias

Thanks for the info and sorry about the /proc mistake - was typing that quickly off the top of my head

lsof output looks fine, but the spinelplus receiver / driver seems to be hardwired to just the remote it came with (which is quite common for USB HID IR receivers).

So that combination won't work. You either need a generic IR receiver (a lot of motherboards come with that, you only need to plug in the IR receiver module) or use the remote that came with your IR receiver.

so long,

Hias

This is odd. Eventlircd should pick up the device, just checked and the udev rule matching the usb id is present in 98-eventlircd.rules.

Could you post the output of "lsof | grep /dev/input" and "cat /proc/bus/devices/input"?

If event7 is opened by eventlircd then most probably the spinelplus IR receiver doesn't support your remote - it's not configurable like the other IR receivers via ir-keytable.

so long,

Hias

Update to LE 8.1.1, there were reports that on LE 8.0.x eventlircd sometimes didn't grab the IR input device.

Details about the remote handling in LE 8.1 and newer are in the wiki:

infrared_remotes [LibreELEC]

so long,

Hias

Thanks for the feedback!

We've added the patch to our development branches and LE 8.2.0 will include the fix.

so long,

Hias

Thanks for the update!

There's nothing obvious in the logs. You seem to be using a Hifiberry DAC, in which case the clocks are generated by the RPi. Therefore my best guess now is the RPi kernel PCM clock patch in combination with the way mpd uses alsa.

In order to track down the issue I'll need to be able to reproduce this locally, so I'll need some more information and detailed step how to reproduce this:

set log_level=verbose in mpd.conf, reboot the RPi, then try to trigger the issue.

After that post the mpd log, output of "journalctl -a | paste" and your config.txt and mpd.conf files.

It could be related to the file played (or the file played immediately before that), so having the "mediainfo" output of these files would also help.

so long,

Hias

FYI: the patch is also in the latest Milhouse testbuilds for RPi/RPi2:

LibreELEC Testbuilds for RaspberryPi (Kodi 18.0)

so long,

Hias