From owner-freebsd-questions@FreeBSD.ORG Fri Sep 15 04:21:27 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E735916A412 for ; Fri, 15 Sep 2006 04:21:27 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B02943D4C for ; Fri, 15 Sep 2006 04:21:27 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.102] (adsl-65-65-209-166.dsl.rcsntx.swbell.net [65.65.209.166]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTP id 5C863114314 for ; Thu, 14 Sep 2006 23:14:44 -0500 (CDT) Date: Thu, 14 Sep 2006 23:21:27 -0500 From: pauls@utdallas.edu To: FreeBSD Questions Message-ID: <3B3CF11BD6874E8B81EC3848@paul-schmehls-powerbook59.local> In-Reply-To: References: X-Mailer: Mulberry/4.0.5 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========AB69B7E64D0777EFC87A==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: unknown ethernet card X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2006 04:21:28 -0000 --==========AB69B7E64D0777EFC87A========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On September 15, 2006 12:55:49 PM +0900 Garrett Cooper=20 wrote: > > Those particular cards should use a generic driver (in this case bc). > The fact that your interfaces are found though seems to point to the > fact that things are not configured properly, network-wise. Are you > sure the network settings you're providing are correct, or that the > actual NICs themselves have a solid link to a switch and are working? After a reboot and solving an id10t problem, it's working fine now. Sorry = I bothered the list. Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========AB69B7E64D0777EFC87A==========--