<div class="gmail_quote">On Tue, Jul 20, 2010 at 11:18 PM, Jarod Wilson <span dir="ltr"><<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Tue, Jul 20, 2010 at 11:14 AM, Larry K <<a href="mailto:lunchtimelarry@gmail.com">lunchtimelarry@gmail.com</a>> wrote:<br>
>> 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>
>><br>
><br>
> Jarod, you are da man! That did the trick!. Once I upgraded my kernel,<br>
> progress went pretty smoothly. Maybe I'll update the wiki to reflect that<br>
> 2.6.29.1 is really not the minimum kernel that is required. I wasted a lot<br>
> of time and energy and I sure don't wish that on anyone.<br>
<br>
</div>Yeah, its been a bit rocky, I haven't had time to keep on top of everything.<br>
<div class="im"><br>
> When I ran the send_power_new script, I noticed that several codes worked<br>
> with my DCX3200. Even some of the satellite codes (1_29 and 1_39, I<br>
> think). For cable codes, I think 0_80 through 0_85 all worked. I just<br>
> randomly picked 0_85, I think it was. Not sure if there is any reason to<br>
> pick one over the other?<br>
<br>
</div>Probably not. Almost all Motorola boxes use pretty much the same<br>
codes, only minor differences here and there, so far as I've seen.<br>
<div class="im"><br>
> Per your recommendation, I dumped lirc_i2c in favor of just lirc_zilog, so<br>
> now my OFA remote control commands are picked up by the HD-PVR receiver,<br>
> which I suppose will be OK. It did seem to be more sluggish to respond, as<br>
> compared to the IR receiver on my old PVR-250. Does this make sense? Still<br>
> contemplating whether to stick with this, or try to go back to the more<br>
> responsive IR receiver. One thing I never tried is using the IR receiver on<br>
> my HDHR. I guess I have several options. I welcome any comments or advice<br>
> on this.<br>
<br>
</div>I'd forgot about reports of sluggishness w/the hdpvr receiver. Hrm.<br>
Something I'll have to look at shortly. You could certainly take a<br>
crack at running dual lircd instances with both lirc_zilog and<br>
lirc_i2c loaded up. I hope to improve lirc_zilog Real Soon Now though.<br>
<font color="#888888"><br>
<br></font></blockquote><div>Thanks for the feedback.<br><br>As it turns out, now that I have the silly channel changer working over IR, I have discovered troublesome instability with the HD-PVR. I can record one show (the channel changer seems to work) but then, after that, I just get "recording failed", with lots of interesting stuff in the system log. I've been poring over this forum, reading all about similar issues, but much of it dates back to mid-2009, and I wonder how much of this is now OBE. However, I did switch from optical audio to analog audio, confirmed that my STB is set to 720p, with 4:3 override disabled. Before I hooked up the PVR to Myth, I hooked up to Windoze and I downloaded the latest driver/firmware. I *assume* that the process worked and I got the latest firmware installed. Not sure how I can tell. Does myth report the firmware version somewhere? Or, will I need to go back to windows and look there?<br>
<br>Anyway, as a hedge, I have a firewire card on the way from Newegg. I'll probably end up switching to that to see if all this instability goes away. Meanwhile, the investigation continues, and the WAF goes down the tubes...<br>
</div></div><br>