nve (4)
Leading comments
Copyright (c) 2003 Quinton Dolan All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or othe...
NAME
nve - NVIDIA nForce MCP Networking Adapter device driverSYNOPSIS
Warning: This driver is deprecated and will not be available in Fx 11.0 and later. Please consider using the nfe(4) driver instead.To compile this driver into the kernel, place the following lines in your kernel configuration file:
device miibus device nve
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf5:
if_nve_load="YES"
DESCRIPTION
The ifconfig driver provides support for the NVIDIA nForce MCP and nForce2 MCP2 networking adapter that is embedded in the southbridge of most nForce and nForce2 motherboards.This driver is a reimplementation of the NVIDIA supported Linux nvnet driver and uses the same closed source API library to access the underlying hardware. There is currently no programming documentation available for this device, and therefore little is known about the internal architecture of the MAC engine itself.
The ifconfig driver supports the following media types:
- autoselect
- Enable autoselection of the media type and options.
- 10baseT/UTP
- Set 10Mbps operation.
- 100baseTX
- Set 100Mbps (Fast Ethernet) operation.
- 1000baseTX
- Set 1000Mbps (Gigabit Ethernet) operation.
The ifconfig driver supports the following media options:
- full-duplex
- Set full duplex operation.
For more information on configuring this device, see ifconfig(8).
HARDWARE
The ifconfig driver supports the NVIDIA MCP onboard adapters of mainboards with the following chipsets:
- nForce
- nForce2
- nForce3
- nForce4
DIAGNOSTICS
- "nve%d: couldn't map memory"
- A fatal initialization error has occurred.
- "nve%d: couldn't map interrupt"
- A fatal initialization error has occurred.
- "nve%d: failed to allocate memory"
- There are not enough mbufs available for allocation.
- "nve%d: device timeout"
- The device has stopped responding to the network, or there is a problem with the network connection (cable).