My guess is that some of the ports on the switch are configured as being forced to specific speed/duplex. By specification both sides of the connection need to be set the same. So either both need to be forced or both set to auto-neg. There could also be peoblems with cables or connectors. These kinds of problems are never the driver but somehow related to the environment. I also assume you mean switch when you say "hub". There are no gigabit hubs.
If you leave the NICs in auto-neg mode and plug 2 NICs back-to-back do they link correctly? Cheers, John ----------------------------------------------------------- "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety.", Benjamin Franklin 1755 >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf >Of Charley Chu >Sent: Tuesday, August 19, 2008 6:10 PM >To: e1000-devel@lists.sourceforge.net >Subject: [E1000-devel] auto-negotiation issue > >Hi there, > >We have board with Intel 82571EB Ethernet controller, running >RHELE4-U4. >Sometime, the Ethernet port can only setup 100Mb-T full duplex >connection with Gigabit hub (saw this problem on different >Gigabit hub). >The connection can be re-connected as 1000Mb-FD by forcing >re-negotiation with "ethtool". > >Here is the registers dump at 100Mb-T: > >- MAC registers: >Device Control Register - CTRL(00000h) = 081c0241h >Device Status Register - STATUS(00008h = 00080347h > >- PHY registers: >Auto-Negotiation Advertisement Register - (04d) = 0x0de1 >Auto-Negotiation Base Page Ability Register - (05d) = 0xc1e1 >Auto-Negotiation Expansion Register - (06d) = 0x000f >Auto-Negotiation Next Page Transmit Register - (07d) = 0x2801 >Auto-Negotiation Next Page Ability Register - (08d) = 0x4a47 >1000BASE-T/100BASE-T2 Control Register - (09d) = 0x0200 >1000BASE-T/100BASE-T2 Status Register - (10d) = 0x0800 > >>From bit PHY9.9 and bit PHY10.11 (=1), we see both sides are 1000BAST- >full duplex capable. But the receiver status for both sides somehow are >wrong (bit PHY10.12 and bit PHY10.13 = 0). We're wondering what could >cause this problem. > >Any help is appreciated, > >Thanks, > >Charley > >--------------------------------------------------------------- >---------- >This SF.Net email is sponsored by the Moblin Your Move >Developer's challenge >Build the coolest Linux based applications with Moblin SDK & >win great prizes >Grand prize is a trip for two to an Open Source event anywhere >in the world >http://moblin-contest.org/redirect.php?banner_id=100&url=/ >_______________________________________________ >E1000-devel mailing list >E1000-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/e1000-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
