Netra CP32x0 10GbE Advanced Rear Transition Module, Dual Port User’s Guide

C H A P T E R 3

Driver Installation and Configuration

Uninstalling drivers. Uninstalling drivers is the most difficult part of the process, and it’s still not that hard. It’s a necessary step to take in order to install Bluetooth Driver Installer. You’ll need to navigate to your Device Manager through the Windows start menu. Then, you’ll right-click on the device you want and click. Welcome to the NETGEAR Download Center!! To find documentation, firmware, software, or other files, enter a whole or partial Model number in the text search box. An unknown device isn’t just unknown — it’s not functioning until you install the right driver. Windows can identify most devices and download drivers for them automatically. When this process fails — or if you disable automatic driver downloads — you’ll have to identify the device and hunt the driver down on your own.

This chapter explains how to download and install the nxge driver used to operate certain ports on the Netra CP32x0 10GbE Ethernet Advanced Rear Transition Module, Dual Port (ARTM-10G). More specifically, the nxge driver facilitates use of SFP ports 1, 2, 3 and 4.

This chapter contains the following topics:

These are the newest CH Drivers for CH Game Port devices. These new drivers will work with the CH F-16 Combatstick, CH F-16 Flightstick, CH Fighterstick, CH Flight Sim Yoke PC, CH Flightstick Pro.

3.1 Installing the nxge Driver

The nxge driver is the Gigabit Ethernet driver that operates the Netra CP32x0 ARTM-10G in a Solaris or Linux environment. The nxge driver is managed by the dladm command-line utility, which allows VLANs to be defined on top of nxge instances and for nxge instances to be aggregated. See the dladm(1M) man page for more details on configuring the size='1'>

Note - At this time, there is not a command or process available to route traffic to these ports. Refer to the Netra CP32x0 Advanced Rear Transition Module Product Notes Notes (820-3261).

3.1.1 Download and Install for Solaris Operating Systems

The nxge device driver is required for systems using the SPARC-based or x86-based Solaris Operating System.

To Download and Install the Driver for Solaris Operating Systems

1. Locate and download the patch with the nxge device driver software from the following web site:

http://www.sun.com/download

Refer to the README file and the Netra CP32x0 Advanced Rear Transition Module Product Notes (820-3261) for the most current information.

2. Install the driver onto your system.

a. Uncompress or unzip the patch into the target directory.

b. Type the following commands to install the patch into the target directory:

3. Verify that the nxge driver is installed on the system.

3.1.2 Download and Install for Linux Operating Systems

The nxge device driver is required for systems using the Linux operating system.

To Download and Install the Driver for Linux Operating Systems

1. Locate and download the patch with the nxge device driver software from the following web site:

http://www.sun.com/download

Refer to the README file and the Netra CP32x0 Advanced Rear Transition Module Product Notes (820-3261) for the most current information.

2. Choose the rpm that matches your OS distribution, for example:

Where x.x-x is the version number.

3. List the network interfaces that exist prior to adding the driver package:

4. Install the driver on Linux.

Where x is the most current version available.

5. List the network interfaces again, and note the new network interface instances corresponding to the Netra CP32x0 ARTM-10G:

The additional Netra CP32x0 ARTM-10G instances, eth9 through eth12, are shown. The MAC address of the ARTM resource is easily identified as 00:11:0d:xx:xx:xx.

6. Add the nxge interfaces to the /etc/modules.conf file to automatically load the driver after system reboot:

7. Check the parameter configurations that apply to the nxge driver.

3.2 Configuring the nxge Driver

The Netra CP32x0 ARTM-10G includes six ports, which are controlled by the nxge driver:

• Two 1-Gigabit full duplex networking interfaces (ports 1 and 2)
• Two 10-Gigabit full-duplex network interfaces (ports 3 and 4)
• Two 10-Gigabit full-duplex network interfaces driven by ATCA front board resource (ports 5 and 6)

This section provides procedures for configuring nxge driver attributes and parameters, based on your OS.

3.2.1 Configuring nxge Driver Parameters on a Solaris Platform

You can configure and modify nxge device driver parameters in two ways:

• Using the ndd utility
• Using the nxge.conf file

If you use the ndd utility, the parameters are valid only until you reboot the system. This method is good for testing parameter settings.

3.2.1.1 Modifying Parameters Using the ndd Utility

Use the nddutility to configure parameters that are valid until you reboot the system (non-persistent configurations).

The following sections describe how to use the ndd utility to modify (with the -set option) or display (without the -set option) parameters for each nxge device.

The ndd utility can be invoked in either of two modes:

• Interactive menu mode. In this mode, the utility displays a menu of commands, and prompts you for each input value. You can set and get multiple parameters before exiting the utility.
• Non-interactive mode. In this mode, invoke the utility to execute a single command. Once the command is executed, the utility exits and returns to the command prompt.

Refer to the ndd(1M) man page for more information.

To Specify Device Instances

Before you use the ndd utility to get or set a parameter for an nxge device, you must specify the device instance for the utility.

Check the /etc/path_to_inst file to identify the instance associated with a device.

To Modify Parameters in Interactive Mode

1. Type ? to see all the parameters supported by the nxge driver.

2. Modify a parameter value by specifying ndd/dev/nxge<x>, such as the following example.

3. Enter the parameter name.

After you enter the parameter name, the ndd utility prompts you for the parameter value.

4. Enter the parameter value or ? for more information.

Refer to the ndd(1M) man page for more information.

To Modify Parameter Values in Non-Interactive Mode

1. Invoke the ndd utility with or without the -set option.

• When you invoke the ndd utility with the -set option, the utility passes value, which must be specified, down to the named /dev/nxgedriver-instance, and assigns the value to the parameter:

Where x is the driver instance, for example /dev/nxge0,/dev/nxge1, and parameter-value is a valid input or option.

• When you omit the -set option, the utility queries the named driver instance, retrieves the value associated with the specified parameter, and prints the value:

Where x is the driver instance.

2. Display the value of a parameter by specifying the parameter name and omitting the value.

3. Modify a parameter value.

Refer to the ndd(1M) man page for more information.

3.2.1.2 Modifying Parameters Using the nxge.conf File

Use an nxge.conf file when you want to establish persistent parameter values for a device in the system.

For more information, refer to the prtconf(1M) and driver.conf(4) man pages.

To Modify Parameters Using nxge.conf File

1. Obtain the hardware path names for the nxge devices in the device tree.

2. Check the /etc/driver_aliases file to identify the name associated with a device.

3. Locate the path names and the associated instance numbers in the /etc/path_to_inst file.

This command returns two nxge interfaces, and for each, includes three descriptive parameters:

• Instance pathname in quotes
• Instance Number (integer, no quotes)
• Instance driver name in quotes

The nxge.conf will likely contain information for several nxge interfaces. The output from steps 1 and 2 is used to specify the nxge interface, if needed. In this example:

4. Edit the /kernel/drv/nxge.conf file to set nxge parameters.

For an output of all the parameters you can modify, see CODE EXAMPLE 3-1.

5. To set persistence for all parameters, specify the driver parameter properties for each device by creating an nxge.conf file located in the following directory:

• For SPARC-based host, /platform/sunv4/kernel/drv/nxge.conf
• For x86-based host, /kernel/drv/nxge.conf

Edits to /kernel/drv/nxge.conf file may be made with any ASCII, text editor.

To apply an edit to all ports, entries are listed with no specific node prefix. In this example, all modules are being set for load balancing RX traffic based on the IP source address. The default value is F80, indicating RX load balancing based on IP 5-tuple. Notice the semicolon at the end of the last parameter.

6. To set persistence for a specific parameter, edit the nxge.conf file to add the specific parameter values.

These parameters are reloaded at each reboot.

To apply an edit to specific ports, an entry is prefixed with the node/interface specific information as shown:

7. Save the nxge.conf file.

The following CODE EXAMPLE 3-1 provides an output of all the parameters modifiable via the nxge.conf file. See also Chapter 4 for instructions on how to configure the network settings.

CODE EXAMPLE 3-1 Driver Parameters Modifiable via nxge.conf File

3.2.2 Configuring Driver Parameters on a Linux Platform

Use the ethtool utility or the configtool utility to modify nxge driver parameters on a Linux platform.

3.2.2.1 Modifying Parameters Using the ethtool Utility

This section describes ethtool commands for modifying driver parameters. Refer to the ethtool(1M) man page for more information and detailed usage examples.

To Determine Modifiable Parameters

Use the ethtool utility to list all driver parameters that can be modified.

CODE EXAMPLE 3-2 Listing Modifiable Driver Parameters on a Linux Platform

Following are common parameters that can be changed:

CODE EXAMPLE 3-3 Common Parameters That are Modifiable on a Linux Platform

The parameters rx-usecs and rx-frames control the RX interrupt rate per RX DMA channel. RX interrupt will be generated after rx-frames have been received or after rxusecs time interval, if fewer than rx-frames have been received within the interval.

• For low latency applications, set rx-usecs to a smaller value.
• For bulk traffic, use larger values of rx-usecs and control the rate with rx-frames.

The rx-frames-irq controls the maximum number of RX packets processed with a single RX interrupt.

To Change RX Coalesce Parameters

Use the ethtool-C command.

CODE EXAMPLE 3-4 Changing RX Coalesce Parameters

To Obtain the Status of L4 Hardware

Use the ethtool-k command.

CODE EXAMPLE 3-5 Obtaining Status of L4 Hardware

3.2.2.2 Modifying Parameters Using configtool Utility

This section describes how to use the configtool utility to modify driver parameters.

To Obtain a List of Modifiable Parameters

Use the nxge_configif-nameget command.

CODE EXAMPLE 3-6 Obtaining a List of Tunable Driver Parameters on a Linux Platform

These classification variables define how each IP class is configured. These parameters also control how the flow template is constructed and how packets are distributed within RDC groups.

NDD Port Devices Driver Download

Note - The classification variables are modified on an ARTM basis. That is, if any of these variables is modified for one port, the change carries over to all other ports of the ARTM.

To Display a Parameter

Use the nxge_config<if-namegetparam-name> command.

To Modify a Specific Parameter

Use the /usr/local/bin/nxge_config<if_namesetparam_name> command.

3.3 Tuning Performance on a Linux Platform

The following procedure improves the performance of the Netra CP32x0 ARTM-10G ports on a system running the Linux OS.

To Tune Ethernet Port Performance

1. Using any ASCII text editor, create a new .conf file that will be passed to the sysctl utility.

For example, sysctl_e1000.conf

CODE EXAMPLE 3-7 Sample .conf File for Tuning Ethernet Ports on a Linux Platform

2. To apply your settings, invoke the sysctl utility, including the configuration file as follows:

Ndd Port Devices Driver Download Mac

3.4 Enabling Host Board PCI-Express Communication

Presently, only the Sun Netra CP3260 blade server can be configured to use PCI-express signals to communicate with the Netra CP32x0 ARTM-10G. By default, the host blade server is usually shipped with these signals disabled. The following procedure enables PCI-express signals.

To Enable PCI-Express Signals

1. Do one of the following:

• If using a SPARC-based host board, skip to Step 2.
• If using an x86-based host board, perform the following:

a. At boot, invoke the BIOS menu (ESC 2, F2, Ctrl-C, or Ctrl-E).

b. Under the Chipset menu/Southbridge menu, disable Spread Spectrum clocking for PCI-E.

c. Save and Exit the BIOS.

2. Establish a console connection with the shelf manager.

3. Type the shelf command clia to determine the slot location of the host board that will connect to the Netra CP32x0 ARTM-10G.

The shelf manager will show a Device ID String indicating the host board.

4. Enter the cliasendcmdxx2e8b00002a91c command.

Where xx is the board address.

5. At the shelf manager, type cliaboard to find the correct number for your host board installation.

6. Type the shelf cliaboardreset2 command.

3.5 Removing the nxge Driver

If you want to remove the nxge driver from your system, perform the following procedure, based on your OS.

To Remove the Driver From a Solaris Platform

1. Determine the driver packages:

2. Remove the driver packages:

To Remove the Driver From a Linux Platform

Type the following:

Netra CP32x0 10GbE Advanced Rear Transition Module, Dual Port User’s Guide

820-3150-10

Ndd Port Devices Driver Download Free

Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved.

Ndd Port Devices Driver Download Windows 7

• August 22, 2019 2.9.8

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.8	Released August 22, 2019	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added several internal interfaces for particular sensors (J003).

• January 25, 2019 2.9.6

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.6	Released January 25, 2019	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added missing Tonemapping Auto property.

• May 4, 2018 2.9.5

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.5	Released May 4, 2018	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Enabled tonemapping for 8bit video formats, e.g. Y800, RGB24 and RGB32.

• November 21, 2017 2.9.4

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.4	Released November 21, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Repaired not working J003 mono sensor pattern fix on particular video formats. This driver version is the last that works in Windows XP.

• January 9, 2017 2.9.3

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.3	Released January 9, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added a pattern fix for J003 mono sensors.

• January 9, 2017 2.9.1

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.1	Released January 9, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed the driver signature Code 52 error on new Windows 10 v1607 systems.

• January 15, 2016 2.8.9

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.9	Released January 15, 2016	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Changed certificates so that the driver can also be installed in Vista.

• November 9, 2015 2.8.7

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.7	Released November 9, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed an error which can appear when using sharpness on older CPUs.

• October 20, 2015 2.8.5

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.5	Released October 20, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed a bug which can appear on LivePause call.

• July 15, 2015 2.8.0

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.0	Released July 15, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Support of DFK ECU010-L34 with serial number property. Added tone mapping.

• February 17, 2015 2.7.33

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.33	Released February 17, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog The Auto Focus Onepush Running flag now resets correctly after the auto focus has finished.

• February 5, 2015 2.7.32

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.32	Released February 5, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Video format MJPG (2592x1944) of DFK AFU050-L34 camera can now be used.

• January 14, 2015 2.7.31

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.31	Released January 14, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Support for IMX236 based cameras. Support for RGB64 color formats. Several performance improvements.

• June 6, 2014 2.7.9.1152

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.9.1152	Released June 6, 2014	Type ZIP	Filesize 2.1MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added new properties: Brightness, sharpness, de-noise, saturation, hue and contrast. Added new property: Highlight reduction. Added new property: White balance temperature controls. Pixelfix for Y16 cameras now works as expected. VideoControl_ExternalTrigger (DirectShow property) can now be set as expected.

• January 1, 2014 2.6.5.1014

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.6.5.1014	Released January 1, 2014	Type ZIP	Filesize 1.9MB
  Requirements Intel Pentium IV or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed missing auto-gain for DFK AFU130. Fixed focus when start value is out of auto_focus_range. Fixed problem with AUTOFOCUS_ROI_RIGHT: minimum possibly wrong. Fixed auto focus ROI not working for 21*UC cameras. Fixed crash on load/connect with certain cameras 22/72xUC. Fixed previous exposure settings not being loaded on reconnect. Complete reworking of internal property system. Fixed Windows XP driver load crash. Fixed drop counter to be accessible from DirectShow. Fixed Windows 8 problem with certain video formats needing converters with standard DirectShow filters (e.g. Y800, capturing to an Y800 avi file was not possible). Fixed a problem with Windows 8 usbxhci driver not allowing transfers larger then 4 MB.

• February 26, 2013 2.4.14.851

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.4.14.851	Released February 26, 2013	Type ZIP	Filesize 1.9MB
  Requirements Intel Pentium IV or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit) DirectX 9.0c or higher
  Changelog WHQL certification.