Lirc update broke functionality

ctxfi-user · 2010-11-29 20:33:46

@Perre:

don't mix it up. i still use lirc-utils (and so the lirc daemon) for xbmc. you don't need lirc (contains lirc_mceusb). add the lirc daemon to rc.conf again and neither blacklist any of the modules related to IR nor modprobe -r any of these modules in rc.local. restart. test with irw. all buttons should work, notice the double key problem. try modprobe -r ir_rc6_decoder. and test again. notice, that the double key problem is gone. (hopefully!)

apparently, this isn't the best solution. anyone?

ctxfi-user · 2010-11-29 23:37:27

I found a post from the lirc dev Jarod Wilson (http://www.gossamer-threads.com/lists/m … 693#460693):
> echo none +lirc > /sys/class/rc/rc0/protocols
>
> This will disable the in-kernel decoders and enable only the lirc bridge
> driver.

Solution:
- no need for lirc package (old modules)
- need for lirc-utils ("since full native input layer support is not quite a reality yet")
- no blacklisting
- ir-keytable -p lirc (does the same as discribed above for all remotes)

For now, i put the line above in rc.local, but a udev rule should be the better place...

falconindy · 2010-11-30 02:09:42

ctxfi-user wrote:

I found a post from the lirc dev Jarod Wilson (http://www.gossamer-threads.com/lists/m … 693#460693):
> echo none +lirc > /sys/class/rc/rc0/protocols
>
> This will disable the in-kernel decoders and enable only the lirc bridge
> driver.
Solution:
- no need for lirc package (old modules)
- need for lirc-utils ("since full native input layer support is not quite a reality yet")
- no blacklisting
- ir-keytable -p lirc (does the same as discribed above for all remotes)
For now, i put the line above in rc.local, but a udev rule should be the better place...

Thanks for doing the legwork on this and providing multiple solutions.

Perre · 2010-11-30 18:27:10

ctxfi-user wrote:

@Perre:
don't mix it up. i still use lirc-utils (and so the lirc daemon) for xbmc. you don't need lirc (contains lirc_mceusb). add the lirc daemon to rc.conf again and neither blacklist any of the modules related to IR nor modprobe -r any of these modules in rc.local. restart. test with irw. all buttons should work, notice the double key problem. try modprobe -r ir_rc6_decoder. and test again. notice, that the double key problem is gone. (hopefully!)
apparently, this isn't the best solution. anyone?

I got a little confused, yes.
But now the remote is working perfectly. Putting the lirc daemon back in rc.conf and adding modprobe -r ir_rc6 in rc.local did the trick!

As falconindy said: Thanks for doing the work with this, ctxfi-user! It's greatly appreciated.

lynix · 2010-12-02 20:18:18

ctxfi-user wrote:

For now, i put the line above in rc.local, but a udev rule should be the better place...

Which package contains the binary for "ir-keytable"? Can't find that in lirc-utils.

ctxfi-user · 2010-12-03 17:09:58

@lynix:
It's v4l-utils. (The new IR modules are part of the V4L-DVB project.)

palmaway · 2010-12-12 05:56:42

Ok, guys, I don't really understand what's going on here...

So... back then, I had a working iMon remote. Now, with the new kernel, I don't. the first time I had a problem, I think with kernel 2.6.35, just blacklisting "ir-core" was enough to get back to a working lircd. With 2.6.36, not anymore.

I tried:

- loading lirc_imon (apparently it's not needed anymore), but I don't have a /dev/lirc0

- doing:
# echo none +lirc > /sys/class/rc/rc0/protocols
# ir-keytable -p lirc
and now I get a crash in XBMC (!), and still no remote functionality.

- changing my /etc/conf.d/lircd.conf to:
LIRC_DEVICE="/dev/input/event5"
LIRC_DRIVER="devinput"
to no use.

What can I try now? And, what this change of getting the drivers into the kernel is good for, if it's so awfully complicated to get working something that was working perfectly before?

Thanks to anyone willing to help here, and sorry if I sound a little bit annoyed but... well, I am!

Last edited by palmaway (2010-12-12 05:58:13)

palmaway · 2010-12-12 06:56:25

palmaway wrote:

- changing my /etc/conf.d/lircd.conf to:
LIRC_DEVICE="/dev/input/event5"
LIRC_DRIVER="devinput"
to no use.

Ok... some good news!

The procedure quoted above actually worked, but (of course) I had to replace my existing /etc/lircd.conf with the default one for the driver "devinput".

Now everything seems to be fine again!

guisacouto · 2010-12-12 13:39:26

++lirc_problems; :\

My problem is a bit different.. irw does detect everything I press, however, irexec doesn't launch anything, and xbmc does nothing when I press a key... everything was working just fine and now it doesn't..

Did this happen to anyone else?

Best regards!

Last edited by guisacouto (2010-12-12 13:39:38)

colbert · 2010-12-12 20:44:40

Oh man I have the same issue of multiple presses but after reading through this thread I'm confused as to which "solution" to try lol

Last edited by colbert (2010-12-12 20:44:59)

guisacouto · 2010-12-13 01:35:36

Problem solved. If anyone has the same symptoms has I did the problem might me that the name of the remote changed.

Mine used to be mceusb, and now it is mceusb_hauppauge.. I didn't notice this and this was why irexec wasn't working (using wrong name!), and xbmc defaults to mceusb so I just had to change /opt/xbmc/system/Lircmap.xml to use mceusb_hauppauge too.

Hope this is useful to someone!

best regards!

phreique · 2010-12-26 06:09:26

vparask wrote:

1. DO NOT remove lirc or REINSTALL it if you removed it
2. CHANGE rc.conf modules section to something like this
MODULES=(...... !ir_core lirc_mceusb ......)
3. reboot
THIS worked for me!

After an upgrade today, this worked for me! Much easier and less time-consuming than a kernel recompile! My computer + Linux = TIME VAMPIRE

azleifel · 2011-01-01 11:03:01

Variation on the theme that worked for my Microsoft RC6 remote / Hauppauge Nova-T-500:

1. Keep lirc-utils installed and lircd in the rc.conf DAEMONS array.
2. Uninstall lirc.
3. Replace lirc_mceusb with mceusb in the rc.conf MODULES array.
4. Create /etc/modprobe.d/dvb-usb.conf containing

options dvb_usb disable_rc_polling=1

to resolve the double-keystroke problem without blacklisting any modules.
5. Add

/usr/bin/ir-keytable -p lirc

to /etc/rc.local.

colbert · 2011-01-01 18:29:46

Post 37 quote worked for me as well after reboot Also, I had issue on my laptop with libusb-compat, and all that was needed was a reinstall of libusb-compat, a reboot and it works

fiatguy85 · 2011-04-08 03:05:29

I know this thread is a couple months old, but with recent updates to lirc, they seem to have completely dropped support for the lirc_mceusb module. I had previously used this as a quick fix, like some users suggested. Now, I found that everything is fixed and working as before by implementing what had been previously stated in this thread:

ctxfi-user wrote:

I found a post from the lirc dev Jarod Wilson (http://www.gossamer-threads.com/lists/m … 693#460693):
> echo none +lirc > /sys/class/rc/rc0/protocols
>
> This will disable the in-kernel decoders and enable only the lirc bridge
> driver.

azleifel wrote:

Variation on the theme that worked for my Microsoft RC6 remote / Hauppauge Nova-T-500:
1. Keep lirc-utils installed and lircd in the rc.conf DAEMONS array.
2. Uninstall lirc.
3. Replace lirc_mceusb with mceusb in the rc.conf MODULES array.
4. Create /etc/modprobe.d/dvb-usb.conf containing
options dvb_usb disable_rc_polling=1
to resolve the double-keystroke problem without blacklisting any modules.
5. Add
/usr/bin/ir-keytable -p lirc
to /etc/rc.local.

I did not have to add mceusb to my MODULES line in rc.conf, it was automatically detected with udev enabled. I'm not sure if the line

echo none +lirc > /sys/class/rc/rc0/protocols

is absolutely necessary, but it is compatible with my AVS Gear MCE remote.

colbert · 2011-04-08 05:28:47

I've encountered broken LIRC again after rebooting my laptop. I have no lirc_mceusb/2 or lirc-mceusb/2 module when trying to load any. I have uninstalled and reinstalled LIRC, moved my /etc/lircd.conf to /etc/lirc/lircd.conf, restarted LIRC, and loaded the mceusb module. Trying irw shows no recognition of button presses at all

edit:

ctxfi-user wrote:

I found a post from the lirc dev Jarod Wilson (http://www.gossamer-threads.com/lists/m … 693#460693):
> echo none +lirc > /sys/class/rc/rc0/protocols
>
> This will disable the in-kernel decoders and enable only the lirc bridge
> driver.

I don't have any /sys/class/rc/rc0/protocols when trying this command.

azleifel wrote:

Variation on the theme that worked for my Microsoft RC6 remote / Hauppauge Nova-T-500:
1. Keep lirc-utils installed and lircd in the rc.conf DAEMONS array.
2. Uninstall lirc.
3. Replace lirc_mceusb with mceusb in the rc.conf MODULES array.
4. Create /etc/modprobe.d/dvb-usb.conf containing
options dvb_usb disable_rc_polling=1
to resolve the double-keystroke problem without blacklisting any modules.
5. Add
/usr/bin/ir-keytable -p lirc
to /etc/rc.local.

I did this, rebooted and still the same

Last edited by colbert (2011-04-08 05:30:20)

azleifel · 2011-04-08 17:51:29

Well, my remote's still working properly but I'm using the mceusb module that ships with kernel26 and don't have the lirc package installed, only lirc-utils. Did you by any chance mix up your lircd.confs? /etc/conf.d/lircd.conf should be something like

#
# Parameters for lirc daemon
#

LIRC_DEVICE="/dev/lirc0"
LIRC_DRIVER=""
LIRC_EXTRAOPTS=""
LIRC_CONFIGFILE=""

and /etc/lirc/lircd.conf should be

#
# brand:                        HP 
# model no. of remote control:  TSGH-IR01
# devices being controlled by this remote: HP Slimline S3100y
#
# RC-6 config file
[etc]

plantoschka · 2011-04-08 22:26:52

Since the Lirc update i have the same problem like colbert.

Previously i was using lirc_mceusb but now it's not available. I tried to set up mceusb module instead, uninstall lirc and copying the mceremoteconfig to /etc/lirc/lircd.conf

Only the Up,left,right,down and volume keys are working. With lirc_mceusb everything was working perfect.

I'm using an original Microsoft MCE Remote (RC6)v2 with the original IR-Receiver.

Last edited by plantoschka (2011-04-08 22:27:52)

colbert · 2011-04-09 04:57:10

azleifel wrote:

Well, my remote's still working properly but I'm using the mceusb module that ships with kernel26 and don't have the lirc package installed, only lirc-utils. Did you by any chance mix up your lircd.confs? /etc/conf.d/lircd.conf should be something like
#
# Parameters for lirc daemon
#

LIRC_DEVICE="/dev/lirc0"
LIRC_DRIVER=""
LIRC_EXTRAOPTS=""
LIRC_CONFIGFILE=""
and /etc/lirc/lircd.conf should be
#
# brand:                        HP 
# model no. of remote control:  TSGH-IR01
# devices being controlled by this remote: HP Slimline S3100y
#
# RC-6 config file
[etc]

Nope, they are correct. This is kind of baffling

azleifel · 2011-04-09 07:09:56

I'm sure that I'm not doing anything special. What's in the logs?

$ dmesg | grep -e lirc -e LIRC -e mceusb
lirc_dev: IR Remote Control driver registered, major 251 
IR LIRC bridge handler initialized
usbcore: registered new interface driver mceusb
rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
mceusb 5-2:1.0: Registered Philips eHome Infrared Transceiver on usb5:2

plantoschka · 2011-04-09 09:35:55

$ dmesg | grep -e lirc -e LIRC -e mceusb
lirc_dev: IR Remote Control driver registered, major 252 
IR LIRC bridge handler initialized
usbcore: registered new interface driver mceusb
rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
mceusb 4-2:1.0: Registered Philips eHome Infrared Transceiver on usb4:3

My output looks almost like yours but remote still not working :-(

akb825 · 2011-04-09 09:48:12

As was mentioned, you need to modify /sys/class/rc/rc0/protocols. (you can either use "none +lirc" or just "lirc") If that file doesn't exist, make sure your remote is plugged in and the mceusb module is loaded.

Another change they made was changing the button names in the default provided lircd.conf file, so be careful if you implement your lircd.conf file by including the default one, or overwrote your lircd.conf file when debugging the issue. (that ended up happening to me...)

I started a thread earlier that documents the issues, since I didn't see this thread until now. (https://bbs.archlinux.org/viewtopic.php?id=116515) I also updated the wiki page documenting both issues, and I included the old lircd.conf in case you're stuck with the new one that changed the button names.

Last edited by akb825 (2011-04-09 10:03:21)

plantoschka · 2011-04-09 10:19:49

akb825 wrote:

As was mentioned, you need to modify /sys/class/rc/rc0/protocols. (you can either use "none +lirc" or just "lirc") If that file doesn't exist, make sure your remote is plugged in and the mceusb module is loaded.

Finally worked for me. The protocols file now look like this:

rc-5 nec rc-6 jvc sony [lirc]

azleifel · 2011-04-09 17:20:41

ir-keytable from the v4l-utils package, which is what I've been using, has the same effect:

$ sudo ir-keytable -p lirc
Password: 
Protocols changed to LIRC 
$ cat /sys/class/rc/rc0/protocols
rc-5 nec rc-6 jvc sony [lirc]

Clouseau · 2011-05-18 17:19:37

I've posted my problem here https://bugs.archlinux.org/task/24275. The problem is with kernel 2.6.37 and newer... I can't figure it out what has changed or if I could find some changelog between the 2.6.36 and 2.6.37. that would probably help

EDIT: found the changelog http://kernelnewbies.org/Linux_2_6_37 but nothing indicates what would be the problem...

EDIT2: Ok, with 2.6.36 I have nothing in /sys/class/rc/ and the remote works out of the box. With next kernel and newer I have now /sys/class/rc/rc0/... which is probably where the bug is, this is created as extra and it obviously interferes with the remote often accepting one click as two... What to do, what to do.

Last edited by Clouseau (2011-05-18 18:14:56)

Arch Linux

#26 2010-11-29 20:33:46

Re: Lirc update broke functionality

#27 2010-11-29 23:37:27

Re: Lirc update broke functionality

#28 2010-11-30 02:09:42

Re: Lirc update broke functionality

#29 2010-11-30 18:27:10

Re: Lirc update broke functionality

#30 2010-12-02 20:18:18

Re: Lirc update broke functionality

#31 2010-12-03 17:09:58

Re: Lirc update broke functionality

#32 2010-12-12 05:56:42

Re: Lirc update broke functionality

#33 2010-12-12 06:56:25

Re: Lirc update broke functionality

#34 2010-12-12 13:39:26

Re: Lirc update broke functionality

#35 2010-12-12 20:44:40

Re: Lirc update broke functionality

#36 2010-12-13 01:35:36

Re: Lirc update broke functionality

#37 2010-12-26 06:09:26

Re: Lirc update broke functionality

#38 2011-01-01 11:03:01

Re: Lirc update broke functionality

#39 2011-01-01 18:29:46

Re: Lirc update broke functionality

#40 2011-04-08 03:05:29

Re: Lirc update broke functionality

#41 2011-04-08 05:28:47

Re: Lirc update broke functionality

#42 2011-04-08 17:51:29

Re: Lirc update broke functionality

#43 2011-04-08 22:26:52

Re: Lirc update broke functionality

#44 2011-04-09 04:57:10

Re: Lirc update broke functionality

#45 2011-04-09 07:09:56

Re: Lirc update broke functionality

#46 2011-04-09 09:35:55

Re: Lirc update broke functionality

#47 2011-04-09 09:48:12

Re: Lirc update broke functionality

#48 2011-04-09 10:19:49

Re: Lirc update broke functionality

#49 2011-04-09 17:20:41

Re: Lirc update broke functionality

#50 2011-05-18 17:19:37

Re: Lirc update broke functionality

Board footer