From owner-freebsd-questions@FreeBSD.ORG Tue Jul 3 02:44:29 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AB27E16A400 for ; Tue, 3 Jul 2007 02:44:29 +0000 (UTC) (envelope-from uthoffp@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.freebsd.org (Postfix) with ESMTP id 610BC13C447 for ; Tue, 3 Jul 2007 02:44:29 +0000 (UTC) (envelope-from uthoffp@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so3421656pyb for ; Mon, 02 Jul 2007 19:44:28 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=RXdC+nzQMjeXnfdo3brOshdPzyOAsqi63zd/s1Wm52yTeJVh1KSIIQFyF/vaB6XQCt1pdYWnGAZZ/xr1db3IKiCYNNzFgvsbwbsJmvPfA921LohW1sqqJhIocdJMUbsBTBmMB4e5yFBOAw8WMhsU+yNWs6dnEpQwv9OiyngJRLA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Y9un3fN+3q2ycWc9a3GBqMeBsczt82OOKyUUTtue4krJlbklewAsHZFEUiqNNuOOjFdwujrkXdT4UL9EzoMsmFN+7PiiLm2jth0Wt24ps4tgKAAtFZvOWgLSjHHOAGI6rTqzxiUY0unGAk1j47LtAimC/ve6UYObX5rkg6rb+/k= Received: by 10.65.224.11 with SMTP id b11mr8095281qbr.1183430668293; Mon, 02 Jul 2007 19:44:28 -0700 (PDT) Received: by 10.64.204.8 with HTTP; Mon, 2 Jul 2007 19:44:28 -0700 (PDT) Message-ID: <7a49f37b0707021944j28146fboaeb31c4b0d349211@mail.gmail.com> Date: Mon, 2 Jul 2007 21:44:28 -0500 From: PU To: freebsd-questions@freebsd.org In-Reply-To: <20070703114048.637b0018@localhost> MIME-Version: 1.0 References: <7a49f37b0707021436p4e52e2e8mc165307ba610b5c7@mail.gmail.com> <46897B2F.1040700@tundraware.com> <20070703114048.637b0018@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Problem with a NIC in FBSD 6.2 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: Tue, 03 Jul 2007 02:44:29 -0000 Thank you all, for your replies. After messing around and trying a few things (including messing with the BIOS settings by disabling serial and parallel ports as well as manually setting IRQs), I ended up taking out one of the Netgear cards and putting in an old 3com 3c905 that I had sitting around. Once I did that, I was able to install with no problem and all the cards are recognized with no conflicts. And, to answer Iams question: It's for a firewall. :) Thanks much, Peter On 7/2/07, Norberto Meijome wrote: > > On Mon, 02 Jul 2007 17:24:47 -0500 > Tim Daneliuk wrote: > > > PU wrote: > > > Hello, > > > > > > I have a bit of a problem I'm hoping someone here can help with. I > built a > > > 6.2 FBSD box and wound up with a bad NIC out of 3 and what I thought > might > > > have been a bad pci slot. I replaced the NIC with a new one, and moved > the > > > card to another slot just to make sure I took care of the problem. > > > However, now when I boot up, my rl0 interface is recognized, but isn't > > > 'initialized'. What I mean by that is that I see entries in dmesg, but > an > > > ifconfig does not show that interface. I can't even plumb the thing as > the > > > OS says it doesn't exist. What really throws me is that the other two > NICs > > > and a video card that were also moved are recognized with no problems > at > > > all. Problems just seem to follow the rl0 interface. > > > > [....] > > b) All NICs work in some slots but fail on others. This would hint > > to one of two possibilities: A bad PCI slot or a motherboard > > that does strange and perverse things by hardwiring certain > > interrupts to certain slot positions (yes, I've seen this and > > it's maddening). Remedy: Run over the motherboard with a large > > tank. > > Before heading to your local military surplus shop for a second hand tank, > you > may want to have a play with the PCI IRQ settings in your motherboard : > - Change them from auto to one different IRQ to each slot. > > - DISABLE devices you dont need. Do you need 2 COM ports + LPT + who knows > what > else? This is usually the problem - you're NIC, in a certain pci slot, > conflicts with other devices. > > In most motherboards, the IRQ assignment is shown just after POST and just > before the OS boots (best way to see it is to remove all bootable devices > so > it's stuck after POST). You *really* want to have individual IRQs for each > NIC.\ > > I've had this problem with some ASUS motherboards, Award bios + 3+ fxp > cards. > > [....] > _________________________ > {Beto|Norberto|Numard} Meijome > > Law of Conservation of Perversity: > we can't make something simpler without making something else more > complex > > I speak for myself, not my employer. Contents may be hot. Slippery when > wet. > Reading disclaimers makes you go blind. Writing them is worse. You have > been > Warned. >