Bug 16536 - pcmcia_cs in kernel 2.2.16-1 confuses Eth NICs in 2-nic installs if eth0 not present at boot
Summary: pcmcia_cs in kernel 2.2.16-1 confuses Eth NICs in 2-nic installs if eth0 not ...
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel   
(Show other bugs)
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-08-18 15:52 UTC by Bishop Clark
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-18 15:52:46 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bishop Clark 2000-08-18 15:52:44 UTC 
On my 2.2.16-1 system, I have two nics.  In cases where I boot without the Eth0 nic in place, the system sees the eth1 NIC, activates it and  
assigns it the parameters for Eth0.  I have my conf.modules associating the correct and different module with the correct card, and the cardctl 
ident shows eth1 is present... but it's still set up with eth0's info.

If required, I can test with 2.2.16-3 / Pinstripe.
Comment 1 Michael K. Johnson 2000-08-18 16:26:27 UTC 
This is just the way the Linux kernel works.  I suggest that
if you are in the habit of removing eth0, that you change
them around, so that your old eth0 becomes eth1 and vice versa;
also change around your configuration files
(/etc/sysconfig/network-scripts/ifcfg-eth* at least) to match.
Note You need to log in before you can comment on or make changes to this bug.