ThinkWiki - User contributions [en]

Talk:How to make use of IrDA

2011-02-20T19:00:56Z

Hagen-cool: /* LIRC and IrDA */

The "wrong chip version ff" is a real issue, and having it mentioned makes sure that google searches turn it up with a solution.
[[User:Tonko|Tonko]] 01:41, 8 Oct 2005 (CEST)

----
The present text confused me (as you now have noticed). Maybe it should better reflect that the error is incorrect ("wrong chip version ff" instead of "FIR mode not enabled" or whatever). Would that be acceptable?

[[User:Pebolle|Paul Bolle]] 02:05, 8 Oct 2005 (CEST)
----
If you think you can explain it better, go right ahead. The IrDA document could use some major cleaning.

As long as we still point out that the only error in syslog is "Wrong chip version ff" when trying to load the FIR module without first activating the PnP device. It would be nice if the ISA-PNP patch to the nsc-ircc driver got accepted upstream, so we dont have to do these hacks anymore.
[[User:Tonko|Tonko]] 03:58, 8 Oct 2005 (CEST)
----
Tonko,

Is there a reason why you deleted the TODO entry for linux 2.6 kernel config for SIR? I would like to readd it, but like to hear your reason to remove it first.

[[User:Pebolle|Paul Bolle]] 10:23, 14 Oct 2005 (CEST)

== T23 debianized kernel with probs ==

Found another crazy thing here. T23 2648-2GG, with 2.6.13 and 2.6.14 (Debianized Source). Clear init of nsc-ircc and dongle, but the dongle stays offline (dark and blind). Booted with Knoppix or Bart-PE Windows give correct function of the whole device, viewed with a digicam shows some blinks at init. But not with plain 2.6.13 an 2.6.14 from Debian.
Eric

== setpnp ==

Hello,

since the nsc-ircc patch isn't in 2.6.15, I tried to go the setpnp route, but I don't even get to see {{path|/proc/bus/pnp}} even though I enabled the support for it in the kernel config (once I found out that I need to enable ISA support to even get the option). Has anyone successfully used setpnp to enable the IRDA port or is that just some sort of urban legend? ;)

--[[User:Spiney|spiney]] 19:12, 4 Jan 2006 (CET)
----

Make sure you enable pnp-bios support specifically when compiling the kernel, just enabling pnp support is not enough.
I must however admit that I have not done this, since my ancient TP 770 running a 2.4 kernel, which was at least 5 years ago.

I just looked at a 2.6 menuconfig myself, and could not find the option, but looking at my .config file I can see the CONFIG_PNPBIOS option, so you might just want to edit the config file directly, enable the PNPBIOS option, and run make oldconfig.

--[[User:Tonko|Tonko]] 19:38, 4 Jan 2006 (CET)
----

I do have the pnp-bios support enabled (the option is depending on ISA among others, checked the Kconfig file in the source tree to find it), and also the proc-Interface option, but still no go... maybe it's not compatible with CONFIG_PNPACPI? Oh well, nevermind, going back to the patch, that works with less hassles, I just hope it'll end up in the vanilla kernel eventually. Still thanks for the help.

--[[User:Spiney|spiney]] 20:22, 4 Jan 2006 (CET)
----

Ok, on further investigation (not giving up that easily ;) it really seems that CONFIG_PNPACPI is disabling PnPBIOS, at least dmesg showed something along the lines of "PnPBIOS: disabled by PnPACPI". But, after recompiling without PnPACPI, I still can't get it to work. I can use {{cmd|setpnp|}} and {{cmd|lspnp|}} just fine, but the nsc-ircc module won't load:

<pre>
t43p:~# lspnp 12
12 IBM0071 IBM Thinkpad infrared port
t43p:~# setpnp 12 io 0x2f8 irq 3
t43p:~# lspnp -v 12
12 IBM0071 IBM Thinkpad infrared port
dma 3
io 0x02f8-0x02ff
irq 3
t43p:~# modprobe nsc-ircc io=0x2f8 irq=3 dongle_id=0x09
FATAL: Error inserting nsc_ircc (/lib/modules/2.6.15/kernel/drivers/net/irda/nsc-ircc.ko): No such device
</pre>

Hmm, I'm getting somewhat annoyed... any ideas?

--[[User:Spiney|spiney]] 20:58, 4 Jan 2006 (CET)
----

have you tried just doing {{cmd|setpnp 12 on|}}

--[[User:Tonko|Tonko]] 21:05, 4 Jan 2006 (CET)
----

Yes, that was the first thing I tried, didn't help. BTW, I just fiddled around with lirc a bit (never tried it before), and the lirc_sir module works just fine:

<pre>
lirc_sir: I/O port 0x02f8, IRQ 3.
lirc_sir: Installed.
</pre>

and I was able to get it to control xmms.

{{cmd|setserial|}} doesn't claim the device either:

<pre>
t43p:~# setserial -ag /dev/ttyS0
/dev/ttyS0, Line 0, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 921600, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test
</pre>

I'm really out of ideas.

--[[User:Spiney|spiney]] 21:20, 4 Jan 2006 (CET)
----

Hmm, it should not be ttyS0, but ttyS1 which might be stepping on the resources
ttyS0 is IO 0x3f8 and IRQ 4, while ttyS1 is IO 0x2f8 and IRQ 3.

ttyS0 is your integrated serial port, which even ThinkPads without physical serial port have.

--[[User:Tonko|Tonko]] 21:29, 4 Jan 2006 (CET)
----
Sorry, I cut'n'paste the wrong device since I checked them both, the output for ttyS1 is identical (apart from "/dev/ttyS1, Line 1" of course).

--[[User:Spiney|spiney]] 21:36, 4 Jan 2006 (CET)
----
No idea what might be wrong, perhaps it does not work on more recent machines, or kernels.

As I said, it worked for me a long time ago on my 770X with ''something'' like this:

/bin/setserial /dev/ttyS1 uart none port 0 irq 0
setpnp 12 io 0x2f8 irq 3
setpnp 12 on
modprobe nsc-ircc dongle_id=0x09 io=0x2f8 irq=3

What is the error you get from nsc-ircc in syslog? the "Wrong chip version ff" error?

--[[User:Tonko|Tonko]] 22:22, 4 Jan 2006 (CET)
----

No errors are recorded at all (dmesg, syslog), just the message above on stderr from {{cmd|modprobe|}}.

--[[User:Spiney|spiney]] 09:27, 5 Jan 2006 (CET)
----

BTW, is it just me or does the nsc-ircc patch only work if CONFIG_PNPACPI is set in the kernel config? Otherwise the module loads fine, (but without stating in the kernel log that it found the dongle) and using IRDA does not work, irattach returns "irattach: ioctl(SIOCGIFFLAGS): No such device".

--[[User:Spiney|spiney]] 14:37, 12 Jan 2006 (CET)
----

== Not even SIR working on R52 ==

I don't want/need FIR right now, so i thought i wouldn't have to mess with it.
I don't have /proc/bus/pnp, but i'm pretty sure infrared should work without it as well.
I do not have a kernel patch and am using the current Ubuntu Breezy 2.6.12-10 kernel.
Problem is, that when starting
irattach /dev/ttyS1 -s
It complains in syslog: no such device
On ttyS0 it works fine, but well does not find any packets.

# setserial -ag /dev/ttyS1
/dev/ttyS1, Line 1, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 921600, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test

# cat /dev/ttyS1
cat: /dev/ttyS1: input-/outputerror

So i tried:
sudo setserial /dev/ttyS1 uart 16550A port 0x02f8 irq 3

Well ''now'' irattach will attach to ttyS1, irdadump will show me the packets '''sent''' by my computer,
but won't receive my cellphone's packets (Nokia 6210). In Windows, everything works fine.

===Same case here===
I have the same problem here, it used to work on 2.6.15. nsc-irc works, even a MCS7780 USB-IRDA adapter works, but the chip doesn't seem to send/receive on 2.6.17 and 2.6.18 (I checked with a CCD camera, no light signal at all), also ''findchip -d'' says:

root@golem3:/etc# findchip -d
Probing for FDC37C669 ...
Wrong chip id=0xff
Wrong chip id=0xff
Probing for FDC37C669FR ...
Wrong chip id=0xff
Wrong chip id=0xff
Probing for FDC37N869 ...
Wrong chip id=0xff
Wrong chip id=0xff
Probing for FDC37C93xFR ...
Wrong chip id=0xff
Wrong chip id=0xff
Probing for FDC37N957FR ...
Wrong chip id=0xff
Wrong chip id=0xff
Probing for FDC37N958FR ...
Wrong chip id=0xff
Wrong chip id=0xff
Probing for PC87108 ...
no chip at 0x150
no chip at 0x398
no chip at 0x0ea
Probing for PC87338 ...
no chip at 0x398
no chip at 0x15c
Wrong chip id=0x00
Probing for EFER at 0x03f0 ...
hefras = 0xff
Probing for EFER at 0x0370 ...
hefras = 0xff
EFER seems to be probed at 0x0370
chip id = 0xff, revision = 0xff
Wrong device ID = 0xff
Probing for EFER at 0x0250 ...
hefras = 0xff
Probing for EFER at 0x0250 ...
hefras = 0xff
Probing for EFER at 0x03f0 ...
hefras = 0xff
hefere = 0xff
Probing for EFER at 0x03f0 ...
hefras = 0xff
hefere = 0xff
EFER seems to be probed at 0x03f0
chip ID is 0x0f : no known chip was detected.
Couldn't find Winbond superI/O chip.

dmesg:

nsc-ircc, chip->init
nsc-ircc, Found chip at base=0x02e
nsc-ircc, driver loaded (Dag Brattli)
IrDA: Registered device irda0
nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500
IBM TrackPoint firmware: 0x0e, buttons: 3/3
serial8250: too much work for irq3
sirdev_get_instance - ttyS1
irtty_open - ttyS1: irda line discipline opened
irlap_change_speed(), setting speed to 9600
nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 3.
nsc-ircc, chip->init
nsc-ircc, Found chip at base=0x02e
nsc-ircc, driver loaded (Dag Brattli)
IrDA: Registered device irda0
nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500
--[[GuySoft]]

>Have you enabled infrared in BIOS?
[[User:Defiant|Defiant]] 21:25, 29 September 2006 (CEST)

Yes I did, It used to function in 2.6.15! its the new 2.6.17 kernel that messed it up, also 2.6.18 doesn't help.

==update - IBM31T1100 and lirc==

Working now in 2.6.18, however I can't get lirc to work.

In dmesg i get:
[code]
lirc_dev: lirc_register_plugin: sample_rate: 0
lirc_sir: i/o port 0x02f8 already in use.
[/code]

Also "/bin/setserial /dev/ttyS1 uart none" doesn't help

Any help there?
[[User:Guysoft|Guysoft]] 19:40, 31 December 2006 (CET)

==lirc and FIR works on R52!!==
I got both lirc and the FIR module to work on my thinkpad r52.

For lirc I had to :
$ killall -9 irattach
$ setserial /dev/ttyS1 uart none
$ rmmod nsc_ircc
then:
$ modprobe lirc_sir
and then run:
$ lircd -d /dev/lirc0 /etc/lircd.conf --nodaemon

For FIR i need to:
modprobe nsc_ircc
I hope this helps anyone that has problems.

[[User:Guysoft|Guysoft]] 15:08, 15 January 2007 (CET)

The lirc_sir module has problems with suspend (disk/ram both).

I'm using Debian Etch kernel 2.6.18-4-686 (version 2.6.18.dfsg.1-11)
with the lirc-modules-source (version 0.8.0-9.2). The lirc_sir module
was built with "other" as type of the SIR device.

With this kernel the nsc_ircc module suspends/resumes properly.

I tried to do a module unload and reload, but surprisingly even that failed.
Before the suspend I get normal output from mode2 but after the resume there is
no output at all :-(

[[User:Kapil|Kapil]] 15:39, 09 March 2007 (PST)

One a separate note. The "nsc_ircc" module and the "lirc_sir" module seem to conflict.

If I load one module and then the other, the system appears to hang. So I wonder how Guysoft managed to get this working.

[[User:Kapil|Kapil]] 15:46, 09 March 2007 (PST)

== T23 IrDA silent? ==

Hi.
I got SIR working pretty easily on my T20. I cannot get anything to work on my T23. I can get the nsc-ircc module to load, and now irattach works (both with and without nsc-ircc), and I've checked the relevant info in /proc/sys/net/irda, but nothing shows up in /proc/net/irda/discovery, and irdadump gives nothing at all. No errors in dmesg or the log. The red LED never lights. It flashes constantly in Windows.

--[[User:SystemParadox|SystemParadox]] 16:58, 1 May 2006 (CEST)

== Problems accessing a Nokia phone ==

i just compiled a brand new 2.6.18 Linux Kernel. Now, even tough the Kernel modules are loaded and irda-utils start correctly i am having trouble accessin my Nokia 6135.

This are the contents of my /etc/modprobe.d/irda-utils:

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3
install nsc-ircc /bin/setserial /dev/ttyS1 uart none port 0 irq 0; /sbin/modprobe --ignore-install nsc-ircc

/var/log/syslog:

Sep 28 11:33:00 raziel kernel: pnp: Device 00:0b activated.
Sep 28 11:33:00 raziel kernel: nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 3.
Sep 28 11:33:00 raziel kernel: nsc-ircc, chip->init
Sep 28 11:33:00 raziel kernel: nsc-ircc, Found chip at base=0x02e
Sep 28 11:33:00 raziel kernel: nsc-ircc, driver loaded (Dag Brattli)
Sep 28 11:33:00 raziel kernel: IrDA: Registered device irda0
Sep 28 11:33:00 raziel kernel: nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500
Sep 28 11:34:34 raziel irattach: got SIGTERM or SIGINT
Sep 28 11:34:34 raziel irattach: Stopping device irda0
Sep 28 11:34:34 raziel irattach: exiting ...
Sep 28 11:34:35 raziel irattach: executing: '/sbin/modprobe irda0'
Sep 28 11:34:35 raziel irattach: executing: 'echo raziel > /proc/sys/net/irda/devname'
Sep 28 11:34:35 raziel irattach: executing: 'echo 1 > /proc/sys/net/irda/discovery'
Sep 28 11:34:35 raziel irattach: Starting device irda0
Sep 28 11:34:35 raziel kernel: irlap_change_speed(), setting speed to 9600

But when wammu tries to find the phone (which is right in front of the left side of laptop, where the IR port supposedly is AND it has IR reception enabled):

Starting /dev/ttyS0 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Starting /dev/ttyS1 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Starting /dev/ttyS2 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Scanning for bluetooth devices using PyBluez
Could not access Bluetooth subsystem (error accessing bluetooth device)
Finished /dev/ttyS0 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyS1 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyS2 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
All finished, found 0 phones

This phone does not have bluetooth so im basically out of options, ideas anyone?

Any suggestions much appreciated

--[[User:Havok1977|Havok1977]] 12:05, 28 Sep 2006 (CEST)

== No irrecord output ==

So I loaded lirc_sir on my T43 and it says all is ok. However I don't seem to get anything out of irrecord. I am pretty sure my remote control is ok. What am I missing?

--[[User:mr.dnme|mr.dnme]] 19:29, 25 Jan 2008

== 2.6.27 auto sets dongle_id ==

Just a quick note that as of 2.6.27 the nsc_ircc driver auto sets the dongle_id to 0x09 when loading on a ThinkPad (based on IrDA ISA PnP ID).
So one less thing that needs to be configured. In fact with this change I think all the outstanding issues are resolved and the nsc_ircc driver should load without any modprobe.conf modifications.
--[[User:Tonko|Tonko]] 21:51, 20 October 2008 (CEST)

== LIRC and IrDA ==

LIRC and IrDA now works on my Thinkpad 600.
The hardest part was to keep away nsc-ircc from configuring
the system. Finally i decided to move the complete irda-path
from /lib/modules... to another location :-)
Now the IR-module receives commands from all of my 4 remote
controls. I will create a lircd.conf with irrecord, using
with the generic/NEC.conf, for the RC from Aiwa, RC-AVR05
the next days. Now i have go to the cinema, Berlinale is calling.
Bye

--[[User:Hagen-cool|Hagen]] 20:00, 20 February 2011 (CET)

Talk:How to make use of IrDA

2011-02-20T19:00:29Z

Hagen-cool: /* LIRC and IrDA */

The "wrong chip version ff" is a real issue, and having it mentioned makes sure that google searches turn it up with a solution.
[[User:Tonko|Tonko]] 01:41, 8 Oct 2005 (CEST)

----
The present text confused me (as you now have noticed). Maybe it should better reflect that the error is incorrect ("wrong chip version ff" instead of "FIR mode not enabled" or whatever). Would that be acceptable?

[[User:Pebolle|Paul Bolle]] 02:05, 8 Oct 2005 (CEST)
----
If you think you can explain it better, go right ahead. The IrDA document could use some major cleaning.

As long as we still point out that the only error in syslog is "Wrong chip version ff" when trying to load the FIR module without first activating the PnP device. It would be nice if the ISA-PNP patch to the nsc-ircc driver got accepted upstream, so we dont have to do these hacks anymore.
[[User:Tonko|Tonko]] 03:58, 8 Oct 2005 (CEST)
----
Tonko,

Is there a reason why you deleted the TODO entry for linux 2.6 kernel config for SIR? I would like to readd it, but like to hear your reason to remove it first.

[[User:Pebolle|Paul Bolle]] 10:23, 14 Oct 2005 (CEST)

== T23 debianized kernel with probs ==

Found another crazy thing here. T23 2648-2GG, with 2.6.13 and 2.6.14 (Debianized Source). Clear init of nsc-ircc and dongle, but the dongle stays offline (dark and blind). Booted with Knoppix or Bart-PE Windows give correct function of the whole device, viewed with a digicam shows some blinks at init. But not with plain 2.6.13 an 2.6.14 from Debian.
Eric

== setpnp ==

Hello,

since the nsc-ircc patch isn't in 2.6.15, I tried to go the setpnp route, but I don't even get to see {{path|/proc/bus/pnp}} even though I enabled the support for it in the kernel config (once I found out that I need to enable ISA support to even get the option). Has anyone successfully used setpnp to enable the IRDA port or is that just some sort of urban legend? ;)

--[[User:Spiney|spiney]] 19:12, 4 Jan 2006 (CET)
----

Make sure you enable pnp-bios support specifically when compiling the kernel, just enabling pnp support is not enough.
I must however admit that I have not done this, since my ancient TP 770 running a 2.4 kernel, which was at least 5 years ago.

I just looked at a 2.6 menuconfig myself, and could not find the option, but looking at my .config file I can see the CONFIG_PNPBIOS option, so you might just want to edit the config file directly, enable the PNPBIOS option, and run make oldconfig.

--[[User:Tonko|Tonko]] 19:38, 4 Jan 2006 (CET)
----

I do have the pnp-bios support enabled (the option is depending on ISA among others, checked the Kconfig file in the source tree to find it), and also the proc-Interface option, but still no go... maybe it's not compatible with CONFIG_PNPACPI? Oh well, nevermind, going back to the patch, that works with less hassles, I just hope it'll end up in the vanilla kernel eventually. Still thanks for the help.

--[[User:Spiney|spiney]] 20:22, 4 Jan 2006 (CET)
----

Ok, on further investigation (not giving up that easily ;) it really seems that CONFIG_PNPACPI is disabling PnPBIOS, at least dmesg showed something along the lines of "PnPBIOS: disabled by PnPACPI". But, after recompiling without PnPACPI, I still can't get it to work. I can use {{cmd|setpnp|}} and {{cmd|lspnp|}} just fine, but the nsc-ircc module won't load:

<pre>
t43p:~# lspnp 12
12 IBM0071 IBM Thinkpad infrared port
t43p:~# setpnp 12 io 0x2f8 irq 3
t43p:~# lspnp -v 12
12 IBM0071 IBM Thinkpad infrared port
dma 3
io 0x02f8-0x02ff
irq 3
t43p:~# modprobe nsc-ircc io=0x2f8 irq=3 dongle_id=0x09
FATAL: Error inserting nsc_ircc (/lib/modules/2.6.15/kernel/drivers/net/irda/nsc-ircc.ko): No such device
</pre>

Hmm, I'm getting somewhat annoyed... any ideas?

--[[User:Spiney|spiney]] 20:58, 4 Jan 2006 (CET)
----

have you tried just doing {{cmd|setpnp 12 on|}}

--[[User:Tonko|Tonko]] 21:05, 4 Jan 2006 (CET)
----

Yes, that was the first thing I tried, didn't help. BTW, I just fiddled around with lirc a bit (never tried it before), and the lirc_sir module works just fine:

<pre>
lirc_sir: I/O port 0x02f8, IRQ 3.
lirc_sir: Installed.
</pre>

and I was able to get it to control xmms.

{{cmd|setserial|}} doesn't claim the device either:

<pre>
t43p:~# setserial -ag /dev/ttyS0
/dev/ttyS0, Line 0, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 921600, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test
</pre>

I'm really out of ideas.

--[[User:Spiney|spiney]] 21:20, 4 Jan 2006 (CET)
----

Hmm, it should not be ttyS0, but ttyS1 which might be stepping on the resources
ttyS0 is IO 0x3f8 and IRQ 4, while ttyS1 is IO 0x2f8 and IRQ 3.

ttyS0 is your integrated serial port, which even ThinkPads without physical serial port have.

--[[User:Tonko|Tonko]] 21:29, 4 Jan 2006 (CET)
----
Sorry, I cut'n'paste the wrong device since I checked them both, the output for ttyS1 is identical (apart from "/dev/ttyS1, Line 1" of course).

--[[User:Spiney|spiney]] 21:36, 4 Jan 2006 (CET)
----
No idea what might be wrong, perhaps it does not work on more recent machines, or kernels.

As I said, it worked for me a long time ago on my 770X with ''something'' like this:

/bin/setserial /dev/ttyS1 uart none port 0 irq 0
setpnp 12 io 0x2f8 irq 3
setpnp 12 on
modprobe nsc-ircc dongle_id=0x09 io=0x2f8 irq=3

What is the error you get from nsc-ircc in syslog? the "Wrong chip version ff" error?

--[[User:Tonko|Tonko]] 22:22, 4 Jan 2006 (CET)
----

No errors are recorded at all (dmesg, syslog), just the message above on stderr from {{cmd|modprobe|}}.

--[[User:Spiney|spiney]] 09:27, 5 Jan 2006 (CET)
----

BTW, is it just me or does the nsc-ircc patch only work if CONFIG_PNPACPI is set in the kernel config? Otherwise the module loads fine, (but without stating in the kernel log that it found the dongle) and using IRDA does not work, irattach returns "irattach: ioctl(SIOCGIFFLAGS): No such device".

--[[User:Spiney|spiney]] 14:37, 12 Jan 2006 (CET)
----

== Not even SIR working on R52 ==

I don't want/need FIR right now, so i thought i wouldn't have to mess with it.
I don't have /proc/bus/pnp, but i'm pretty sure infrared should work without it as well.
I do not have a kernel patch and am using the current Ubuntu Breezy 2.6.12-10 kernel.
Problem is, that when starting
irattach /dev/ttyS1 -s
It complains in syslog: no such device
On ttyS0 it works fine, but well does not find any packets.

# setserial -ag /dev/ttyS1
/dev/ttyS1, Line 1, UART: unknown, Port: 0x0000, IRQ: 0
Baud_base: 921600, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test

# cat /dev/ttyS1
cat: /dev/ttyS1: input-/outputerror

So i tried:
sudo setserial /dev/ttyS1 uart 16550A port 0x02f8 irq 3

Well ''now'' irattach will attach to ttyS1, irdadump will show me the packets '''sent''' by my computer,
but won't receive my cellphone's packets (Nokia 6210). In Windows, everything works fine.

===Same case here===
I have the same problem here, it used to work on 2.6.15. nsc-irc works, even a MCS7780 USB-IRDA adapter works, but the chip doesn't seem to send/receive on 2.6.17 and 2.6.18 (I checked with a CCD camera, no light signal at all), also ''findchip -d'' says:

root@golem3:/etc# findchip -d
Probing for FDC37C669 ...
Wrong chip id=0xff
Wrong chip id=0xff
Probing for FDC37C669FR ...
Wrong chip id=0xff
Wrong chip id=0xff
Probing for FDC37N869 ...
Wrong chip id=0xff
Wrong chip id=0xff
Probing for FDC37C93xFR ...
Wrong chip id=0xff
Wrong chip id=0xff
Probing for FDC37N957FR ...
Wrong chip id=0xff
Wrong chip id=0xff
Probing for FDC37N958FR ...
Wrong chip id=0xff
Wrong chip id=0xff
Probing for PC87108 ...
no chip at 0x150
no chip at 0x398
no chip at 0x0ea
Probing for PC87338 ...
no chip at 0x398
no chip at 0x15c
Wrong chip id=0x00
Probing for EFER at 0x03f0 ...
hefras = 0xff
Probing for EFER at 0x0370 ...
hefras = 0xff
EFER seems to be probed at 0x0370
chip id = 0xff, revision = 0xff
Wrong device ID = 0xff
Probing for EFER at 0x0250 ...
hefras = 0xff
Probing for EFER at 0x0250 ...
hefras = 0xff
Probing for EFER at 0x03f0 ...
hefras = 0xff
hefere = 0xff
Probing for EFER at 0x03f0 ...
hefras = 0xff
hefere = 0xff
EFER seems to be probed at 0x03f0
chip ID is 0x0f : no known chip was detected.
Couldn't find Winbond superI/O chip.

dmesg:

nsc-ircc, chip->init
nsc-ircc, Found chip at base=0x02e
nsc-ircc, driver loaded (Dag Brattli)
IrDA: Registered device irda0
nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500
IBM TrackPoint firmware: 0x0e, buttons: 3/3
serial8250: too much work for irq3
sirdev_get_instance - ttyS1
irtty_open - ttyS1: irda line discipline opened
irlap_change_speed(), setting speed to 9600
nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 3.
nsc-ircc, chip->init
nsc-ircc, Found chip at base=0x02e
nsc-ircc, driver loaded (Dag Brattli)
IrDA: Registered device irda0
nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500
--[[GuySoft]]

>Have you enabled infrared in BIOS?
[[User:Defiant|Defiant]] 21:25, 29 September 2006 (CEST)

Yes I did, It used to function in 2.6.15! its the new 2.6.17 kernel that messed it up, also 2.6.18 doesn't help.

==update - IBM31T1100 and lirc==

Working now in 2.6.18, however I can't get lirc to work.

In dmesg i get:
[code]
lirc_dev: lirc_register_plugin: sample_rate: 0
lirc_sir: i/o port 0x02f8 already in use.
[/code]

Also "/bin/setserial /dev/ttyS1 uart none" doesn't help

Any help there?
[[User:Guysoft|Guysoft]] 19:40, 31 December 2006 (CET)

==lirc and FIR works on R52!!==
I got both lirc and the FIR module to work on my thinkpad r52.

For lirc I had to :
$ killall -9 irattach
$ setserial /dev/ttyS1 uart none
$ rmmod nsc_ircc
then:
$ modprobe lirc_sir
and then run:
$ lircd -d /dev/lirc0 /etc/lircd.conf --nodaemon

For FIR i need to:
modprobe nsc_ircc
I hope this helps anyone that has problems.

[[User:Guysoft|Guysoft]] 15:08, 15 January 2007 (CET)

The lirc_sir module has problems with suspend (disk/ram both).

I'm using Debian Etch kernel 2.6.18-4-686 (version 2.6.18.dfsg.1-11)
with the lirc-modules-source (version 0.8.0-9.2). The lirc_sir module
was built with "other" as type of the SIR device.

With this kernel the nsc_ircc module suspends/resumes properly.

I tried to do a module unload and reload, but surprisingly even that failed.
Before the suspend I get normal output from mode2 but after the resume there is
no output at all :-(

[[User:Kapil|Kapil]] 15:39, 09 March 2007 (PST)

One a separate note. The "nsc_ircc" module and the "lirc_sir" module seem to conflict.

If I load one module and then the other, the system appears to hang. So I wonder how Guysoft managed to get this working.

[[User:Kapil|Kapil]] 15:46, 09 March 2007 (PST)

== T23 IrDA silent? ==

Hi.
I got SIR working pretty easily on my T20. I cannot get anything to work on my T23. I can get the nsc-ircc module to load, and now irattach works (both with and without nsc-ircc), and I've checked the relevant info in /proc/sys/net/irda, but nothing shows up in /proc/net/irda/discovery, and irdadump gives nothing at all. No errors in dmesg or the log. The red LED never lights. It flashes constantly in Windows.

--[[User:SystemParadox|SystemParadox]] 16:58, 1 May 2006 (CEST)

== Problems accessing a Nokia phone ==

i just compiled a brand new 2.6.18 Linux Kernel. Now, even tough the Kernel modules are loaded and irda-utils start correctly i am having trouble accessin my Nokia 6135.

This are the contents of my /etc/modprobe.d/irda-utils:

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3
install nsc-ircc /bin/setserial /dev/ttyS1 uart none port 0 irq 0; /sbin/modprobe --ignore-install nsc-ircc

/var/log/syslog:

Sep 28 11:33:00 raziel kernel: pnp: Device 00:0b activated.
Sep 28 11:33:00 raziel kernel: nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 3.
Sep 28 11:33:00 raziel kernel: nsc-ircc, chip->init
Sep 28 11:33:00 raziel kernel: nsc-ircc, Found chip at base=0x02e
Sep 28 11:33:00 raziel kernel: nsc-ircc, driver loaded (Dag Brattli)
Sep 28 11:33:00 raziel kernel: IrDA: Registered device irda0
Sep 28 11:33:00 raziel kernel: nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500
Sep 28 11:34:34 raziel irattach: got SIGTERM or SIGINT
Sep 28 11:34:34 raziel irattach: Stopping device irda0
Sep 28 11:34:34 raziel irattach: exiting ...
Sep 28 11:34:35 raziel irattach: executing: '/sbin/modprobe irda0'
Sep 28 11:34:35 raziel irattach: executing: 'echo raziel > /proc/sys/net/irda/devname'
Sep 28 11:34:35 raziel irattach: executing: 'echo 1 > /proc/sys/net/irda/discovery'
Sep 28 11:34:35 raziel irattach: Starting device irda0
Sep 28 11:34:35 raziel kernel: irlap_change_speed(), setting speed to 9600

But when wammu tries to find the phone (which is right in front of the left side of laptop, where the IR port supposedly is AND it has IR reception enabled):

Starting /dev/ttyS0 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Starting /dev/ttyS1 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Starting /dev/ttyS2 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Scanning for bluetooth devices using PyBluez
Could not access Bluetooth subsystem (error accessing bluetooth device)
Finished /dev/ttyS0 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyS1 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyS2 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
All finished, found 0 phones

This phone does not have bluetooth so im basically out of options, ideas anyone?

Any suggestions much appreciated

--[[User:Havok1977|Havok1977]] 12:05, 28 Sep 2006 (CEST)

== No irrecord output ==

So I loaded lirc_sir on my T43 and it says all is ok. However I don't seem to get anything out of irrecord. I am pretty sure my remote control is ok. What am I missing?

--[[User:mr.dnme|mr.dnme]] 19:29, 25 Jan 2008

== 2.6.27 auto sets dongle_id ==

Just a quick note that as of 2.6.27 the nsc_ircc driver auto sets the dongle_id to 0x09 when loading on a ThinkPad (based on IrDA ISA PnP ID).
So one less thing that needs to be configured. In fact with this change I think all the outstanding issues are resolved and the nsc_ircc driver should load without any modprobe.conf modifications.
--[[User:Tonko|Tonko]] 21:51, 20 October 2008 (CEST)

== LIRC and IrDA ==

LIRC and IrDA now works on my Thinkpad 600.
The hardest part was to keep away nsc-ircc from configuring
the system. Finally i decided to move the complete irda-path
from /lib/modules... to another location :-)
Now the IR-module receives commands from all of my 4 remote
controls. I will create a lircd.conf with irrecord, using
with the generic/NEC.conf, for the RC from Aiwa, RC-AVR05
the next days. Now i have go to the cinema, Berlinale is calling.
Bye
--Hagen [[User:Hagen-cool|Hagen]] 20:00, 20 February 2011 (CET)

Talk:How to make use of IrDA

2011-02-20T18:56:10Z

Hagen-cool: /* LIRC and IrDA */ new section

How to make use of IrDA

2011-02-20T18:46:50Z

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

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#efefef; align:right;">
The purpose of this document is to get the [[IrDA]] hardware in your ThinkPad operational, setting up communication to other devices is not covered. However, the external links section can prove useful for this.
</div>
|}

== Serial IR (SIR) ==
SIR is limited to serial datarates up to 115.2Kb/s

On modern distributions all configuration might be taken care of automatically by starting the irda service {{cmdroot|service irda start}}. If not try the following;

To use it, run {{cmdroot|irattach /dev/ttyS1 -s; modprobe ircomm-tty}}

Then turn on your IrDA-capable device and put it within range, and point your software (e.g., <tt>minicom</tt>) to {{path|/dev/irda0}}.

===Kernel configuration===

Edit {{path|/etc/modprobe.conf}} and add the following lines
alias tty-ldisc-11 irtty-sir
alias char-major-161 ircomm-tty

== Fast IR (FIR) ==
FIR is the preferred mode of IrDA operation and operates at a maximum bandwidth of 4 Mbps

On modern distributions this should all be automatically handled by simply starting the idra service {{cmdroot|service irda start}}. If not try the following;

===Kernel configuration===
Edit {{path|/etc/modprobe.conf}} and add the following lines

alias irda0 nsc-ircc

Make sure that setserial is in right directory (e.g not in /usr/bin/setserial).After that if irdadump still gives nothing try:
echo 1 > /proc/sys/net/irda/discovery

== 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 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; modprobe nsc_ircc

== Some other things you might want to do with IrDA ==
* add fast PPP support:
:{{cmdroot|modprobe irnet}}
* if needed, limit further the size of the transmit window
:{{cmdroot|echo 1 > /proc/sys/net/irda/max_tx_window}}
* set the connection speed to 4Mbit in FIR mode:
:{{cmdroot|echo 4000000 > /proc/sys/net/irda/max_baud_rate}}

==LIRC and IrDA==
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}}
====Success reports====
* R40
* T41
* T60
* 600

====Failure reports====
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.

Boot into Linux, and first ensure the setserial program is installed. Running {{cmdroot|/bin/setserial /dev/ttyS1}} should return at this point:
/dev/ttyS1, UART: undefined, Port: 0x02f8, IRQ: 3
If setserial cannot be found, install the setserial package with your distributions package management software

Then create a file {{path|/etc/modprobe.d/lirc.conf}} with the following content:
# prevent nsc_ircc from loading (blacklist might not be enough)
blacklist nsc_ircc
install nsc_ircc /bin/true
# pass options to lirc_sir to load it on ttyS1
options lirc_sir io=0x2f8 irq=3
# ensure serial resources are cleared before loading lirc_sir
# not doing so can result in a device busy error, or can even hang your system
install lirc_sir /bin/setserial /dev/ttyS1 uart none port 0 irq 0; /sbin/modprobe --ignore-install lirc_sir

At this point it is best to reboot, to ensure that nsc_ircc was never loaded. Several things can go wrong if the steps are not followed accurately. You might get an error when loading lirc_sir that the device is busy, or your system may even hang.

Now do a {{cmdroot|modprobe lirc_sir}} and check {{cmdroot|dmesg}} output. You should see something like this:
lirc_dev: IR Remote Control driver registered, major 61
lirc_dev: lirc_register_plugin: sample_rate: 0
lirc_sir: I/O port 0x02f8, IRQ 3.
lirc_sir: Installed.

===Configuring LIRC===
If you did not yet install LIRC, then do so now using your distributions package management system.

====Ubuntu====
Make sure your {{path|/etc/lirc/hardware.conf}} looks like this:
REMOTE="SIR IrDA (built-in IR ports)"
REMOTE_MODULES="lirc_dev lirc_sir"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_LIRCD_CONF=""
REMOTE_LIRCD_ARGS=""
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""
START_LIRCD="true"
START_LIRCMD=""
LOAD_MODULES=""
LIRCMD_CONF=""
FORCE_NONINTERACTIVE_RECONFIGURATION="false"

After this, start (or re-start) the lirc daemon, and set it to automatically start on bootup.

{{cmdroot|service lirc restart}}<br>
{{cmdroot|update-rc.d lirc defaults}}
====Fedora====
On Fedora the default LIRC device is already set to /dev/lirc0

{{Todo|best way of ensuring lirc_sir is loaded before lircd is started? The config file /etc/sysconfig/lirc does not seem to help. Perhaps an alias line in the modules config file if someone knows the correct syntax?}}

{{cmdroot|service lirc restart}}<br>
{{cmdroot|chkconfig lirc on}}

===Testing LIRC===
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.

You are now able to start configuring LIRC for your specific remote control.

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|$}}.

{{NOTE|Current versions of gnome-lirc-properties (at least up to 0.3.1) do not support lirc_sir, you need to first edit {{path|/usr/share/gnome-lirc-properties/receivers.conf}} and add the following:<br><pre>[Generic: IrDA SIR Receiver]
kernel-module = lirc_sir
device-nodes = /dev/lirc0</pre>
After this you can select Generic - IrDA SIR Receiver from the drop down menus (autodetect will not pick it up)}}

== External Sources ==
*[http://irda.sourceforge.net/ Linux-IrDA Project] (External)
*[http://pcmcia-cs.sourceforge.net/ Linux PCMCIA Project] (External)
*[http://tpctl.sourceforge.net/ tpctl homepage] (External)
*[http://www.lirc.org/ Linux Infrared Remote Control (LIRC)] (External)

How to make use of IrDA

2011-02-20T18:46:18Z

Hagen-cool: /* Success reports */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#efefef; align:right;">
The purpose of this document is to get the [[IrDA]] hardware in your ThinkPad operational, setting up communication to other devices is not covered. However, the external links section can prove useful for this.
</div>
|}

== Serial IR (SIR) ==
SIR is limited to serial datarates up to 115.2Kb/s

On modern distributions all configuration might be taken care of automatically by starting the irda service {{cmdroot|service irda start}}. If not try the following;

To use it, run {{cmdroot|irattach /dev/ttyS1 -s; modprobe ircomm-tty}}

Then turn on your IrDA-capable device and put it within range, and point your software (e.g., <tt>minicom</tt>) to {{path|/dev/irda0}}.

===Kernel configuration===

Edit {{path|/etc/modprobe.conf}} and add the following lines
alias tty-ldisc-11 irtty-sir
alias char-major-161 ircomm-tty

== Fast IR (FIR) ==
FIR is the preferred mode of IrDA operation and operates at a maximum bandwidth of 4 Mbps

On modern distributions this should all be automatically handled by simply starting the idra service {{cmdroot|service irda start}}. If not try the following;

===Kernel configuration===
Edit {{path|/etc/modprobe.conf}} and add the following lines

alias irda0 nsc-ircc

Make sure that setserial is in right directory (e.g not in /usr/bin/setserial).After that if irdadump still gives nothing try:
echo 1 > /proc/sys/net/irda/discovery

== 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 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; modprobe nsc_ircc

== Some other things you might want to do with IrDA ==
* add fast PPP support:
:{{cmdroot|modprobe irnet}}
* if needed, limit further the size of the transmit window
:{{cmdroot|echo 1 > /proc/sys/net/irda/max_tx_window}}
* set the connection speed to 4Mbit in FIR mode:
:{{cmdroot|echo 4000000 > /proc/sys/net/irda/max_baud_rate}}

==LIRC and IrDA==
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}}
====Success reports====
* R40
* T41
* T60
600

====Failure reports====
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.

Boot into Linux, and first ensure the setserial program is installed. Running {{cmdroot|/bin/setserial /dev/ttyS1}} should return at this point:
/dev/ttyS1, UART: undefined, Port: 0x02f8, IRQ: 3
If setserial cannot be found, install the setserial package with your distributions package management software

Then create a file {{path|/etc/modprobe.d/lirc.conf}} with the following content:
# prevent nsc_ircc from loading (blacklist might not be enough)
blacklist nsc_ircc
install nsc_ircc /bin/true
# pass options to lirc_sir to load it on ttyS1
options lirc_sir io=0x2f8 irq=3
# ensure serial resources are cleared before loading lirc_sir
# not doing so can result in a device busy error, or can even hang your system
install lirc_sir /bin/setserial /dev/ttyS1 uart none port 0 irq 0; /sbin/modprobe --ignore-install lirc_sir

At this point it is best to reboot, to ensure that nsc_ircc was never loaded. Several things can go wrong if the steps are not followed accurately. You might get an error when loading lirc_sir that the device is busy, or your system may even hang.

Now do a {{cmdroot|modprobe lirc_sir}} and check {{cmdroot|dmesg}} output. You should see something like this:
lirc_dev: IR Remote Control driver registered, major 61
lirc_dev: lirc_register_plugin: sample_rate: 0
lirc_sir: I/O port 0x02f8, IRQ 3.
lirc_sir: Installed.

===Configuring LIRC===
If you did not yet install LIRC, then do so now using your distributions package management system.

====Ubuntu====
Make sure your {{path|/etc/lirc/hardware.conf}} looks like this:
REMOTE="SIR IrDA (built-in IR ports)"
REMOTE_MODULES="lirc_dev lirc_sir"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_LIRCD_CONF=""
REMOTE_LIRCD_ARGS=""
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""
START_LIRCD="true"
START_LIRCMD=""
LOAD_MODULES=""
LIRCMD_CONF=""
FORCE_NONINTERACTIVE_RECONFIGURATION="false"

After this, start (or re-start) the lirc daemon, and set it to automatically start on bootup.

{{cmdroot|service lirc restart}}<br>
{{cmdroot|update-rc.d lirc defaults}}
====Fedora====
On Fedora the default LIRC device is already set to /dev/lirc0

{{Todo|best way of ensuring lirc_sir is loaded before lircd is started? The config file /etc/sysconfig/lirc does not seem to help. Perhaps an alias line in the modules config file if someone knows the correct syntax?}}

{{cmdroot|service lirc restart}}<br>
{{cmdroot|chkconfig lirc on}}

===Testing LIRC===
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.

You are now able to start configuring LIRC for your specific remote control.

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|$}}.

{{NOTE|Current versions of gnome-lirc-properties (at least up to 0.3.1) do not support lirc_sir, you need to first edit {{path|/usr/share/gnome-lirc-properties/receivers.conf}} and add the following:<br><pre>[Generic: IrDA SIR Receiver]
kernel-module = lirc_sir
device-nodes = /dev/lirc0</pre>
After this you can select Generic - IrDA SIR Receiver from the drop down menus (autodetect will not pick it up)}}

== External Sources ==
*[http://irda.sourceforge.net/ Linux-IrDA Project] (External)
*[http://pcmcia-cs.sourceforge.net/ Linux PCMCIA Project] (External)
*[http://tpctl.sourceforge.net/ tpctl homepage] (External)
*[http://www.lirc.org/ Linux Infrared Remote Control (LIRC)] (External)