Bug 85566

Summary: xircom_cb device eth0 seems not to be present
Product: [Retired] Red Hat Public Beta Reporter: Mikael Carneholm <carniz>
Component: bootyAssignee: Jeremy Katz <katzj>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: phoebe   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-04-02 05:24:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mikael Carneholm 2003-03-04 14:50:04 UTC
Description of problem:
During boot, the error message "xircom_cb device eth0 seems not to be present,
delaying initialization." [FAILED]. Could this have to do with the order in
which the services are started? Looking in /var/log/boot.log, this is how it looks:

Mar  4 11:22:41 citation pcmcia: Starting PCMCIA services:
Mar  4 11:22:39 citation network: Setting network parameters:  succeeded 
Mar  4 11:22:39 citation ifup: Cannot find device "eth0" 
Mar  4 11:22:39 citation network: Bringing up loopback interface:  succeeded 
Mar  4 11:22:42 citation pcmcia:  cardmgr.      // <-- pcmcia started AFTER network
Mar  4 11:22:43 citation rc: Starting pcmcia:  succeeded  // <-- isn't eth0
avaiable first now?

How reproducible:

Steps to Reproduce:
1. Boot
2. Done

Actual results:
pcmcia NIC initialised (later), but an confusing error message is displayed.

Expected results:
No error message should be displayed.

Additional info:
This laptop did not have the same problem with 8.0.

Comment 1 Jeremy Katz 2003-04-02 05:24:44 UTC
This is due to the way pcmcia devices are now detected and some other things all
coming together.  Summary is to ignore it :(