[mythtv-users] Save my WAF: HD-PVR IR blaster problems - mythbuntu 64bit - valid lirc_t numbers?

[Yannick Moussette]

Hello Jarod,

first off, thanks for all your efforts with lirc (along with a slew of other
people as well)!

Were you able to talk with Christoph for the conversion of the lirc_t
variable to something 64-bit-compatible?

Thanks!

Yannick.

On Fri, Mar 26, 2010 at 11:09 PM, Jarod Wilson <jarod at wilsonet.com> wrote:

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