FS#29346 - [lirc] is not working after kernel upgrade 3.3.1-1

Attached to Project: Arch Linux
Opened by kiko loche (kikoloche) - Monday, 09 April 2012, 07:34 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 14 November 2012, 11:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Lirc is not working after kernel upgrade 3.3.1-1


Additional info:
* package version(s)
I have only lirc-utils 0.9.0-15 instaled
* config and/or log files etc.
cat /proc/bus/input/devices output:

I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="i2c IR (HVR 1110)"
P: Phys=i2c-1/1-0071/ir0
S: Sysfs=/devices/virtual/rc/rc0/input8
U: Uniq=
H: Handlers=kbd event8
B: PROP=0
B: EV=100013
B: KEY=10afc312 214201700000000 0 118000 41a800004801 9e16c000000000 10000ffc
B: MSC=10

my /etc/conf.d/lircd.conf:

#
# Parameters for lirc daemon
#

LIRC_DEVICE="/dev/input/event8"
LIRC_DRIVER="devinput"
LIRC_EXTRAOPTS=""
LIRC_CONFIGFILE="/etc/lircd.conf"

and /etc/lircd.conf is:

# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.9.0(devinput) on Mon Aug 1 16:42:59 2011
#
# contributed by
#
# brand: devinput
# model no. of remote control:
# devices being controlled by this remote:
#

begin remote

name devinput
bits 56
eps 30
aeps 100

one 0 0
zero 0 0
pre_data_bits 8
pre_data 0x0
gap 106662
toggle_bit_mask 0x0

begin codes
key_power 0x0400040000003D
key_home 0x0400040000003B
key_tv 0x0400040000001C
key_video 0x04000400000018
key_audio 0x04000400000019
key_info 0x0400040000001B
key_up 0x04000400000014
key_ok 0x04000400000025
key_left 0x04000400000016
key_radio 0x0400040000000C 0x01018100000001
key_right 0x04000400000017
key_down 0x04000400000015
key_back 0x0400040000001F 0x01017900000001
key_menu 0x0400040000000D 0x01007100000001
key_volumeup 0x04000400000010 0x01007300000001
key_volumedown 0x04000400000011 0x01007200000001
key_previous 0x04000400000012
key_mute 0x0400040000000F
key_channelup 0x04000400000020 0x01019200000001
key_channeldown 0x04000400000021 0x01019300000001
key_record 0x04000400000037
key_stop 0x04000400000036
key_forward 0x04000400000034
key_rewind 0x04000400000032
key_play 0x04000400000035
key_pause 0x04000400000030
key_previoussong 0x04000400000024
key_nextsong 0x0400040000001E 0x01018E00000001
key_1 0x04000400000001 0x01000200000001
key_2 0x04000400000002 0x01000300000001
key_3 0x04000400000003 0x01000400000001
key_4 0x04000400000004 0x01000500000001
key_5 0x04000400000005 0x01000600000001
key_6 0x04000400000006 0x01000700000001
key_7 0x04000400000007 0x01000800000001
key_8 0x04000400000008 0x01000900000001
key_9 0x04000400000009 0x01000A00000001
key_0 0x04000400000000 0x01000B00000001
key_red 0x0400040000000B
key_blue 0x04000400000029
key_green 0x0400040000002E 0x01017400000001
key_yellow 0x04000400000038
end codes

end remote

Steps to reproduce:irw produces no output

This task depends upon

Closed by  Tobias Powalowski (tpowa)
Wednesday, 14 November 2012, 11:46 GMT
Reason for closing:  Not a bug
Comment by Alfredo Amatriain (amatriain) - Wednesday, 02 May 2012, 19:02 GMT
Lirc stopped working for me a while ago. IR remote drivers were moved to the kernel some time ago, that's what caused lirc to stop working for me. More info about the change here (very technical):

http://lwn.net/Articles/364515/

With the new in-kernel drivers lirc is no longer needed, and no daemon is needed to use our remotes. Assuming this is what's happening to you, you may find some useful and to the point information about how to use the new drivers instead of lirc in this thread:

http://forum.xbmc.org/showthread.php?tid=114124

Among other things, now you can use "ir-keytable -t" to see the commands your remote is sending, instead of irw.

I haven't found a good comprehensive guide for migrating from lirc to the new drivers anywhere, which is quite surprising.

Of course if your problem is unrelated to the new kernel drivers, ignore this post :)
Comment by Alexander F. Rødseth (xyproto) - Saturday, 08 September 2012, 22:36 GMT
Is this still a problem? The package is currently an orphan. Assigning to last packager.
Comment by Greg (dolby) - Monday, 15 October 2012, 10:03 GMT
Status with latest kernel?
Comment by Olivier (litemotiv) - Monday, 22 October 2012, 00:00 GMT
I ran into the same problem with lirc (Nuvoton driver) but can confirm that the new approach as mentioned by Alfredo above is a working alternative.

Loading...