Hello Jarod,<div><br></div><div>first off, thanks for all your efforts with lirc (along with a slew of other people as well)!</div><div><br></div><div>Were you able to talk with Christoph for the conversion of the lirc_t variable to something 64-bit-compatible?</div>
<div><br></div><div>Thanks!</div><div><br></div><div>Yannick.<br><br><div class="gmail_quote">On Fri, Mar 26, 2010 at 11:09 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">On Fri, Mar 26, 2010 at 7:57 AM, Randy Thomae <<a href="mailto:slick@alum.mit.edu">slick@alum.mit.edu</a>> wrote:<br>
...<br>
<div class="im">> On this install, I can not make lirc read the satellite codes in lircd.conf.<br>
> I have tried about 20 different approaches. Yesterday, I went back to the<br>
> beginning and slowly stepped through the process. Here is the good news:<br>
> [ 24.352787] lirc_dev: IR Remote Control driver registered, major 251<br>
> [ 24.354653] lirc_zilog: Zilog/Hauppauge IR driver initializing<br>
> [ 24.356753] lirc_zilog: chip found with RX and TX<br>
> [ 24.356848] lirc_dev: lirc_register_driver: sample_rate: 0<br>
> [ 24.356903] Zilog/Hauppauge i2c IR 1-0071: firmware: requesting<br>
> haup-ir-blaster.bin<br>
> [ 26.822145] lirc_zilog: Zilog/Hauppauge IR blaster firmware version 1.3.0<br>
> loaded<br>
> [ 26.826918] lirc_zilog: chip found with RX and TX<br>
> [ 26.827343] lirc_dev: lirc_register_driver: sample_rate: 0<br>
> [ 27.073189] lirc_zilog: Zilog/Hauppauge IR blaster firmware version 2.1.0<br>
> loaded<br>
> [ 27.073228] lirc_zilog: initialization complete<br>
> Here is the bad news:<br>
> slick@mBAQ:~$ cat /var/log/daemon.log | grep -i lircd<br>
> Mar 26 04:51:33 mBAQ lircd-0.8.6[1280]: error in configfile line 62:<br>
> Mar 26 04:51:33 mBAQ lircd-0.8.6[1280]: "2147549184": must be a valid<br>
> (lirc_t) number<br>
<br>
</div>iirc, lirc_t is an int, so its got an upper limit of 2147483648. Try<br>
commenting out the offending line. I should talk to Christoph about<br>
replacing lirc_t with uint64_t or uint32_t...<br>
<div class="im"><br>
> Mar 26 04:51:33 mBAQ lircd-0.8.6[1280]: reading of file<br>
> '/etc/lirc//lircd.conf' failed<br>
> Mar 26 04:51:33 mBAQ lircd-0.8.6[1280]: reading of config file failed<br>
> Mar 26 04:51:33 mBAQ lircd-0.8.6[1311]: lircd(default) ready, using<br>
> /var/run/lirc/lircd<br>
> Remember this worked on my 32 bit install on ancient hardware. I think I was<br>
> using 2.6.31-14 on that box.<br>
<br>
</div>I wonder if an older lircd simply ignored the range error and continued...<br>
<div class="im"><br>
> I have googled all week for this problem and found a couple of things:<br>
> 1. people "fix" this problem by deleting all the satellite codes from their<br>
> lircd.conf. Unfortunately I have a DirecTv sat box using codeset 1_125, so<br>
> that wont work for me.<br>
<br>
</div>Yeah, this probably requires some fixage to lircd.<br>
<div class="im"><br>
> 2. Some people seem to be using this in 64bit Linux, but they may all be<br>
> using Fedora? Is anyone out there using mythbuntu 64bit and HD-PVR IR<br>
> blasting to a Satellite box?<br>
<br>
</div>Shouldn't really matter what Linux distro you're using, I push all my<br>
fixes upstream too, though other distros might not track the fixes as<br>
closely as Fedora, since I'm the one who commits the fixes for Fedora<br>
too...<br>
<div class="im"><br>
> 3. Some people were posting about a 64bit bug related to this?<br>
<br>
</div>I'm not sure exactly what that might be.<br>
<div class="im"><br>
> 4. Jarod Wilson - (to whom anyone wanting to use an HD-PVR owes their next<br>
> born child for all of his incredible work on this - THANK YOU!!!!!!!)<br>
<br>
</div>No, Janne Grunau deserves far more credit, he did the bulk of the<br>
hdpvr driver work, I just did a few little things here and there for<br>
the IR part, which isn't even fully stabilized for most people yet. :)<br>
<div class="im"><br>
> has<br>
> made a number of patches, some include changing the variable<br>
> types: <a href="http://cvs.fedoraproject.org/viewvc/F-12/lirc/" target="_blank">http://cvs.fedoraproject.org/viewvc/F-12/lirc/</a><br>
> I tried applying these patches, but I was not able to successfully do that.<br>
> I also noticed that he is running 64 bit and said these patches would help<br>
> 32bit users - the opposite of my situation although I did notice he is<br>
> running Fedora.<br>
<br>
</div>They're irrelevant here, they're for the ioctl interface types. I<br>
patched the ioctl interface in the Fedora kernel and forgot to make<br>
the corresponding change to the Fedora userspace. As long as the two<br>
match, you're fine on that front.<br>
<div class="im"><br>
> Can anyone help me fix this, or would you recommend:<br>
> A. Fedora?<br>
<br>
</div>Nah, Linux is Linux.<br>
<div class="im"><br>
> B. Different blaster device - which one?<br>
<br>
</div>An mceusb transceiver. Even if you get things sorted w/the hdpvr<br>
blaster, its not stable for a lot of people -- the hdpvr locks up<br>
during recording if the IR part is enabled.<br>
<font color="#888888"><br>
--<br>
Jarod Wilson<br>
<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a><br>
</font><div><div></div><div class="h5">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br></div>