<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12"> <TITLE>RE: fc2 - network restart fails - e1000 / Extreme Network Switch</TITLE> </HEAD> <BODY> What type of cable are you using...Cat5, Cat5e or Cat 6? Cat 5e is the minimum recommended for gigabit and Cat 6 is preferred. Standard Cat 5 is iffy at that speed. > -----Original Message----- > From: Joe Robertson [<A HREF="mailto:jrobertson@convera.com">mailto:jrobertson@convera.com</A>] > Sent: Monday, June 21, 2004 3:46 PM > To: fedora-test-list@redhat.com > Subject: fc2 - network restart fails - e1000 / Extreme Network Switch > > > I'm using machines with Intel GB NIC (Supermicro 6013P-T and > Dell 1600sc - both with e1000 drivers). The OS is fc2 release > (I've tried updating the kernel to 2.6.6-1-535 and saw the > same symptoms). > > If I connect to an Extreme Network GB Switch (summit 400-48t) > and issue a "service network restart" command, it works every > other time (and fails every other time) - consistently. > When it fails, I get the following message: "Determining ip > information for eth0... failed: no link present. Check cable?" > > If I do a sequence of "service network stop" and "service network > start", it works every time. > > I have not seen this with a Netgear unmanaged switch (haven't > tried others). > > Any ideas? > > Thanks, > Joe Robertson > > > -- > fedora-test-list mailing list > fedora-test-list@redhat.com > To unsubscribe: > <A HREF="http://www.redhat.com/mailman/listinfo/fedora-test-list" TARGET="_blank">http://www.redhat.com/mailman/listinfo/fedora-test-list</A> > </BODY> </HTML>