Sponsored Content
Special Forums IP Networking NIC speed 100M/full duplex problem Post 302158696 by AirWalker83 on Wednesday 16th of January 2008 05:28:57 AM
Old 01-16-2008
NIC speed 100M/full duplex problem

I have a TOSHIBA AS7000 B150 Sun Box
I wanted to run it with 100M/full duplex
I had added this to the /etc/system file to make to setting permenant So it would be set correctly on reboot.
set eri:eri_adv_100fdx_cap=1
set eri:eri_adv_100hdx_cap=0
set eri:eri_adv_autoneg_cap=0

But when I rebooted the Sun Box and checked to nic configuration, all the setting were reset to 1
ndd -get /dev/eri adv_autoneg_cap
1
ndd -get /dev/eri adv_10hdx_cap
1
ndd -get /dev/eri adv_10fdx_cap
1
ndd -get /dev/eri adv_100hdx_cap
1
ndd -get /dev/eri adv_100fdx_cap
1
Anything thoughts on what might be causing this to happen?
 

9 More Discussions You Might Find Interesting

1. Programming

full -duplex ?

what is meant by full duplex and half duplex? b'coz in differences b\w hub and switch ,i heard lot this duplex word so please help me (1 Reply)
Discussion started by: parvathy
1 Replies

2. Solaris

change NIC to 1000 Mbps full duplex

Hi all, I tried to use this command ndd -set /dev/eri adv_1000fdx_cap 1 but i get a "operation failed, Invalid argument" anyone can help ? Thanks (5 Replies)
Discussion started by: DarReNz
5 Replies

3. Solaris

gigabit - fix speed/duplex on the switch ? or autoneg ?

Hi there We have a bit of a debate going here over what the prefered method is for setting 1000/Full on e1000g or nge interfaces is. As you aware the Solaris configration files for nge and e1000g dont allow you to "fix" 1000/Full but instead allow you to set auto-negotiate to ON but only... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

4. Infrastructure Monitoring

How to find the duplex speed on Windows

Hi, In UNIX, it's very easy to find the duplex speed. But in Windows, is there a easy way to find the duplex speed? I can't go to over 100 servers to find this out, I was wondering if I run one command to do this? Please advice. (2 Replies)
Discussion started by: samnyc
2 Replies

5. Solaris

Solaris 10 Speed and Duplex Settings: bge

Evening, I am attempting to change the speed and duplex settings on a single interface on a bge card on an m3000 SPARC server. Currently the settings are as follows: bge0 link: up speed: 1000 Mbps duplex: full bge1 link: up speed: 100 Mbps ... (13 Replies)
Discussion started by: brialt1
13 Replies

6. Solaris

How to find half duplex or full duplex

Hi, How to find whether the server is running with half duplex or full duplex. I tried with the following command ndd -get /dev/ but am not getting any output,. Is the command correct? Also let me know how to change from half to full duplex. (1 Reply)
Discussion started by: rogerben
1 Replies

7. AIX

How to change Speed Duplex

How to change Speed Duplex ! How to change Speed Duplex by command chdev -P -l ent1 -a media_speed=1000_Full_Duplex How to change Speed Duplex by Smitty . smitty chgenet -> select adapter -> change Media speed etc. -> set "Apply change to DATABASE only" to yes -> Enter -> ... (0 Replies)
Discussion started by: ITHelper
0 Replies

8. AIX

Connected and Running with half duplex speed

VIO Server connected to switch port and running with half duplex speed on one of the shared ethernet adapter. We have verified at switch end and everythings looks good. Other ethernet adapter in the VIO server are connected and running in Full duplex speed. Please help me find why this shared... (4 Replies)
Discussion started by: mugunthanvh
4 Replies

9. Solaris

Haed code nxge0 nic interface with full duplex & 1000mbps

Hi All I would need to do hard code of nxge0 nic to full duplex & 1000mbps. So that whenever solaris server come up after reboot. it will show full duplex & 1000mbps setting only. Please also let me know how to do it online through command. regards (0 Replies)
Discussion started by: amity
0 Replies
TI(4)							   BSD Kernel Interfaces Manual 						     TI(4)

NAME
ti -- Alteon Networks Tigon I and Tigon II gigabit Ethernet driver SYNOPSIS
ti* at pci? dev ? function ? DESCRIPTION
The ti driver provides support for PCI gigabit Ethernet adapters based on the Alteon Networks Tigon gigabit Ethernet controller chip. The Tigon contains an embedded R4000 CPU, gigabit MAC, dual DMA channels and a PCI interface unit. The Tigon II contains two R4000 CPUs and other refinements. Either chip can be used in either a 32-bit or 64-bit PCI slot. Communication with the chip is achieved via PCI shared memory and bus master DMA. The Tigon I and II support hardware multicast address filtering, VLAN tag extraction and insertion, and jumbo Ethernet frames sizes up to 9000 bytes. Note that the Tigon I chipset is no longer in active production: all new adapters should come equipped with Tigon II chipsets. There are several PCI boards available from both Alteon and other vendors that use the Tigon chipset under OEM contract. The ti driver has been tested with the following Tigon-based adapters: o The Alteon AceNIC V gigabit (1000BASE-SX and 1000BASE-T variants) Ethernet adapter o The 3Com 3c985-SX gigabit Ethernet adapter o The Netgear GA620 gigabit (1000BASE-SX and 1000BASE-T variants) Ethernet adapter o The Digital EtherWORKS 1000SX PCI Gigabit Adapter (DEGPA) The following should also be supported but have not yet been tested: o Silicon Graphics PCI gigabit Ethernet adapter While the Tigon chipset supports 10, 100 and 1000Mbps speeds, support for 10 and 100Mbps speeds is only available on boards with the proper transceivers. Most adapters are only designed to work at 1000Mbps, however the driver should support those NICs that work at lower speeds as well. 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. Using jumbo frames can greatly improve performance for certain tasks, such as file transfers and data streaming. The ti driver supports the following media types: autoselect Enable autoselection of the media type and options. 10baseT/UTP Set 10Mbps operation. The mediaopt option can also be used to select either full-duplex or half-duplex modes. 100baseTX Set 100Mbps (fast Ethernet) operation. The mediaopt option can also be used to select either full-duplex or half-duplex modes. 1000baseSX Set 1000Mbps (gigabit Ethernet over multimode fiber) operation. Only full full-duplex mode is supported at this speed. 1000baseT Set 1000Mbps (gigabit Ethernet over twisted pair) operation. Only full full-duplex mode is supported at this speed. The ti driver supports the following media options: full-duplex Force full duplex operation. half-duplex Force half duplex operation. The Alteon Tigon and Tigon II support IPv4/TCP/UDP checksumming in hardware. The ti supports this feature of the chip's firmware. See ifconfig(8) for information on how to enable this feature. For more information on configuring this device, see ifconfig(8). DIAGNOSTICS
ti%d: can't map memory space A fatal initialization error has occurred. ti%d: couldn't map / establish interrupt A fatal initialization error has occurred. ti%d: jumbo buffer allocation failed The driver failed to allocate memory for jumbo frames during initialization. ti%d: bios thinks we're in a 64 bit slot, but we aren't The BIOS has programmed the NIC as though it had been installed in a 64-bit PCI slot, but in fact the NIC is in a 32-bit slot. This happens as a result of a bug in some BIOSes. This can be worked around on the Tigon II, but on the Tigon I initialization will fail. ti%d: board self-diagnostics failed! The ROMFAIL bit in the CPU state register was set after system startup, indicating that the on-board NIC diagnostics failed. ti%d: unknown hwrev The driver detected a board with an unsupported hardware revision. The ti driver supports revision 4 (Tigon 1) and revision 6 (Tigon 2) chips and has firmware only for those devices. ti%d: watchdog timeout The device has stopped responding to the network, or there is a problem with the network connection (cable). SEE ALSO
netintro(4), pci(4), ifconfig(8) HISTORY
The ti device driver first appeared in NetBSD 1.4.2. AUTHORS
The ti driver was written by Bill Paul <wpaul@ctr.columbia.edu>. BUGS
The driver currently tries to access some on-board memory transparently. This mapping (BUS_SPACE_MAP_LINEAR) fails on systems where the cor- responding PCI memory range is located in "sparse" space only. This driver currently does not work on big-endian systems. BSD
June 2, 2001 BSD
All times are GMT -4. The time now is 07:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy