http://qa.mandrakesoft.com/show_bug.cgi?id=3358
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |UNCONFIRMED
------- Additional Comments From [EMAIL PROTECTED] 2003-03-17 17:12 -------
Then it appears that devfs is broken, or something else.
devfsd-1.3.25-23mdk
Before installing lircd:
[EMAIL PROTECTED] dev]# ls -l /dev/li*
srw-rw-rw- 1 root root 0 Mar 15 10:35 /dev/lircd=
/dev/lirc:
total 0
[EMAIL PROTECTED] dev]# urpmi lirc
installing
/var/cooker/ftp.orst.edu/.1/mandrake-devel/cooker/cooker/Mandrake/RPMS/lirc-0.6.6-1mdk.i586.rpm
Edited /etc/sysconfig/lirc to use pinsys, serial and COM2:
# Customized setings for lirc daemon
# The hardware driver to use, run lircd --driver=? for a list
DRIVER=pinsys
# Hardware driver module to load
HWMOD=serial
# The device node that communicates with the IR device.
# with devfs enabled
DEVICE=/dev/lirc/1
#DEVICE=/dev/lirc/serial
# without devfs
#DEVICE=/dev/lirc
# Serial port for the receiver (for serial driver)
# COM1 (/dev/ttyS0)
#COM_PORT=/dev/ttyS0
#DRIVER_OPTS="irq=4 io=0x3f8"
# COM2 (/dev/ttyS1)
COM_PORT=/dev/ttyS1
DRIVER_OPTS="irq=3 io=0x2f8"
<save>
# /etc/rc.d/init.d/lircd start
Starting Linux Infrared Remote Control daemon: [ OK ]
/var/log/messages:
Mar 17 09:58:09 backend2 lircd 0.6.6[7173]: lircd(any) ready
Mar 17 09:58:09 backend2 lircd: lircd startup succeeded
[EMAIL PROTECTED] dev]# ls -l li*
srw-rw-rw- 1 root root 0 Mar 15 10:35 lircd=
lirc:
total 0
[EMAIL PROTECTED] dev]#
[Note that there is no symlink in /dev/lirc/1 back to ttyS1]
[EMAIL PROTECTED] mythtv]$ irw
[Immediately returns]
Mar 17 10:00:10 backend2 lircd 0.6.6[7173]: accepted new client on /tmp/.lircd
Mar 17 10:00:10 backend2 lircd 0.6.6[7173]: readlink() failed for "/dev/lirc/1"
Mar 17 10:00:10 backend2 lircd 0.6.6[7173]: No such file or directory
Mar 17 10:00:10 backend2 lircd 0.6.6[7173]: could not create lock files
Mar 17 10:00:10 backend2 lircd 0.6.6[7173]: caught signal
[EMAIL PROTECTED] dev]# /etc/rc.d/init.d/lircd status
lircd dead but subsys locked
[EMAIL PROTECTED] dev]# cd lirc
[EMAIL PROTECTED] lirc]# ls -l
total 0
[EMAIL PROTECTED] lirc]# ln -sf ../ttyS1 1
[EMAIL PROTECTED] lirc]# ls -l
total 0
lr-xr-xr-x 1 root root 8 Mar 17 10:02 1 -> ../ttyS1
[EMAIL PROTECTED] lirc]# /etc/rc.d/init.d/lircd restart
Stopping Linux Infrared Remote Control daemon: [FAILED]
Starting Linux Infrared Remote Control daemon: [ OK ]
[EMAIL PROTECTED] lirc]#
[EMAIL PROTECTED] mythtv]$ irw
000000000000001a 00 middle PinnacleSysPCTVRemote
000000000000003f 00 Chan+Play PinnacleSysPCTVRemote
000000000000002f 00 Power PinnacleSysPCTVRemote
Mar 17 10:08:49 backend2 lircd 0.6.6[7366]: accepted new client on /tmp/.lircd
Mar 17 10:08:49 backend2 lircd 0.6.6[7366]: could not create lock file
"/var/lock/LCK..1"
Mar 17 10:08:49 backend2 lircd 0.6.6[7366]: File exists
Mar 17 10:08:49 backend2 lircd 0.6.6[7366]: tts/1 is locked by PID 7366
[ie, it works.]
So, I maintain that something is not correct; lirc did not work until I manually
created the
symlink in /dev/lirc/ from /dev/ttyS1 to /dev/lirc/1
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date:
description:
I have a pinnacle systems "dumb" IR receiver which connects to the COM1 / COM2 serial
port.
The example /etc/sysconfig/lircd file gives the user no indication that they need to
create a
symlink between the actual tty device and the /dev/lirc entry.
Here's a working example:
# Customized setings for lirc daemon
# The hardware driver to use, run lircd --driver=? for a list
DRIVER=pinsys
# Hardware driver module to load
HWMOD=serial
# The device node that communicates with the IR device.
# with devfs enabled
DEVICE=/dev/lirc/1
<snip>
[EMAIL PROTECTED] dev]# ls -l /dev/lirc/1
lr-xr-xr-x 1 root root 10 Mar 15 21:48 /dev/lirc/1 -> /dev/ttyS1
It took me about 2 hours to figure this out. I recommend that the lircd file be a
little more
verbose with examples.
Here is an updated /etc/sysconfig/lircd file that I think explains things better.
(Note that the symlink is created correctly when manually installing lirc from a
tarball because
the lirc configure program does this as a part of the installation process)
[EMAIL PROTECTED] sysconfig]# cat lircd
# Customized setings for lirc daemon
# The hardware driver to use, run lircd --driver=? for a list
DRIVER=UNCONFIGURED
# Hardware driver module to load
# Choices are:
# serial
# lirc_serial (for home-brew serial port IR receivers)
# lirc_parallel
# etc. See /lib/modules/{kern-version}/kernel/3rdparty/lirc for a
# list of modules.
HWMOD=UNCONFIGURED
# The device node that communicates with the IR device.
# If you are using a serial device, create a symlink between the actual
# hardware device and the /dev/lirc/ entry
# Example for receiver connected to COM1
# <as root># cd /dev
# <as root># ln -sf ttyS0 lirc/0
# or <as root># ln -sf ttyS0 lirc/serial
# If you are using devfs, use one of the following and create the symlink
# as shown above
# DEVICE=/dev/lirc/0
# DEVICE=/dev/lirc/serial
# Without devfs:
# If you are using a serial device, create a symlink between the actual
# hardware device and the /dev/lirc entry
# Example for receiver connected to COM1
# <as root># cd /dev
# <as root># ln -sf ttyS0 lirc
# DEVICE=/dev/lirc
# Serial port for the receiver (for serial driver)
# COM1 (/dev/ttyS0)
#COM_PORT=/dev/ttyS0
#DRIVER_OPTS="irq=4 io=0x3f8"
# COM2 (/dev/ttyS1)
#COM_PORT=/dev/ttyS1
#DRIVER_OPTS="irq=3 io=0x2f8"
# COM3 (/dev/ttyS2)
#COM_PORT=/dev/ttyS2
#DRIVER_OPTS="irq=4 io=0x3e8
# COM4 (/dev/ttyS3)
#COM_PORT=/dev/ttyS3
#DRIVER_OPTS="irq=3 io=0x2e8"
