Bug 5639 - IRDA not working on Asus M2400N
Summary: IRDA not working on Asus M2400N
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Config-Interrupts (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Samuel Ortiz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-23 04:46 UTC by Andrej Podzimek
Modified: 2006-08-06 03:49 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.14.2
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
The output of dmesg -s 1000000 (15.10 KB, text/plain)
2006-01-01 05:35 UTC, Andrej Podzimek
Details
The same situation with different acpi_irq_isa (15.46 KB, text/plain)
2006-01-01 16:07 UTC, Andrej Podzimek
Details
This is an output from findchip. (1.03 KB, text/plain)
2006-04-16 06:43 UTC, Andrej Podzimek
Details

Description Andrej Podzimek 2005-11-23 04:46:36 UTC
Most recent kernel where this bug did not occur: 2.6.9
Distribution: Using Vanilla kernel, not the stack kernel. (Distribution: ArchLinux)
Hardware Environment: Asus M2400N, Centrino
Software Environment: Linux/X.org/KDE

Problem Description:
The IRDA port does not work. There are at least five howtos on various websites,
but none of them really works. The recommended options acpi_irq_balance and
acpi_irq_isa=3,12 do not help at all. The situation remains the same. Dmesg says:
nsc-ircc, Found chip at base=0x02e
nsc-ircc, driver loaded (Dag Brattli)
nsc_ircc_open(), can't get iobase of 0x2f8
None of the module options recommended in various howtos work. Modprobe always
falis with "no such device".

Steps to reproduce:
Simply boot and try to modprobe nsc-ircc.
Comment 1 Andrej Podzimek 2005-11-25 07:33:09 UTC
Exactly the same problem in 2.6.14.3.
Comment 2 Adrian Bunk 2006-01-01 04:20:12 UTC
Jean, can you look into this bug?

Andrej, please attach the complete output of "dmesg -s 1000000" to this bug.
Comment 3 Andrej Podzimek 2006-01-01 05:35:53 UTC
Created attachment 6909 [details]
The output of dmesg -s 1000000

Here it is. :-)
Comment 4 Andrej Podzimek 2006-01-01 16:07:22 UTC
Created attachment 6911 [details]
The same situation with different acpi_irq_isa

The previous output was generated with the acpi_irq_isa option set in a
different way than recommended. Now I changed it to "3,7,12". IRQs 3 and 12
should be used by the IRDA port driver. (IRQ 7 is used by the LPT printer
driver.) Three last lines show what happens when nsc_ircc is loaded.
Comment 5 Adrian Bunk 2006-04-15 02:33:34 UTC
Samuel, can you look into this bug?

Andrej, I assume this issue is still present in kernel 2.6.16?
Comment 6 Andrej Podzimek 2006-04-15 05:51:46 UTC
Yes, unfortunately... Still present in 2.6.16.1. Shell I also try 2.6.16.5?
Comment 7 Adrian Bunk 2006-04-15 05:58:55 UTC
I don't see anything between 2.6.16.1 and 2.6.16.5 that have any influence on
your problem.
Comment 8 Samuel Ortiz 2006-04-15 12:32:11 UTC
Andrej, can you try compiling nsc-ircc as a module and running "setserial
/dev/ttySX uart none port 0 irq 0" before modprobing it ? ttySX should
correspond to the UART your nsc-ircc is connected to.
Comment 9 Andrej Podzimek 2006-04-15 17:48:54 UTC
The module does load after setserial. However, it does not work. After
experimenting with multiple howtos about my machine, I gave up. None of the
irda-utils can connect to the device.
Comment 10 Samuel Ortiz 2006-04-16 03:45:05 UTC
Could you please provide us with some syslog/dmesg when you're trying to use the
device with irda-utils ?
Comment 11 Andrej Podzimek 2006-04-16 06:43:41 UTC
Created attachment 7881 [details]
This is an output from findchip.
Comment 12 Andrej Podzimek 2006-04-16 06:51:51 UTC
This is what happens when I start lircd -n and irkick.

lircd: lircd(all) ready
lircd: accepted new client on /dev/lircd
lircd: could not open /dev/lirc
lircd: default_init(): No such device or address
lircd: caught signal

I tried to create /dev/lirc using mknod c 61 0 and mknod c 61 4. None of them
worked.
Comment 13 Andrej Podzimek 2006-04-16 06:56:27 UTC
I used information from these two howtos:
http://www.bigendian.dk/ASUSM2400N.html
http://tuxmobil.org/asus_m2400n.html
No success so far.
Before modprobing nsc_ircc, I used setserial /dev/ttyS1 uart none port 0 irq 0,
based on dmesg | grep tty, which returns "serial8250: ttyS1 at I/O 0x2f8 (irq =
3) is a NS16550A".
Comment 14 Samuel Ortiz 2006-04-23 10:34:23 UTC
Andrej, could you try the following:
1) Remove anything related to nsc-ircc from your modules.conf file
2) modprobe nsc-ircc dongle_id=0x09
3) irattach irda0 -s
4) irdadump 

I need the dmesg output for 2), 3) and 4).

Comment 15 Adrian Bunk 2006-08-06 03:49:15 UTC
Please reopen this bug if:
- it is still present in kernel 2.6.17 and
- you can provide the requested data.

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