Dennis <[EMAIL PROTECTED]> : [...] > So if you are using exactly the same equipment, I think that only two points > can cause the problem:
You are optimistic :o) > 2. Cables not fitting the requirements. I am using CAT 5e actually, but it may > be that this is a part of the problem. Can you say something about this > point? I can get a fine 100Mb/s with this equipment + poor cables (a few tens of meters + same path as the power distribution). With this setup, negociation takes ages though. YMMV. [...] > > - If it still sucks, can you try 2.6.13-rc6 ? > Is there any known problem related to the driver with the kernel I am using? > Just to make sure that to drive to the shop and get the devices replaced is > worth it. Apparently you use a kernel: - on a laptop (hello suspend !); - heavily vendor patched; - with vmware module; - with a wireless module (proprietary + same irq as the r8169 -> *yuck*). Add to the mix: - X - some interesting file transfer application -> There are too many unknown. Please remove whatever pcmcia card you can on the laptop and try a 2.6.13-rc6 kernel on both hosts _without the proprietary stuff_ loaded after boot, without X. Do not force the media, even if it takes some time to settle down, issue a simple ssh -c blowfish $BIG_FILE between the two hosts and report the transfer rate (include dmesg on both hosts + vmstat 1 + cat /proc/interrupts). You should be able to directly connect the laptop to the desktop computer with a simple cable: the r8169 is supposed to automagically cross the signal. I have not tried this feature with very long cables but it otherwise works here (50cm cat5 cable allows immediate detection of the link + solid 1000Mb full duplex). -- Ueimor - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
