<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Nope, this doesn't sound familiar to me. The error message is<br>
indicating some problem with your lircd.conf though. You should<br>
effectively be able to 'cat<br>
/usr/share/lirc/transmitters/dish/general.conf > /etc/lirc/lircd.conf'<br>
(or your config may have an include of that file). <br></blockquote><div><br>Alex, <br><br>Looks like you're using Ubuntu - I grabbed the latest lirc deb and extracted the /dish/general.conf just on the off chance something was different. I went through every iteration in the file, but unforunately no dice.<br>
Just incase anyone has an idea, this is the merry-go-round I've been playing on the last few days:<br><br>/var/log/messages:<br><br>Dec 16 22:31:03 localhost lircd-0.8.6[4994]: accepted new client on /dev/lircd1<br>Dec 16 22:31:03 localhost lircd-0.8.6[4994]: write failed<br>
Dec 16 22:31:03 localhost lircd-0.8.6[4994]: Protocol error<br>Dec 16 22:31:03 localhost lircd-0.8.6[4994]: error processing command: SEND_ONCE dish16 1<br>Dec 16 22:31:03 localhost lircd-0.8.6[4994]: transmission failed<br>
Dec 16 22:31:03 localhost lircd-0.8.6[4994]: removed client<br>Dec 16 22:31:03 localhost kernel: lirc_zilog: failed to get data for code 0, key 525 -- check lircd.conf entries<br><br>dmesg:<br><br>lirc_zilog: failed to get data for code 0, key 525 -- check lircd.conf entries<br>
<br><br>I transmit on /dev/lircd1, as you can see above. <br><br>The HD-PVR has firmware 1.5.6.1, and the only difference between the above log and what I was getting before is that the lircd.conf files for dish I had previously were complaining about 'code 0, key 400'.<br>
<br>If there are no suggestions, no biggie; I'll keep plugging away and I'll post when it finally starts working... even if I have to build a robot to physically push the buttons on the stupid remote, it WILL work eventually.<br>
<br>Charlie<br><br><br></div></div>