Posts by HiassofT

double check that the config.txt line is correct. On success you should get the following lines in dmesg - and ir-keytable should work:

[    5.865255] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0
[    5.865488] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input1
[    5.876159] rc rc0: lirc_dev: driver ir-lirc-codec (gpio-rc-recv) registered at minor = 0

If you can't get it working add the following line to config.txt

dtdebug=1

Then reeboot and post the output of the following commands:

paste /flash/config.txt
vcdbg log msg 2>&1 | paste
dmesg | paste

so long,

Hias

dmesg indicates that you have "dtoverlay=lirc-rpi" in your config.txt. Remove that line, use "dtoverlay=gpio-ir" (which is the modern replacement of lirc-rpi) instead and ir-keytable should work.

so long,

Hias

Unfortunately the strace isn't telling us much more than we already knew - sound device doesn't seem to be accepting data (maybe didn't manage to start running).

I did another test here with LE8.1.2 and still haven't been able to reproduce your issue.

I used a RPi2 with the PCM5102 based pimoroni pHat, connected ethernet and HDMI cables and a USB keyboard. Then I did this

- fresh installation of LE 8.1.2 image on SD card

- after bootup only enabled SSH

- SSHed in, added "dtoverlay=hifiberry-dac" to end of config.txt, then rebooted

- copied a 10 seconds wav file (44.1kHz, stereo, 16 bit) via scp to the sdcard

- SSHed in, ran "aplay -Dhw:0 cd-10sec.wav" about 15 times without any issues

Try if you can replicate using the exact same setup and steps. If you get issues my best bet is some hardware/cabling issue with your soundcard or an issue with your power supply (the number one cause of mysterious problems on RPi).

so long,

Hias

You can't turn on your RPi via the IR remote.

There are addon boards which allow you to do this - you need a small microcontroller that's running when the RPi is off that "listens" for a power-on IR button press and then turns on power to the RPi.

But considering that the costs of these boards is about the same as the electricity costs of having your RPi continously on for 3-5 years it's debatable if they are actually useful.

so long,

Hias

Please post the contents of config.txt and the output of

dmesg | paste
journalctl -a | paste

You can do that by masking the kodi systemd service, plus maybe some others you don't need/want (eventlircd etc)

systemctl mask kodi

Only drawback is that then you have to care about addon updates / installation yourself.

Search the forum, we've discussed that before.

so long,

Hias

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