Barth Weishoff writes: > Well how does one make a strong request? =) We've had this issue > appear once, we're using Supermicro's H8DCE mainboard which makes > use of the affected nVidia chipset.
Besides contacting the author of the code in question, the next stronger thing you can do is ask your vendor for support. > I've been trying to reproduce the error, but have yet to do so. > I've been using an HP Procurve 2626 switch in my attempts to > reproduce the problem -- the only thing I've found so far is if the > switch port is hard-coded, the nge interface seems to default to > half duplex -- regardless of the duplex setting -- eg switch=100FDx > the card will detect 100HDx.... That's correct behavior. When you force duplex, the system is prohibited from negotiating it. The default when not negotiated (per the standard) is half-duplex. Thus, if you force one side to full duplex, the other must drop to half duplex, unless it's forced as well. The answer is, "don't do that." -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
