Red Hat Bugzilla – Bug 223751
irda breaks orinoco
Last modified: 2008-08-02 19:40:36 EDT
Description of problem:
After applying recent updates my wireless card quit working. It is an
old Prism2-based 802.11b card using orinoco and orinoco_cs. The symptom
was that when I tried to bring up the interface using DHCP I would get
the error "failed; no link present. Check cable?"
Coincident to this I noticed I had a new network interface I'd never
seen before, irda0. Putting two and two together I started unloading
modules associated with the irda0 interface. After unloading the
nsc_ircc module I was able to bring up and pass traffic over the
wireless interface. Unloading the other IRDA modules (irda and crc_ccitt)
was not required.
I booted to the last few FC6 kernels to see when this may have started
but all of the recent kernels demonstrated the same problem. What is new
is that I never had an irda0 interface before. So something I updated
(udev?) is now loading the modules for irda0 during system boot whereas
before they were not getting loaded.
Version-Release number of selected component (if applicable):
kernel-2.6.19-1.2895.fc6, 2.6.18-1.2869.fc6, and 2.6.18-1.2868.fc6.
Steps to Reproduce:
1. Get a laptop with IRDA and add a Prism2-based wireless PCMCIA card.
(My combo is an IBM A20m Thinkpad and an Addron 802.11b card)
2. Boot FC6. Verify that you have network interfaces for both
irda and wireless. Modules loaded should include nsc_ircc, irda,
crc_ccitt, orinoco, orinoco_cs, and hermes.
3. Configure the wireless interface. If you use DHCP it will fail
to get an address. If you use a static address then it will configure
fine but it won't pass any traffic.
No traffic able to pass over the wireless interface.
Traffic is able to pass over the wireless interface.
Workaround - unload the nsc_ircc module.
(This is a mass-update to all current FC6 kernel bugs in NEW state)
I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug, however this version of Fedora is no longer
Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.
Thanks for using Fedora!
Sorry. You were too slow on this one. I no longer have the hardware setup
necessary to reproduce the problem. Maybe if you had responded in something
less than two years I could have helped you out.