Red Hat Bugzilla – Bug 104703
Can't lock NIC settings in kickstart
Last modified: 2007-11-30 17:06:58 EST
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 have a couple of issues with the Ent WS 3.0.
1- I am still unable to get the NIC to lock at a desired speed / Duplex in the
kickstart Process. I have tries numerous thing including:
device eth e1000 --opts "Speed=100, Duplex=2"
device eth bcm5700 --opts "speed 100, duplex full"
but have not had any luck.
2- has redhat come up with a utility to build a customized bootnet image
supporting only the desired devices and fits on a single floppy? This has
become an issue as we supply these scripts to our clients, and the headless
servers are built without any operator interface.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Only some drivers support module options for doing this. The recommended way is
using ethtool. If you're getting your kickstart config from a local media
source, add '--ethtool="speed 100 duplex full"' to the network line of your
ks.cfg. If you're getting your kickstart config over the network, you need to
add 'ethtool="speed 100 duplex full"' to your boot command line.
For modules which have options, specify the options separated by spaces (not
commas). Note that this is used too late if you are pulling your ks.cfg over
As far as floppies, there are a few scripts available, but none which we
support. Also, you probably want to start transitioning to using some larger
media form than floppies (such as CDs, for which boot.iso is available) as the
2.6 kernel is very likely to be too large to fit on a floppy disk.
Adding --ethtool to the network line worked. Where is the kickstart
documentation supporting this.