lirc stop working with new kernel 2.6.37

kikoloche · 2011-02-02 22:17:25

i have a hauppage hvr 1100 tv card.

Lirc was working perfectly with the ir remote supply by this card running kernel 2.6.36 with devinput driver on /dev/input/even4, but with new kernel 2.6.37 this device has disappeared, and lirc is not able to find it when then lircd daemon start.

any suggestion?

petelewis · 2011-03-04 22:25:16

Yeah, I found this too. Did you solve it?

Padfoot · 2011-03-05 20:03:06

Hi Kikoloche,

I am having a similar problem with a tv card remote. See this thread: https://bbs.archlinux.org/viewtopic.php?id=114549

My remote is being treated as a keyboard and I cannot work out how to get it going.

Have you run cat /proc/bus/input/devices to see if your remote is still being loaded?

I know with mine, even though support is built in to the kernel, I manually have to add an saa7134 modprobe option to change the card to 99 as my card type is not recognised by the kernel and udev automatically.

It could be with the latest update to the kernel that your card type is no longer recognised and just needs this little push.

Is it a pci card or usb? The output of dmesg will help in finding which kernel module it uses and www.linuxtv.org will help you find the modprobe options you might need to add for that module.

Hopefully we will both find our solutions.

Cheers.

Last edited by Padfoot (2011-03-05 21:15:32)

petelewis · 2011-03-05 20:43:22

Hi Padfoot,

You can stop X picking up the remote as a keyboard by adding the following to /etc/X11/xorg.conf.d/10-evdev.conf

Section "InputClass"
    Identifier     "no need for remote control to be picked up"
    MatchProduct   "Remote"
    Option         "Ignore" "on"
EndSection

You'll still need to get lirc working though, if you want to use that instead.

Padfoot · 2011-03-05 21:18:51

Hi Pete,

I have tried that. Here is my /etc/X11/xorg.conf.d/10-evdev.conf

#
# Catch-all evdev loader for udev-based systems
# We don't simply match on any device since that also adds accelerometers
# and other devices that we don't really want to use. The list below
# matches everything but joysticks.

Section "InputClass"
        Identifier "evdev pointer catchall"
        MatchIsPointer "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev keyboard catchall"
        MatchIsKeyboard "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev touchpad catchall"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev tablet catchall"
        MatchIsTablet "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev touchscreen catchall"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
    Identifier "ignore remote control"
    MatchProduct "saa7134 IR (AVerMedia TV Hybrid"
    Option    "Ignore" "on"
EndSection

and the output of cat /proc/bus/input/devices:

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: EV=40001
B: SND=6

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0001 Vendor=1461 Product=2c00 Version=0001
N: Name="saa7134 IR (AVerMedia TV Hybrid"
P: Phys=pci-0000:01:05.0/ir0
S: Sysfs=/devices/pci0000:00/0000:00:1e.0/0000:01:05.0/rc/rc0/input3
U: Uniq=
H: Handlers=kbd event3 
B: EV=100013
B: KEY=fc310 82140000 0 0 0 0 2148000 180 4001 9e0000 0 0 ffc
B: MSC=10

I: Bus=0003 Vendor=1532 Product=0105 Version=0110
N: Name="Razer Pro|Type Keyboard"
P: Phys=usb-0000:00:1d.2-2.2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2.2/4-2.2:1.0/input/input4
U: Uniq=
H: Handlers=kbd event4 
B: EV=120013
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=1532 Product=0105 Version=0110
N: Name="Razer Pro|Type Keyboard"
P: Phys=usb-0000:00:1d.2-2.2/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2.2/4-2.2:1.1/input/input5
U: Uniq=
H: Handlers=kbd event5 
B: EV=1f
B: KEY=837fff 2c3027 bf004444 0 0 1 c04 b27c000 267bfa d941dfed 9e0000 0 0 0
B: REL=40
B: ABS=1 0
B: MSC=10

Unfortunately, the remote is still being read as a keyboard.

Any suggestions?

Padfoot · 2011-03-05 21:48:25

Well, I have solved my issue.

The udev rule I used to map a consistent device node for my remote was not working. The symlink was created but not actually connected to the device.

I re-mapped lirc to use the event directly and my remote is now working.

Now to just get the consistent node working (as I sometimes have a mouse and keyboard attached and sometimes i don't so the event mapped to the remote does change).

Thanks for your assistance.

petelewis · 2011-03-06 00:48:01

What udev rule are you using? I'm using this one to map whatever /dev/input/event* to /dev/input/irremote:

KERNEL=="event*",ATTRS{vendor}=="0x8086",SYMLINK="input/irremote"

which is in /etc/udev/rules.d/10-local.rules.

You can get the right vendor code to match against by doing something like:

udevadm info -a -p $(udevadm info -q path -n /dev/input/event12) |grep vendor

which, for example, for me shows:

ATTRS{vendor}=="0x8086"
ATTRS{subsystem_vendor}=="0x104d"

HTH.

(Don't forget you'll need to reboot or reload your udev rules at least.)

Padfoot · 2011-03-06 00:57:09

Hi Pete,

That is the same udev rule I had, of course details changed for my remote.

It just isn't working. All good now though, I have lirc mapped directly to /dev/input/by-path which, for now, appears to be static.

Cheers.

kikoloche · 2011-04-20 07:56:36

I solved the problem instaling kernel 2.6.68 and uninstaling lirc package, but not lirc-utils package.

Thanks a lot

Arch Linux

#1 2011-02-02 22:17:25

lirc stop working with new kernel 2.6.37

#2 2011-03-04 22:25:16

Re: lirc stop working with new kernel 2.6.37

#3 2011-03-05 20:03:06

Re: lirc stop working with new kernel 2.6.37

#4 2011-03-05 20:43:22

Re: lirc stop working with new kernel 2.6.37

#5 2011-03-05 21:18:51

Re: lirc stop working with new kernel 2.6.37

#6 2011-03-05 21:48:25

Re: lirc stop working with new kernel 2.6.37

#7 2011-03-06 00:48:01

Re: lirc stop working with new kernel 2.6.37

#8 2011-03-06 00:57:09

Re: lirc stop working with new kernel 2.6.37

#9 2011-04-20 07:56:36

Re: lirc stop working with new kernel 2.6.37

Board footer