Re: [mythtv-users] Re: Problems with lirc and PVR-250 on FC2

[Lane S. <dow...@gm...>]

> > -----Original Message-----
> > From: lir...@li...
> > [mailto:lir...@li...] On Behalf Of
> > Lane Schwartz
> > Sent: Monday, November 22, 2004 7:39 PM
> > To: Discussion about mythtv; lir...@li...
> > Subject: Re: [mythtv-users] Re: Problems with lirc and PVR-250 on FC2
> >
> > On Mon, 22 Nov 2004 15:50:02 -0800, Jarod Wilson
> > <jc...@wi...> wrote:
> > > On Monday 22 November 2004 15:01, Lane Schwartz wrote:
> > >
> > >
> > > > > > Earlier in this thread, Christoph Bartelmus suggested that I
> > > > > > "Load lirc_i2c in debug mode and check in the logs
> > whether key
> > > > > > codes are received by the module."
> > > > > >
> > > > > > I'm not sure how to do that... waiting for a reply
> > from him. If
> > > > > > anybody else knows how, that'd be grand.
> > > > >
> > > > > I *think* you just need to add a line to modprobe.conf:
> > "options
> > > > > lirc_i2c debug=1", unload and reload the module, then
> > try irw. You
> > > > > should get a bunch of stuff logged in /var/log/messages
> > for the lirc_i2c module.
> > > >
> > > > Hmm... just tried this. Nothing new shows up in /vor/log/messages.
> > >
> > > Dunno if that's good or bad, or if I even gave you the right
> > > instructions. :-)
> >
> > Ya, me neither. :) I'm hoping Christoph will know and reply.
> >
> > > > > > As it stands now, irw just sits there and doesn't
> > show any signs
> > > > > > that I'm pressing buttons.
> > > > >
> > > > > Not good. I thought others having problems were at
> > least getting
> > > > > feedback from irw. Do you register any button presses
> > with irrecord?
> > > >
> > > > Just tried this. irrecord doesn't recognize the button
> > presses either.
> > > >
> > > > [root@myth mythtv]# irrecord /tmp/file ....
> > > >
> > > > Hold down an arbitrary button.
> > > > irrecord: gap not found, can't continue
> > >
> > > Very not good. Dead batteries in the remote? Receiver not
> > plugged in
> > > all the way? If you have a Windows machine, you might double-check
> > > that things work there... If the modules are loading, the
> > receiver is
> > > plugged in and your batteries are okay, you should definitely be
> > > getting at least something w/irrecord
> >
> > Batteries are definitely OK. I even switched them with those
> > in a working remote just to be sure.
> >
> > I've re-plugged the receiver several times. It's plugged in
> > all the way.
> >
> > Don't have a windows machine, but I have successfully used
> > this remote and card before, on a different machine.
> >
On Tue, 23 Nov 2004 10:06:56 -0500, zeek <ze...@sp...> wrote:
> 
> 
> Greetings,
> 
> I'm seeing the "gap not found" problem as well.
> 
> I've confirmed the functionality of my remote by using the program "IR
> Monitor," a Palm application. I'd recommend mentioning this the
> troubleshooting section of the documentation for people trying to use
> "garage" remotes.
> 
> After several weeks of hacking away at lirc, it would be nice to get some
> response beyond "gap not found."
> 
> In looking at the source, irrecord.c, this seems to happen for two reasons:
> 
>                 if(remotes==NULL && !get_lengths(&remote,force))
>                 {
>                         if(remote.gap==0)
>                         {
>                                 fprintf(stderr,"%s: gap not found,"
> 
> and/or:
> 
>                 if(hw.rec_mode==LIRC_MODE_CODE) remote.bits=CHAR_BIT;
>                 else remote.bits=hw.code_length;
>                 if(!get_gap_length(&remote))
>                 {
>                         fprintf(stderr,"%s: gap not found,"
> 
> But I've no idea what these mean. I'm actually going to rewrite the 2nd err
> to be more specific.
> 
> -zeek

zeek,

That's good information. Hopefully it means something to the lirc developers. :)

I'll give IR Monitor a try on my Palm to verify that the remote
control is properly sending signals.

Thanks,
Lane


-- 
"No, we've had no evidence that Saddam Hussein was involved in 9/11."
-- George W. Bush, 17 Sept 2003