<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">You will need to upgrade your kernel to the latest one currently<br>
available in updates, 2.6.32.16-141.fc12. There was a flub when I<br>
restored the hdpvr-ir-enable patch in earlier kernels after it got<br>
accidentally dropped sometime after the initial f12 release, which I<br>
finally fixed properly in that kernel (just triple-checked that its<br>
working here a few seconds ago). Then you should be able to get a bit<br>
more verbose dmesg, and more importantly, a working device. ;)<br>
<font color="#888888"><br>
</font></blockquote><div><br>Jarod, you are da man! That did the trick!. Once I upgraded my kernel, progress went pretty smoothly. Maybe I'll update the wiki to reflect that 2.6.29.1 is really not the minimum kernel that is required. I wasted a lot of time and energy and I sure don't wish that on anyone.<br>
<br>When I ran the send_power_new script, I noticed that several codes worked with my DCX3200. Even some of the satellite codes (1_29 and 1_39, I think). For cable codes, I think 0_80 through 0_85 all worked. I just randomly picked 0_85, I think it was. Not sure if there is any reason to pick one over the other?<br>
<br>Per your recommendation, I dumped lirc_i2c in favor of just lirc_zilog, so now my OFA remote control commands are picked up by the HD-PVR receiver, which I suppose will be OK. It did seem to be more sluggish to respond, as compared to the IR receiver on my old PVR-250. Does this make sense? Still contemplating whether to stick with this, or try to go back to the more responsive IR receiver. One thing I never tried is using the IR receiver on my HDHR. I guess I have several options. I welcome any comments or advice on this.<br>
<br>Thanks to everyone for weighing in on this issue!<br><br><br><br><br></div></div><br>