mii(4) [netbsd man page]
MII(4) BSD Kernel Interfaces Manual MII(4) NAME
mii -- IEEE 802.3 Media Independent Interface network bus SYNOPSIS
acphy* at mii? phy ? # Altima AC101 10/100 PHY amhphy* at mii? phy ? # AMD 79c901 PHY (10BASE-T part) bmtphy* at mii? phy ? # Broadcom BCM5201/5202 PHYs brgphy* at mii? phy ? # Broadcom BCM5400/5401 Gig-E PHYs ciphy* at mii? phy ? # Cicada CS8201 Gig-E PHYs dmphy* at mii? phy ? # Davicom DM9101 PHYs exphy* at mii? phy ? # 3Com internal PHYs gentbi* at mii? phy ? # Generic ten-bit 1000BASE-X PHYs glxtphy* at mii? phy ? # Level One LXT-1000 Gig-E PHYs gphyter* at mii? phy ? # NatSemi DP83861 Gig-E PHYs icsphy* at mii? phy ? # Integrated Circuit Systems ICS1890 PHYs ikphy* at mii? phy ? # Intel 82563 PHYs inphy* at mii? phy ? # Intel 82555 PHYs iophy* at mii? phy ? # Intel 82553 PHYs lxtphy* at mii? phy ? # Level One LXT-970 PHYs makphy* at mii? phy ? # Marvel 88E1000 Gig-E PHYs nsphy* at mii? phy ? # NatSemi DP83840 PHYs nsphyter* at mii? phy ? # NatSemi DP83843/DP83815 PHYs pnaphy* at mii? phy ? # Generic HomePNA PHYs qsphy* at mii? phy ? # Quality Semiconductor QS6612 PHYs rgephy* at mii? phy ? # Realtek 8169S/8110S internal PHYs rlphy* at mii? phy ? # Realtek 8139/8201L PHYs sqphy* at mii? phy ? # Seeq 80220/80221/80223/80225 PHYs tlphy* at mii? phy ? # ThunderLAN internal PHYs tqphy* at mii? phy ? # TSC Semiconductor 78Q2120 PHYs ukphy* at mii? phy ? # Generic/unknown PHYs urlphy* at mii? phy ? # Realtek RTL8150L internal PHYs options MIIVERBOSE DESCRIPTION
Media Independent Interface is an IEEE standard serial bus for connecting MACs (network controllers) to PHYs (physical media interfaces). The mii layer allows network device drivers to share support code for various PHY models, and allows unused support for PHYs which are not present in a system to be removed from the kernel. Network device drivers which use the mii layer carry the ``mii'' autoconfiguration attribute. This allows kernel configuration files to sim- ply specify PHYs as described above in the synopsis. The following is an example of the messages displayed when a network interface with an attached PHY is detected by the kernel: epic0 at pci0 dev 12 function 0: SMC EPIC/100 Fast Ethernet epic0: interrupting at kn20aa irq 4 epic0: SMC9432TX, Ethernet address 00:e0:29:07:17:c4 qsphy0 at epic0 phy 3: QS6612 10/100 media interface, rev. 1 qsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto All PHY drivers display the media types supported by the PHY when it is detected by the kernel. These media types are valid media keywords for use with the ifconfig(8) program. SEE ALSO
acphy(4), amhphy(4), bmtphy(4), brgphy(4), ciphy(4), dmphy(4), exphy(4), gentbi(4), glxtphy(4), gphyter(4), icsphy(4), ifmedia(4), ikphy(4), inphy(4), iophy(4), lxtphy(4), makphy(4), nsphy(4), nsphyter(4), pnaphy(4), qsphy(4), rgephy(4), rlphy(4), sqphy(4), tlphy(4), tqphy(4), ukphy(4), urlphy(4), ifconfig(8) The OUI assignments list can be found at: http://standards.ieee.org/regauth/oui/index.shtml BSD
October 13, 2006 BSD
Check Out this Related Man Page
MII-TOOL(8) Linux System Administrator's Manual MII-TOOL(8) NAME
mii-tool - view, manipulate media-independent interface status SYNOPSIS
mii-tool [-v, --verbose] [-V, --version] [-R, --reset] [-r, --restart] [-w, --watch] [-l, --log] [-A, --advertise=media,...] [-F, --force=media] [-p, --phy=addr] interface ... NOTE
This program is obsolete. For replacement check ethtool. DESCRIPTION
This utility checks or sets the status of a network interface's Media Independent Interface (MII) unit. Most fast ethernet adapters use an MII to autonegotiate link speed and duplex setting. Most intelligent network devices use an autonegotiation protocol to communicate what media technologies they support, and then select the fastest mutually supported media technology. The -A or --advertise options can be used to tell the MII to only advertise a subset of its capabilities. Some passive devices, such as single-speed hubs, are unable to autonegotiate. To handle such devices, the MII protocol also allows for establishing a link by simply detecting either a 10baseT or 100baseT link beat. The -F or --force options can be used to force the MII to operate in one mode, instead of autonegotiating. The -A and -F options are mutually exclusive. The default short output reports the negotiated link speed and link status for each interface. OPTIONS
-v, --verbose Display more detailed MII status information. If used twice, also display raw MII register contents. Alert: If used three times, will force reading all MII registers, including non standard ones. It's not guaranteed any valid answer from PHY while PHY communication can even hang. With driver e1000e will fail while reading register 0x07. -V, --version Display program version information. -R, --reset Reset the MII to its default configuration. -r, --restart Restart autonegotiation. -w, --watch Watch interface(s) and report changes in link status. The MII interfaces are polled at one second intervals. -l, --log Used with -w, records link status changes in the system log instead of printing on standard output. -F media, --force=media Disable autonegotiation, and force the MII to either 100baseTx-FD, 100baseTx-HD, 10baseT-FD, or 10baseT-HD operation. -A media,..., --advertise=media,... Enable and restart autonegotiation, and advertise only the specified media technologies. Multiple technologies should be separated by commas. Valid media are 100baseT4, 100baseTx-FD, 100baseTx-HD, 10baseT-FD, and 10baseT-HD. -p addr, --phy=addr Override the MII address provided by kernel with value addr. DIAGNOSTICS
SIOCGMIIPHY on 'eth?' failed: Invalid argument If the interface is not running (up), kernel will refuse to report its link state. SIOCGMIIPHY on 'eth?' failed: Operation not permitted Most kernels restrict access to root. SIOCGMIIPHY on 'eth?' failed: No such device This error is shown, if the kernel does not know about the named device. SIOCGMIIPHY on 'eth?' failed: Operation not supported The interface in question does not support MII queries. Most likely, it does not have MII transceivers, at all. SEE ALSO
ethtool(8) AUTHORS
David Hinds - dhinds@pcmcia.sourceforge.org Donald Becker - becker@scyld.com Bernd Eckenfels - net-tools@lina.inka.de SEE ALSO
http://net-tools.sourceforge.net - Homepage of the net-tools project net-tools 2013-02-15 MII-TOOL(8)