Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18474 - [kernel26] irda not working on acer aspire 5010
Attached to Project:
Arch Linux
Opened by Kiss Ákos (akosch) - Friday, 26 February 2010, 14:45 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 10 August 2010, 07:36 GMT
Opened by Kiss Ákos (akosch) - Friday, 26 February 2010, 14:45 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 10 August 2010, 07:36 GMT
|
Details"modprobe nsc-ircc" gives me:
nsc-ircc 00:0a: activated nsc-ircc, chip->init nsc-ircc, Found chip at base=0x02e nsc-ircc, driver loaded (Dag Brattli) IrDA: Registered device irda0 nsc-ircc, Found dongle: Supports SIR Mode only nsc-ircc, chip->init nsc-ircc, Found chip at base=0x02e nsc-ircc, driver loaded (Dag Brattli) nsc_ircc_open(), can't get iobase of 0x2f8 load-modules.sh: 'platform:nsc-ircc' is not a valid module or alias name in messages.log. With "irattach /dev/ttyS1 -s" I get the following: irattach: Stopping device /dev/ttyS1 irattach: ioctl(SIOCGIFFLAGS): No such devi ce irattach: exiting ... Output of "dmesg | grep -n2 Serial": 347-io scheduler cfq registered (default) 348-Linux agpgart interface v0.103 349:Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled 350-serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A 351-serial 0000:00:14.6: PCI INT B -> GSI 17 (level, low) -> IRQ 17 |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Tuesday, 10 August 2010, 07:36 GMT
Reason for closing: No response
Additional comments about closing: No response in +2 months. If this issue persist, please open a ticket in bugzilla at kernel.org
Tuesday, 10 August 2010, 07:36 GMT
Reason for closing: No response
Additional comments about closing: No response in +2 months. If this issue persist, please open a ticket in bugzilla at kernel.org
Comment by Kiss Ákos (akosch) -
Friday, 26 February 2010, 14:46 GMT
And yes, I have the device enabled in the BIOS.
Comment by Gerardo Exequiel Pozzi (djgera) -
Sunday, 28 February 2010, 00:18 GMT
Please try with latest 2.6.33 and report back. If persist, ensure that the module is correct for your hardware and report to upstream. Thanks.
Comment by Thomas Dziedzic (tomd123) -
Thursday, 03 June 2010, 04:33 GMT
status?
Comment by Kiss Ákos (akosch) -
Thursday, 03 June 2010, 05:16 GMT
I'll try again sometime this week and report back any progress.