On Thu, 7 Feb 2002, Magnus Sjogren wrote: > When compiled into the kernel or used as a module, the driver can't > auto-negotiate or be forced into full duplex. > > Environment is D-Link DES-1005D "mini-switch" 100baseTX. > > If i boot into windows (which detects full duplex) and then back into > linux it will use full duplex. > > The eeprom is programmed to use 100baseTX-FD with the help of 3Com's > setup utility. Hmmm, forcing 100baseTx-FD turns off autonegotation. The Linux driver is doing just what it is configured to do. I'm guessing that your Windows configuration overrides the EEPROM setting and turns on autonegotiation. > 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html > See Documentation/networking/vortex.txt > 00:0b.0: 3Com PCI 3c905C Tornado at 0xe000. Vers LK1.1.16 > 00:02:1e:f2:61:21, IRQ 11 > product code 464a rev 00.13 date 11-13-00 > Full duplex capable > Internal config register is 2400000, transceivers 0xa. > 8K byte-wide RAM 5:3 Rx:Tx split, 100baseTX interface. What there any message about detecting the transceiver? It should be found at MII address #24. ... > mii-diag.c:v2.03 11/5/2001 Donald Becker (becker@scyld.com) > MII PHY #0 transceiver registers: Not #0?? The driver you are using has a problem here. Run vortex-diag -m: > vortex-diag -aaeef: > Saved EEPROM settings of a 3Com Vortex/Boomerang: > 3Com Node Address 1A:51:53:A1:23:6C (used as a unique ID only). > OEM Station address 00:02:1E:F2:61:21 (used as the ethernet address). > Manufacture date (MM/DD/YYYY) 11/13/2000, division H, product FJ. > Options: force full duplex, link beat required. Yup, set to forced full duplex. Don't do that. Donald Becker becker@scyld.com Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993 - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
