Bug 1265 - lirc is not functional
Summary: lirc is not functional
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Anssi Hannula
QA Contact:
URL:
Whiteboard: MGA1TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-13 19:12 CEST by Gilles Mouchard
Modified: 2015-03-31 16:17 CEST (History)
6 users (show)

See Also:
Source RPM: lirc
CVE:
Status comment:


Attachments
Lirc setup (3.50 KB, text/plain)
2012-06-07 00:32 CEST, Derek Jennings
Details

Description Gilles Mouchard 2011-05-13 19:12:38 CEST
Description of problem:

IR support in Mageia does not seems functional at least with a Windows Media Center IR receiver plugged on USB.

A summary of my dmesg is:
Registered IR keymap rc-rc6-mce
input: Media Center Ed. eHome Infrared Remote Transceiver (2304:0225) as /devices/pci0000:00/0000:00:04.0/usb3/3-5/3-5:1.0/rc/rc0/input4
rc0: Media Center Ed. eHome Infrared Remote Transceiver (2304:0225) as /devices/pci0000:00/0000:00:04.0/usb3/3-5/3-5:1.0/rc/rc0
rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
mceusb 3-5:1.0: Registered Pinnacle Systems PCTV Remote USB on usb3:2

Doing cat /dev/lirc/0 as root do not output anything when pressing keys of the remote controller.
Hence after starting lircd doing '/etc/init.d/lircd start' and then 'irw /var/run/lirc/lircd' do not print anything.

Although lircd says in /var/run/syslog that it sucessfully open /dev/lirc/0, and that a client has connected, nothing more happens on both lircd side or client side.

My lirc configuration was fully functional on Mandriva 2009.0, 2009.1, 2010.0, 2010.1, 2010.2 (see attachments).
Don't know whether it's a kernel bug or an lirc bug.
The bug is very similar to that one in previous releases of Ubuntu: 

Version-Release number of selected component (if applicable):

0.8.7

How reproducible:



Steps to Reproduce:
1. cat /dev/lirc0 as root, then nothing is printed on the console, so even if the lircd daemon was started, it would not translate any remote controller keys to logical keys defined in /etc/lirc/lircd.conf
2.
3.
Ahmad Samir 2011-05-13 19:15:37 CEST

Assignee: bugsquad => anssi.hannula

Comment 1 Gilles Mouchard 2011-05-13 19:26:51 CEST
Sorry for the incomplete sentence in bug report.

The bug is very similar to that one in previous releases of Ubuntu: http://ubuntuforums.org/archive/index.php/t-1627289.html
Comment 2 Kristoffer Grundström 2011-05-19 16:53:42 CEST
There's a newer version avaliable for release: http://sourceforge.net/projects/lirc/files/LIRC/0.9.0/lirc-0.9.0.tar.bz2/download

CC: (none) => kristoffer.grundstrom1983

Comment 3 Derek Jennings 2011-06-08 12:33:31 CEST
dkms-lirc-0.8.7-1.mga1  does not build on kernel 2.6.38.7-desktop-1.mga

I rebuilt the rpm using lirc-0.9.0 which works fine.

CC: (none) => derekjenn

Comment 4 claire robinson 2011-06-30 12:33:05 CEST
Will this be updated? It is currently non functional in mga1 i586.

CC: (none) => claire

Comment 5 Anssi Hannula 2011-09-07 23:41:21 CEST
I'm sorry for the long delay.

Gilles, can you test whether your issue still present in Mageia 1?
If so, can you test updating your lirc package to 0.9.0, available in core/updates_testing repository of Mageia 1 (bug #2661)?

The dkms-lirc issue should be fixed by the update (see bug #2661). Note that dkms-lirc is not needed by most users anymore, as the kernel now includes most of the lirc modules.
Comment 6 Gilles Mouchard 2011-09-09 21:50:36 CEST
My issue is still present in Mageia.

I have enabled core/update_testing repository and installed kernel-desktop-2.6.38.8-5.mga and lirc-0.9.0
My issue still exists after the update and a reboot. Neither /dev/lirc0 nor /dev/lirc/0 return any data (obviously when lirc service is stopped).

On the boot screen, I've remarked that udev is complaining about a kernel name and NAME= disagree.
So I tried to replace the content of /etc/udev/rules.d/lirc.rules with the following:
KERNEL=="lirc[0-9]*",   NAME="lirc/%n", MODE="0666", SYMLINK+="%k"

But the issue still exists even after patching the udev rule.

Version: Cauldron => 1

Peter Miller 2011-10-26 13:55:22 CEST

CC: (none) => pfmiller

Comment 7 Anssi Hannula 2011-12-16 06:10:33 CET
Please install v4l-utils package and provide the output of "ir-keytable".
Comment 8 Peter Miller 2011-12-16 09:36:30 CET
I am having problems with LIRC too, this is my ir-keytable output:

root@lenore /home/pete # ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event5) with:
        Driver mceusb, table rc-rc6-mce
        Supported protocols: NEC RC-5 RC-6 JVC SONY LIRC
        Enabled protocols: RC-6
        Repeat delay = 500 ms, repeat period = 33 ms
Comment 9 claire robinson 2011-12-16 11:27:52 CET
These are both the same remotes as I was having problems with in bug 2661.

There must be some issues there. I wasn't able to get it to work at the time but put it down to misconfiguration.
Comment 10 Anssi Hannula 2011-12-16 11:31:25 CET
Peter, seems LIRC is disabled for that remote.

What happens if you switch from kernel decoding to lirc passthrough:
ir-keytable --protocol=LIRC
Comment 11 Gilles Mouchard 2012-02-18 17:29:46 CET
It works very well with the 'ir-keytable --protocol=LIRC' work around.
Thanks.
Comment 12 Marja Van Waes 2012-06-06 21:56:58 CEST
3-monthly ping

Does Anssi's workaround (see comment 10) solve this for everyone?

CC: (none) => marja11

Comment 13 Derek Jennings 2012-06-07 00:32:37 CEST
Created attachment 2434 [details]
Lirc setup

lirc-0.9.0-3.mga2.src.rpm is working for me. (on x86_64 )

I am using it with a remote supplied with my TV capture card.
The setup and test method I used is attached. It may help people with other remotes.
Derek Jennings 2012-06-07 00:33:23 CEST

Attachment 2434 mime type: application/octet-stream => application/text

Derek Jennings 2012-06-07 00:34:15 CEST

Attachment 2434 mime type: application/text => text/plain

Comment 14 Marja Van Waes 2012-06-07 08:13:45 CEST
(In reply to comment #13)
> Created attachment 2434 [details]
> Lirc setup
> 
> lirc-0.9.0-3.mga2.src.rpm is working for me. (on x86_64 )
> 
> I am using it with a remote supplied with my TV capture card.
> The setup and test method I used is attached. It may help people with other
> remotes.

Thanks, Derek :D

I started a wiki page for LIRC https://wiki.mageia.org/en/LIRC 
and gave a link to your example. Hopefully someone will find time to finish that page
Comment 15 Marja Van Waes 2012-07-06 15:03:27 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 16 Gilles Mouchard 2012-07-06 15:14:30 CEST
I still need the 'ir-keytable --protocol=LIRC' work around with Mageia 2.
I have put it in /etc/rc.local.
Marja Van Waes 2012-07-08 20:46:55 CEST

Version: 1 => 2
Whiteboard: (none) => MGA1TOO

Comment 17 Gilles Mouchard 2013-06-15 22:39:13 CEST
Same with Mageia 3.
Adding "ir-keytable --protocol=LIRC" in /etc/rc.d/rc.local fixes the problem too.

Version: 2 => 3

Comment 18 Mark Adams 2013-09-29 01:51:06 CEST
Under Mageia 2 running Mythtv (mythtv-backend-0.25-20120602.0.1.mga2, etc.), lirc lirc-0.9.0-3.mga2, 
libv4l-wrappers-0.8.6-1.mga2, 
Kernel 3.4.52-desktop-1.mga2,
and the mceusb2 that came with my Hauppauge pvr 150

Not seeing any output from irw.

Added "ir-keytable --protocol=LIRC" in /etc/rc.d/rc.local, did not resolve the issue.

Checked systemctl output:

# systemctl status lircd.service
lircd.service - LSB: Linux Infrared Remote Control daemon
          Loaded: loaded (/etc/rc.d/init.d/lircd)
          Active: active (running) since Fri, 20 Sep 2013 15:19:49 -0600; 17min ago
         Process: 10513 ExecStop=/etc/rc.d/init.d/lircd stop (code=exited, status=0/SUCCESS)
         Process: 10530 ExecStart=/etc/rc.d/init.d/lircd start (code=exited, status=0/SUCCESS)
        Main PID: 10539 (lircd)
          CGroup: name=systemd:/system/lircd.service
                  â 10539 lircd --device=/dev/lirc/0 <------ NOTE

Sep 20 15:33:02 pvr lircd-0.9.0[10539]: accepted new client on /var/run/lirc/lircd
Sep 20 15:33:02 pvr lircd-0.9.0[10539]: could not get file information for /dev/lirc/0  <------ NOTE
Sep 20 15:33:02 pvr lircd-0.9.0[10539]: default_init(): Not a directory
Sep 20 15:33:02 pvr lircd-0.9.0[10539]: Failed to initialize hardware
Sep 20 15:33:02 pvr lircd-0.9.0[10539]: removed client

Note references to "/dev/lirc/0"

Checked /dev and observed:

ll /dev/lirc*
lrwxrwxrwx 1 root root     10 Sep 20 14:56 /dev/lirc -> /dev/lirc0
crw------- 1 root root 251, 0 Sep 20 08:42 /dev/lirc0

RESOLUTION

Edited the config for /etc/sysconfig/lircd. Specifically, comment out line 15:
#DEVICE=/dev/lirc/0

and uncomment line 19
DEVICE=/dev/lirc

Then I just restarted lircd.

I vaguely remember creating the symlink from /dev/lirc0 to /dev/lirc, but I suppose you could edit the config file to point to /dev/lirc0 and not create the link.

At any rate, that fixed it for me and I don't know why this didn't work out of the box.

I hope this helps.

Mark

CC: (none) => mark9117

Comment 19 Mark Adams 2013-09-29 01:56:16 CEST
Meant to mention, see this link for more including a possible solution for Mageia 3.

https://forums.mageia.org/en/viewtopic.php?f=7&t=6114
Comment 20 Anssi Hannula 2014-02-09 16:33:01 CET
I'm sorry for the delay.

On Cauldron, kernel protocol decoders that interfere with using LIRC can now be disabled on a per-device basis by using the LIRC_IR_DEVICE configuration directive in /etc/sysconfig/lirc or for all remote control devices by installing the new lirc-disable-kernel-rc subpackage. Most LIRC users should be fine by just
installing the new package, without needing to use LIRC_IR_DEVICE.

There is an update/testing request for mga4, bug #12685.
I don't think there will be a separate update for mga3 for this, but I'll keep this open just in case.
Comment 21 Marja Van Waes 2015-03-31 16:02:43 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 22 Gilles Mouchard 2015-03-31 16:14:08 CEST
It's *resolved* at least on Mageia 4.
More precisely, I can confirm that I no longer need to put "ir-keytable --protocol=LIRC" in my /etc/rc.d/rc.local to make remote controller work. 
I did not modify /etc/sysconfig/lirc.
From my point of view, it's the expected behavior.

Thanks.

Version: 3 => 4

Comment 23 Marja Van Waes 2015-03-31 16:17:37 CEST
(In reply to Gilles Mouchard from comment #22)
> It's *resolved* at least on Mageia 4.
> More precisely, I can confirm that I no longer need to put "ir-keytable
> --protocol=LIRC" in my /etc/rc.d/rc.local to make remote controller work. 
> I did not modify /etc/sysconfig/lirc.
> From my point of view, it's the expected behavior.
> 
> Thanks.

Thanks for the feedback. :-)

Changing to FIXED, then, since you changed the version to 4 ;-)

Resolution: OLD => FIXED


Note You need to log in before you can comment on or make changes to this bug.