Re: Progress with ATI Remote Wonder Plus

[Eric D. <ic...@gm...>]

Thanks Aidan and Cymen!  that looks like it was my problem also
(duplcate lirc_* modules and the ati_remote module) after upgrading to
2.6.16 for the RWP.  (i used cymen's patch to lirc_atiusb.c).  after i
patched+recompiled and removed/overwrote the extra kernel modules and
i'm seeing all the button events with lircd+irw. yay!

i've got a working remote wonder plus lircd.conf from:
http://raw-io.superbios.com/rwp/lircd.conf

what about the integration with mythtv?  i can copy over the mythtv
distributed lircrc.example to ~mythtv/.lircrc however the button names
are different and not very many are defined in the rc file.  is there
a better .lircrc i should use?  anyone want to share? :)

also,my mythtv package is compiled "using_lirc" so do i still need to
use irxevent?  how can i debug whether mythtv is seeing the events
from lircd?  not seeing anything in the mythbackend logs and the docs
seem kinda sparse on this to me.  any pointers?

background info:
*  distro =3D FC4
*  Mythtv =3D 0.19 w/ lirc support
*  linux =3D 2.6.16
*  remote =3D ATI remote wonder plus
*  lirc =3D 0.8.1-CVS + Cymen's patch

thanks,
eric


On 4/9/06, Aidan Crook <ai...@mi...> wrote:
> Hi,
>
> Thanks for your reply -- lirc was not registering a device at all in my
> case. Although now I've just managed to succeed in getting my ATI Remote
> Wonder Plus to work. My problem was that the ati_remote.ko kernel module
> was also loading by default with FC4. This is apparently a problem with
> all the ATI remotes - that lirc_atiusb.ko and ati_remote.ko must not
> both be in the kernel build direcory.
>
> Renaming ati_remote.ko to something else in the kernel-build directory &
> rebooting allowed lirc_atiusb to register the lirc device on major no.
> 61.
>
> I applied the patch located at http://raw-io.com/rwp/ manually (going
> through the file and altering the lines) to lirc_atiusb.c
>
> Then recompiled lirc. In my case there were 2 instances of
> lirc_atiusb.ko under the kernel-build directory - one inserted by
> compiling the source, and a second from a previous installation of lirc
> via yum. I had to copy the lirc_atiusb.ko from the directory where I
> compiled lirc over both of these before it worked. Now I have a fully
> functioning remote!
>
> Thanks for your help on this -- it's much appreciated!
>
> Aidan
>
>
> On Sun, 2006-04-09 at 17:09 -0500, Cymen Vig wrote:
> > On 3/15/06, Aidan Crook <Ai...@mi...> wrote:
> > > Am I right in thinking that the major is the 1st number after the dev=
ice
> > > name? If so, then there are no such devices! ??
> > >
> > > >ls -l | grep 61
> > > crw-rw----  1 root   tty      4,  61 Mar 13 19:44 tty61
> > >
> > > It's possible I have missed a line needed in one of the startup files=
.
> > > Everything that is present is mentioned in the original email.
> >
> > I missed your posts to the list so I apologize for the delay. Were you
> > able to get this working? My lirc device is /dev/lirc/0 and (perhaps
> > Gentoo specific), my /etc/conf.d/lircd has:
> > ---
> > # Options to pass to the lircd process
> > LIRCD_OPTS=3D"-d /dev/lirc/0"
> > ---
> >
> > Here are the fs details:
> >
> > ---
> > [screen] mythtv lirc # pwd
> > /dev/lirc
> > [screen] mythtv lirc # ls -al 0
> > crw-rw----  1 root root 61, 0 Apr  8 21:01 0
> > ---
> >
> > Regards,
> > Cymen
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting langua=
ge
> that extends applications into web and mobile media. Attend the live webc=
ast
> and join the prime developer group breaking into this new coding territor=
y!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=
=3D121642
>