Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Installation - Getting started with Red Hat Linux
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
X Windows problem (xauth)
Upgrading openoffice 1 1 rpm
FTP: connection refused
FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
broadcom network interface
make mrproper
sendmail configuration on redhat
Couldn 't open PID file /var/run/named/named pid Permission denied
Promise 378 controller
kernel 2 6 and /dev/sound/mixer not found
Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
Lotus Notes under Wine
/etc/security/limits conf question
Intel E/1000 driver
Command stream end of file while reading
rpm database corrupt
qla2300 modules
 
kickstart installation still has problem even in RHELv4U3(i386)

kickstart installation still has problem even in RHELv4U3(i386)

2006-06-17       - By jOe

 Back
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

Hello all,<br><br>Does anyone here install the RHELv4U3(i386) via kickstart+NFS
without problem?<br><br>I've tried dozens of times and i'm sure there still
exists problem in RHELv4U3's kickstart installation.<br>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 !!
<br>But the issue still appear in v4U3 !!&nbsp; Did the Redhat team really
fixed it or not?<br>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.
<br><br>The RedHat's Knowledge Base brief can be found at <a href="http://kbase
.redhat.com/faq/FAQ_42_5549.shtm.and">http://kbase.redhat.com/faq/FAQ_42_5549
.shtm.and</a> I also paste it here.<br>__ ____ ____ ____ ____ ____ ____ ____ ___
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __
__ ____ ____ ____ ___
<br>
Issue:
<div class="Ques">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?
</div>

<div class="resolution">Resolution:</div>
<b>Release Found:</b> Red Hat Enterprise Linux 4
<br><br>
<b>Problem:</b> 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.
<br><br>
One or all of the following symptoms may be observed:
<ul><li>Boot using anaconda with the kickstart file located on either an
HTTP server, NFS server, or FTP server (&quot;ks=http://....&quot;) in text
mode.The</li><li> installer will probe for a DHCP address and fail (if you do
not have a DHCP server on your network, this is expected).</li><li>
Enter the proper static IP information for your network adapter, select OK and
continue.The</li><li> 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 <tt class="COMMAND">alt+F4</tt> keys) says that the
installer cannot set the default route and that the network is unreachable.The<
/li><li> network adapter is properly recognized by the installer and the
proper modules for the adapter have been loaded. This can be observed
by pressing <tt class="COMMAND"> alt+F3 </tt> during the installation.If</li>
<li> you select to obtain the IP address via DHCP, the installation proceeds
without issue.</li></ul>

<b>Solution:</b> 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.<br clear="all">__ ____ ____ ____ ____ ____ ____ ____ ____
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ __
__ ____ ____ ____ ______<br><br><br>Regards,<br>Jun

__ ____ ____ ____ ____ ____ ____ ____ ____ ____
Redhat-install-list mailing list
Redhat-install-list@(protected)
https://www.redhat.com/mailman/listinfo/redhat-install-list
To Unsubscribe Go To ABOVE URL or send a message to:
redhat-install-list-request@(protected)
Subject: unsubscribe