<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000066">
    <font face="FreeSans">
      <blockquote type="cite">
        <blockquote type="cite" style="color: rgb(102, 51, 102);">
          <pre wrap=""><span class="moz-txt-citetags">&gt; </span>/usr/sbin/lircd --output=/var/run/lirc/lircd1 --device=/dev/lircd --connect=localhost 8765 --pidfile=/var/run/lirc/lircd1.pid
</pre>
        </blockquote>
        <pre wrap="">I hope that's a transcription error. --device=/dev/lircd is bogus. That
is a symlink to a socket, not a device. Should be /dev/lirc1 or similar.

</pre>
      </blockquote>
      Nope; that's what it showed in System Monitor.<br>
      <blockquote type="cite">
        <blockquote type="cite" style="color: rgb(102, 51, 102);">
          <pre wrap=""><span class="moz-txt-citetags">&gt; </span>and
<span class="moz-txt-citetags">&gt; </span>
<span class="moz-txt-citetags">&gt; </span>/usr/sbin/lircd --output=/var/run/lirc/lircd --driver=dsp --device=/dev/lircd --listen
</pre>
        </blockquote>
        <pre wrap="">Where did --driver=dsp come from, and again with the bogus --device?
</pre>
      </blockquote>
      Looks like that was pulling in from hardware.conf - I can't recall
      if I put that there and, if so, why...<br>
      <blockquote type="cite">
        <pre wrap="">Your primary lircd instance isn't using the right driver (default)
or the right device (/dev/lirc0) for your hdpvr. Seems its somehow
getting snarfed out of your hardware.conf, based on your original
post in this thread. That definitely needs fixing.

</pre>
      </blockquote>
      OK, making progress! I've changed hardware.conf to this:<br>
      <br>
      TRANSMITTER="hauppauge_pvr"<br>
      TRANSMITTER_MODULES="lirc_dev lirc_zilog"<br>
      TRANSMITTER_DRIVER="default"<br>
      TRANSMITTER_DEVICE="/dev/lirc0"<br>
      TRANSMITTER_SOCKET=""<br>
      TRANSMITTER_LIRCD_CONF="/etc/lirc/lircd.conf"<br>
      TRANSMITTER_LIRCD_ARGS=""<br>
      <br>
      <br>
      #Chosen Remote Control<br>
      REMOTE="hauppauge_pvr"<br>
      REMOTE_MODULES="lirc_dev lirc_zilog"<br>
      REMOTE_DRIVER="default"<br>
      REMOTE_DEVICE="/dev/lirc0"<br>
      REMOTE_SOCKET=""<br>
      REMOTE_LIRCD_CONF="/etc/lirc/lircd.conf"<br>
      REMOTE_LIRCD_ARGS=""<br>
      <br>
      Now I get this new error:<br>
      <br>
      $ sudo irsend SEND_ONCE hauppauge_pvr CH+<br>
      irsend: command failed: SEND_ONCE hauppauge_pvr CH+<br>
      irsend: transmission failed<br>
      <br>
      Syslog shows:<br>
      <br>
      accepted new client on /var/run/lirc/lircd<br>
      write failed<br>
      Protocol error<br>
      error processing command: SEND_ONCE hauppauge_pvr CH+<br>
      transmission failed<br>
      <br>
      We seem to be heading in the right direction, because now it seems
      my system recognizes there's a blaster and acknowledges that it
      has transmitting capability.<br>
    </font>
    <pre class="moz-signature" cols="72">-- 

Kind regards,

Martin</pre>
  </body>
</html>