GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  NVE (4)

NAME

nve - NVIDIA nForce MCP Networking Adapter device driver

CONTENTS

Synopsis
Description
Hardware
Diagnostics
See Also
History
Authors
Bugs

SYNOPSIS

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:



.Cd device miibus
.Cd device nve

Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

if_nve_load="YES"

DESCRIPTION

The nve 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 nve 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 nve driver supports the following media options:
full-duplex
  Set full duplex operation.

For more information on configuring this device, see ifconfig(8).

HARDWARE

The nve 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).

SEE ALSO

altq(4), arp(4), miibus(4), netintro(4), nfe(4), ng_ether(4), rgephy(4), ifconfig(8)

HISTORY

The nve driver first appeared in
.Fx 6.0 .

AUTHORS


.An -nosplit The nve driver was written by
.An Quinton Dolan Aq q@onthenet.com.au and
.An David E. O’Brien Aq obrien@FreeBSD.org .

BUGS

There are reports that when the card is in auto select mode, ifconfig output reports a 10baseT/UTP output while the LEDs and bandwidth show that the card is actually in 100baseTX mode.
Search for    or go to Top of page |  Section 4 |  Main Index


Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.