Sponsored Content
Full Discussion: lan card autonegotiation?
Special Forums Cybersecurity lan card autonegotiation? Post 53519 by RTM on Friday 16th of July 2004 08:59:48 PM
Old 07-16-2004
Real simply, Autonegotiation between two devices is simply the devices 'talking' to each other to find the speed and mode that both can 'talk' at. Just like when modems connect to each other...they go through the 'conversation' of finding out at what speed they can both talk without losing the 'conversation'. If you have one ethernet card that can autonegotiate and another that can't, then the autonegotiation will be pointless since they will run at the speed/mode that the second card is set to. Sometimes, two cards that are suppose to autonegotiate can't...due to problems between vendors.

As far as your second question, that is dependent on what you have....see this article for some help.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

LAN Card Problem !

The Lan card in one of our UIII WS's seem doesn't work,so with ping command i can not see any of the machines in LAN and with some other tests i'm sure it's not OK. I tried to use the second card on PCI port ,but the replaced card was one of the ordinary card for PC's ...by the way after... (1 Reply)
Discussion started by: nikk
1 Replies

2. SCO

LAN card problem

Dear all Im facing one problem in SCO 5.0.5 , its that in the server there are three LAN cards INTEL PRO 100 series but when we configure all the three cards then LAN stops working . self ping is possible but no one can ping the server. If we remove driver of any one card LAN starts working. Is... (1 Reply)
Discussion started by: ccvyas
1 Replies

3. Solaris

Does x86 solaris 9 support PCI RealTek Lan Card

Hi, i have a RealTek Lan Card on my machine. Does Solaris 9 supports this lan card . Thank You, Shafi (3 Replies)
Discussion started by: sol8admin
3 Replies

4. SCO

lan card not detecting

hi all i have installed SCO 5.0.5 on a "Netfinity 5000" IBM server. But the OS is not detecting the lan card. how can i detect it.... help and thanks in advance . bidhayak (3 Replies)
Discussion started by: bidhayakm
3 Replies

5. Programming

LAN card status Information

Please tell me API in Solaris / Linux / UNIX to get status information of LAN card. (1 Reply)
Discussion started by: mansoorulhaq
1 Replies

6. Linux

How to check the LAN card?

Hi. I have a lan card installed on my server. I want to check the duplex speed of it. How can I check it? Help is appreciated. Thank you. (3 Replies)
Discussion started by: Amol21
3 Replies

7. Solaris

Timed out waiting for Autonegotiation to complete

Received the Timed out message consistently when I tried to jumpstart an M5000 with: boot jsnet:speed=1000,duplex=full - install Made the error go away by adding link-clock parameter: boot jsnet:speed=1000,duplex=full,link-clock=master - install "link-clock=master" disables... (1 Reply)
Discussion started by: markoakley
1 Replies

8. Solaris

Can't ping new PCI LAN card x4270_m2

Hi, I've recently moved my pci LAN card from Slot2 Slot5 on my sun x4270_m2 server (solaris 10). I've done the touch / reconfigure and devfsadm, however my issue is that im able to configure the e1000g7 port with an ip address (192.168.0.1) but if i plug my laptop (set with static ip... (7 Replies)
Discussion started by: kerrygold
7 Replies

9. Linux

Lan card not reaching Gateway

Hi, I have this problem on RHEL box. I am using two NIC's of same model and make (Intel 82557) in the adjacent PCI slots . I am using each one for different subnet and have assigned them ipaddresses and gateways of respective subnets . While one is O.K. connecting to its ... (5 Replies)
Discussion started by: dextergenious
5 Replies

10. Red Hat

PC cannot reach two lan card Linux box

we have red hat 6 linux box There are two lan card one lan card eth0 have ip 10.82.190.31/24 GW 10.82.190.254 2th lan card eth1 have ip 10.82.188.33/24 GW 10.82.188.254 I have below route ... I use two route table root@xxx# netstat -rn Kernel IP routing table Destination Gateway ... (5 Replies)
Discussion started by: chuikingman
5 Replies
HCIATTACH(8)						    Linux System Administration 					      HCIATTACH(8)

NAME
hciattach - attach serial devices via UART HCI to BlueZ stack SYNOPSIS
hciattach [-b] [-n] [-p] [-t timeout] [-s speed] [-l] [-r] tty type|id speed flow bdaddr DESCRIPTION
Hciattach is used to attach a serial UART to the Bluetooth stack as HCI transport interface. OPTIONS
-b Send break. -n Don't detach from controlling terminal. -p Print the PID when detaching. -t timeout Specify an initialization timeout. (Default is 5 seconds.) -s speed Specify an initial speed instead of the hardware default. -l List all available configurations. -r Set the HCI device into raw mode (the kernel and bluetoothd will ignore it). tty This specifies the serial device to attach. A leading /dev can be omitted. Examples: /dev/ttyS1 ttyS2 type|id The type or id of the Bluetooth device that is to be attached, i.e. vendor or other device specific identifier. Currently supported types are type description any Unspecified HCI_UART interface, no vendor specific options ericsson Ericsson based modules digi Digianswer based cards xircom Xircom PCMCIA cards: Credit Card Adapter and Real Port Adapter csr CSR Casira serial adapter or BrainBoxes serial dongle (BL642) bboxes BrainBoxes PCMCIA card (BL620) swave Silicon Wave kits bcsp Serial adapters using CSR chips with BCSP serial protocol ath3k Atheros AR300x based serial Bluetooth device intel Intel Bluetooth device Supported IDs are (manufacturer id, product id) 0x0105, 0x080a Xircom PCMCIA cards: Credit Card Adapter and Real Port Adapter 0x0160, 0x0002 BrainBoxes PCMCIA card (BL620) speed The speed specifies the UART speed to use. Baudrates higher than 115.200bps require vendor specific initializations that are not implemented for all types of devices. In general the following speeds are supported: 9600, 19200, 38400, 57600, 115200, 230400, 460800, 921600 Supported vendor devices are automatically initialised to their respective best settings. flow If the keyword flow is appended to the list of options then hardware flow control is forced on the serial link ( CRTSCTS ). All above mentioned device types have flow set by default. To force no flow control use noflow instead. sleep Enables hardware specific power management feature. If sleep is appended to the list of options then this feature is enabled. To disable this feature use nosleep instead. All above mentioned device types have nosleep set by default. Note: This option will only be valid for hardware which support hardware specific power management enable option from host. bdaddr The bdaddr specifies the Bluetooth Address to use. Some devices (like the STLC2500) do not store the Bluetooth address in hardware memory. Instead it must be uploaded during the initialization process. If this argument is specified, then the address will be used to initialize the device. Otherwise, a default address will be used. AUTHORS
Written by Maxim Krasnyansky <maxk@qualcomm.com> Manual page by Nils Faerber <nils@kernelconcepts.de> BlueZ Jan 22 2002 HCIATTACH(8)
All times are GMT -4. The time now is 04:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy