On Wednesday, June 30, 2010 10:09 AM, K. Posern wrote: > Hi, > > Thanks for the answer! > > Just to confirm that my problem is clear: > pump and dhcpcd work, but only when I invoke it on the command line. > > I checked what my colleagues with their Ubuntu distros use: > dhclient v3.1 > > I tried dhclient v3.1.2 --> it worked! Below you will see the syslog: > It > is *much* slower though than dhclient or pump when run from > commandline!? > > I just updated to the latest (available) version of dhcpcd (v5.2.5) > (Because the author of dhcpcd answered me: > ) > But it seems to have the SAME problem like the v4 I used before: > Jun 30 12:55:01 [dhcpcd] version 5.2.5 starting > Jun 30 12:55:02 [dhcpcd] eth0: broadcasting for a lease > Jun 30 12:55:12 [acpid] ACPI Battery Event: 50% > - Last output repeated twice - > Jun 30 12:55:32 [dhcpcd] timed out > > > Should I still look into the latest driver from > http://e1000.sourceforge.net driver (and see if this makes any > difference on the 3 dhcp clients at hand)? > > If you want I can help you debug some more! > Or does this mean that it *must* be a dhcpcd/pump client problem at > this point?! > > Thanks! > > Knuth > > P.S. > > Here is the successfull run of dhclient: > > Jun 30 13:00:12 [dhclient] Internet Systems Consortium DHCP Client > V3.1.2p1-Gentoo > Jun 30 13:00:12 [dhclient] Copyright 2004-2009 Internet Systems > Consortium. Jun 30 13:00:12 [dhclient] All rights reserved. > Jun 30 13:00:12 [dhclient] For info, please visit > http://www.isc.org/sw/dhcp/ > Jun 30 13:00:13 [dhclient] Listening on LPF/eth0/00:1c:7e:0e:f6:1e > Jun 30 13:00:13 [dhclient] Sending on LPF/eth0/00:1c:7e:0e:f6:1e > Jun 30 13:00:13 [dhclient] Sending on Socket/fallback > Jun 30 13:00:13 [dhclient] DHCPREQUEST on eth0 to 255.255.255.255 > port 67 Jun 30 13:00:14 [acpid] ACPI Battery Event: 53% > Jun 30 13:00:17 [dhclient] DHCPREQUEST on eth0 to 255.255.255.255 > port 67 Jun 30 13:00:27 [dhclient] DHCPDISCOVER on eth0 to > 255.255.255.255 port 67 interval 5 > Jun 30 13:00:30 [acpid] ACPI Battery Event: 53% > Jun 30 13:00:32 [dhclient] DHCPDISCOVER on eth0 to 255.255.255.255 > port 67 interval 6 > Jun 30 13:00:38 [dhclient] DHCPDISCOVER on eth0 to 255.255.255.255 > port 67 interval 14 > Jun 30 13:00:46 [acpid] ACPI Battery Event: 54% > Jun 30 13:00:52 [dhclient] DHCPDISCOVER on eth0 to 255.255.255.255 > port 67 interval 19 > Jun 30 13:00:52 [dhclient] DHCPOFFER from 192.168.0.1 > Jun 30 13:00:52 [dhclient] DHCPREQUEST on eth0 to 255.255.255.255 > port 67 Jun 30 13:00:52 [dhclient] DHCPACK from 192.168.0.1 > Jun 30 13:00:52 [dhclient] bound to 192.168.0.64 -- renewal in 2866 > seconds.
If you have the time, it would be great if you could try the latest e1000e driver (vers 1.2.8) from e1000.sf.net - I am wondering if the changes to the driver's link reporting code (one change that went into the kernel for 2.6.29 and another that went in for 2.6.33) may have broken interoperability with dhcpcd. The sourceforge driver has yet another change that might fix any such issue. Thanks, Bruce. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
