Hello,
I install Centos'es from PXE, with vmlinuz and initrd provided by images/pxeboot from the first CD of centos 3.4.
The server is a PowerEdge 1850 with two integrated e1000 nic interfaces.
So kernel is booting, then it comes to the screen which ask for one nic to do a dhcp query. I choose eth0, dhcp server reply well and then i get an ip address, dns'es, etc. And nothing else happen because the nic link is going down at this point !!! (no light, no way. )
I've tried with PXE install of centos 3.3, and all is working fine on this server....
Do you think there is a problem with the centos 3.4 "installation time" kernel ? I remember that centos 3.1 had problems about this nic too ...
Any ideas ?
Thank you !
On Tue, 8 Feb 2005, Martin Hamant wrote:
Hello,
I install Centos'es from PXE, with vmlinuz and initrd provided by images/pxeboot from the first CD of centos 3.4.
The server is a PowerEdge 1850 with two integrated e1000 nic interfaces.
So kernel is booting, then it comes to the screen which ask for one nic to do a dhcp query. I choose eth0, dhcp server reply well and then i get an ip address, dns'es, etc. And nothing else happen because the nic link is going down at this point !!! (no light, no way. )
I've tried with PXE install of centos 3.3, and all is working fine on this server....
Do you think there is a problem with the centos 3.4 "installation time" kernel ? I remember that centos 3.1 had problems about this nic too ...
Any ideas ?
Thank you !
-- Martin _______________________________________________ CentOS mailing list CentOS@caosity.org http://lists.caosity.org/mailman/listinfo/centos
Just installed a couple of Supermicro servers with e1000 nics this weekend using CentOS 3.4.
Have you tried PXE boot with ksdevice=link ?
//Chris
On Tue, 8 Feb 2005 17:35:57 +0100 (CET) Christian Nygaard chris@math.uu.se disait:
On Tue, 8 Feb 2005, Martin Hamant wrote:
Hello,
I install Centos'es from PXE, with vmlinuz and initrd provided by images/pxeboot from the first CD of centos 3.4.
The server is a PowerEdge 1850 with two integrated e1000 nic interfaces.
So kernel is booting, then it comes to the screen which ask for one nic to do a dhcp query. I choose eth0, dhcp server reply well and then i get an ip address, dns'es, etc. And nothing else happen because the nic link is going down at this point !!! (no light, no way. )
I've tried with PXE install of centos 3.3, and all is working fine on this server....
Do you think there is a problem with the centos 3.4 "installation time" kernel ? I remember that centos 3.1 had problems about this nic too ...
Any ideas ?
Thank you !
Just installed a couple of Supermicro servers with e1000 nics this weekend using CentOS 3.4.
I have very bad experiences with supermicro, but it's not "network interface" related :-|
Have you tried PXE boot with ksdevice=link ?
Nope ! i have to try this .... where can i find documentation about that ?
On Tue, 8 Feb 2005 17:56:01 +0100 Martin Hamant mh@accelance.fr disait:
Have you tried PXE boot with ksdevice=link ?
Nope ! i have to try this .... where can i find documentation about that ?
Ok i've tried. There is no difference ... it just detect which interface has the link but the original problem is the same : the driver ...
On Tue, 8 Feb 2005, Martin Hamant wrote:
I install Centos'es from PXE, with vmlinuz and initrd provided by images/pxeboot from the first CD of centos 3.4.
The server is a PowerEdge 1850 with two integrated e1000 nic interfaces.
So kernel is booting, then it comes to the screen which ask for one nic to do a dhcp query. I choose eth0, dhcp server reply well and then i get an ip address, dns'es, etc. And nothing else happen because the nic link is going down at this point !!! (no light, no way. )
There have been changes over time of the MII link management code used by Anaconda. I encounter these issues with 3-com nic's and Intel switches, but have also encountered them with T-Lan nic's as well.
Simplify the network topology - go to a straight crossover to your dhcp/next server if possible - alternatively, consider trying a single switch between the unit under test and the dhcp/next server -- then vary the switch brand, to test each. If possible, run TCPDUMP on the server side, and see whenre the connection is failing.
-- Russ Herrold
On Tue, 8 Feb 2005 13:26:56 -0500 (EST) R P Herrold herrold@owlriver.com disait:
On Tue, 8 Feb 2005, Martin Hamant wrote:
I install Centos'es from PXE, with vmlinuz and initrd provided by images/pxeboot from the first CD of centos 3.4.
The server is a PowerEdge 1850 with two integrated e1000 nic interfaces.
So kernel is booting, then it comes to the screen which ask for one nic to do a dhcp query. I choose eth0, dhcp server reply well and then i get an ip address, dns'es, etc. And nothing else happen because the nic link is going down at this point !!! (no light, no way. )
There have been changes over time of the MII link management code used by Anaconda. I encounter these issues with 3-com nic's and Intel switches, but have also encountered them with T-Lan nic's as well.
Simplify the network topology - go to a straight crossover to your dhcp/next server if possible - alternatively, consider trying a single switch between the unit under test and the dhcp/next server -- then vary the switch brand, to test each. If possible, run TCPDUMP on the server side, and see whenre the connection is failing.
The switch is a 3com. the dhcp server and the PE1850 is connected to this switch. I will try if i have time to test what you mentioned. Thank you very much !
-
Christian Nygaard -
Martin Hamant -
R P Herrold