http://qa.mandrakesoft.com/show_bug.cgi?id=3358
------- Additional Comments From [EMAIL PROTECTED] 2003-03-17 22:24 -------
More information:
>From a fresh reboot.
Mar 17 11:57:00 backend2 lircd 0.6.6[2568]: lircd(any) ready
Mar 17 11:57:00 backend2 lircd: lircd startup succeeded
Mar 17 11:57:00 backend2 lircd 0.6.6[2568]: accepted new client on /tmp/.lircd
Mar 17 11:57:00 backend2 lircmd: lircmd startup succeeded
Mar 17 11:57:00 backend2 lircd 0.6.6[2568]: readlink() failed for "/dev/lirc/serial"
Mar 17 11:57:00 backend2 lircd 0.6.6[2568]: No such file or directory
Mar 17 11:57:00 backend2 lircd 0.6.6[2568]: could not create lock files
Mar 17 11:57:00 backend2 lircd 0.6.6[2568]: caught signal
[EMAIL PROTECTED] dev]# ls -l li*
srw-rw-rw- 1 root root 0 Mar 17 05:50 lircd=
prw-r--r-- 1 root root 0 Mar 17 11:52 lircm|
# 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"
Using the "serial" driver, no /dev/lirc/serial directory was created by devfs -
because serial is
compiled into the kernel?
When I reboot, and re-run with driver=lirc_serial, devfs does the right thing and
creates a
device, but apparently this is the wrong driver for the pinnacle systems remote, which
needs
just standard access to the serial port?
Anyway, the only way I can get this to work is to manually create a symlink in
/dev/lirc/
pointing back to the actual COM port I'm connected to and by using the "serial" vs.
"lirc_serial" HWMOD.
Thanks.
------- 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"
