At 10:33 PM -0500 2002/12/04, Craig Reyenga wrote:
At the very least, try hard-wiring the configuration at both ends to be 100Mbps full-duplex. There's a chance that 4.7 and 5.0 will handle auto-negotiation differently.Unfortunately, I have no extra hardware available to me, so I can't experiment with switches and whatnot. Also, wouldn't some sort of software experimentation be more appropriate, considering that my existing setup works _perfetcly_ in 4.7?
Other than that, you should try swapping out as much hardware as you can -- the cards, the cables, etc.... If possible, you should also test with other computers (in case the problem is with one specific machine when it is running 5.0).
Just because something appears to work perfectly in another OS is not an indication that there is not anything wrong with that setup. If that was the case, there would never be a need for any replacement for any Microsoft OSes, because many vendors stop trying to debug the problem when they can prove that things work just fine under Windows.
If you really want to try swapping software, you'll have to do a binary search on each potential piece of software involved.I'm not sure what to do; should I be trying various versions of if_rl.c? Or is there something else that I should be trying?
However, since there are many potential software components that could be involved, while testing each component individually between now and then should theoretically be doable in 10 tests (as previously mentioned), the combinatorial explosion will be exceptionally nasty.
--
Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.
GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E W+++(--) N+ !w---
O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message