[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
http://qa.mandrakesoft.com/show_bug.cgi?id=3358
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution||FIXED
--- Additional Comments From [EMAIL PROTECTED] 2003-04-08 17:24 ---
Fixed in lirc-0.6.6-3mdk
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
--- 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: RESOLVED
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-x1 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
[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
http://qa.mandrakesoft.com/show_bug.cgi?id=3358
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDINFO
--- Additional Comments From [EMAIL PROTECTED] 2003-03-18 10:11 ---
There is absolutely no need to create a link for lircd to work..
just use DEVICE=/dev/ttySx in /etc/sysconfig/lirc
--- 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: NEEDINFO
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-x1 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
[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
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-18 15:38 ---
Directly specifying the DEVICE=/dev/ttyS0 works. Can the inline documentation in the
/etc/sysconfig/lirc file be expanded a little to include that as a possibility? I
posted a
recommended lirc file that was more verbose in the various options available, such as
telling
the user where the 3rd party modules were, etc.
So, in your comment #2 where you said that devfs would automatically create the device
when
the driver loads, that's true in all cases except for direct serial access because the
Mandrake
kernel has serial compiled into the source, correct?
--- 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-x1 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
[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
http://qa.mandrakesoft.com/show_bug.cgi?id=3358
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDINFO
--- Additional Comments From [EMAIL PROTECTED] 2003-03-18 15:54 ---
I'll add some stuff to the inline documentation in /etc/sysconfig/lirc..
But you are wrong about devfs.. Since you are not using a kernel driver for your
remote, devfs has absolutely no way to know it should create such a device (and
it doesn't need to..).. Having serial in the kernel doesn't affect devfs at all..
Your initial bug report was about a serial IR receiver so I guessed it needed
lirc_serial..
--- 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: NEEDINFO
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-x1 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
[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
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-18 15:59 ---
OK - If you're going to be changing the inline documentation in the
/etc/sysconfig/lirc file for the case where the user is using a serial port IR
receiver that doesn't require a kernel driver, then this bug can be closed out.
Many 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-x1 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
[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
http://qa.mandrakesoft.com/show_bug.cgi?id=3358
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDINFO
--- Additional Comments From [EMAIL PROTECTED] 2003-03-17 15:18 ---
What are you talking about ?
There is no need to create devices when using devfs..
It is doing that itself when drivers are loaded..
--- 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: NEEDINFO
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-x1 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
[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
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 root0 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 root0 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-x1 root root8 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 001a 00 middle PinnacleSysPCTVRemote 003f 00 Chan+Play PinnacleSysPCTVRemote 002f 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-x1 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
[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
http://qa.mandrakesoft.com/show_bug.cgi?id=3358
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDINFO
--- Additional Comments From [EMAIL PROTECTED] 2003-03-17 17:29 ---
Is lirc_serial loaded correctly ?
--- 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: NEEDINFO
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-x1 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
[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
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 18:48 ---
lirc_serial is apparently used for custom hardware that is attached to the COM ports;
when I
change serial in /etc/sysconfig/lirc to lirc_serial and restart lirc, devfs creates a
device in
/dev/lirc/ called serial, so that works ok, and lsmod shows lirc_serial loaded.
[EMAIL PROTECTED] dev]# ls -l li*
srw-rw-rw-1 root root0 Mar 15 10:35 lircd=
lirc:
total 0
crw---1 root root 61, 0 Dec 31 1969 serial
[EMAIL PROTECTED] dev]#
Mar 17 11:30:23 backend2 kernel: lirc_serial: auto-detected active high receiver
Mar 17 11:30:23 backend2 lircd 0.6.6[11247]: lircd(any) ready
Mar 17 11:30:23 backend2 lircd: lircd startup succeeded
[EMAIL PROTECTED] mythtv]$ irw
immediately exits
Mar 17 11:30:41 backend2 lircd 0.6.6[11247]: accepted new client on /tmp/.lircd
Mar 17 11:30:41 backend2 lircd 0.6.6[11247]: could not reset tty
Mar 17 11:30:41 backend2 lircd 0.6.6[11247]: caught signal
I don't believe that lirc_serial is the proper device driver for my hardware, and the
device that
it creates is a different major than ttyS1:
[EMAIL PROTECTED] dev]# ls -l ttyS1
lr-xr-xr-x1 root root5 Mar 15 04:33 ttyS1 - tts/1
[EMAIL PROTECTED] dev]# cd tts
[EMAIL PROTECTED] tts]# ls -l 1
crw-rw1 mythtv tty4, 65 Dec 31 1969 1
[EMAIL PROTECTED] tts]#
Note: the kernel that I'm using has standard serial manipulation built-in, not as a
module.
Linux backend2 2.4.21-0.13mdk #1 Fri Mar 7 06:31:12 CET 2003 i686 unknown unknown
GNU/Linux
Again, if I change lirc_serial to serial and create the symlink manually in lirc
everything works
again. The pinnacle doesn't use custom hardware, so lirc_serial isn't the correct
driver.
--- 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-x1 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
[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
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 root0 Mar 17 05:50 lircd=
prw-r--r--1 root root0 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-x1 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
[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
http://qa.mandrakesoft.com/show_bug.cgi?id=3358
--- Additional Comments From [EMAIL PROTECTED] 2003-03-17 23:30 ---
Viestissä Maanantai 17. Maaliskuuta 2003 23:24, rkulagow kirjoitti:
When compiling the kernel, it states:
#warning **
#warning Your serial port driver is compiled into
#warning the kernel. You will have to release the
#warning port you want to use for LIRC with:
#warning setserial /dev/ttySx uart none
#warning **
Is this done automatic? if not... should it...
Thomas
--- 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-x1 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
[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
http://qa.mandrakesoft.com/show_bug.cgi?id=3358
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution||INVALID
--- Additional Comments From [EMAIL PROTECTED] 2003-03-17 23:31 ---
Closing as Invalid, since there was no real bug here..
--- 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: RESOLVED
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-x1 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
[Cooker] [Bug 3358] [lirc] lirc not correctly creating symlinks for serial devices
http://qa.mandrakesoft.com/show_bug.cgi?id=3358
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID |
--- Additional Comments From [EMAIL PROTECTED] 2003-03-17 23:42 ---
I'm sorry, how is the fact that I need to manually create the symlink not a bug?
1) The pinnacle PCTV remote does not use lirc_serial
2) If I use HWMOD=serial, then no device gets created in /dev/lirc/, and I must
manually
create the symlink from /dev/ttySx to /dev/lirc/serial, otherwise lircd immediately
errors out
when the readlink call fails.
However, I'm not the packager, and you really feel that this isn't a bug, then I
certainly can't
force the issue. If you feel that this isn't a bug, then what is your recommended
solution to my
problem? Remember, when compiled from source, the lirc install routine _does_ create
a
symlink pointing to the device that you said the pinnacle receiver was on, ie ttyS0,
ttyS1, etc.
Thomas: the serial ports default to the status recommened when you compile from
source.
--- 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-x1 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
