Linux Infrared Remote Control

On 7/21/05, Bob Cottingham <bob@...> wrote:
> Jim Reith wrote:
> > I'm running KnoppMyth R5A16 with ivtv 3.6y and I find that lircd
> > 0.7.1pre2 is failing to read the remote after a while of running
> >
> (snipped)
> >
> > I have a PVR-150 and a PVR-350 and am using the 350 tv-out. The IR
> > receiver is plugged into the 150 and the 150 is detected first of the t=
wo
> > cards.
> (more stuff snipped)
>=20
> This is a problem with the ivtv drivers and the PVR-150. I have the same
> problem, which occurs everytime the PVR-150 is used to record something
> for longer than about 20 minutes or so.
>=20
> Bryan Mayland on the ivtv list has stated that he will look into it, but
> that was a couple months ago and he hasn't had the time yet. Bring it up
> on the ivtv list to refresh his memory and further validate the issue.
>=20
> Bob
>=20

Bob,
   I understood that this problem was, at least for the StreamZap, a
problem with lirc. There is a patch in CVS that fixed it for me. My
remotes now work all the time since I started using CVS.

   Possibly it is a problem with ivtv for other remotes but I hadn't heard =
that.

Hope this helps,
Mark

I'm in touch with Bryan on ivtv-dev list now. He needs a broken case to
debug and I've offered my services

Jim

At 10:12 AM 7/21/2005, you wrote:
>On 7/21/05, Bob Cottingham <bob@...> wrote:
> > Jim Reith wrote:
> > > I'm running KnoppMyth R5A16 with ivtv 3.6y and I find that lircd
> > > 0.7.1pre2 is failing to read the remote after a while of running
> > >
> > (snipped)
> > >
> > > I have a PVR-150 and a PVR-350 and am using the 350 tv-out. The IR
> > > receiver is plugged into the 150 and the 150 is detected first of the two
> > > cards.
> > (more stuff snipped)
> >
> > This is a problem with the ivtv drivers and the PVR-150. I have the same
> > problem, which occurs everytime the PVR-150 is used to record something
> > for longer than about 20 minutes or so.
> >
> > Bryan Mayland on the ivtv list has stated that he will look into it, but
> > that was a couple months ago and he hasn't had the time yet. Bring it up
> > on the ivtv list to refresh his memory and further validate the issue.
> >
> > Bob
> >
>
>Bob,
>    I understood that this problem was, at least for the StreamZap, a
>problem with lirc. There is a patch in CVS that fixed it for me. My
>remotes now work all the time since I started using CVS.
>
>    Possibly it is a problem with ivtv for other remotes but I hadn't
> heard that.
>
>Hope this helps,
>Mark
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&opick

Hi!

Do the lirc-modules work under kernel 2.6.13-rc3??
I used actual CVS version of lirc and the modules compiled without an 
error but when I want to load a module I get errors:

Video:~# modprobe lirc_mceusb
WARNING: Error inserting lirc_dev 
(/lib/modules/2.6.13-rc3/misc/lirc_dev.ko): Unknown symbol in module, or 
unknown parameter (see dmesg)
FATAL: Error inserting lirc_mceusb 
(/lib/modules/2.6.13-rc3/misc/lirc_mceusb.ko): Unknown symbol in module, 
or unknown parameter (see dmesg)
Video:~#


Did anyone try this kernel-Version already??

Jens

Hello Jens,

* Jens Krehbiel-Grther <jens.krehbiel-graether@...> [21-07-05 21:01]:
> Do the lirc-modules work under kernel 2.6.13-rc3??
> I used actual CVS version of lirc and the modules compiled without an 
> error but when I want to load a module I get errors:
> 
> Video:~# modprobe lirc_mceusb
> WARNING: Error inserting lirc_dev 
> (/lib/modules/2.6.13-rc3/misc/lirc_dev.ko): Unknown symbol in module, or 
> unknown parameter (see dmesg)
> FATAL: Error inserting lirc_mceusb 
> (/lib/modules/2.6.13-rc3/misc/lirc_mceusb.ko): Unknown symbol in module, 
> or unknown parameter (see dmesg)
> Video:~#
> 
> 
> Did anyone try this kernel-Version already??

look at the archive, i have posted a patch for this problem.

-- 
Bye
Matthias