How to make use of IrDA - Revision history

KotCzarny: /* LIRC and IrDA */ english

2011-07-26T17:07:43Z

‎LIRC and IrDA: english

Bombenbach: /* Success reports */

2011-04-19T17:25:47Z

‎Success reports

Bombenbach: /* Testing LIRC */

2011-04-19T17:22:22Z

‎Testing LIRC

Bombenbach: /* Ubuntu */

2011-04-19T17:11:58Z

‎Ubuntu

Hagen-cool: /* Success reports */ 600 added

2011-02-20T18:46:50Z

‎Success reports: 600 added

Hagen-cool: /* Success reports */

2011-02-20T18:46:18Z

‎Success reports

Tonko: /* LIRC and IrDA */

2010-01-07T09:40:12Z

‎LIRC and IrDA

Tonko: Reverted edits by Hieuln (Talk) to last version by Tonko

2010-01-07T09:38:28Z

Reverted edits by Hieuln (Talk) to last version by Tonko

Hieuln at 13:50, 5 January 2010

2010-01-05T13:50:27Z

Tonko: /* Known problems */

2009-05-18T20:38:12Z

‎Known problems

@@ Line 51: / Line 51: @@
 LIRC allows the use of infrared remote controls with Linux as input devices. This can be especially useful to control applications like mplayer, xine, mythtv or boxee. Usually, IrDA ports are not compatible with LIRC, but you may have luck using lirc_sir, as follows;
 {{NOTE|lirc_sir is incompatible with the regular Linux IrDA drivers (nsc_ircc). You can only use one at a time, and will have to reboot before you can switch}}
-{{NOTE|Even if your successful in getting this to work, you might find that the distance between remote control and receiver on the ThinkPad cannot exceed ~50cm, rendering it effectively useless. This can vary depending on Remote and ThinkPad used, there has been one successful report of a T60 with >2M}}
+{{NOTE|Even if you are successful in getting this to work, you might find that the distance between remote control and receiver on the ThinkPad cannot exceed ~50cm, rendering it effectively useless. This can vary depending on Remote and ThinkPad used, there has been one successful report of a T60 with >2M}}
 ====Success reports====
 * R40
@@ Line 62: / Line 63: @@
 lirc_sir does not always work, particular on newer machines it seems the module loads when following these instructions, but the device {{path|/dev/lirc0}} cannot be opened and returns a device or resource busy. You can simply test this by typing {{cmdroot|cat /dev/lirc0}}
 * T60
 ===Configuring lirc_sir===
 Go into your BIOS setup, and ensure that Infrared is fully enabled and that resources are assigned. I suggest using IO 2f8 and IRQ 3.

@@ Line 57: / Line 57: @@
 * T60
 * 600
 ====Failure reports====

@@ Line 127: / Line 127: @@
 Now we are ready to test if we can receive IR data from a remote control.
-Try running {{cmdroot|irrecord -d /dev/lirc0 foo}} and follow the onscreen instructions. When asked keep a button on a remote pressed while pointing at the ThinkPad IR port and you should see dots appear.
+Try running {{cmdroot|irrecord -d /dev/lirc0 foo}} and follow the onscreen instructions. When asked keep a button on a remote pressed while pointing at the ThinkPad IR port and you should see dots appear.  After having configured your specific remote control, copy {{path|foo}} to {{path|/etc/lirc/lircd.conf}} and restart LIRC. You can use '''irw''' to check whether the remote control is working properly.
-You are now able to start configuring LIRC for your specific remote control.
+To make it perform something useful, try '''irexec'''. It looks for a {{path|.lircrc}} in your home directory. If you don't have one, here is an example which maps KEY_UP and KEY_DOWN (key names can be chosen while performing '''irrecord''') to Up and Down.
 Configuring remote controls is out of scope for this document and you should check the LIRC website for detailed instructions. But if your using Gnome you might want to try {{cmd|gnome-lirc-properties|$}}, or in the case of KDE {{cmd|kdelirc|$}}.

@@ Line 90: / Line 90: @@
 ====Ubuntu====
 Make sure your {{path|/etc/lirc/hardware.conf}} looks like this:
   REMOTE="SIR IrDA (built-in IR ports)"
@@ Line 111: / Line 113: @@
 After this, start (or re-start) the lirc daemon, and set it to automatically start on bootup.
-{{cmdroot|service lirc restart}}<br>
+{{cmdroot|sudo service lirc restart}}<br>
-{{cmdroot|update-rc.d lirc defaults}}
+{{cmdroot|sudo update-rc.d lirc defaults}}
 ====Fedora====
 On Fedora the default LIRC device is already set to /dev/lirc0

@@ Line 56: / Line 56: @@
 * T41
 * T60
+* 600
 ====Failure reports====

@@ Line 37: / Line 37: @@
 == Known problems ==
 * If you read something like "ttyS1: LSR safety check engaged!" and "irattach: tcgetattr: Input/output error" in the system log, try limiting the FIR max baud rate (echo 57600 > /proc/sys/net/irda/max_baud_rate). This did the trick for me when I was trying to synchronize my Ericsson T39m with my Thinkpad R51 (multisync, evolution-2.8, KDE 3.5.5, openSUSE 10.2).
-* If you get an error in syslog like "nsc_ircc_open(), can't get iobase of 0x2f8" it probably means you have manually specified resources for IrDA in the BIOS. When you do that you effectively allow the serial driver to take control, and as a result the nsc_ircc driver can no longer take control of the resources. Options are to either restore the BIOS settings for IrDA to factory default, or you can try to use setserial to clear the resources before loading the nsc_ircc kernel module
+* If you get an error in syslog like "nsc_ircc_open(), can't get iobase of 0x2f8" it probably means you have manually specified resources for IrDA in the BIOS. When you do that you effectively allow the serial driver to take control, and as a result the nsc_ircc driver can no longer take control of the resources. Options are to either restore the BIOS settings for IrDA to factory default, or you can work around it by using setserial to clear the resources before loading the nsc_ircc kernel module
-  setserial /dev/ttyS1 uart none port 0 irq 0
+  setserial /dev/ttyS1 uart none port 0 irq 0; modprobe nsc_ircc
 == Some other things you might want to do with IrDA ==