Bug 149871 (IT_69401)
| Summary: | kickstart fails to assign IP address with AS4 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Simon Hargrave <bugzilla> |
| Component: | anaconda | Assignee: | Chris Lumens <clumens> |
| Status: | CLOSED ERRATA | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | cjones, clumens, kurt, rafiq_maniar, tao |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHBA-2005-220 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-06-09 11:29:36 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Simon Hargrave
2005-02-28 15:17:32 UTC
I have done some further investigation (using my PC, a compaq deskpro to eliminate the server as being the sole problem). It would appear that the issue is setting static IP parameters after a failed DHCP attempt. I have reproduced this as follows: - On my PC, boot the AS4 CD with the network cable DETACHED. Boot parameters as: linux ks=nfs:server:/path DHCP fails, I give the TCP/IP parameters manually, and the error once again is: tg3: eth0: Link is up at 100 Mbps, full duplex. tg3: eth0: Flow control is off for TX and off for RX. loader: failed to set default route: Network is unreachable If I reboot off the CD and specify the TCP/IP parameters manually on the boot line, ie: linux ks=nfs:server:/path ip=xxx.xxx.xxx.xxx netmask=xxx.xxx.xxx.xxx gateway=xxx.xxx.xxx.xxx dns=xxx.xxx.xxx.xxx The install doesn't attempt to perform a DHCP request, and the network is initialised correctly. This has now been reproduced on both a dual-nic server and a single- nic PC, on different LANs (and with ethernet cables disconnected) so the problem is definately somewhere in the installer. One other note, when booting on a LAN with a DHCP server, the DHCP address is accepted and installation works as expected. Could you check the comments in bug 149682 and see if using the driver from Broadcom (bcm5700-7.3.5.tar.gz) fixes these issues? The driver disk DD that comes in that doesn't support the AS4 kernel. I will try and create a driver disk and feed this to the install, however I don't believe the tg3 driver to be the problem. I can reproduce the problem on a PC with an Intel NIC, which doesn't use the tg3 driver. Does it work if you pass the IP information on the boot command line (the syntax is in /usr/share/doc/anaconda*/command-line.txt or it should also be in the kernel parameters appendix of the install guide) Yes it does work passing the IP on the boot command line, as per Comment #1 of this bug report. *** Bug 150844 has been marked as a duplicate of this bug. *** Fixed in CVS *** Bug 157640 has been marked as a duplicate of this bug. *** An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-220.html |