Greg Woods wrote:
On Tue, 2005-11-15 at 19:49 -0500, dave sailer wrote:
Yea, for me, the /dev/lirc/0 char device file just dissappears.
I presume you did at least check to make sure lircd was running? If so,
try running something like "lsof -c lircd" to see what device files it
has open.
--Greg
------------------------------------------------------------------------
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
mmm. I thought the loading of the module (lirc_i2c) created the device
file and then once created you specify that device to lircd like...
lircd -d /dev/lirc/0
I didn't know about lsof though - thanks, In fact had to emerge it.
results are...
myth1 ~ # lsof -c lircd
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
lircd 5972 root cwd DIR 8,3 4096 128 /
lircd 5972 root rtd DIR 8,3 4096 128 /
lircd 5972 root txt REG 8,3 65032 83969178 /usr/sbin/lircd
lircd 5972 root mem REG 8,3 1440788 421456995
/lib/libc-2.3.5.so
lircd 5972 root mem REG 8,3 106008 421457047 /lib/ld-2.3.5.so
lircd 5972 root 0u CHR 1,3 8 /dev/null
lircd 5972 root 1u CHR 1,3 8 /dev/null
lircd 5972 root 2u CHR 1,3 8 /dev/null
lircd 5972 root 3u REG 8,3 5 536871619
/var/run/lircd.pid
lircd 5972 root 4u unix 0xc31070e0 209882 /dev/lircd
lircd 5972 root 5u unix 0xc409ad80 209896 socket
with lircd running the modules are loaded but nothing using them..
myth1 etc # lsmod | grep -i lirc
lirc_i2c 8836 0
lirc_dev 12996 1 lirc_i2c
if I "modprobe -r lirc_i2c" and then "modprobe lirc_i2c" I see in the log..
Nov 16 03:10:16 [kernel] lirc_dev: IR Remote Control driver registered,
at major 61
but still only have
myth1 ~ # ll -d /dev/lirc*
srwxrwxrwx 1 dsailer lirc 0 Nov 16 02:48 /dev/lircd
prwxrwxrwx 1 dsailer lirc 0 Nov 14 13:28 /dev/lircm
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
