I've done thousands of kicks before. I normally only get this problem if I have a system with multiple dissimilar NICs (eth0 during PXE may swap to become eth1 and vice versa). In this case, this hardware has the exact same e1000 NICs. This hardware kicks fine with CentOS 4.1 (32-bit) and Fedora Core 5. It just won't kick with CentOS 4.3 x64. However, another server (different hardware) kicks fine using this exact same CentOS 4.3 x64 kick. dhcpd logs multiple discover requests follow by multiple offers. The client just won't accept the offer: May 24 16:01:36 fong-31-100 dhcpd: DHCPDISCOVER from 00:07:e9:32:b8:46 via eth1 May 24 16:01:37 fong-31-100 dhcpd: DHCPOFFER on 192.168.1.254 to 00:07:e9:32:b8:46 via eth1 May 24 16:01:38 fong-31-100 dhcpd: DHCPREQUEST for 192.168.1.254 (192.168.1.1) from 00:07:e9:32:b8:46 via eth1 May 24 16:01:38 fong-31-100 dhcpd: DHCPACK on 192.168.1.254 to 00:07:e9:32:b8:46 via eth1 May 24 23:01:38 fong-31-100 in.tftpd[29880]: tftp: client does not accept options May 24 16:02:16 fong-31-100 dhcpd: DHCPDISCOVER from 00:07:e9:32:b8:46 via eth1 May 24 16:02:16 fong-31-100 dhcpd: DHCPOFFER on 192.168.1.254 to 00:07:e9:32:b8:46 via eth1 May 24 16:02:19 fong-31-100 dhcpd: DHCPDISCOVER from 00:07:e9:32:b8:46 via eth1 May 24 16:02:19 fong-31-100 dhcpd: DHCPOFFER on 192.168.1.254 to 00:07:e9:32:b8:46 via eth1 May 24 16:02:25 fong-31-100 dhcpd: DHCPDISCOVER from 00:07:e9:32:b8:46 via eth1 May 24 16:02:25 fong-31-100 dhcpd: DHCPOFFER on 192.168.1.254 to 00:07:e9:32:b8:46 via eth1 May 24 16:02:36 fong-31-100 dhcpd: DHCPDISCOVER from 00:07:e9:32:b8:46 via eth1 May 24 16:02:36 fong-31-100 dhcpd: DHCPOFFER on 192.168.1.254 to 00:07:e9:32:b8:46 via eth1 May 24 16:02:46 fong-31-100 dhcpd: DHCPDISCOVER from 00:07:e9:32:b8:46 via eth1 May 24 16:02:46 fong-31-100 dhcpd: DHCPOFFER on 192.168.1.254 to 00:07:e9:32:b8:46 via eth1 May 24 16:02:46 fong-31-100 dhcpd: DHCPDISCOVER from 00:07:e9:32:b8:46 via eth1 May 24 16:02:46 fong-31-100 dhcpd: DHCPOFFER on 192.168.1.254 to 00:07:e9:32:b8:46 via eth1 The kickstart server (dhcp, tftp, etc.) and the machine being kicked (dhcp client) are directly connected via a crossover cable. On 5/24/06, Karanbir Singh <mail-lists@xxxxxxxxx> wrote:
Fong Vang wrote: > > Any idea what else to check for? Could it be that the e1000 driver in > CentOS 4.3 x64 is older than the CentOS 4.1 driver? dont know about the rest of your issues, but the e1000 driver has definitely been updated since 4.1 days... - KB -- Karanbir Singh : http://www.karan.org/ : 2522219@icq _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
