|
From: Alec L. <lea...@gm...> - 2018-12-29 16:02:32
|
On 29/12/18 14:48, André Weidemann wrote: > On 29.12.2018 12:02, Alec Leamas wrote: >> >> Hi, >> >> what are you running on the raspberry? you could compare your setup to >> the appendix on multiple capture devices-- it's similar, just running >> on different hosts > > The Raspberry is running Debian Jessie with lirc 0.9.0~pre1-1.2 and the > following inside my hardware.conf: > > LIRCD_ARGS="--uinput -l" > LOAD_MODULES=true > DRIVER="default" > DEVICE="/dev/lirc0" > MODULES="lirc_rpi" OK, this is somewhat obscure (why forward the decoded events to the kernel?), Still the -l option means that lircd listens to incoming connections on the default udp port 8765. Since this has worked before, let's assume the firewall on the raspberry allows traffic to said port. Which means that the main lircd instance should connect to the raspberry. The driver could then by anything (sorry for pointing to the udp driver, I got it wrong, but it shouldn't really matter). As you say, the output clearly indicates that an option decoding problem. IIRC, there actually was some such bugs in early versions. These are fixed in Debian (currently on 0.10.1-3), but perhaps not in the ubuntu 0.10.0-2 version. Are you able to rebuild the debian 0.10.1-3 source package on your ubuntu machine and check? Cheers! --alec |