I have been fooling with lirc a bit.
Run lircd with the -n option to prevent forking daemon; you may get more information on what the problem is. You may also want to specify the -d option for the device.
Also, when you modprobe the creative lirc driver, you may need to specify io and irq, at least that is what I had to do with the irda driver.
gl
--)> oRiGiNaL MeSsAgE
From --)> David Huerta <huertanix@gmail.com>
Date --)> Thu, 26 Aug 2004 13:36:32 -0700
Subject --)> lirc issues
> 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
>
> --
> .dh
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
>
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)