RE: No network drivers for doing kickstart

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I am able to use RHEL v4 Update 1 with no problems now.  It has the
appropriate network drivers. But I am now having an issue where
kickstart fails finding the network interface.  I have had this problem
in the past where I was assuming that it was eth0 interface when
Anaconda seen the interface as eth3.  But I am unable to get around it
this time on my DL585 servers.  These servers have two NICS, eth0 and
eth1.  I have tried both with no success.  I have booted from CD #1 and
went into linux rescue.  DHCP will assign IP addresses to eth0 and eth1
but kickstart will still fail. Any suggestions?

Liz Brosch
TSH System Services
Philadelphia, PA  19104
office:  (215) 386-0100 x1144
cell:     (267) 784-9166

-----Original Message-----
From: kickstart-list-bounces@xxxxxxxxxx
[mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Shabazian, Chip
Sent: Tuesday, March 21, 2006 1:27 PM
To: Discussion list about Kickstart
Subject: RE: No network drivers for doing kickstart

I have had issues in the past where a newer initrd worked, but for many
reasons, we had to stay with the build based off an older version.  In
these cases, I found that you could replace the loader in the older
initrd with the loader from the newer one, and all was fine.

If you still want to build with the latest to minimize packages that
need to be upgraded, you could give this a shot.

Chip 


[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux