Comment 19 for bug 125384

It seems we don't need lirc_gpio anymore.

I've followed the steps found at http://bugs.archlinux.org/task/7660?pagenum=11 and http://www.sthoughts.com/?p=332 to make it working. However, we should find a plug-and-go solution to this.

First, unload lirc_dev, lirc_gpio, bttv. Then create this file: /etc/modprobe.d/bttv with this contents:

alias char-major-81 videodev
alias char-major-81-0 bttv
options bttv card=6 radio=1 pll=1 tuner=5

This will cause the remote work with dev/input interface. If you load the bttv module you will see now the new input entry:

I: Bus=0001 Vendor=1461 Product=0004 Version=0001
N: Name="bttv IR (card=6)"
P: Phys=pci-0000:02:03.0/ir0
S: Sysfs=/class/input/input14
U: Uniq=
H: Handlers=kbd event6
B: EV=100003
B: KEY=40fc310 82140000 0 0 0 0 2048000 180 4001 9e0000 0 0 ffc

This is, the remote is now working from /dev/input/event6. We need to say this to lirc. In /etc/lirc/hardware.conf:

DRIVER="dev/input"
DEVICE="/dev/input/event6"
MODULES="lirc_dev"

You can also create a udev rule to make this more consistent:

/etc/udev/rules.d/10-lirc.rules:
SUBSYSTEM=="input", ATTR{dev}=="13:70", NAME="input/irdev"

Look at the major:minor numbers of your event file to make sure the minor number is 70. It's known that some people have a minor number of 72. Some programs like irkick will need this file to be /lirc/lircX, as /dev/lirc0 to work properly.

Then invoke-rc.d lirc restart, and the remote should work now. As said in that page, it works but you will need a new lircd.conf. I've recorded a new one using irrecord, and it's attached to this post.

Everything is working now, but that was... nearly crazyness!! We need to easy this to final users.