Date: Sun, 24 Jan 2010 05:51:28 +0100 From: Polytropon <freebsd@edvax.de> To: Programmer In Training <pit@joseph-a-nagy-jr.us> Cc: freebsd-questions@freebsd.org Subject: Re: Finding Drivers For winWiFi Card 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 23 Jan 2010 22:35:32 -0600, Programmer In Training <pit@joseph-a-nagy-jr.us> 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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100124055128.f5e742d3.freebsd>