From owner-freebsd-questions@FreeBSD.ORG Sun Jan 24 04:51:31 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE3A21065670 for ; Sun, 24 Jan 2010 04:51:31 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id 6C4C78FC13 for ; Sun, 24 Jan 2010 04:51:31 +0000 (UTC) Received: from r55.edvax.de (port-92-195-164-220.dynamic.qsc.de [92.195.164.220]) by mx02.qsc.de (Postfix) with ESMTP id 17DF21E226; Sun, 24 Jan 2010 05:51:30 +0100 (CET) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id o0O4pSM6003335; Sun, 24 Jan 2010 05:51:29 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Sun, 24 Jan 2010 05:51:28 +0100 From: Polytropon To: Programmer In Training Message-Id: <20100124055128.f5e742d3.freebsd@edvax.de> In-Reply-To: <4B5BCE14.3040107@joseph-a-nagy-jr.us> References: <4B5BC60A.5040101@joseph-a-nagy-jr.us> <20100124040551.GA12664@orion.hsd1.pa.comcast.net> <20100124040756.GA12755@orion.hsd1.pa.comcast.net> <4B5BCE14.3040107@joseph-a-nagy-jr.us> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Finding Drivers For winWiFi Card X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jan 2010 04:51:31 -0000 On Sat, 23 Jan 2010 22:35:32 -0600, Programmer In Training wrote: > I hope ifconfig will help more then dmesg as I have no way of getting > files (like dmesg.log that I created) off the box (floppy drive isn't > even hooked up, IIRC) and rl0 is my wired NIC, non-internal. The ifconfig program (often used as "ifconfig -a") tells you only about NICs that are already connected to a driver. Most wireless NICs require loading a specific kernel module (which is not in the GENERIC kernel), and therefore it's helpful to know what exact model it is, so you can load the correct driver. There are of course programs that help you with this: "pciconf -lv" and "usbdevs -v" are common tools for this particular tasks. As soon as you can tell what the name of the wireless NIC is, you can check which driver it needs and the load it, e. g. with "kldload if_bge.ko", where "bge" is the name of the driver (remember to check "man bge" to see what it is intended for). As soon as you've loaded it, "dmesg" will show its existance and "ifconfig -a" will print its settings. PS. The plip0 interface is the "printer port Internet Protocol driver". -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...