Bug 51293 - DHCPCD fails to get IP address on RTL8139
Summary: DHCPCD fails to get IP address on RTL8139
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: dhcpcd (Show other bugs)
(Show other bugs)
Version: roswell
Hardware: i386 Linux
Target Milestone: ---
Assignee: Elliot Lee
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2001-08-09 04:01 UTC by Matt Luker
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-09 04:01:53 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Matt Luker 2001-08-09 04:01:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010803

Description of problem:
When the network card (RTL8139) is setup to use DHCP, it fails to retrieve
DHCP information with the following error message:
"Determining IP information for eth0... failed; no link present.  Check cable?"

Checked cable just in case I was an idiot--it turned out not to be the case
this time.

Repeated attempts also fail.  Recycling of the DHCPD server changed
nothing.  Recycling network via /etc/rc.d/init.d/network also failed.  Made
sure all firewalling code (chains and tables) were off.  No effect.

Reconfigure the network card to use a static ip address.  The card then
came up and could see the network.

How reproducible:

Steps to Reproduce:
1.setup card (rtl8139, using 8139too) to use DHCP
2.execute 'ifup eth0'
4.setup card (rtl8139, using 8139too) to use static settings
5.execute 'ifup eth0'

Actual Results:  Fails for DHCP, succeeds for static.

Expected Results:  Succeeds for DHCP, succeeds for static.

Additional info:

Worked fine under RH 7.1 (i386).

Comment 1 Bill Nottingham 2001-08-09 06:21:09 UTC
The calls to mii-tool to check for a device link are removed in
initscripts-6.11-1; the device should work fine with dhcp then.

Note You need to log in before you can comment on or make changes to this bug.