> I have FC5 on a vanilla Athlon 64 CPU. I also have a Netgear WPN311 > NIC. I've never used madwifi, so I can't describe how it works. For what it's worth, if nothing else helps you, perhaps this will. I generally do the following: 1. First try to use system-config-network to configure a new network interface. If the card is plugged in, and there is a native driver available, this should find it and let you set up a network connection. In the past, I've had success with Netgear cards, so you might be able to work with what is provided out-of-the-box. 2. If there's no native driver, then the next step is up to you. You can try to find a vendor-supplied driver for Linux or use ndiswrapper. I've gone the ndiswrapper route for cards that don't have native drivers and I've had good success. To use ndiswrapper, you need to have a native Windows driver for your wireless card, which is not usually hard to come by. You also need a working network connection so that you can access the ndiswrapper Wiki for installation instructions. The general process for ndiswrapper goes like this: You obtain the ndiswrapper source and install the wireless-tools package while you're at it. On your friendly, neighborhood Windows machine, yank the Windows driver files off your card's install CD (or you can obtain the driver files by hunting on the ndiswrapper project site or elsewhere. You build ndiswrapper from source. You'll need the kernel-devel package to get necessary kernel headers. Once this is done, you install the built code as root (make install). >From there, it's a matter of installing your Windows driver per the ndiswrapper instructions on the Wiki, and configuring the card. A quick search of the Madwifi site seems to uncover a lot of useful info for the newcomer, too. Erik > > Thanks > Chris Jones