Nvidia Nforce Networking Controller For Mac

Posted : admin On 1/30/2022

NForce 6 Series: nForce 680i SLI, nForce 680i LT SLI, nForce 680a SLI. NForce 5 Series: nForce 590 SLI AMD, nForce 570 SLI AMD, nForce 570 Ultra AMD, nForce 550. Aug 28, 2018 Step 2: Expand Network adapters section in Device Manager, right click on NVIDIA nForce Networking Controller and select Uninstall Device option. Step 3: Download NVIDIA nForce Networking Controller driver from NVIDIA website and install it. Solution 2: Change MAC Address of the NVIDIA nForce Controller via Device Manager.

  1. Module Parameters

The nForce chipset contains a number of hardware devices that can berun under Linux. Along with a display processor, the chipset includes anetwork device (MAC), audio hardware, an IDE controller, and an OHCI USBcontroller. Many of the components of the nForce chipset use industrystandard interfaces; thus, not all components require custom drivers tobe used on Linux.

Bug reports and installation questions may be directed to:

Please be sure read the TroubleShooting section first, and to reportall relevant details, such as Linux Disribution, Kernel version, binaryor source RPM, the fact that you checked the SBIOS configuration, thecontents of /etc/modules.conf, and a listing of any error messges youfind (you can run dmesg, or look at /var/log/messages as root). If youare having operational problems, please be as specific as possible, sowe can try to reproduce the problem, and determine if we have a fix forit.

This package can be found at the NVIDIA web site:

We strongly urge you to only use software obtained from this websiteor a trusted Linux distribution for your nForce hardware.

At the current time, the nForce drivers require a 2.4 series kernel.

The network driver provided by NVIDIA is subject to the NVIDIAsoftware license; the license is available on the NVIDIA website, and isincluded in this package. By using this software, you are agreeing tothe terms of the license. The rest of the software is provided underthe GNU public license, which is also included in this package.

The packages contain the following items:

  1. This Installation Guide
  2. The GNU license
  3. The NVIDIA license for the network driver software
  4. Makefiles with all, install, and uninstall targets
  5. Source for the nForce audio driver
  6. Source and binary files for building a network driver for NVIDIAhardware
  7. A kernel patch for GART support on nForce chipsets

This package will build a network driver and an audio driver, thenplace them in the appropriate locations for loadable kernelmodules. The network driver is from NVIDIA, the audio driver isbased on the open source i810 audio driver but has been modified towork with NVIDIA hardware. A kernel patch to enable GART supporton nForce chipsets is also supplied, this patch must be merged into thekernel to be used.

The binary packages will also update the modules configuration file,commenting out existing network, audio and usb entries, and add entriesfor the new drivers. A backup file is created before any changes aremade to the configuration file. If the binary package is uninstalled,the package attempts to restore the original version of the file fromthis backup.

Nvidia

The tar files don't try to modify the module configuration files.You should make sure the following lines are in the configuration file(it will be named /etc/modules.conf on most current distributions):

  • alias eth0 nvnet
  • alias sound-slot-0 nvaudio
  • alias usb-interface usb-ohci

Neither the binary nor the source packages will load the kerneldrivers during the installation. You can do this manually using insmodor modprobe. (USAGE: 'insmod modulename' or 'modprobemodulename') Upon reboot, the kernel modules should insert themselvesautomatically.

Nvidia has provided precompiled binary RPMs for several versions ofRedHat and Mandrake. You should select the RPM appropriate to yourcurrent kernel version. You can check what kernel your machine isrunning by checking the output of 'uname -r'.

If you are using a different version of Red Hat or Mandrake, amodified kernel, or a different rpm-based distribution, you should usethe SRPM to build an RPM appropriate for your system. If you are usingthe SuSE RPM, see NOTE: SuSE INSTALLATIONS, below.

If you are using a non-RPM based system, or if you prefer not to useRPM, you should download and install from the source tarballs.

To install a binary rpms, you only need use rpm to install thepackage. This should install and configure the drivers. A source rpmrequires building and installing the drivers yourself. The files inthis package are organized into a build hierarchy to make this taskeasier.

You might want to check the BIOS configuration on your system toensure that the audio and networking devices will be detected. See theSystem BIOS Configuration description in the Troubleshooting section.

NOTE: SuSE INSTALLATIONS

Upgrading the SuSE Kernel:

If you are using the SuSE Linux distribution, note that the binaryRPM for SuSE only supports SuSE versions using the upgraded kernel. Thisnote contains directions from SuSE on upgrading to the new kernel forSuSE versions 7.1, 7.2 and 7.3:

Get the upgraded kernel from one of the following sites (dependingon SuSE distribution):

For update instructions, see SuSE's SBD article, located at

Alternative SuSEInstallations:

The following instructions should be used before proceeding with asource RPM or tar file installation. You will need to use one of theseinstallation methods if you want to install nForce drivers withoutupgrading your kernel. Please note that these installation methodswon't work for SuSE 7.1 or 7.2.

Install with YaST(2) the following d (development) series packages

  • make
  • gcc
  • binutils
  • glibc-devel
  • kernel-source

Use the following commands to set up your development environment

You can now proceed with the tar file or source RPM installationsteps below, omitting the steps to become root.

Binary RPM Installation

The binary installation procedure involves downloading the binaryRPM file appropriate to your distribution and installing it. If you areusing the SuSE distribution, see NOTE: SuSE INSTALLATIONS, above.

Become root and install using rpm:

Source RPM Installation

The Source RPM will create an RPM appropriate for your system. Ifyou are using the SuSE RPM, see NOTE: SuSE INSTALLATIONS, above. Toinstall:

At this point, the SRPM will be recompiled. When this command hascompleted, look for a line that says:

This will provide you with the name and location of the new RPM. Youshould then install this RPM per the instructions in the Binary RPMInstallation section.

Tar File Installation

The tar file package contains source code, libraries, makefiles anddocumentation organized into a single tar file.

To install the tar file, unpack it, build the sources and installthem. If you are using the SuSE RPM, see NOTE: SuSE INSTALLATIONS,above:

GART Patch Installation

NOTE: This patch only supportskernel 2.4.20. You will need to either install kernel 2.4.20 andsources before patching, or manually merge these changes to other kernelversions.

Patching the Kernel

  1. Change to the Linux kernel source directory.
  2. Patch the kernel. Watch out for any warnings or errors.

Configuring the Kernel

  • In order to use NVIDIA AGP chipset support, the kernel must beconfigured accordingly.
  • In the kernel source directory, run a kernel configuration toolsuch as menuconfig:
  • In the 'Processor type and features', make sure that an x86compatible CPU is selected.
  • In the 'Character devices' section, select '/dev/agpgart (AGPSupport)' as an included or modularized kernel feature.
  • In the same section, enable 'NVIDIA chipset support'.

Rebuilding and Reinstalling the Kernel

MacRebuild and reinstall the kernel and the kernel modules following theappropriate procedure for your GNU/Linux distribution.

To remove the contents of one of the binary rpm files, use rpm toremove it:

To remove the contents of one of the source rpm or tar file, go tothe build directory, and run 'make uninstall':

nvnet Module Parameters

The nForce network driver supports the following optional parameters:
  1. optimization
  2. speed
  3. duplex

Optimization

The nForce network driver supports two optimization modes:
  1. CPU optimization
  2. Throughput optimization
CPU optimization mode ruduces the CPU utilization by using interruptmoderation.
Throughput optimization mode maximizes the throughput. This modehas higher CPU consumption.
By default, the driver runs in throughput optimization mode. Theoptimization mode can be specified by supplying the module parameter'optimization'

Speed

The 'speed' module parameter can be used set the interface speed of theethernet controller. By default the controller will autosense theinterface speed, but also supports the following values:
  • speed=0 ; auto
  • speed=1 ; 10Mbps
  • speed=2 ; 100Mpbs

Duplex

The 'duplex' module parameter can be used to specify the interfaceduplex. By default the controller will autoselect duplex, but alsosupports the following values:
  • duplex=0 ; auto
  • duplex=1 ; half duplex
  • duplex=2 ; full duplex

nvaudio Module Parameters

The nForce audio driver supports the following optional parameters:
  1. spdif_status

spdif_status

The 'spdif_status' module parameter is used to enable or disable S/PDIFsupport in the driver. By default S/PDIF is enabled, but can bedisabled by setting spdif_status to 0. The driver can onlysupport 48kHz sample rate when S/PDIF is enabled, so disabling it willincrease compatability with applications that make assumptions aboutwhat sample rates the driver supports.

Configuration

Module parameters can be specified either on the command line whenloading the module, or in the module configuration file(/etc/modules.conf). For example to have the nForce ethernetdriver use throughput optimized mode, add the following to the moduleconfiguration file:

options nvnet optimization=1
Or if loading the module manually from the command line:
modprobe nvnet optmization=1
The module parameters for the ethernet driver can be verified using thecommand 'modinfo -p nvnet'

System BIOS Configuration

Since the audio and network drivers work on the nForce chipset,these devices along with other motherboard devices are controlled by theSystem BIOS. If the installed drivers don't recognize hardware on yoursystem, the problem may be your System BIOS's plug and playconfiguration. If your system BIOS expects the operating system toconfigure hardware devices, and your Linux kernel doesn't supportACPI-style configuration, you'll need to change your BIOS settings.

To view or change an Award-style system BIOS, reboot the machine,and press the Delete key. When you get a configuration screen, select'PnP/PCI Configurations' in that screen if 'PNP OS Installed []' Has'Yes' choosen, change the selection to 'No'.

If your BIOS is Phoenix-style, use the F2 key instead of Delete, andscroll through the menus to find OS Type, and chose 'Other'. The exactdetails of System BIOS configuration vary with BIOS vendor, so thescreens may not be exactly the same.

Warning: You should write down the original configuration of theBIOS before changing it. Changing your system BIOS configuration mayadversely affect the operation of the system, and even make itunbootable.

  • Q: Is NVIDIA going to supply a Linux AGPGART driver for nForceproducts so that I can use my non-NVIDIA card in 3d accelerated modeunder Linux?

    A: The current release of the Linux nForce package contains akernel source code patch that will enable GART support using thestandard Linux GART driver. NVIDIA is working with the maintainersof this driver to make it available in future versions of the Linuxkernel.

  • Q: My IDE hard drive is running very slowly, how can I enableDMA mode?

    A: A kernel patch was added in kernel 2.4.21pre3-ac1 whichenables DMA for the nForce2 IDE controller and should be available inthe final released 2.4.21 kernel. An alternative to upgrading yourkernel is to use the 'hdparm' utility to enable DMA for your harddrive. For example:

    Where /dev/hdX is the IDE device you wish to enable DMA for. Youmust do this every time you reboot, or add it to an rc script. Somedistributions have a file '/etc/sysconfig/harddisks' where you canenable this for all hard drives on system boot.

  • Q: Does NVIDIA supply a Linux driver for the USB and USB2.0devices?

    A: The USB and USB2.0 devices use the industry standard OHCI andEHCI interfaces, and will work with the standard Linux USB drivers.

  • Q: I've rebuilt the Nforce driver, but when I try to insert it, I get a message telling me I have unresolved symbols.

    A. Unresolved symbols are most often caused by a mismatchbetween your kernel sources and your running kernel. They must match forthe nForce driver modules to build correctly. Please make sure yourkernel sources are installed and configured to match your runningkernel.

  • Q: How do I tell if I have my kernel sources installed?

    A: If you're running on a distro that uses RPM (Red Hat,Mandrake, SuSE, etc), then you can use RPM to tell you. At a shellprompt, type:

    and look at the output. You should see a package thatcorresponds to your kernel (often named something like kernel-2.4.18-3)and a kernel source package with the same version (often namedsomething like kernel-source-2.4.18-3). If none of the lines seemto correspond to a source package, then you'll probably need toinstall it. If the versions listed mismatch (ex: kernel-2.4.18-10 vs.kernel-source-2.4.18-3), then you'll need to update the kernel-sourcepackage to match the installed kernel. If you have multiple kernelsinstalled, you need to install the kernel-source package thatcorresponds to your running kernel (or make sure your installedsource package matches the running kernel). You can do this bylooking at the output of 'uname -r' and matching versions.

  • Q: 'rpm -rebuild' gives an error 'unknown option'.

    A: Recent versions of rpm no longer support the '-rebuild'option; if you have such a version of rpm, you should instead use thecommand 'rpmbuild -rebuild'. The 'rpmbuild' executable is provided bythe rpm-build package.

  • Q: When I try to build, I get a message telling me that Ishould never try to use system headers. What's wrong?

    A: You need to install the sources for your kernel. Pleasedownload and install the appropriate kernel-source package for yourkernel.

  • Q: I'm seeing hangs playing games such as Quake III and UnrealTournament 2003.
    A: These games makeassumptions about the audio sample rates the driver supports. When S/PDIF is enabled the driver only supports 48kHZ audio. You must disable S/PDIF support for these games to work. See the section on moduleparameters for the audio driver for instructions on disabling S/PDIFsupport.
  • Q: Does NVIDIA have a Linux driver for 1394 on nForce2?

    A: NVIDIA has been working with the Linux 1394 group to addsupport for nForce2. Support was added into the 2.5 series kernelin 2.5.68 and a patch for 2.4 is in progress (2.4.21-rc1). Testpatches are available from linux1394.org


Most recent changes at top of list. Each bullet indicates a publicrelease on NVIDIA web site.

  • Added kernel patch to support nForce GART
    Added 'spdif_status' module parameter to audio driver to enable/disableS/PDIF support for compatability
    Fixed bug in audio driver that was causing MSI nForce board to only use2 channels
    Fixed mmap bug in audio driver causing Quake III to hang.
    Fixed RedHat 9 build issue with remap_page_range().
    Fixed problem with rebuilding SRPM on RedHat 9.
    Added RedHat 9 and Mandrake 9.1 binary RPMs.
  • Fixed problem with compiler arguments between gcc3.X and gcc2.X

    Changed installation script to use lowest available number whenenumerating network and audio devices in modles.conf

    Changed audio driver to be self contained source file based offi810_audio driver.
    Added SPDIF support to audio driver

    Updated binary packages for latest releases of RedHat kernels.

    Added FAQ section to release notes.

  • Added PCI ID support for MCP2 and MCP2 to the i810_audio driver.

    Some cleanup of spec file and Makefiles

    SRPMs and tar files now use local system's i810_audio.c file,and complain if it's not there; this makes them more distro independent.

  • Changed code to compile properly with gcc3.X and gcc2.X

    Added support for Mandrake9.0 and Redhat8.0

    nForce2 support for network driver.


  1. Loading The Drivers
  2. Audio Control Panel
  3. Acknowledgments

The nForce chipset contains a number of hardware devices that can berun under Linux; a network device (MAC), audio hardware, storagecontrollers (IDE and SATA), and OHCI/EHCI USB controllers. Many of thecomponents of the nForce chipset use industry standard interfaces; thus,not all components require custom drivers to be used on Linux.

Bug reports and installation questions may be directed to:

Before submitting a bug report, please read the Troubleshooting and FAQsections first, and review the Known Problems list for the driverversion you are using. This can be found at NVIDIA's web site, on therelease page for the driver version.

If you decide to submit a bug report, make sure to includenforce-bug-report.log in the bug report by running nforce-bug-report.sh.

This package can be found at the NVIDIA web site:

We strongly urge you to only use software obtained from this websiteor a trusted Linux distribution for your nForce hardware.

At the current time, the nForce drivers require a 2.4 or 2.6 serieskernel running on 32- or 64-bit AMD CPUs.
NVIDIA's audio driver is an OSS driver, and requires OSS sound supportin the kernel. NVIDIA's audio control panel is a Qt-based application,and requires Qt run-time libraries in order to run.

The network and audio driver provided by NVIDIA is subject to theNVIDIA software license; the license is available on the NVIDIA website,and is included in this package. By using this software, you areagreeing to the terms of the license.

The package contains the following items:

  1. This Installation Guide
  2. The NVIDIA license for the network driver software
  3. Pre-built kernel library for the nForce audio driver
  4. Pre-built kernel library for the nForce network driver
  5. Audio control panel binary
  6. Pre-built kernel interface binaries for major distributions
  7. Source for the kernel interface portion of the audio driver
  8. Source for the kernel interface portion of the network driver

This installer will prepare a network driver and an audio driver,then place them in the appropriate locations for loadable kernelmodules. The network and audio drivers are from NVIDIA. Ifthe audio driver is installed, the installer will also install the audiocontrol panel application.

Nvidia has provided a self-extracting installer that will preparethe drivers and install them into the appropriate location for yourkernel's module tree. Note that there is a 32-bit installer aswell as a 64-bit installer. The 64-bit installer is required forx86_64 kernels. You can check what kind of machine you arecurrently running on by checking the output of uname -m.If the output reports x86_64, you are running a 64-bitkernel and should use the 64-bit installer.

To install the drivers, simply run the installer binary under ashell with root privileges, and follow the onscreen instructions.

The .run file accepts many command line options. Here are afew of the more common options:

--info
Print embedded info about the .run file and exit.

--check
Check integrity of the archive and exit.

--extract-only
Extract the contents of the .run file, but do not run'nforce-installer'.

--help
Print usage information for the common command line options and exit.

--advanced-options
Print usage information for the common command line options as well asthe advanced options, and exit.

The installer will use an ncurses-based user interface if it canfind the correct ncurses library. Otherwise, it will fall back toa simple interactive text interface. To disable use of the ncursesuser interface, use the option '--ui=none'.

The installer contains pre-built drivers for major Linuxdistributions. In the event that the installer cannot find apre-built driver for your kernel, the installer will attempt to buildthe driver. In this case, it is necessary to install the kernelsource corresponding to the kernel for which the driver will beinstalled for.

You might want to check the BIOS configuration on your system toensure that the audio and networking devices will be detected. See theSystem BIOS Configuration description in the Troubleshooting section.

Nvidia Nforce Networking Controller For Mac

NOTE that for network driverupdates, you must first deactivate the NVIDIA network device prior torunning the installer. Otherwise the module count for that device willnot be zero and installation of network driver will fail.

The installer does not update configuration files. Afterinstalling the drivers, configure the system to use the drivers by usingthe distribution's built-in configuration mechanisms for networking andsound, or edit the required files manually.

ModuleConfiguration File Location

Module configuration files aredifferent for 2.4 and 2.6 series kernels. The various Linuxdistributions also differ in how they handle module configuration.

  • For distributions based on a 2.4 series kernel, the moduleconfiguration file is typically called /etc/modules.conf.

  • For distributions based on a 2.6 series kernel, the moduleconfiguration file is typically called /etc/modprobe.conf.Some distributions use a subdirectory, /etc/modprobe.d/ ,to hold individual configuration files for sound modules, etc.

Configuring the network driver

SuSE

For SuSE Linux Enterprise Server 9,use YaST to configure the network driver. Start the YaST GUI, select'Network Devices', then select 'Network Card'. This should bring up the'Network cards configuration' dialog.
Select 'Other (not detected)', then select the 'Configure' button. Inthe 'Kernel Module' section, set 'Module Name' to 'nvnet', then selectthe 'Next' button. Configure the interface parameters as required,select the 'Next' button to return to the card configuration dialog, andselect 'Finish'.

Red Hat

For Red Hat Enterprise Linux version3, Red Hat 8, Red Hat 9and Fedora Core 1, follow theinstructions in otherdistributions to edit the configuration file /etc/modules.conf.Once this is done, configure the network interface parameters using theNetwork Configuration tool on the System Settings menu. Theconfiguration tool can also be launched directly as 'neat'.
For Fedora Core 2, followthe instructions in otherdistributions to edit the configuration file /etc/modprobe.conf.Once this is done, configure the network interface parameters using theNetwork Configuration tool on the System Settings menu. Theconfiguration tool can also be launched directly as 'neat'.

Mandrake

For Mandrake 10, use Mandrake Control Center(available via the mcc command) to configure the networkdriver. Select 'Network & Internet', then select 'New Connection'.Select 'LAN Connection', select 'Next', then select 'ManualChoice'. From the list of available network drivers, select'nvnet', then select 'Next'. and select 'autoprobe'. At this point, thedriver will be configured and a new interface made availabe; select thenewly-added interface to configure IP address settings, etc.
For earlier Mandrake distributions, follow the instructions in other distributions to edit theconfiguration file /etc/modules.conf. Once this is done,Mandrake Control Center can be used to configure IP address settings,etc., on the network interface supported by nvnet.

Other distributions

If the distribution you are using provides a configuration mechanismfor network drivers, use it to select the nvnet driver module for usewith the nForce ethernet device, and to set the networking parameters(IP address, etc.) for the interface. Otherwise, manually edit themodule configuration file.
If your configuration file already contains an entry for the forcedethdriver (an open-source network driver that supports the nForce networkcontroller), that entry needs to be commented out with a #or removed:
# alias eth0 forcedeth
Add the following line to the configuration file:
alias eth0 nvnet
If your system has multiple ethernet interfaces, you may need to use'eth1' or higher in place of 'eth0'.

Configuring the audio driver

SuSE

For SuSE Linux Enterprise Server 9, at the time of writing it isn't possible to use YaST to configurethe nvsound audio driver. Following the instructions in other distributions to edit theconfiguration file /etc/modprobe.d/sound.

Red Hat

For Red Hat Enterprise Linux version3, Red Hat 8, Red Hat 9and Fedora Core 1, follow theinstructions in other distributionsto edit the configuration file /etc/modules.conf.
For Fedora Core 2, followthe instructions in otherdistributions to edit the configuration file /etc/modprobe.conf.

Mandrake

At the time of writing, it isn't possible to use Mandrake ControlCenter to configure the nvsound audio driver.
Follow the instructions in otherdistributions to manually edit the configuration file. For Mandrake 10 or other Mandrakedistributions running 2.6 kernels, the configuration file is /etc/modprobe.conf.For earlier distributions that run 2.4 kernels, the configuration fileis /etc/modules.conf.

Other distributions

If the distribution you are using provides a configuration mechanismfor audio drivers, use it to select the nvsound driver module for usewith the nForce audio device. Otherwise, manually edit the moduleconfiguration file.
If your configuration file already contains an entry for thei810_audio, snd-intel8x0, or nvaudio drivers (open-source audio driversthat supports the nForce audio controller), that entry needs to becommented out with a # or removed:
# alias sound-slot-0 i810_audio
Add the following line to the configuration file:
alias sound-slot-0 nvsound
On some distributions, you may need to replace sound-slot-0with snd-card-0.

The installer may or may not leave the new modules loaded after theinstallation, depending on the existing configuration. You can force themodule to be loaded using insmod or modprobe :

insmod <modulename>

or
modprobe <modulename>

On subsequent reboots, the modules should load automatically.

The run-time behavior of NVIDIA drivers may be configured by use ofmodule parameters. These can be specified either on the commandline when loading the module, or in the module configuration file(such as /etc/modules.conf). For example, to have the nForce ethernetdriver use throughput optimized mode, add the following to the moduleconfiguration file:

options nvnet optimization=1
Or if loading the module manually from the command line:
modprobe nvnet optimization=1
The module parameters for the ethernet driver can be verified using thecommand:
modinfo -p nvnet
The following sections contain descriptions of all driver moduleparameters.

nvnet Module Parameters

The nForce network driver supports the following optional parameters:
  1. hardware offload mode
  2. optimization
  3. negotiation mode
  4. speed and duplex
  5. media
  6. max TX packets
  7. max RX packets
  8. MTU
  9. poll interval
  10. segmentation offload
  11. TX checksum offload
  12. RX checksum offload

Hardware Offload Mode

This parameter controls the hardware offload mode. The nForcenetwork driver supports two hardware offload modes:
  • hwmode=1 - off
  • hwmode=2 - on
When hardware offload mode is on, TX checksum offload, RX checksumoffload, segmentation offload, and RGMII (Reduced Gigabit MediaIndependent Interface) is used, and the MTU can be set to a non-defaultvalue. When hardware offload mode is off, these offload modes areturned off and MII (Media Independent Interface) is used, and the MTUparameter is ignored.
The default hardware offload mode will depend on the networkcontroller. The hardware offload mode can be specified bysupplying the module parameter 'hwmode'.

Optimization

NforceThe nForce network driver supports two optimization modes:
  • optimization=0 - Throughput optimization
  • optimization=1 - CPU optimization
CPU optimization mode reduces the CPU utilization by using interruptmoderation.
Throughput optimization mode maximizes the throughput. This modehas higher CPU consumption.
By default, the driver runs in throughput optimization mode. Theoptimization mode can be specified by supplying the module parameter'optimization'.

Negotiation Mode

The nForce network driver supports two negotiation modes:
  • autonegotiate=0 - disabled
  • autonegotiate=1 - enabled
When negotiation mode is enabled, the controller will negotiate for thedesired speed and duplex. If negotiation mode is disabled, thecontroller will force the speed and duplex setting without negotiation.
By default, autonegotiate is enabled.

Speed and Duplex

The 'force_speed_duplex' module parameter can be used set the interfacespeed and duplex of the ethernet controller. The following valuesare supported:
  • force_speed_duplex=0 - autonegotiate
  • force_speed_duplex=1 - 10Mbps half duplex
  • force_speed_duplex=2 - 10Mbps full duplex
  • force_speed_duplex=3 - 100Mbps half duplex
  • force_speed_duplex=4 - 100Mbps full duplex
  • force_speed_duplex=5 - autonegotiate for 10Mbps half duplex
  • force_speed_duplex=6 - autonegotiate for 10Mbps full duplex
  • force_speed_duplex=7 - autonegotiate for 100Mbps half duplex
  • force_speed_duplex=8 - autonegotiate for 100Mbps full duplex
  • force_speed_duplex=9 - autonegotiate for 1000Mbps full duplex
If a value of 0 (autonegotiate) is used, the controller will negotiatefor the optimum speed and duplex.
If a value between 1 and 4, inclusive, is set for this parameter, thennegotiation behavior will depend on the value of the autonegotiatemodule parameter. If autonegotiate is enabled, the controller willnegotiate for the desired speed and duplex. If autonegotiate isdisabled, the controller will set the speed and duplex of the controllerwithout negotiation.
If a value between 5 and 9, inclusive, is set for this parameter, thenthe controller will negotiate for the desired speed and duplex. Inthis case, the autonegotiate module parameter is implicitly enabled.
By default, the controller will autonegotiate for the optimum speed andduplex.

Media

The 'media' module parameter can be used to specify the interfacemedia. This module parameter supports the following values:
  • media=0 - auto
  • media=1 - RGMII
  • media=2 - MII
The default value of this parameter depends on whether hardware offloadmode is enabled or disabled. If hardware offload mode is enabled,RGMII is the default. If hardware offload mode is disabled, MII isthe default.

Max TX packets

The 'max_tx_packets' module parameter controls the maximum number ofoutstanding TX (transmit) packets. This parameter takes a valuebetween 32 and 1024, inclusive. By default, 64 maximum TX packetswill be used.

Max RX packets

The 'max_rx_packets' module parameter controls the maximum number ofoutstanding RX (receive) packets. This parameter takes a valuebetween 32 and 1024, inclusive. By default, 64 maximum RX packetswill be used.

MTU

The 'mtu' module parameter controls the MTU size in bytes. Thisparameter takes a value between 576 and 9202, inclusive. Bydefault, a 1500 byte MTU is used. This parameter is only relevantwhen hardware offload mode is turned on.

Poll Interval

The 'poll_interval_in_us' module parameter is used to control the rateat which hardware events are polled, and is only relevant when runningin CPU optimization mode. This parameter is ignored in throughputoptimization mode. This parameter takes a microsecond valuebetween 0 and 2000, and defaults to 0.

Segmentation Offload

The nForce network driver supports two modes for segmentation offload:
  • seg_offload=0 - disabled
  • seg_offload=1 - enabled
If hwmode=0 (disabled), the 'seg_offload' module parameter defaults to0 (disabled). If hwmode=1 (enabled), the 'seg_offload' moduleparameter defaults to 1 (enabled).

TX checksum Offload

The nForce network driver supports two modes for TX checksum offload:
  • tx_checksum_offload=0 - disabled
  • tx_checksum_offload_offload=1 - enabled
If hwmode=0 (disabled), the 'tx_checksum_offload' module parameterdefaults to 0 (disabled). If hwmode=1 (enabled), the'tx_checksum_offload' module parameter defaults to 1 (enabled).

RX checksum Offload

The nForce network driver supports two modes for RX checksum offload:
  • rx_checksum_offload=0 - disabled
  • rx_checksum_offload_offload=1 - enabled
If hwmode=0 (disabled), the 'rx_checksum_offload' module parameterdefaults to 0 (disabled). If hwmode=1 (enabled), the'rx_checksum_offload' module parameter defaults to 1 (enabled).

nvsound Module Parameters

There are currently no nvsound module parameters.
A control panel application, nvmixer, is included with the audiodriver to control the features of the nForce audio driver. Thesefeatures include:
  • Speaker setup
  • Master volume control
  • Per channel volume control / mute
  • Input source selection
  • Analog and digital output control
  • SoundStorm HW mixing

Usage

The audio control panel may be invoked by typing 'nvmixer' at thecommand line:For those that are migrating from an existing NVIDIA audio driver, notethat the old 'nvaudio' control panel will not work with the new audiodriver.

System Requirements

The nvmixer application uses the Qt graphical user interface toolkit.The pre-built nvmixer shipped with this release is built using Qtversion 3.1, and requires Qt 3.1 run-time libraries to be present onyour system in order to run.
If your system does not have Qt 3.1 libraries installed, you will mostlikely receive an 'relocation error: ... undefined symbol' error messagewhen you try to run nvmixer. If this occurs, there are two ways to solvethis problem:
  • Download and install Qt 3.1 libraries for your Linuxdistribution, so that the pre-built nvmixer application works correctly.
  • Download the source code for nvmixer from NVIDIA and build itusing a Qt version that is readily available for your Linux distribution(3.1 or later is required). The nvmixer source code package is availablefor download via anonymous FTP at:
    Pre-requisites and instructions for building nvmixer are included inthe source code package.

This section covers problems that commonly occur when installingnForce drivers on Linux. If you encounter problems, please read thissection and the FAQ , and review the Known Problemslist for the driver version you are using. This can be found at NVIDIA'sweb site, on the release page for the driver version.

If you decide to submit a bug report, make sure to includenforce-bug-report.log in the bug report by running nforce-bug-report.sh.

Bug reports and installation questions may be directed to:

System BIOS Configuration

Since the audio and network drivers work on the nForce chipset,these devices along with other motherboard devices are controlled by theSystem BIOS. If the installed drivers don't recognize hardware on yoursystem, the problem may be your System BIOS's plug and playconfiguration. If your audio or network devices are disabled in theBIOS, or the system BIOS expects the operating system to configurehardware devices, and your Linux kernel doesn't support ACPI-styleconfiguration, you'll need to change your BIOS settings.

To view or change an Award-style system BIOS, reboot the machine,and press the Delete key. When you get a configuration screen, select'PnP/PCI Configurations' in that screen if 'PNP OS Installed []' Has'Yes' chosen, change the selection to 'No'.

If your BIOS is Phoenix-style, use the F2 key instead of Delete, andscroll through the menus to find OS Type, and chose 'Other'. The exactdetails of System BIOS configuration vary with BIOS vendor, so thescreens may not be exactly the same.

Warning: You should write down the original configuration of theBIOS before changing it. Changing your system BIOS configuration mayadversely affect the operation of the system, and even make itunbootable.

Installer

  • Q: When I try to build, I get a message telling me that Ishould never try to use system headers. What's wrong?

    A: You need to install the sources for your kernel. Pleasedownload and install the appropriate kernel-source package for yourkernel

  • Q: How do I tell if I have my kernel sources installed?

    A: If you're running on a distro that uses RPM (Red Hat,Mandrake, SuSE, etc), then you can use RPM to tell you. At a shellprompt, type:

    and look at the output. You should see a package thatcorresponds to your kernel (often named something like kernel-2.4.18-3)and a kernel source package with the same version (often named somethinglike kernel-source-2.4.18-3). If none of the lines seem to correspond toa source package, then you'll probably need to install it. If theversions listed mismatch (ex: kernel-2.4.18-10 vs.kernel-source-2.4.18-3), then you'll need to update the kernel-sourcepackage to match the installed kernel. If you have multiple kernelsinstalled, you need to install the kernel-source package thatcorresponds to your running kernel (or make sure your installedsource package matches the running kernel). You can do this by lookingat the output of 'uname -r' and matching versions.

  • Q: I just upgraded my kernel,and now the NVIDIA kernel module will not load. What is wrong?
    A: The kernel interface layer of the NVIDIA kernel module must becompiled specifically for the configuration and version of yourkernel. If you upgrade your kernel, then the simplest solution isto reinstall the driver.
    ADVANCED: You can install the NVIDIA kernel module for a non runningkernel (for example: in the situation where you just built and installeda new kernel, but have not rebooted yet) with the command line option--kernel-name='KERNEL_NAME', where KERNEL_NAME is what 'uname -r' wouldreport if the target kernel were running.
  • Q: nforce-installer does notwork on my computer. How can I install the driver contained withinthe .run file?
    A: To install the NVIDIA driver contained within the .run file withoutusing nforce-installer, you can use the included makefile that isextracted with the --extract-only command-line option. Themakefile for the audio driver is in the nvsound/main directory of theextracted .run file, and the makefile for the network driver is in thenvnet directory of the extracted .run file. This method ofinstallation is not recommended, and is only provided as a last resort,should nforce-installer not work correctly on your system.
  • Q: I have multiple kernelsinstalled. When I run the NVIDIA installer under one kernel, it removesmodules I previously installed for one of the other kernels. How do Iprevent the installer doing that?
    A: You can avoid this by using the --kernel-module-only option to theinstaller when you install for the second and subsequent kernels in yourinstallation. This advanced option installs the kernel module only (nodocumentation, etc.) and does not remove any previously installed drivermodule.

Audio driver

  • Q: I've installed the nvsounddriver, but xmms doesn't produce any audio output when I try to playsound files.

    A: Check that xmms is configured to use the OSS output plugin(nvsound is an OSS driver). The xmms output plugin settings can beviewed on xmms's Options->Preferences submenu.

  • Q: When I try to start nvmixer,I get a 'relocation error: ... undefined symbol' message andnvmixer doesn't start. What's wrong?

    A: This is most likely caused by your system not having the Qtrun-time libraries that nvmixer requires in order to run. Refer to thesection on nvmixer's system requirementsfor details on how to fix this.

  • Q: When I start KDE with thenvsound driver loaded, I get an error message, 'Sound server fatalerror: AudioSubSystem::handleIO: write failed len=-1,can_write=1024, errno=11 (Resource temporarily unavailable)'.
    A: Open the KDE Control Center (using a menu or the kcontrolcommand). Select 'Sound & Multimedia', then select 'Sound System'.Select the 'Hardware' tab and, in the 'Select the audio device'pulldown control, select 'Threaded Open Sound System'. Select 'Apply',then exit the Control Center. This should fix the sound server errormessage seen on startup.

Network driver

There is currently no troubleshooting information for the nvnetnetwork driver.

Installer FAQ

  • Q: Why does NVIDIA not provideRPMs anymore?
    A: Not every Linux distribution uses RPMs, and NVIDIA wanteda single solution that would work across all Linux distributions. As indicated in the NVIDIA Software License, Linux distributions arewelcome to repackage and redistribute the NVIDIA Linux driver inwhatever package format they wish.

Nvidia Nforce Networking Controller For Mac Installer

  • Q: How do I extract thecontents of the .run file without actually installing the driver?
    A: Run the installer with the --extract-only command line option. This will create a directory which contains the uncompressed contents ofthe .run file.
  • Q: How can I see the sourcecode to the kernel interface layer?
    A: Kernel interface layer source files for the audio driver are in thenvsound/main directory of the extracted .run file. The kernelinterface layer source files for the network driver are in the nvnetdirectory of the extracted .run file.
  • Q: Can I add my own precompiledkernel interfaces to a .run file?
    A: Yes, the '--add-this-kernel' .run file option will unpack the .runfile, build a precompiled kernel interface for the currently runningkernel, and repackage the .run file, appending '-custom' to the filename. This may be useful, for example, if you administer multipleLinux machines, each running the same kernel.
  • Q: Where can I find the sourcecode for the nforce-installer utility?
    A: The nforce-installer utility for the nForce drivers is derived fromthe nvidia-installer utility used for the NVIDIA video drivers. The NVIDIA video driver nvidia-installer utility is released under theGPL. The latest source code for it is available at:
    ftp://download.nvidia.com/XFree86/nvidia-installer/
67.8.9.0

Driver FAQ

Nforce Networking Controller Windows 10

  • Q: My IDE hard drive is running very slowly, how can I enableDMA mode?

    A: A kernel patch was added in kernel 2.4.21pre3-ac1 whichenables DMA for the nForce2 IDE controller and should be available inthe final released 2.4.21 kernel. An alternative to upgrading yourkernel is to use the 'hdparm' utility to enable DMA for your hard drive.For example:

    Where /dev/hdX is the IDE device you wish to enable DMA for. Youmust do this every time you reboot, or add it to an rc script. Somedistributions have a file '/etc/sysconfig/harddisks' where you canenable this for all hard drives on system boot.

  • Q: Does NVIDIA supply a Linux driver for the USB and USB2.0devices?

    A: The USB and USB2.0 devices use the industry standard OHCI andEHCI interfaces, and will work with the standard Linux USB drivers.

  • Q: I've rebuilt the Nforce driver, but when I try to insertit, I get a message telling me I have unresolved symbols.

    A. Unresolved symbols are most often caused by a mismatchbetween your kernel sources and your running kernel. They must match forthe nForce driver modules to build correctly. Please make sure yourkernel sources are installed and configured to match your runningkernel.

  • Q: Does NVIDIA have a Linux driver for 1394 on nForce2?

    A: The Linux 1394 driver supports the nForce2 1394 controller inkernel versions 2.4.21 and newer.

  • Q: Is the nForce3 IDE controller supported by Linux?

    A: nForce3 IDE controller will exist in kernel 2.4.23 and later

  • Q: Are there open source networking and audio drivers fornForce hardware?

    A: For audio you can use the i810 audio driver. For networking,it depends on the version of the kernel you are working with. Someversions of the kernel will have a driver called forcedeth. Olderversions of the driver only support nForce2 while later versions of thedriver will also support nForce3 gigabit Ethernet.

  • Q: Linux distributions aremoving towards ALSA as the standard sound driver architecture, butnvsound is an OSS driver. Why don't you provide an ALSA driver?

    A: Our priority in shipping the nvsound driver was to providesupport for nForce hardware features that were missing in the earliernvaudio driver. NVIDIA plans to provide an nForce ALSA driver in futureas our resources allow.


The nforce-installer for the nForce drivers is derived from thenvidia-installer used for the NVIDIA video drivers. The videodriver nvidia-installer was inspired by the loki_update tool:(http://www.lokigames.com/development/loki_update.php3).
The self-extracting archive (aka '.run file') is generated usingmakeself.sh: (http://www.megastep.org/makeself/).

What Is A Networking Controller


The most recent changes are at the top of the list. Each bulletindicates a public release on NVIDIA's web site.

  • Added pre-built 64-bit binaries for various distributions.
    Added support for kernel installations that use separate kernel sourceand generated kernel object trees.
    Fixed nvnet problem that caused rmmod to crash on systems with morethan one network interface.
    Fixed nvnet build issue on uniprocessor systems that have spinlockdebugging enabled.
    Fixed nvsound module hangs when APIC is enabled on some distributions.
    Fixed nvsound module bugs causing lack of sound or delay in sound withsome games.
  • Changed installation method to use the new self-extractinginstaller instead of RPM or tarball
    Added support for SoundStorm (Hardware Mixing supported)
    Added AC3 pass-through
    Added support for ethernet driver statistics and configurationinformation through procfs
    Added support for 2.6 series kernels
    Audio control panel executable is now 'nvmixer', not 'nvaudio'
  • Fixed performance problem in network driver that was causingstuttering in audio playback
    Added support for nForce3 platforms
    Added support for x86-64 architecture
    Added binary RPMs for SuSE Enterprise Server 8 x86-64
    Added audio control panel application
    Added 6 channel output, audio input selection, speaker selection, perchannel volume control, and analog / digital enable to audio driver.
    Added GART patch for kernel 2.4.21
  • Added kernel patch to support nForce GART
    Added 'spdif_status' module parameter to audio driver to enable/disableS/PDIF support for compatability
    Fixed bug in audio driver that was causing MSI nForce board to only use2 channels
    Fixed mmap bug in audio driver causing Quake III to hang.
    Fixed RedHat 9 build issue with remap_page_range().
    Fixed problem with rebuilding SRPM on RedHat 9.
    Added RedHat 9 and Mandrake 9.1 binary RPMs.

Update Nvidia Nforce Networking Controller

  • Fixed problem with compiler arguments between gcc3.X and gcc2.X

    Changed installation script to use lowest available number whenenumerating network and audio devices in modles.conf

    Changed audio driver to be self contained source file based offi810_audio driver.
    Added SPDIF support to audio driver

    Updated binary packages for latest releases of RedHat kernels.

    Added FAQ section to release notes.

  • Added PCI ID support for MCP2 and MCP2 to the i810_audio driver.

    Some cleanup of spec file and Makefiles

    SRPMs and tar files now use local system's i810_audio.c file,and complain if it's not there; this makes them more distro independent.

  • Changed code to compile properly with gcc3.X and gcc2.X

    Added support for Mandrake9.0 and Redhat8.0

    nForce2 support for network driver