On Wed, Sep 22, 2004 at 05:57:14PM +0200, Alien wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> thanks for all the help, i believe i have found it,
> it appeared to be a problem with the mandrake patches in the kernel and
> programs, it must try to read from /tmp/.lircd instead of /dev/lircd, so i
> removed the fifo and made a symlink to /tmp/.lircd instead
> thanks for all the help...
This is in the FAQ :-)
> Op woensdag 22 september 2004 15:58, schreef Roeland Moors:
> > On Wed, Sep 22, 2004 at 03:10:21PM +0200, Roeland Moors wrote:
> > > > yes, the lircd deamon is running
> > >
> > > If the lirc modules are loaded and the lircd deamon is running
> > > and you have fulll permissions to /dev/lircd then I'm out of
> > > ideas.
> > >
> > > You could try starting lircd in debug mode, check log files, ...
> > >
> > > I'm thinking of creating a test script to test all of the above.
> > > This could be usefull for more people with trouble.
> > >
> > > I'll post a message if it's finished.
> > I created a small test script:
> > http://rlirc.rubyforge.org/lirc_test.rb
> > You need ruby installed.
> > Don't shoot me if the script doesn't works.
> > It's quick and uggly code.
> - --
> AL13N is my name and head-biting is my game
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> -----END PGP SIGNATURE-----
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php