Posts by HiassofT
-
-
What kind of info are you looking for and/or which kind of problem are you trying to solve?
In general: if you use a typical x86 HTPC box with an integrated IR receiver (like eg a NUC) and an original (or 100% compatible) Microsoft MCE remote it will work out of the box.
so long,
Hias
-
Try decreasing the command repeat settings in the harmony software as described here: Fixing Repeats
We recently diagnosed an issue with harmony remotes on kernel 4.14, and it looks like the harmony command feature uses a too long delay (about 240ms between signals instead of the expected ~100ms), setting command repeat to 0 or 1 fixed that.
so long,
Hias
-
On RPi1 (non-plus model) you also may need to short out the polyfuse F3 - it can contribute to a significant voltage drop.
Even a very short dip on the voltage rail might make your RPi crash, so if in doubt stick to the official RPi power supplies - they are known to work well.
Back in the day I had very good success (more than half a dozen installs for friends & family) with official RPi power supply and the following overclock:
so long,
Hias
-
The IR receiver device you are using only seems to support the raw lirc protocol - which is a bit odd. Usually IR receiver devices typically support rc-5, rc-6 and nec and some of them in addition to that the lirc protocol.
Please test with the latest LE beta release (currently 8.1.2). If you still only see "lirc" listed under supported protocols you'll have to use Lirc for remote support - just enable Lirc in LE Settings->Services.
BTW: Up-to-date instructions on remote handling in LE 8.1 and newer are in the wiki: infrared_remotes [LibreELEC]
so long,
Hias
-
It's all in the release notes that nobody seems to care to read LibreELEC (Krypton) v8.1.2 BETA – LibreELEC
QuoteIf you experience “double button presses” after updating the Lirc service can be disabled in the ‘Services’ tab of the LibreELEC settings add-on.
-
-
Try to find out at which exact build the issue started and report that in the Milhouse thread on the kodi forum.
Other than that: you also seem to have added "dtparam=audio=on" in your confiig.txt so you have both the analog on-board audio of the RPi (bcm2835 ALSA) and the hifiberry card enabled.
Remove the "dtparam=audio=on" line from config.txt, looks like kodi is struggling when there are 2 audio devices installed.
so long,
Hias
-
double check that the config.txt line is correct. On success you should get the following lines in dmesg - and ir-keytable should work:
Code[ 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 = 0If you can't get it working add the following line to config.txt
Then reeboot and post the output of the following commands:
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
-
-
-
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:
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