Bug 11546

Summary:	pcmcia starts too late for laptop ethernets
Product:	[Retired] Red Hat Linux	Reporter:	Cameron Simpson <cs>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	6.2	CC:	rvokal, sxpert, 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:	2000-07-26 18:55:53 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 Cameron Simpson 2000-05-21 02:22:48 UTC

On many laptops the ethernet is attached to a PCMCIA card.
The RedHat 6.2 startup tries to initialise the ethernet before starting
the card services, and fails if eth0 is on the PCMCIA card.

I encountered this on an IBM Thinkpad. It was sufficient to move the PCMCIA
startup to before the ethernet startup. Since PCMCIA doesn't depend on
much this should be pretty safe to do across the board.

Comment 1 Bill Nottingham 2000-05-31 22:36:54 UTC

This shouldn''t be a problem, as PCMCIA should start
up the network card itself; are you saying it doesn''t?

Comment 2 Tomasz Kepczynski 2000-07-26 18:55:53 UTC

Well, it usually is not a problem with device initialization. But PCMCIA is
initialized
after YP, NFS, NFSFS and so on. This causes problems if laptop is usually
connected
to a network and depends on these services. Shouldn't PCMCIA statrup be moved
so it initialises befor network services are started?

Comment 3 Bill Nottingham 2000-08-07 05:13:04 UTC


*** This bug has been marked as a duplicate of 15275 ***

Comment 4 Bill Nottingham 2003-05-19 00:29:02 UTC

*** Bug 90609 has been marked as a duplicate of this bug. ***