kickstart waits when machines have two network cards

[ha haha]

Joe, Sharon and Tim Moloney,

 Thanks a lot!!!

 Now the problem goes a step further. It's related to
modules load sequence for network cards.

 I have a machine with two networks cards, originaly
the built-in Broadcom network card is detected as
eth0, and external Intel gigabit as eth1, by former
FC2. 

 And the installs only happens on eth0, the built-in
Broadcom NIC.

 Now the FC4 detects network cards in reverse order,
so former eth0(built-in Broadcom) is detected as eth1,
while the former eth1 is assigned as eth0.

 Is there configuration file I can change
(/etc/modprobe.conf doesn't help) to alter the network
card modules' load sequence, both during kickstart and
post-install?

 Thanks.......



 The 



--- Sharon and Tim Moloney <st.moloney at gte.net> wrote:

> "ha haha" <hahaha_30k at yahoo.com> wrote:
> 
> > I try to begin unattended kickstart installation
> for
> > FC4 onto my machine but it fails, because
> > unfortunately the machine has e two network cards
> and
> > so the kickstart hangs for manual input, to select
> > which network card to continue.
> >
> > Is there a way to specify a network card
> explicitly
> > to grasp ks.cfg for NFS installation?
> 
> On the boot command line, you can add
> "ksdevice=eth0" to specify the first 
> NIC or "ksdevice=link" to specify the one that has
> an active link status 
> (assuming only one has an active link status).
> 
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
>
https://www.redhat.com/mailman/listinfo/kickstart-list
> 



		
____________________________________________________ 
Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
http://football.fantasysports.yahoo.com