Bug 162053 - Installer detects two NICS, but doesn't bring them up
Installer detects two NICS, but doesn't bring them up
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2005-06-29 10:44 EDT by Todd Warfield
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-08 14:26:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Todd Warfield 2005-06-29 10:44:12 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
Using kickstart on a HP ML380G4 with two Broadcom integrated NICs on RHEL ES 3 Update 4 will present the selection to choose a NIC. Found the suggestion to use ksdevice=eth<#> but that still presents the options. Looking at the Alt-F4 screen output does not show the card coming up. Even attempted to disable the second card in the BIOS, but the installer still sees both.

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

How reproducible:

Steps to Reproduce:
1.boot off boot ISO
2.at boot prompt, typing linux ks=cdrom:/ks.cfg ksdevice=eth0 ip=<ip> gateway=<gw> netmask=<mask> dns=<dns,dns,dns> method=nfs:<nfsserver>:/path
3.prompted to select NIC

Actual Results:  ananconda will not bring the interface up. If we go back and select the other NIC, it will then come up, but anaconda will go back to the selecting the adapter. Selecting the eth0 NIC will now proceed through the installer.

Expected Results:  Using the ksdevice=<eth#> should just continue to go through anaconda and finish the install.

Additional info:
Comment 1 Todd Warfield 2005-06-29 10:46:14 EDT
This is on RHEL ES 3 Update 5 {not 4 as mentioned in the original}
Comment 2 Jeremy Katz 2005-07-08 14:26:35 EDT
Make sure your kickstart config also specifies a device in the network line
(--device foo)

Note You need to log in before you can comment on or make changes to this bug.