Re: Opteron 252 install

[Jason DePaul <jdepaul@xxxxxxxxxxxxx>]

it turned out that I need to build a new isolinux boot disk.  booting off of the first cdrom for x86_64, apparently does not allow a kickstart over the network.  I built and burned a iso from the contents of /isolinux on disk1 and I was good after that

Thanks
JD
--- Bogdan Costescu <Bogdan.Costescu@xxxxxxxxxxxxxxxxxxxxx> wrote:

From: Bogdan Costescu <Bogdan.Costescu@xxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 19 Apr 2005 19:01:08 +0200 (CEST)
To: Jason DePaul <jdepaul@xxxxxxxxxxxxx>
Cc: amd64-list@xxxxxxxxxx
Subject: Re: Opteron 252 install

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.

--
Bogdan Costescu

IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
E-mail: Bogdan.Costescu@xxxxxxxxxxxxxxxxxxxxx

-- 

amd64-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/amd64-list