Sponsored Content
Operating Systems Solaris Solaris 10 Changing of nic link_speed Post 302596956 by pseudocoder on Wednesday 8th of February 2012 07:29:21 PM
Old 02-08-2012
Quote:
Originally Posted by admin_xor
First of all if the adaptor e1000g0 supports only 100 mbps, you will not be able to set it to 1000 mbps. Hardware cannot be pushed to go beyond the limit with software. Upgrade the NIC!! Smilie
You obviously don't have a clue Smilie

Intel® PRO/1000 MT Server Adapter - Overview

Didn't you notice there are 2 equal nic's and one is already correctly set to run in gigabit mode? Smilie

---------- Post updated at 01:29 ---------- Previous update was at 01:21 ----------

Quote:
Originally Posted by freshmeat
i try to use command:
ndd -set /dev/e1000g0 link_speed=1000
Did you run
Code:
# ndd -get /dev/e1000g0 ?

before? Check this, especially configuration chapter: http://docs.oracle.com/cd/E19253-01/...g4j/index.html
You can't force this nic to 1000mbs ^^
 

9 More Discussions You Might Find Interesting

1. IP Networking

not able to add nic in solaris 8

Hi Folks, I've just installed solaris 8, but i cannot add my network card. i've reboot the box, got into the configmode, and try'd to add a network card. but it doesn't work. I can't add a ip address to the card, an error occurs. Who do i add it. Kind Regards (3 Replies)
Discussion started by: noripsni
3 Replies

2. UNIX for Advanced & Expert Users

Changing MAC address of a NIC

All, I have a need to software change the MAC address of a NIC in a Sparc Ultra 10 - I believe there is a command that allows to do this at boot up? Is it a missing (to me) part of ifconfig ? If so, what is the syntax? All replies gratefully received ! Thanks Andrew (3 Replies)
Discussion started by: wretch
3 Replies

3. Solaris

NIC drivers+solaris 10

Installed solaris 10 and now i want to connect to internet,to make work this i need to NIC drivers can some body tell me is it possible to get drivers and how to install. I am dying to get rid of this problem..please help me (1 Reply)
Discussion started by: srinivas2828
1 Replies

4. Red Hat

changing ethernet NIC names?

I have an RHEL 5 server with 2 Broadcom on-board NICs and 2 quad-port Intel NICs. After I installed the OS, the Intel NICs became eth0-7, and the onboards are eth8 and eth9. I really need the onboard NICs to be eth0 and eth1 (I have plans to later remove the quad-ports and replace them with 10gE... (1 Reply)
Discussion started by: GKnight
1 Replies

5. Linux

changing speed of NIC Card in linux

Hi, I would like to know how to change the speed of ethernet card in linux? as it is showing auto-neg using mii-tool -v eth0 and my requirement is 100mbps full duplex. Regards, Manoj (3 Replies)
Discussion started by: manoj.solaris
3 Replies

6. Solaris

Solaris, identifying NIC hw issues

Can someone point out which steps are to be done to get information if NIC on Solaris is malfunctioned and/or not working properly. Since my Solaris knowledge is very modest, i would apreciate any help. OS is Solaris 10 x86 Regards. Peasant. ---------- Post updated at 11:57 AM... (0 Replies)
Discussion started by: Peasant
0 Replies

7. Solaris

NIC detection problem in solaris

Hi, Hardware: Mother board: Asus P5G4IC-M LX On board NIC: PCIe Gigabite LAN Kernel Ver.: SunOS 5.10 Generic_141445-09 I've NIC detection problem in Solaris 10. When I was trying to install in x86 machine, it was not asking for any Network settings which means it couldn't find NIC. But... (7 Replies)
Discussion started by: vicky86ind
7 Replies

8. Solaris

x86 Solaris 10 nic driver added but not attached. NIC is not detected.

I couldn't install my nic in solaris 10. I compiled and added the driver but failed to attach the driver and ifconfig output shows only loopback dev. Please see the following output and tell me whether my nic has been detected and why the driver failed to attach? My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies

9. UNIX for Advanced & Expert Users

Changing single path NIC to a teamed connection in same subnet

Dear all, I have a remote CentOS7 server that has two network cards. Each card has four ports and port one of card one was defined with the IP address assigned to the server. So far, so good and it's been working for over a year. We have now got cables sorted out so there are four paths... (4 Replies)
Discussion started by: rbatte1
4 Replies
EM(4)							   BSD Kernel Interfaces Manual 						     EM(4)

NAME
     em -- Intel(R) PRO/1000 Gigabit Ethernet adapter driver

SYNOPSIS
     To compile this driver into the kernel, place the following line in your kernel configuration file:

	   device em

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

	   if_em_load="YES"

DESCRIPTION
     The em driver provides support for PCI Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545,
     82546, 82546EB, 82546GB, 82547, 82571, 81572, 82573, and 82574 Ethernet controller chips.	The driver supports Transmit/Receive checksum off-
     load and Jumbo Frames on all but 82542-based adapters.  Furthermore it supports TCP segmentation offload (TSO) on all adapters but those
     based on the 82543, 82544 and 82547 controller chips.  The identification LEDs of the adapters supported by the em driver can be controlled
     via the led(4) API for localization purposes.  For further hardware information, see the README included with the driver.

     For questions related to hardware requirements, refer to the documentation supplied with your Intel PRO/1000 adapter.  All hardware require-
     ments listed apply to use with FreeBSD.

     Support for Jumbo Frames is provided via the interface MTU setting.  Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility
     configures the adapter to receive and transmit Jumbo Frames.  The maximum MTU size for Jumbo Frames is 16114.

     This driver version supports VLANs.  The em driver supports the following media types:

     autoselect   Enables auto-negotiation for speed and duplex.

     10baseT/UTP  Sets 10Mbps operation.  Use the mediaopt option to select full-duplex mode.

     100baseTX	  Sets 100Mbps operation.  Use the mediaopt option to select full-duplex mode.

     1000baseSX   Sets 1000Mbps operation.  Only full-duplex mode is supported at this speed.

     1000baseTX   Sets 1000Mbps operation.  Only full-duplex mode is supported at this speed.

     The em driver supports the following media options:

     full-duplex  Forces full-duplex operation

     half-duplex  Forces half-duplex operation.

     Only use mediaopt to set the driver to full-duplex.  If mediaopt is not specified, the driver defaults to half-duplex.

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

HARDWARE
     The em driver supports Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB,
     82546GB, 82547, 82571, 82572, 82573, and 82574 controller chips:

     o	 Intel PRO/1000 CT Network Connection (82547)
     o	 Intel PRO/1000 F Server Adapter (82543)
     o	 Intel PRO/1000 Gigabit Server Adapter (82542)
     o	 Intel PRO/1000 GT Desktop Adapter (82541PI)
     o	 Intel PRO/1000 MF Dual Port Server Adapter (82546)
     o	 Intel PRO/1000 MF Server Adapter (82545)
     o	 Intel PRO/1000 MF Server Adapter (LX) (82545)
     o	 Intel PRO/1000 MT Desktop Adapter (82540)
     o	 Intel PRO/1000 MT Desktop Adapter (82541)
     o	 Intel PRO/1000 MT Dual Port Server Adapter (82546)
     o	 Intel PRO/1000 MT Quad Port Server Adapter (82546EB)
     o	 Intel PRO/1000 MT Server Adapter (82545)
     o	 Intel PRO/1000 PF Dual Port Server Adapter (82571)
     o	 Intel PRO/1000 PF Quad Port Server Adapter (82571)
     o	 Intel PRO/1000 PF Server Adapter (82572)
     o	 Intel PRO/1000 PT Desktop Adapter (82572)
     o	 Intel PRO/1000 PT Dual Port Server Adapter (82571)
     o	 Intel PRO/1000 PT Quad Port Server Adapter (82571)
     o	 Intel PRO/1000 PT Server Adapter (82572)
     o	 Intel PRO/1000 T Desktop Adapter (82544)
     o	 Intel PRO/1000 T Server Adapter (82543)
     o	 Intel PRO/1000 XF Server Adapter (82544)
     o	 Intel PRO/1000 XT Server Adapter (82544)

LOADER TUNABLES
     Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5).

     hw.em.rxd
	     Number of receive descriptors allocated by the driver.  The default value is 256.	The 82542 and 82543-based adapters can handle up
	     to 256 descriptors, while others can have up to 4096.

     hw.em.txd
	     Number of transmit descriptors allocated by the driver.  The default value is 256.  The 82542 and 82543-based adapters can handle up
	     to 256 descriptors, while others can have up to 4096.

     hw.em.rx_int_delay
	     This value delays the generation of receive interrupts in units of 1.024 microseconds.  The default value is 0, since adapters may
	     hang with this feature being enabled.

     hw.em.rx_abs_int_delay
	     If hw.em.rx_int_delay is non-zero, this tunable limits the maximum delay in which a receive interrupt is generated.

     hw.em.tx_int_delay
	     This value delays the generation of transmit interrupts in units of 1.024 microseconds.  The default value is 64.

     hw.em.tx_abs_int_delay
	     If hw.em.tx_int_delay is non-zero, this tunable limits the maximum delay in which a transmit interrupt is generated.

DIAGNOSTICS
     em%d: Unable to allocate bus resource: memory  A fatal initialization error has occurred.

     em%d: Unable to allocate bus resource: interrupt  A fatal initialization error has occurred.

     em%d: watchdog timeout -- resetting  The device has stopped responding to the network, or there is a problem with the network connection
     (cable).

SUPPORT
     For general information and support, go to the Intel support website at: http://support.intel.com.

     If an issue is identified with the released source code on the supported kernel with a supported adapter, email the specific information
     related to the issue to <freebsdnic@mailbox.intel.com>.

FILES
     /dev/led/em*  identification LED device nodes

EXAMPLES
     Make the identification LED of em0 blink:

	   echo f2 > /dev/led/em0

     Turn the identification LED of em0 off again:

	   echo 0 > /dev/led/em0

SEE ALSO
     altq(4), arp(4), igb(4), led(4), netintro(4), ng_ether(4), polling(4), vlan(4), ifconfig(8)

HISTORY
     The em device driver first appeared in FreeBSD 4.4.

AUTHORS
     The em driver was written by Intel Corporation <freebsdnic@mailbox.intel.com>.

BUGS
     Hardware-assisted VLAN processing is disabled by default.	You can enable it on an em interface using ifconfig(8).

BSD								   May 14, 2010 							       BSD
All times are GMT -4. The time now is 06:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy