Module ir_common interfeers with lirc

[hexion]

Binary package hint: linux-source-2.6.17

Since 2.6.17 kernel (edgy's images and vanilla self-compiled kernels), theres a module called ir_common that provides a new "feature" to manage remote control's keys.

This makes, by default (live cd included), an echo of numbers keys on my remote control to the active window, and also opens "shutdown menu" when pressing to the shutdown button.

Ok, cool new feature, BUT the problem comes when trying to use lirc, as that module CANNOT be unloaded and interfeers with normal behaviour of lirc.

In example, if I configure button 1 to launch firefox, with kernel 2.6.15 and lirc running it will launch firefox, BUT with kernel 2.6.17 and lirc running it will launch firefox AND outputs the character 1 to the active window.

That module cannot be unloaded because it depends on bttv, and it's neccesary to make TV card work.

My TV card is an avermedia capture 98.

This bug is confirmed in dapper with 2.6.17 kernel compiled from kernel.org, and with edgy (default kernels in knot, knot2, knot3, beta, and RC1)

ir_common module is not a bug itself, it can be considered as a new feature, but it becomes an annoying bug when someone want to use lirc, so it should be unloaded when lircd process is running (or at least there should be a way to unload it manually)

[hexion (hexium)]

I've made the trick.

There's to do this in order to keep lirc users able to user lirc as in dapper:

In kernel source tree, edit this file:

drivers/media/common/ir-keymaps.c

It contains definitions of certain tv card remote controls. To avoid kernel catching remote control signals, there's to delete such definitions.

I've attached the file that made the trick with last edgy kernel.

When compiling kernel with new ir-keymaps.c, ir_common module is still present, but it wont do any harm to lirc users again.

When kernel.org provides a way to change functions to remote control keys (or even deactive it), ubuntu should come back to use their ir-keymaps.c archive.

[Patrick Dixon (patrick-dixon)]

This is a major pita for anyone wanting to install mythtv on ubuntu.

I really don't want to have to build a new kernel!

[Leann Ogasawara (leannogasawara)]

This bug was reported a while ago and there hasn't been any recent activity. Just curious if someone can confirm if this is still an issue with the latest Hardy Heron 8.04 Alpha release: http://www.ubuntu.com/testing ? The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. We'll keep this report open against the actively developed kernel bug against 2.6.17 this will be closed as it does not qualify for a stable release update. Thanks.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Simon Harrison (simon-harrison1)]

Sorry I'm new here so forgive any etiquette slips.

I can confirm that in Hardy 8.04 and 8.04.1 i386 Desktop LTS, this behaviour does NOT happen. When LIRC is not loaded, the common buttons (0-9, ESC, Return, Mute, Vol +/-) are passed to the kernel. When LIRC is loaded, they are passed to the correct apps as defined in lircrc.
HTH

[Leann Ogasawara (leannogasawara)]

Thanks for the update Simon. It would seem this is resolved with Hardy. I'm marking this "Fix Released" then. Thanks.

[Paul McCormack (dibble5504)]

Not so fast! I am using 2.6.24 (latest Hardy updates) but I have this problem. As other users report, this is a major deal for MythTV users as it makes the remote practically useless. I'm waiting for the Ibex release next week in the hope that it is fixed with the new release, but I'm concerned that this bug has been marked as fixed when it isn't working for me.

[Liam O'Reilly (aliam13-2)]

I am new to MythTV and are trying to get a nice setup. Trying to get my rmeote to work is a nightmare. Soem buttons work such as 1..9, vol+/- power, mute and play - i believe these are being handled by ir_common. I have followed the tutorials for getting lirc to work, but it cannot get exclisive access to the event driver /dev/input/event6 in my case.

I am using Ubuntu 8.10 output of "uname -a" is
Linux mypc 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 GNU/Linux

I believe this is still a bug that is not fixed.

[Paul McCormack (dibble5504)]

Liam, I managed to fix mine by following this guide:
http://ubuntuforums.org/showthread.php?t=183545

The only problem now is that the remote works intermittently (about one in four presses). I believe that this is a kernel timing issue as stated here:
http://forums.whirlpool.net.au/forum-replies.cfm?t=566843&p=3#r54

I haven't tried that yet so I cannot confirm if this completes the solution.

Paul

[itchy8me (itchy8me)]

module ir_common is still loaded by default in kernel 2.6.32-23-server (ubuntu lucid). Lirc still not usable when its loaded. blacklisting ir_common in blacklist.conf and then reinstalling lirc worked for me.

[Unkraut (unkraut2)]

This issue is still present in Maverik.
Blacklisting ir_common does not work for me (using saa7134). The only solution seems to fiddle around in the kernel. Not very nice! Is there any more viable solution?

[Paul McCormack (dibble5504)]

 I purchased a USB remote in the end. Worked out of the box.

***Paul McCormack* | <email address hidden> |
http://www.paulmccormack.com

Feed <feed://http:/www.paulmccormack.com/feed>blankicon_linkedin
<http://au.linkedin.com/in/paulmccormack>blankTwitter-icon
<http://twitter.com/dibble5504>blankgoogle-icon
<http://www.google.com/profiles/paullymac>blankYouTube_icon
<http://www.youtube.com/dibble5504>jabber-icon
<xmmp:<email address hidden>>google-talk-icon
<gtalk:chat?<email address hidden>>blankskype-icon <callto:dibble5504>

On 25/09/2010 7:26 AM, SimonW wrote:
> This issue is still present in Maverik.
> Blacklisting ir_common does not work for me (using saa7134). The only solution seems to fiddle around in the kernel. Not very nice! Is there any more viable solution?
>

[Tom (brommage)]

Hello!
I am Julia, I am 27 y.o.
I search for boy-friend.
My photos and new message for you here:

http://hotbrides.ru