From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4 Description of problem: After upgrading to kernel 2.6.11-1.35_FC3 I was unable to obtain IP-address. Loading with the previous kernel made everything work as normal. A workaround was found in the Fedora-list: On Mon, 2005-06-27 at 13:29, Truls Gulbrandsen wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi, >> after updating the kernel I am no longer able to obtain an IP-adress >> from my router. Loading the previous kernel makes everything working fine. >> >> My configuration is an IBM TP T23 with a Cisco 350 Series PCMCIA Wlan card. >> >> Does anyone have an ide for a different workaround or should I wait for >> the next kernel update? Try deleting the CHANNEL line (or comment it out) in the ifcfg file. I have experienced a problem with ipw2200bg chipset where that appears to be a possible fix. Was able to see the access points but the card was never able to establish a connection and get an IP address. Suspect this points to a fundamental flaw in how the wireless cards are handled by the system. -- Scot L. Harris webid.com Version-Release number of selected component (if applicable): 2.6.11-1.35_FC3 How reproducible: Always Steps to Reproduce: 1. boot FC3 with kernel 2.6.11-1.35_FC3 without commenting out CHANNEL in in ifcfg 2. 3. Actual Results: I was unable to obtain IP-address from the router, however, kwifimanager showed that I had contact with it. Expected Results: I should have received an IP-address. Additional info:
There were no IPW changes in the last kernel update (nor have there been for some time in FC3). Additionally, this sounds more like a configuration problem than a driver bug.
Please tell me, how can this be a configuration problem when everything works using kernel 2.6.11-1.27_FC3 but fails using kernel 2.6.11-1.35_FC3 without any other changes? Does applying the work-around, commenting out the CHANNEL line, have any negative consequence to my system? Truls
This seems to be a change within the driver... If this behaviour is considered standard, then $ rpm -qf /etc/sysconfig/network-scripts/ifup-wireless initscripts-8.11.1-1 should be corrected
See comment #1. "There were no IPW changes in the last kernel update"
If channel is not needed, then it probably shouldn't be in the config file; why was it specified beforehand?
Closing this bug - FC3 is older and no longer supported. Please reopen if this persists on a current release. Apologies for the delay.