From owner-freebsd-questions Wed Sep 1 13:49:59 1999 Delivered-To: freebsd-questions@freebsd.org Received: from uncle.cult.cu (uncle.cult.cu [169.158.120.12]) by hub.freebsd.org (Postfix) with ESMTP id 5C83315AE5 for ; Wed, 1 Sep 1999 13:49:44 -0700 (PDT) (envelope-from elie@uncle.cult.cu) Received: from localhost (1502 bytes) by uncle.cult.cu via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Wed, 1 Sep 1999 16:49:00 -0400 (CDT) (Smail-3.2.0.101 1997-Dec-17 #4 built 1998-Sep-15) Date: Wed, 1 Sep 1999 16:49:00 -0400 (CDT) From: Eliezer Rodriguez Gonzalez To: questions@freebsd.org Subject: Full-duplex on a NIC Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everyone: I have a FreeBSD box, v 3.2-STABLE. I also have a ALN 315C NIC, from Acer, sporting a DEC 21143 Ethernet Chip, this is a 10/100 Mbits card. The problems is that on boot up, while the system is recognizing the existence of all the hardware support built into the GENERIC kernel it first negotiates 10 MBits/s instead of 100 MBits/s. This card is hook to a 10/100 MBits/s autosensing switch hub. I have to pass the necessary flags to ifconfig via /etc/rc.conf to turn it to Fast Ethernet, besides it is unnable to run full-duplex. Question number one is: Why it doesn't hook the the switch at Fast Ethernet speed from the first time, I mean, before /etc/rc gets running. Is it a problem of the autonegotiation feature of the card or the kernel. Why it doesn't use its full-duplex capabilities although I "tell" it to do so. I mean, the switch doesn't show the card is in full-duplex mode although I said mediaopt full-duplex to the ifconfig flags. Any help or explanation will be very welcome. ______________________________ Mr. Eliezer Rodriguez Gonzalez Net Manager & Sys Admin CEISIC. Ministry of Culture ______________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message