<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jun 25, 2014 at 11:41 AM, Hika van den Hoven <span dir="ltr"><<a href="mailto:hikavdh@gmail.com" target="_blank">hikavdh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hoi Jon,<br>
<div><div class="h5"><br>
Wednesday, June 25, 2014, 5:59:07 PM, you wrote:<br>
<br>
> Hey,<br>
<br>
<br>
<br>
> I have 2 HD-PVRs and yesterday decided to move the one that has<br>
> been on slave backend to my master backend that has a HD-PVR<br>
> already. I can get everything to work but can only seem to get one<br>
> blaster to work at a time. I end up with.<br>
><br>
> [ 377.424068] lirc_zilog: i2c_master_send failed with -5<br>
> [ 377.424084] lirc_zilog: sending to the IR transmitter chip failed, trying reset<br>
> [ 378.082019] lirc_zilog: Zilog/Hauppauge IR blaster firmware version 2.1.0 loaded<br>
><br>
> Has anyone ran into this or have a successful 2 blaster setup they can share?<br>
<br>
> Thanks,<br>
<br>
> Jon<br>
<br>
</div></div>Basically you have to run two separate instances of lircd under a<br>
different name. So you have to copy your lircd configuration and start<br>
script to for instance lircd1 and adjust this configuration to the<br>
second blaster.<br>
Do you get two lirc instances in /dev/ or /dev/input ?<br><br></blockquote><div><br></div><div>I do get 2 /dev/lirc instances.</div><div><br></div><div>I've tried to have 2 individual /dev/lircd and to use the listen/connect to connect a second lirc a single /dev/lircd </div>
<div><br></div><div>Would it be possible to share your startup scripts? I must be doing something dumb.</div><div><br></div><div>Jon</div><div><br></div><div><br></div></div></div></div>