Bug 106658

Summary: autonegotioantion of network speed not always working working correctly
Product: [Fedora] Fedora Reporter: og <olaf.greis>
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED CURRENTRELEASE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideKeywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-10-09 15:14:58 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 og 2003-10-09 07:08:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
not all network cards will choose the correct speed/duplex combination when
using dhcp for initial boot when ks.cfg later assigns a fixed address.

this might slow down the installation in an environment where 100baseTx-FD is
possible but only 10baseTx-HD is used.

it would be nice if mii-tool could be included into the ramdisk that gets loaded
via the network, since then one could adjust the network speed in the %pre
section and thus reduce installation time.

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

How reproducible:
Always

Steps to Reproduce:
1. boot via vanilla dhcp into kickstart installation
2.
3.
    

Additional info:

Comment 1 Jeremy Katz 2003-10-09 15:14:58 UTC
Functionality is already present :-)

Add '--ethtool="speed 100 duplex full"' to the network line of your ks.cfg or
add 'ethtool="speed 100 duplex full"' to your command line on boot and it will
get set.