On Wed, 16 Nov 2005, Craig Nottingham wrote:
Any advise on how to handle the weird probe order voodoo in the
following setup...
I am having issues with servers that come wit 2 onboard e1000 ports and
and additional e1000 pci expansion card. At boot the first onboard
e1000 is eth0, after grabbing my kernel and initrd the pci expansion
card is now eth0.
Should be possible to hack the initrd to force the loading of the modules
in initrd in the order you need them. Else, by specifying HWADDR
in the /etc/sysconfig/network-scripts and tying eth0, eth1, eth2
to specific MAC addresses, you can force it that way too.
Steve
-----Original Message-----
From: kickstart-list-bounces@xxxxxxxxxx
[mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Ronald Reed
Sent: Tuesday, September 13, 2005 10:01 AM
To: Discussion list about Kickstart
Subject: Re: Ethernet probe order
I may have forgot to mention that if you are using the device parameter
in the kickstart file, then you should probably use the "noprobe" option
on the boot line.
Ron
On Mon, 2005-09-12 at 13:08, Phil Oester wrote:
On Sat, Sep 10, 2005 at 07:11:57PM -0700, Greg Morgan wrote:
So do you want, say,
device eth e1000:tg3:e100
so that the devices are probed in this order?
Thanks, that worked when combined with the 'nonet' boot argument
(apparently
auto-probing devices is done prior to those manually specified).
Still doesn't explain the logic, but gets the job done...
Phil
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
--
------------------------------------------------------------------
Steven C. Timm, Ph.D (630) 840-8525 timm@xxxxxxxx http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team
