First of all I'd like to say that I'm really gald that things cleared up
really quickly in this thread.
John, I certainly accept you apology. Actually I'm doing this job way to
long to become insulted, but I must admit that I was a bit astonished by
your reaction. ;)
John Risby "john@..." wrote:
> Firstly, I've past the last few lines of the log file here.
> Secondly, and more importantly, who are you and what is your connection
> to this project? Having searched the archives I've noticed a few
> messages from you along the lines of "RTFM", and I'd class this
> response in a similar manner - "tail /var/log/lircd" - without even a
> "hi" is, frankly, down right rude.
Just some words of explanation why my answers tend to be, err, quite
brief. I'm doing the work for this project in my free time. Lately,
related to my current job, my free time has become really scarce.
Nevertheless I try answering all mails related to this project. But this
is only possible if I come directly to the point. While throwing a "tail
/var/log/lircd" in your direction might not be very polite, I think it was
enough to push you in the right direction.
> Jan 21 13:43:20 devsys lircd-0.6.4: could not get hardware features
> Jan 21 13:43:20 devsys lircd-0.6.4: this device driver does not support
> the new LIRC interface
> Jan 21 13:43:20 devsys lircd-0.6.4: make sure you use a current version
> of the d river
> Jan 21 13:43:20 devsys lircd-0.6.4: caught signal
Looks like /dev/lirc is still a link to the ttySx that you use to connect
the Silitek receiver. To use the transmitter, you need the lirc_serial
module. This is interfaced by a character device.
rm /dev/lirc && mknod /dev/lirc c 61 0