Bug 167305

Summary:	rmmod ipw2200; modprobe ipw2200 required
Product:	[Fedora] Fedora	Reporter:	Andrew Overholt <overholt>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	jhealy, jjohnstn, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	2.6.13-1.1532_FC4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-11-11 02:30:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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):
NetworkManager-0.4-20.FC4.1

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 (2.6.13.2). 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.

Thanks.

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).