Re: remote control support

Am Tuesday 12 April 2005 22:35 schrieb Zsolt Rizsanyi:
> [email protected] wrote:
> > I guess I don't understand. I have the remote communicating with my
> > box. If
> >  I
> > run irw, I can see the output. I have irkick running, but there's
> > nothing to
> > configure. There's nothing listed in the controller functions box and my
> > remote doesn't show up as a loaded extension. I've search everywhere and
> > cannot find a kdelirc program, config file, or anything. I have kde-base
> > installed.
>
> irkick is part of kdelirc suite (there is the config dialog too, which is a
> separate program) so I was talking about that.
> If you don't have anything to configure in the kdelirc configuration that
> means, that your remote is not supported with it.
> You could easily write a new remote definition file for kdelirc based on
> one existing one in /usr/share/apps/remotes/.
> If you have kernel 2.6 and you are using the linux-input-layer with lirc,
> then I can send you my remote config file for that.
> If you encounter any problems then you could contact the kdelirc maintainer
> for help (he may be able to create the definition file based on your
> lircd.conf).

Well, I have this problem too and filed already a related bug report:
http://bugs.kde.org/show_bug.cgi?id=103668
after some digging in the code and creating a hauppauge remote definition for 
the linux-input-layer. I wouldn't mind comparing it with yours, preferably 
combined with your /etc/lircd.conf..

Unfortunately, Gav hasn't replied to it, and I refrained from bugging him 
directly. Is there a related ML for such problems, which seem not that 
uncommon, as I already know from somebody else, that he can reproduce this 
problem, but hasn't an idea either: Gerd "Mr. BTTV et.al." Knorr. 

I predict, that when SuSE 9.3 ships, all those with a Hauppauge WinTV, who try 
to use irkick will complain... 

Funny is, in some (rare) tries, it works.

BTW, are you able to select certain buttons directly via your remote when 
adding actions? Does your key list contain all keys defined in /etc/lircd?

Unfortunately, both answers are negative here :-(

Cheers,
Pete