Arch Linux

Correction:
point 3 above should read

3. output of ps axu |grep lirc
root 26142 0.0 0.0 22216 528 ? Ss 02:53 0:00 /usr/sbin/lircd -d /dev/lirc0

I can reproduce this with remote for Leadtek DTV2000DS, which is reported to be working with lirc here: http://www.linuxtv.org/wiki/index.php/Leadtek_WinFast_DTV2000DS#Remote_Control_Support_.282.29

gmesg | grep -i lirc:
lirc_dev: IR Remote Control driver registered, major 252
IR LIRC bridge handler initialized

My /var/log/lircd says:
Jan 25 00:53:15 hikari lircd: caught signal
Jan 25 09:03:16 hikari lircd: lircd(devinput) ready, using /var/run/lirc/lircd
Jan 25 09:18:51 hikari lircd: accepted new client on /var/run/lirc/lircd
Jan 25 09:18:51 hikari lircd: initializing '/dev/lirc0'
Jan 25 09:18:51 hikari lircd: unable to open '/dev/lirc0'
Jan 25 09:18:51 hikari lircd: WARNING: Failed to initialize hardware
Jan 25 09:18:54 hikari lircd: accepted new client on /var/run/lirc/lircd

What is the status on .37 series?

Don't know. I don't have .37 yet, not in my repos as I don't have testing. Any idea when it will hit the x64 repos? I'll see if I can test elsewhere other than on my mythtv box.

It does not work for me with .37-3 from testing. I got the same error messages in log, and the /dev/lirc0 is not created either.

But I am not certain, that I have it configured correctly. That is appart from configuration mention in the link (/etc/udev/rules.d/20-mythtv.rules, /etc/lirc/lirc.conf and /etc/lirc/hardware.conf) am I supposed to make any changes elswhere?
Now I looked at the /etc/rc.d/lircd and found it uses /etc/conf.d/lircd.conf file. If I modify it as follows:

#
# Parameters for lirc daemon
#

LIRC_DEVICE="/dev/input/dtv2000ds_remote"
LIRC_DRIVER="devinput"
LIRC_EXTRAOPTS=""
LIRC_CONFIGFILE=""

I no longer get failed to initialize hardware warning, instead I start to get:
Jan 25 16:37:08 hikari lircd: caught signal
Jan 25 16:37:09 hikari lircd: lircd(devinput) ready, using /var/run/lirc/lircd
Jan 25 16:37:19 hikari lircd: accepted new client on /var/run/lirc/lircd
Jan 25 16:37:19 hikari lircd: initializing '/dev/input/dtv2000ds_remote'
Jan 25 16:37:20 hikari lircd: removed client
Jan 25 16:37:20 hikari lircd: closing '/dev/input/dtv2000ds_remote'
Jan 25 16:37:28 hikari lircd: accepted new client on /var/run/lirc/lircd
Jan 25 16:37:28 hikari lircd: initializing '/dev/input/dtv2000ds_remote'
Jan 25 16:37:33 hikari lircd: WARNING: you are using an obsolete devinput config file: Success
Jan 25 16:37:33 hikari lircd: WARNING: get the new version at http://lirc.sourceforge.net/remotes/dev … f.devinput: Success
Jan 25 16:37:47 hikari lircd: removed client

I get the same with config file downloaded from suggested location and I still see nothing when running irw.
Now I am pretty lost with the configuration, so if you want me to test something else/set up something else, please tell me.

I am having the same problem as Nicky726 with lirc 0.9.0pre1 and kernels 2.6.36/37, which may be different from the original bug of emkamau (should we make a new bug?).

I also have a remote using the devinput driver (Haupauge Nova-T Dual) and get the same messages in my lircd log:

Jan 30 17:46:14 dingus lircd: lircd(devinput) ready, using /var/run/lirc/lircd
Jan 30 17:46:38 dingus lircd: accepted new client on /var/run/lirc/lircd
Jan 30 17:46:38 dingus lircd: initializing '/dev/input/by-path/pci-0000:02:07.2-
event-ir'
Jan 30 17:46:39 dingus lircd: WARNING: you are using an obsolete devinput config
file: Success
Jan 30 17:46:41 dingus lircd: WARNING: get the new version at http://lirc.source
forge.net/remotes/devinput/lircd.conf.devinput: Success

I can't get any response from irw with my "obsolete" config or the apparently new one. It is worth noting that the "WARNING: obsolete ..." message only seems to come up once a button is pressed on the remote so it must be triggered by something.

My system worked perfectly with kernel 2.6.35 & lirc 0.8.6-7 (to which I have subsequently downgraded and it still works), but does not work with 0.9.0pre1 & kernels 2.6.36/37.

A little googling tells me there were some major changes with lirc & kernels >2.6.36 and there is a thread on the lirc mailing list that looks like the same issue:
http://web.archiveorange.com/archive/v/Xn95Hb0Qpqy0rYlHmH1V
unfortunately there didn't seem to be any final resolution there and what there is is unfortunately slightly out of my depth at the moment. I would be happy to look further into this but could use a little advice.

Matt, could you post somewhere all your configuration of lirc, so that I can make sure I am not overlooking something? There is a related forum thread, sot that we do not post to much stuff here: https://bbs.archlinux.org/viewtopic.php?id=111902 Thanx in advance.

I've just updated to kernel26 2.6.38 and lirc 0.9.0.pre1-5 from testing. It seems there has been some progress in the kernel and my remote is now fully funtional, although I had to fiddle with some configs. I am using:

DRIVER="devinput"
DEVICE="/dev/input/by-path/{whatever}-event-ir" (could have made a udev rule for this to a create /dev/something)

and lircd.conf from /usr/share/lirc/remotes/devinput/lircd.conf.devinput (this is the only bit I had to change).

This issue is now resolved for me at least.