I'm new at troubleshooting Ubuntu, so bare with me. In Windows I'm getting speeds of 6699 kbps down/8830 up. In Ubuntu however, I get a mere 974/857. Something isn't set up right. I was able to change the duplex prior, but not anymore for some reason. Now I am running a fresh install of Edgy (6.10), sans current updates on my desktop with my ethernet coming straight from the wall (University) to my onboard ethernet. I'm not exactly sure what the specs on my onboard card are other than it's a Nvidia Ethernet Controller, using forcedeth. In Windows I got similar (slow) speeds until I set it to full duplex, that's done with ethtool, correct? Here is the original output.


If I try to set it to full, it still reports half. I have also tried changing it with autonegotiation off as well as on. When autonegotiation is on, setting it to full duplex disconnects and reconnects, but it still remains half. When it's off, changing duplex to full just disconnects and doesn't reconnect unless I change it back to on, duplex still reports half. I was unable to use Ndiswrapper, and disabling IPV6 did nothing to help. I couldn't change anything running off the Dapper (6.06) or Edgy Live CD either, even though I changed it in Edgy once before. Also, NetworkManager reports that no network devices have been found, yet I'm connected. The Fiesty Fawn (7.04) Alpha Live CD lets me change it to full with autonegotiation off, but the install freezes at 94% installing grub. Is there any way to get this working with Edgy? I don't trust Feisty for everyday use yet.

There's something I vaguely remember about the forcedeth driver, that its not *totally* supported/stable, and often when it says "static", it means "autonegotiate".

Now there are known problems with autonegotiation; different manufacturers do it differently, and despite it being useful, its not a real standard, which is why you should *always* set server NICs to "static".

My guess here is that you have a NIC which says it's running static, but is lying and is really running autonegotiate. Then the autonegotiate is failing, and the two ends are defaulting to the only thing they can agree on, 10/half.

You might want to check your cable, too. Make sure its a completely vanilla, straight-through, good-quality cable. I *know* it works with Windoze, but check it anyway...(pins 1-1, 2-2, 3-3, and 6-6 minimum)

Is there an Nvidia proprietary driver you can use? I know it goes against the grain, but it may be the only solution...

The reason that Windows works faster is that when it says 100/full, it means it, there is no "hidden" autonegotiate that you can't control

HTH
Jimbo

I don't think so. Well, they package their stuff with forcedeth now even. They abandoned nvnet it looks like after November 23, 2005. I guess I could try the older driver and see what happens.