Red Hat Bugzilla – Bug 104137
Kickstart unable to lock NIC media type
Last modified: 2007-04-18 12:57:29 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR
1.0.3705; .NET CLR 1.1.4322)
Description of problem:
I am trying to develop a kickstart deployment process for the Dell poweredge
650, the IBM x335, and the Hp/Compaq dl360 g3. I have created a Custom
bootnet.img that supports the e1000 and bcm5700 NIC's, and if I leave the
network switch set to auto negotiate, everything works fine. Unfortunantely,
all of the
switch port will be locked and therfore I need to be able to lock the media
type to 100 / full in the kickstart script. I have tried several variations of
command in the kickstart script without any luck. Here are some of the
kickstart commands that I have tried without success -
device eth e1000 --opts "Speed=100, Duplex=2"
device eth bcm5700 --opts "speed 100 duplex full autoneg off"
None off the kickstart commands I have used work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.create a bootnet.img to support the e1000 and BCM5700 gig NIC's
2.configure the ks.cfg for a network build.
Actual Results: I can tell via the ctl-alt f3 and f3 that the adapter is auto
negotiating rather than being locked at the requested media type.
Expected Results: hopefully it would have been locked at 100 / full
Reassigning to anaconda, seems more appropriate than kernelcfg (which
was a GUI tool to configure /etc/modules.conf ages ago). :-)
Read ya, Phil
This can be done in newer releases with ethtool opts on the install
command line or in the ks.cfg