| Summary: | lirc is not functional | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Gilles Mouchard <gilles.mouchard> |
| Component: | RPM Packages | Assignee: | Anssi Hannula <anssi.hannula> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | derekjenn, eeeemail, lovaren, marja11, mark9117, pfmiller |
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | MGA1TOO | ||
| Source RPM: | lirc | CVE: | |
| Status comment: | |||
| Attachments: | Lirc setup | ||
|
Description
Gilles Mouchard
2011-05-13 19:12:38 CEST
Ahmad Samir
2011-05-13 19:15:37 CEST
Assignee:
bugsquad =>
anssi.hannula 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 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 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 Will this be updated? It is currently non functional in mga1 i586. CC:
(none) =>
claire 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. 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 Please install v4l-utils package and provide the output of "ir-keytable". 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
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. Peter, seems LIRC is disabled for that remote. What happens if you switch from kernel decoding to lirc passthrough: ir-keytable --protocol=LIRC It works very well with the 'ir-keytable --protocol=LIRC' work around. Thanks. 3-monthly ping Does Anssi's workaround (see comment 10) solve this for everyone? CC:
(none) =>
marja11 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 (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 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 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 Same with Mageia 3. Adding "ir-keytable --protocol=LIRC" in /etc/rc.d/rc.local fixes the problem too. Version:
2 =>
3 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.
MarkCC:
(none) =>
mark9117 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 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. 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 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 (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 |