vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, I'm a bit stymied by this: When I connect a jumpstart client (v210) from bge3 to the jumpstart server's ce3 port directly, I get link and when the systems are fully operational I get gigabit autonegotiated (so I could create flarchive on a mount over that wire) no problem. This happens with either a crossed cat5e or a straight thru cat5e (crossing in the port). However, when I use the same cable for the openfirmware boot (boot net3 - install) I get link autonegotiation errors. When I disable the 1000fdx/hdx capabilities on the server's ce3 instance, I get autnegotiation. My question is, why would I get autonegotiation and full performance when fully booted, and not at openfirmware? I can only assume it's something that the bge driver does as it's loaded and/or configured, some sort of retry behavior perhaps? Is there a way to fix this, like say a more recent firmware revision for the v210? Any help appreciated, and TIA, - Matt -- "When in doubt, use brute force." - Ken Thompson |