kickstart installation still has problem even in RHELv4U3(i386)
jOe
smartjoe at gmail.com
Sat Jun 17 19:45:17 UTC 2006
Hello all,
Does anyone here install the RHELv4U3(i386) via kickstart+NFS without
problem?
I've tried dozens of times and i'm sure there still exists problem in
RHELv4U3's kickstart installation.
After searched the redhat's knowledge base, i found the Exactly problem
information. But things strange that according that knowledge base brief,
the problem should be fixed in RHELv4U1 and later !!
But the issue still appear in v4U3 !! Did the Redhat team really fixed it
or not?
I've double checked my nfs server configuration, my network setting and
connection status and parameters that passed to the installation routine to
ensure there are no problem exists.
The RedHat's Knowledge Base brief can be found at
http://kbase.redhat.com/faq/FAQ_42_5549.shtm.and I also paste it here.
______________________________________________________________________________________________________________________________________________
Issue: Why does a kickstart installation of Red Hat Enterprise Linux 4 work
when using a DHCP IP address, but not when providing a static IP address for
the network adapter?
Resolution:
*Release Found:* Red Hat Enterprise Linux 4
*Problem:* Anaconda fails to properly set up networking in Red Hat
Enterprise Linux 4 during a kickstart installation if a static IP address is
supplied for the network adapter on the system to be installed.
One or all of the following symptoms may be observed:
- Boot using anaconda with the kickstart file located on either an
HTTP server, NFS server, or FTP server ("ks=http://....") in text
mode.The
- installer will probe for a DHCP address and fail (if you do not have
a DHCP server on your network, this is expected).
- Enter the proper static IP information for your network adapter,
select OK and continue.The
- installer will fail determining the local hostname via a reverse DNS
lookup. The report from virtual terminal 4 (which can be reached by pressing
the alt+F4 keys) says that the installer cannot set the default route
and that the network is unreachable.The
- network adapter is properly recognized by the installer and the
proper modules for the adapter have been loaded. This can be observed by
pressing alt+F3 during the installation.If
- you select to obtain the IP address via DHCP, the installation
proceeds without issue.
*Solution:* This is a known issue with anaconda in Red Hat Enterprise Linux
4. The fix for this problem will be included in Update 1 of Red Hat
Enterprise Linux 4. Currently, the only workaround available is to use a
DHCP server to obtain IP address settings for your network adapter.
__________________________________________________________________________________________________________________________________________________
Regards,
Jun
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/redhat-install-list/attachments/20060618/b8a7359f/attachment.htm>
More information about the Redhat-install-list
mailing list