It is quite likely that your lirc device file has just moved to /dev/lirc instead of
/dev/lirc/0. You can use -d <correct device> to fix the problem, and edit your init
scripts accordingly. On my system, this device changes for no reason sometimes. What I
did is add a simple
if [ -e /dev/lirc/0 ]; then
To my /etc/init.d/lirc. Its a bit ugly, but works fine.
Mon, 20 Jun 2005 20:23:03 -0400 | Robert La Ferla <robertlaferla@...>
> I had a bad link to my kernel source but even with the corrected link,
> rebuild+install of lirc and reboot, it doesn't work. Is there a debug
> switch so I can better diagnose the problem? BTW lircd shows up in my
> chkconfig but lircd doesn't seem to be running after system startup. If
> I run it manually, using sh /etc/rc.d/init.d/lircd start, it starts up
> but doesn't do anything. This was working fine under 2.6.11-7.
> EC wrote:
> >Sun, 19 Jun 2005 22:12:14 -0400 | Robert La Ferla <robertlaferla@...>
> >>My lirc serial stopped working after upgrading to 2.6.12. I did a fresh
> >>cvs update, configure and make install AFTER installing the new kernel.
> >>How can I diagnose the problem? Anyone have lirc working on 2.6.12 and
> >>Fedora Core 3?
> >I just updated to 2.6.12 with the same kernel options as before, and my lirc works
> >(Using mceusb though).
> 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_id=7477&alloc_id=16492&op=click