Re: eepro100 on SuSE Linux
Donald Becker <[email protected]>
| Newsgroups | gmane.linux.drivers.eepro100.devel |
|---|---|
| Message-ID | <Pine.LNX.4.33.0206261428570.1089-100000@presario> |
On Wed, 26 Jun 2002, Olson, John C wrote: > I'm running SuSE 7.3 professional (2.4.16 kernel) on a compaq ML370 with > Compaq nc3131 NIC's. I've compiled and installed eepro100 version 1.23 and > mii-diag version 2.04 (along with pci-scan version 1.08). I am finding that > I am getting a 100mb half-duplex setting on a card that should be 100/full. Why should it be full duplex? Setting to forced-full-duplex should never be used. If autonegotiation is broken with your switch, you should use half duplex. > When I try to force the setting (mii-diag -F 100baseTx-FD eth0), I get the > following return: > Setting the speed to "fixed", Control register 2100. > SIOCSMIIREG on eth0 failed: Operation not permitted You must be 'root' to change the setting. (More precisely, you must have the CAP_NET_ADMIN capability.) > Basic registers of MII PHY #1: 2000 780d 02a8 0150 05e1 0081 0000 > Basic mode control register 0x2000: Auto-negotiation disabled, with > Speed fixed at 100 mbps, half-duplex. Urrgggg. You have set the speed to forced half duplex. > Your link partner is generating 100baseTx link beat (no > autonegotiation). > Have also tried to set this in /etc/modules.conf (options eepro100 debug=1 > options=0x2100 full_duplex=1) with no success. Huh? Using options=0x100 sets the transceiver to forced 100-half. You could use options=0x200, but you should just use mii-diag as root. -- Donald Becker [email protected] Scyld Computing Corporation http://www.scyld.com 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters Annapolis MD 21403 410-990-9993