lirc is looking in the "old style" location for the lirc device. On devfs systems (most modern distros if not all running 2.4), the location is /dev/lirc/X where X is whichever device. As such, one can have multiple devices and multiple daemons. Read the docs and poke around lircd's init script and insert -D /dev/lirc/0 to tell it what device to look at. This is an old problem that seems not to have been touched recently. On Thu, 2004-08-26 at 13:36, David Huerta wrote: > Hello everyone, > > I've recently acquired an IR reciever/remote which I have set up on my > Slackware machine using LIRC. After looking at /var/log/lircd, I can > see that it is detecting the signals from my device just fine, but > that it cannot access /dev/lirc, which is strange, since /dev/lircd is > detected, modprobes picks lircd up, and I'm not used to seeing daemons > pose as physical devices. Any idea on what I should do? I'm fresh > out, and the documentation isn't terribly helpful. > > Here's the log: > > [time, name, proc, etc.]: caught signal > : lircd(creative) ready > : accepted new client on /dev/lircd > : readlink() failed for "/dev/lirc" > : No such file file or directory > : could not create lock files -- Bryce C CoBryce Communications