Progress.

So I compiled from source on this box like I normally had in the past and
the lirc_serial device was not working as planned. Doing a little checkup I
found that it was still loading the old lirc_serial modules...very odd. I
thought they would be replaced. I moved the folder and ran a depmod and then
make install. Success.

So the patches we tested before I assume did not actually replace the
modules that were loading. I have removed all modules from the system and am
going to patch the 0.8.3pre1 packages and build them again. Hopefully later
tonight.

On Mon, Mar 24, 2008 at 12:02 PM, Andrew Barbaccia <email address hidden>
wrote:

> I'm starting to think this is more of a configuration problem with the
> package than it is with the actual software code itself.
>
> I cannot test the response of my cable box because I am not home (and was
> way to lazy this morning to try and setup a webcam server, etc).
>
> I have the blaster pointed at my remote receiver (they run at the same
> Hz). I ran mode2 to capture the signals and tested sending from the serial
> module. I pasted the output as a chart into this email, i can attach it if
> the formatting is bad.
>
> I'm not sure what to make of this and want to test the response directly
> to the cable box when I return home because that will give me more
> comprehensible output (I'm just guessing which each of these pulses
> translates to).
>
> This is all pointing back to the options that the package was compiled
> with. We'll have to dig further into this tonight. Let me know your
> thoughts.
>
>   lirc packages compiled source  space 16777215 space 16777215  pulse 128 pulse
> 128  space 871862 space 10112  pulse 128 pulse 128  space 6784 space 3456  pulse
> 128 pulse 128  space 14976 space 2514024  pulse 128 pulse 384  space 1664 space
> 1967593  pulse 128 pulse 128  space 1664 space 21888  pulse 128 pulse 128  space
> 1664 space 3809816  pulse 128 pulse 384  space 30080 space 3200  pulse 128 pulse
> 128  space 2742245 space 3200  pulse 128 pulse 128  space 3200 space 3200  pulse
> 384 pulse 128  space 3200 space 3200  pulse 384 pulse 128  space 3200 space
> 896  pulse 128 pulse 128  space 4992 space 640  pulse 128 pulse 384  space
> 13440 space 640  pulse 128 pulse 128  space 21888 space 2432  pulse 128 pulse
> 128  space 2940641 space 640  pulse 128 pulse 384  space 6528 space 2432  pulse
> 384 pulse 128  space 3200 space 1664  pulse 384 pulse 128  space 640 space
> 1664  pulse 128 pulse 128  space 2432 space 11648  pulse 128 pulse 128  space
> 882037 space 4001943  pulse 128 pulse 128  space 2407849 space 6784  pulse
> 384 pulse 128  space 6528 space 3672924  pulse 128 pulse 384  space 18304 space
> 6528  pulse 128 pulse 128  space 14976 space 3200  pulse 128 pulse 128  space
> 13440 space 8320  pulse 128 pulse 128  space 8320 space 4992  pulse 128 pulse
> 128  space 969396 space 38528  pulse 128 pulse 128  space 2687852
>  pulse 128
>  space 135864
>  pulse 128
>  space 3200
>  pulse 384
>  space 3200
>  pulse 384
>  space 3200
>  pulse 128
>  space 896
>  pulse 128
>  space 2432
>  pulse 128
>  space 640
>  pulse 128
>  space 896
>  pulse 128
>  space 3200
>  pulse 128
>  space 3200
>  pulse 128
>  space 4992
>  pulse 128
>  space 13440
>  pulse 128
>  space 6528
>  pulse 128
>
>
>
>
>
>
>
>
>
>
> On Sun, Mar 23, 2008 at 2:07 PM, Andrew Barbaccia <email address hidden>
> wrote:
>
> > Pete,
> >
> > Again, I think this is something to do with your configuration settings
> > rather than the lirc package itself.
> >
> > This bug is trying to address the lack of transmission support in the
> > current lirc package.
> >
> >
> > On Sun, Mar 23, 2008 at 12:32 PM, Andrew Barbaccia <email address hidden>
> > wrote:
> >
> > >
> > >
> > > Regards,
> > > Andrew J Barbaccia
> > >
> > > On Mar 23, 2008, at 12:12 PM, Pete Woods <launchpad.net@pete-
> > > woods.com> wrote:
> > >
> > > > Something I just noticed. 0x03e8 is not the io parameter that I'm
> > > > specifying in /etc/modprobe.d/lirc
> > > >
> > > > I'm specifying 0x03f8. If I load the module manually with irq=4
> > > > io=0x03f8 then the thing works! Is there some step I'm not
> > > performing
> > > > after setting the modprobe.d option?
> > > >
> > > > --
> > > > lirc_serial loads but does not work (Gutsy 7.10 + Hardy 8.04)
> > > > https://bugs.launchpad.net/bugs/182530
> > > > You received this bug notification because you are a direct
> > > subscriber
> > > > of the bug.
> > >
> >
> >
> >
> > --
> > Andrew Barbaccia
> > MonolithMC Sales & Support
> > (631) 865 - 1025
> >
>
>
>
> --
> Andrew Barbaccia
> MonolithMC Sales & Support
> (631) 865 - 1025
>



-- 
Andrew Barbaccia
MonolithMC Sales & Support
(631) 865 - 1025