Bug 600725

Works just fine for me... Can you give some hardware specifics please? Also, have to ask, did you do a 'chkconfig lirc on' after installing/configuring lirc?

(In reply to comment #1)
> Works just fine for me... Can you give some hardware specifics please? Also,
> have to ask, did you do a 'chkconfig lirc on' after installing/configuring
> lirc?    

I am using a Cyberlink remote control on a ThinkPad T42.  For more info on my setup, see: http://mandrivausers.org/index.php?/topic/93743-get-cyberlink-remote-working-w-mandriva-fedora/

Didn't know about 'chkconfig lirc on'.  Never had to use it before, but it seems to have done the trick.  I ran that command as root, rebooted, and my Cyberlink remote worked right off the bat.  Thanks!

(In reply to comment #2)
> (In reply to comment #1)
> > Works just fine for me... Can you give some hardware specifics please? Also,
> > have to ask, did you do a 'chkconfig lirc on' after installing/configuring
> > lirc?    
> 
> I am using a Cyberlink remote control on a ThinkPad T42.  For more info on my
> setup, see:
> http://mandrivausers.org/index.php?/topic/93743-get-cyberlink-remote-working-w-mandriva-fedora/

Okay, standard input layer device. For future reference, you don't need that custom lircd.conf, just use the lircd.conf.devinput config file from the lirc-remotes package (also found in lirc tarballs/cvs). Its also often better to use /dev/input/by-id/<something unique for your remote> versus /dev/input/eventX, as X can change.

> Didn't know about 'chkconfig lirc on'.  Never had to use it before, but it
> seems to have done the trick.  I ran that command as root, rebooted, and my
> Cyberlink remote worked right off the bat.  Thanks!    

Almost all daemons installed in Fedora are installed such that they require the user to explicitly enable them to run at system startup time -- no unexpected surprises from things running you didn't intend to have running. In any case, closing this, as its not a bug, but intended behavior.

(In reply to comment #3)
> Okay, standard input layer device. For future reference, you don't need that
> custom lircd.conf, just use the lircd.conf.devinput config file from the
> lirc-remotes package (also found in lirc tarballs/cvs).

There is no lirc-remotes package in /usr/share/lirc-remotes for my particular remote (Cyberlink or Topseed).

> Its also often better to use /dev/input/by-id/<something unique for your
> remote> versus /dev/input/eventX, as X can change.

You are correct about event numbers changing and I am using the following in /etc/sysconf/lirc to solve that issue (mentioned in post #5 of the link I posted previously).  Still it's good to know about a simpler method.  I will try your method soon.  Thanks for everything!

EV="/dev/input/event"$( grep -l 'TopSeed' /sys/class/input/input*/name | tail -n1 | cut -c 23 )

LIRCD_OPTIONS="-d $EV"

LIRC_DRIVER="devinput"

(In reply to comment #4)
> (In reply to comment #3)
> > Okay, standard input layer device. For future reference, you don't need that
> > custom lircd.conf, just use the lircd.conf.devinput config file from the
> > lirc-remotes package (also found in lirc tarballs/cvs).
> 
> There is no lirc-remotes package in /usr/share/lirc-remotes for my particular
> remote (Cyberlink or Topseed).

Yes, there is. :)

/usr/share/lirc-remotes/devinput/lircd.conf.devinput

This config file works for *all* LIRC_DRIVER="devinput" devices.

Note that gnome-lirc-properties would be able to set this up as well.

> Yes, there is. :)

> /usr/share/lirc-remotes/devinput/lircd.conf.devinput

> This config file works for *all* LIRC_DRIVER="devinput" devices.

OK, thanks.  I'll give that a try later.

> Note that gnome-lirc-properties would be able to set this up as well.

When I tried that in the past, it just messed everything up. I did not install it in F12 or F13.  Of course, things may have changed since I last tried it (in F11 I believe).