Hide Forgot
If this is filed under the wrong component, please forward to the correct one. Description of problem: I have a Dell Optiplex 760 with an onboard Intel 82567LM-3 Gigabit Network Controller. When we turn on power over ethernet (PoE) on the switch it fails to aquire an ip address. After the system boots I have to manually log on a console as root and run 'dhclient eth0'. Then it gets an ip straight away. When running 'service network restart' it gives a message saying there is no link and that I should check the cable. The switch is by Cisco and it is set to portfast (see more details below). When turning off PoE it gets an ip correctly. As we want to turn on PoE on all our switches for IP-telephony it would be good if the Linux machines could handle this. Version-Release number of selected component (if applicable): Linux solli.klientdrift.uib.no 2.6.35.13-92.fc14.x86_64 #1 SMP Sat May 21 17:26:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux How reproducible: Every time on this hardware setup, but we have other hardware setups that work fine. Steps to Reproduce: 1. Reeboot 2. Check link on NIC (light is on) 3. Check status on device (no ip) Actual results: No IP Expected results: Assigned IP from DHCP Additional info: This is the info from the Cisco switch on the port: 292-5a-sw1#sh runn int gi 1/6 Building configuration... Current configuration : 722 bytes ! interface GigabitEthernet1/6 description 292-5a-5607 - Solli switchport mode access switchport port-security authentication control-direction in authentication event fail action authorize vlan 602 authentication event server dead action authorize vlan 602 authentication event no-response action authorize vlan 602 authentication event server alive action reinitialize authentication order mab authentication priority mab authentication port-control auto mab dot1x pae authenticator dot1x timeout tx-period 1 dot1x max-req 1 dot1x max-reauth-req 1 storm-control broadcast level 3.00 spanning-tree portfast spanning-tree bpduguard enable spanning-tree guard loop ip dhcp snooping limit rate 100 end 292-5a-sw1# Bjørge
(In reply to comment #0) > I have to manually log on a console as root and run 'dhclient eth0'. > Then it gets an ip straight away. When > running 'service network restart' it gives a message saying there is no link > and that I should check the cable. That message comes from /etc/sysconfig/network-scripts/ifup-eth if [[ "${PERSISTENT_DHCLIENT}" != [yY1]* ]] && check_link_down ${DEVICE}; then echo $" failed; no link present. Check cable?" exit 1 fi The check_link_down() function from /etc/sysconfig/network-scripts/network-functions probably thinks the interface is down. Reassigning to initscripts for now but the problem could be in kernel or anywhere else. The work-around for you is to set PERSISTENT_DHCLIENT=yes in /etc/sysconfig/network-scripts/ifcfg-eth0
Moving to kernel - if the link is on on the device, but the kernel thinks there isn't a link, that would be a driver bug.
I can confirm that the workaround works, is there a way to set this in a kickstart script?
From what I know about kickstart it should be possible to do that in post-install script. Adding something like the following to the ks script should do the trick: %post echo "PERSISTENT_DHCLIENT=yes" >> /etc/sysconfig/network-scripts/ifcfg-eth0
I have additional info: Using NetworkManager instead of the legacy network service also works (without the networking-scripts workaround). chkconfig network off chkconfig NetworkManager on It was about time we switched anyway, but maybe there is a fix for the problem in any case? Regards Bjørge Solli
given that the interface does eventually come up, I'm not sure this is actually a kernel bug. That it happens slower than normal may be indicative of some hardware incompatibility, or maybe there needs to be some additional switch configuration (I'm no expert on cisco equipment, so I can't offer advice there). It would be interesting to know if this is still a problem on f15, or f16-beta. If it does work without the workaround in those newer releases, given the huge amount of change in networking since 2.6.35, it's unlikely we would backport the e1000 changes to f14 at this stage in its lifecycle.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping