From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 02:56:05 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FB3216A41F for ; Thu, 28 Jul 2005 02:56:05 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from maxlor.mine.nu (c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1975443D45 for ; Thu, 28 Jul 2005 02:56:04 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from localhost (localhost [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id C6863330; Thu, 28 Jul 2005 04:56:02 +0200 (CEST) Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (midgard [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 90136-10; Thu, 28 Jul 2005 04:56:00 +0200 (CEST) Received: from dyn134.intranet (dyn134.intranet [10.0.0.134]) by maxlor.mine.nu (Postfix) with ESMTP id BE52265; Thu, 28 Jul 2005 04:56:00 +0200 (CEST) From: Benjamin Lutz To: Quinton Dolan Date: Thu, 28 Jul 2005 04:55:53 +0200 User-Agent: KMail/1.8.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart31182549.9xO3bp73MY"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200507280456.00258.benlutz@datacomm.ch> X-Virus-Scanned: by amavisd-new at maxlor.mine.nu Cc: current@freebsd.org Subject: FreeBSD nve(4) driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jul 2005 02:56:05 -0000 --nextPart31182549.9xO3bp73MY Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, I'd like to report on the nve(4) driver and it's support of my on-board=20 NIC on my MSI K8N Neo2 Mainboard (which is a nForce3 board). Dmesg says: nve0: port 0xb800-0xb807 mem 0xee005000-0xee005fff irq 21 at device 5.0 on pci0 nve0: Ethernet address 00:11:09:65:fc:0d miibus1: on nve0 nve0: Ethernet address: 00:11:09:65:fc:0d =20 in nve.c, you write: > NVIDIA now support the nForce3 AMD64 platform, however I have been > unable to access such a system to verify support. However, the code is > reported to work with little modification when compiled with the AMD64 > version of the NVIDIA Linux library. All that should be necessary to > make the driver work is to link it directly into the kernel, instead of > as a module, and apply the docs/amd64.diff patch in this source > distribution to the NVIDIA Linux driver source. I've not done any patching, but I've simply kldloaded if_nve. This machine= =20 is running: $ uname -mrs FreeBSD 6.0-BETA1 amd64 The NIC is working, I can ping etc. However, when there isn't any network=20 activity, I'm starting to see these messages, with the timeout occurring=20 about every 30 seconds: nve0: device timeout (1) nve0: link state changed to DOWN nve0: link state changed to UP nve0: device timeout (1) nve0: link state changed to DOWN nve0: link state changed to UP nve0: device timeout (2) nve0: link state changed to DOWN nve0: link state changed to UP ... If you'd like me to run tests, I can do that. While I'm here - this mainboard also has a second on-board NIC, which uses= =20 a RealTek 8169S. Comments in the code for the re(4) driver say that the=20 driver takes advantage of the 8169S' RX/TX checksum offloading. It would=20 appear that despite the name, that chip isn't so bad. How does the MCP7=20 in combination with nve(4) compare? Which of the two chips do you=20 recommend I use under FreeBSD? Cheers Benjamin --nextPart31182549.9xO3bp73MY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBC6ElAgShs4qbRdeQRAicKAJ9Fpycy5ks2m1B4fiMD6avQdc9tOgCgg5+H KUO2ntKX42ecO+LUu7iGEdY= =bhlW -----END PGP SIGNATURE----- --nextPart31182549.9xO3bp73MY--