Greg Vickers wrote:
Hi Andrew,
Andrew Sackville-West wrote:
On Sun, Sep 23, 2007 at 05:14:36PM +1000, Greg Vickers wrote:
Hi all,
I'm trying to get lirc to work with my Hauppauge on my Debian installation
on AMD64. I've used module assistant to create the lirc kernel modules and
the modules install and modprobe successfully:
# lsmod | grep lirc
lirc_i2c 14980 0
lirc_dev 20264 1 lirc_i2c
i2c_core 27776 6
lirc_i2c,cx88xx,bttv,i2c_algo_bit,tveeprom,i2c_nforce2
relevant logs from the module insertion would be good. ON my knoppmyth
box all these modules produce pretty copious and useful output.
# grep lirc /var/log/messages | tail
Sep 24 08:10:19 wushu kernel: lirc_dev: IR Remote Control driver
registered, at major 61
Sep 24 08:10:19 wushu kernel: lirc_i2c: no version for
"lirc_unregister_plugin" found: kernel tainted.
# dmesg | grep lirc
lirc_dev: IR Remote Control driver registered, at major 61
lirc_i2c: no version for "lirc_unregister_plugin" found: kernel tainted.
A bit of a dearth of log information :(
Once the modules are loaded, I can't talk to the /dev/lirc file with mode2
or anything else, so I think there may be something wrong with the udev
rules, the only entry I can find is in the /etc/udev/permissions.rules
file:
KERNEL=="lirc[0-9]*", GROUP="video"
what device nodes are created?
# ll /dev/lirc*
crw-rw---- 1 root root 61, 0 2007-09-23 16:27 /dev/lirc
srw-rw-rw- 1 root root 0 2007-09-23 16:22 /dev/lircd
prw-r--r-- 1 root root 0 2007-09-23 16:22 /dev/lircm
But lirc dissappears after a reboot, and sometimes lircd and lircm go as
well, until I remove the kernel modules package and reinstall. (?)
As I mentioned before, the device is now called /dev/lirc0, at least on my Etch
system. The fact that you see /etc/lirc may imply that you have an old, or
non-debian version of lircd, or at least an old version of the startup script,
/etc/lirc. As a test you could try manually replacing /dev/lirc in the startup
script with /dev/lirc0.
how are you taking to /dev/lirc?
With the lirc programs mode2 or irrecord, even though /dev/lirc is
present, these programs complain about:
mode2: error opening /dev/lirc
mode2: No such device
I'm not familiar with these programs, but they will also have to be reconfigured
to use /dev/lirc0 (if my previous suspicions are correct).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
