(Sorry to be posting this in instalments.)
The problem with the daemon turned out to be a combination of mandrake's
lockfile not being removed, and changing the device from the
original /dev/lirc/0 to /dev/ttyS1.
The voltage on my receive diode is something under 5 volts (a bit less than
half a volt below Vcc on a digital multimeter) and drops about half a volt
DC on receipt of data (I haven't got a CRO,) but nothing shows on mode2, and
irrecord to a new file times out. This is using the Samsung remote and a
module for a different Samsung DVD remote. I also tried irrecord
specifically using the existing lirc.conf file and pressing buttons did
nothing. Gmplayer and xmms still show connection refused. lircd still dies
as soon as it starts, which would explain that. lsmod mentions lirc_serial
used by 0. My /etc/sysconfig/lircd is as follows:
# Customized setings for lirc daemon
# The hardware driver to use, run lircd --driver=? for a list
# Hardware driver module to load
# The device node that communicates with the IR device.
# if you are using lirc_serial, set DEVICE to /dev/ttyS[0-9]
# where 0-9 is the serial port your IR receiver is plugged
# with devfs enabled
# without devfs
# Serial port for the receiver (for serial driver)
# COM1 (/dev/ttyS0)
# COM2 (/dev/ttyS1)
# COM3 (/dev/ttyS2)
# COM4 (/dev/ttyS3)
On Fri, 29 Jul 2005 10:33 pm, Doug Laidlaw wrote:
> Further to what I have already written, I discovered that my transceiver
> had missed the motherboard header pins. I have now fixed that, but:
> (a) Windows keeps telling me that I have two devices blocking each other;
> (b) the daemon starts then exits
> (c) Even with the daemon not running, I have two device files:
> lirc0 and lircm (which has a | (pipe symbol) following it).
> (d) trying irrecord, there is no input, with either my generic remote or a
> Samsung one from the family DVD player.
> On Fri, 29 Jul 2005 7:35 pm, Doug Laidlaw wrote:
> > I have LIRC almost working. I am running Mandrake LE 2005 and installed
> > the LIRC and LIRC-modules packages with their dependencies. I then
> > followed the Mandrake HOWTO as far as I could. My motherboard has a
> > 5-pin header. My interface is from a magazine kit based on the
> > surface-mount TFDS4500 from Vishnay Telefunken. My remote is a
> > replacement unit with no markings whatever.
> > According to the instructions, the BIOS redirects COM2 to the header. I
> > have the icon showing in the system tray under Win98 SE.
> > Following the HOWTO, it seems that Iin /etc/sysconfig/lircd, I should set
> > the HOWTO's
> > # Serial port for the receiver (for serial driver)
> > COM_PORT=/dev/ttyS0
> > DRIVER_OPTS="irq=4 io=0x3f8"
> > to /dev/ttys1 with appropriate parameters, which I have done. (it is just
> > a matter of uncommenting the appropriate lines.)
> > The comments about the DEVICE= line say that it too should be set
> > to /dev/ttyS1, but Mandrake had already set it to
> > # with devfs enabled
> > DEVICE=/dev/lirc/0
> > so I left it like that.
> > I can get the lircd daemon to run, but I then disabled it to run the test
> > with "mode2". This made the device disappear from /dev .
> > If I run "irw" while the daemon is running, I get no output to the
> > terminal (before, there was an error message.)
> > The only app that I know looks for IRC support is mplayer. It still
> > says:
> > Setting up LIRC support...
> > mplayer: could not connect to socket
> > mplayer: Connection refused
> > Failed to open LIRC support.
> > It sounds as though I have the basics working. What is the next step?
> > Doug.
ICQ Number 178748389. Registered Linux User No. 277548.
The place to improve the world is first in one's own heart and head and hands.
- Robert M. Persig