Opteron 252 install

[Lamont R. Peterson]

On Tuesday 19 April 2005 11:01am, Bogdan Costescu wrote:
> On Tue, 19 Apr 2005, Jason DePaul wrote:
> > linux ks=nfs:xxx.xxx.xxx.xxx:/var/ftp/pub/kickstart/ks.cfg ksdevice=eth0
>
> I'm too lazy to search HP's site right now, but if these computers
> have more than one network interface (which would explain the ksdevice
> presence on the command line), try using
>
> ksdevice=link
>
> instead of
>
> ksdevice=eth0
>
> I seem to remember some opposite order of finding network interfaces
> between i386 and x86_64 kernels in my own tests, but as I changed a
> lot of them, I'm not sure anymore - it shouldn't hurt anyway.

FC1/RHEL3 and earlier set up all the devices according to the order listed by 
the PCI order (i.e. PCI bus 0 comes before bus 1).  Since many (all?) 
motherboard manufactures have on-board NICs now on a separate bus (usually 
PCI bus 2) from the physical slots (usually PCI bus 1), the on-board NIC 
would always be detected after add-in cards.  This was "fixed" with FC2 (and 
RHEL4).  Now the on-board hardware will be detected ahead of the add-on cards 
no matter what PCI bus ID they are on.

The problem with ksdevice=link is that in most environments I have been in 
with multiple NICs, they are actually all hooked up and have a link.  
Therefore, ksdevice=eth0 is safer.
-- 
Lamont R. Peterson <lamont at gurulabs.com>
Senior Instructor
Guru Labs, L.C. http://www.GuruLabs.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/amd64-list/attachments/20050419/de648445/attachment.sig>