From owner-freebsd-stable@FreeBSD.ORG Thu Feb 5 01:08:29 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99D3C106564A for ; Thu, 5 Feb 2009 01:08:29 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id 4F4FE8FC13 for ; Thu, 5 Feb 2009 01:08:28 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1165382ywe.13 for ; Wed, 04 Feb 2009 17:08:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=pvTe7X71FWY/JzsPydJTVwCOsnaSgbJYRsMV5CGD7l4=; b=VhKZH0mPjCL/ku4un5P55IWulFcCzS+htfLC/ERLrjxh1T4C/A0k8TWTQuYo2CoU/i gBtQvSCbhBJ9uY1YfIna/Im1jhS+P7/4wTqotcPNk+mD1WJow3rcu9zkKRiRwSBeOLj4 oK5YjkWTO7bX3pzVgNn4Elvg3zhm036ion7ZY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Wie7zeVKagXNoAGhkabcaWL01Q7yhdP1FvQ9PkE2rA4kiyAsUpW+vs5MaHZu9nUt20 U5j4mUmjxJJGEB9X3uWpuqpuIlHSeJMORHFVhCMUoTay27SEOd9ShI8QcefJUXnTEy4Z WZKDaY22vfvvZZz1KejFFcqHLe0BjK0vA+d6M= Received: by 10.151.110.14 with SMTP id n14mr15748ybm.20.1233796108475; Wed, 04 Feb 2009 17:08:28 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id j37sm14068359rne.8.2009.02.04.17.08.24 (version=SSLv3 cipher=RC4-MD5); Wed, 04 Feb 2009 17:08:25 -0800 (PST) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Thu, 5 Feb 2009 10:09:30 +0900 From: Pyun YongHyeon Date: Thu, 5 Feb 2009 10:09:30 +0900 To: Freddie Cash Message-ID: <20090205010930.GB77461@michelle.cdnetworks.co.kr> References: <200706080913.37450.fjwcash+freebsd@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706080913.37450.fjwcash+freebsd@gmail.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Can't get if_txp(4) to attach to a 3CR990B-TXM NIC X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2009 01:08:29 -0000 On Fri, Jun 08, 2007 at 09:13:37AM -0700, Freddie Cash wrote: > Good morning, > > I'm having a bit of an issue getting a 3CR990B-TXM NIC detected and > usable. Just wondering if anyone knows of any issues with this NIC > chipset and/or with the motherboard chipset. > > The motherboard is a Biostar GeForce 6100 AM2 using an nVidia nForce 410 > chipset and nVidia GeForce 6100 vide chipset. > > I've tried FreeBSD 6.1, 6.2, 6-STABLE (from Wed), and 7-CURRENT (from Thu) > on this system. Everything installs nicely, everything on the board is > detected correctly and usable. It's just the PCI NIC that doesn't work. > > If I compile a custom kernel without any network drivers in it, and then > kldload if_txp, the following appears (same message on all 4 versions): > > txp0: <3Com 3cR990B-TXM Etherlink with 3XP Processor> port 0xbc00-0xbc7f > mem 0xfdcff000-0xfdcff07f irq 16 at device 8.0 on pci3 > txp0: not waiting for boot > device_attach: txp0 attach returned -1 > > If I reboot and load if_nve (on 6.2 and 6-stable), then I get: > nve0: port 0xdc00-0xdc07 mem > 0xfe02d000-0xfe02dfff irq 22 at device 20.0 on pci0 > nve0: Ethernet address 00:19:21:37:d5:60 > > Followed by the above messages for txp0 (it seems to detect and load > if_txp automativally when loading if_nve). > > I've updated the BIOS on the motherboard. I've tried different PCI slots > on the motherboard. Nothing changes. The "not waiting for boot" message > keeps appearing. > > Attached are dmesg output from: > 6.1-RELEASE GENERIC kernel dmesg_6.1.txt > 6.2-RELEASE GENERIC kernel dmesg_6.2.txt > 6.2-RELEASE GENERIC kernel verbose boot dmesg_6.2_verbose.txt > 6-STABLE GENERIC kernel dmesg_6_generic.txt > 6-STABLE TEST kernel (no NIC drivers) dmesg_6_custom.txt > 7-CURRENT GENERIC kernel dmesg_7_generic.txt > 7-CURRENT TEST kernel (no NIC drivers) dmesg_7_custom.txt > > I've looked through the cvsweb entries for txp and didn't see anything > related to this issue. Reading the man page for if_txp(4) doesn't show > anything about this error. I tried reading the source, but C is pretty > much Greek to me. > > Everything I've read online says this NIC should work, and other are using > it successfully. My gut feeling is that it's something to do with the > motherboard chipset and the way it detects the NIC. But I could be way > off. > > (As a test, I popped in a Kanotix LiveCD and the 3Com NIC is detected and > usable, so it's [hopefully] not a defective NIC.) > > Anyone have any suggestions? Comments? Methods to destroy the NIC as an > act of defiance? :) > Now I've encountered similar issue. See http://lists.freebsd.org/pipermail/freebsd-current/2009-February/003033.html for possible fix.