Bug 167305 - rmmod ipw2200; modprobe ipw2200 required
Summary: rmmod ipw2200; modprobe ipw2200 required
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 4
Hardware: All Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-09-01 14:34 UTC by Andrew Overholt
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version: 2.6.13-1.1532_FC4
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-11-11 02:30:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Andrew Overholt 2005-09-01 14:34:17 UTC
Description of problem:
The ipw2200 module seems to require a reload for NM to function properly.

Version-Release number of selected component (if applicable):

How reproducible:
Always on kernels 2.6.11-1.1369_FC4 and 2.6.12-1.1447_FC4.

Steps to Reproduce:
1. Start up computer with NetworkManager set to start at boot.
2. Watch as wireless network scan goes and it finds rh-wireless
3. Observe as NM attempts to connect to rh-wireless but seems to time out on
connection attempt and restarts network scan.
4. # rmmod ipw2200; modprobe ipw2200 and service NetworkManager restart
5. NM scans, finds rh-wireless, and connects very quickly

Actual results:
See steps above

Expected results:
No module unload; reload required.

Additional info:
This is a brand new IBM T42.  lspci says:  Intel Corporation PRO/Wireless 2200BG
(rev 05).  I've tried two different versions of the firmware and the same
behaviour occurs in both cases.  dmesg has a entries about WEP decryption
failing.  Sorry if this is a NM bug.

Comment 1 Dave Jones 2005-11-10 22:01:29 UTC
Mass update to all FC4 bugs:

An update has been released (2.6.14-1.1637_FC4) which rebases to a new upstream
kernel ( As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.

Please retest with this update, and update this bug if necessary.


Comment 2 Andrew Overholt 2005-11-11 02:30:17 UTC
This no longer appears to be necessary (as of 2.6.13-1.1532_FC4, actually).

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