Bug 188955

Summary:	device for ipw2200 changes each boot
Product:	[Fedora] Fedora	Reporter:	Benjamin Hardill <b.hardill>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED ERRATA	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	notting, pjones, rbiba, rvokal, tomek
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-09-22 15:18:16 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:
Bug Depends On:
Bug Blocks:	150224

Description Benjamin Hardill 2006-04-13 21:40:01 UTC

Description of problem:
The device created for ipw2200 wireless ethernet card changes each boot. It
apears to be intermitant, it will somethimes be created at /dev/eth1 (expected
behaviour) but also as /dev/dev4083 or simlare.

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


How reproducible:
This apears to occurs about 4 out of 5 times

Steps to Reproduce:
1. Start laptop
2. Let NetworkManager bing up the interface
3.
  
Actual results:
device created as /dev/dev#####

Expected results:
device created as /dev/eth1

Additional info:

Comment 1 Harald Hoyer 2006-04-18 09:34:42 UTC

Bill, is this a problem with the interface renaming?

Comment 2 Radek Bíba 2006-04-18 18:44:29 UTC

I actually use a record in /etc/iftab that automatically renames my wireless
device to wlan0 since I don't like the idea of having eth* for wifi, but am
interested in this bug, too.

Comment 4 Bill Nottingham 2006-04-18 19:06:42 UTC

Please try the updates-testing initscripts.

Comment 5 Jeremy Katz 2006-09-22 04:01:25 UTC

Is this still happening?

Comment 6 Benjamin Hardill 2006-09-22 07:14:45 UTC

Sorry I no longer have the t40p with this card in to test.

Comment 7 Bill Nottingham 2006-09-22 15:18:16 UTC

This should be fixed in either the FC5 updates or the FC6 devel tree. Please
reopen if it is not fixed.