Using: Easuter - How to Configure Your Wireless NetworkI will go through this step by step until I hit an error of some type, and then post it here, stop until reasonable solution.

Identifying card works with Linux. Yes; on list. Has Atheros chipset. Uses ath-pci interface from madwifi. Card reported in several sources, including VL forums, as working with Linux. Other card tried (Belkin) with same interface was not reported anywhere as working, and did not work in procedures as below.

lspci (not going to include all output):...02:00.0 Ethernet controller: Atheros Communications, Inc. 802.11abg NIC (rev 01)NOTE: no ID number in form xxxx:xxxx

VASM finds native module. Configures "alias eth0 ath_pci," which is not preference. Should be ath0. Not stopping at this error. Corrected. Continuing.

Had previously compiled madwifi following instructions from developer. According to developer compile and install worked correctly.

Router has no WEP or any encryption. Is open. Mac address filtering is off for next command. Router uses 192.168.2.x addresses which is set in firewall config file:PERMIT="192.168.2.0/24 445/tcp 137-139/tcp 445/udp 137-139/udp"

Last communication with madwifi developer, he said there is no ap associated, and that dhcpcd, or programs like wifi-radar, will not work unless there is an ap associated. He agreed with command "iwconfig ath0 ap any." But he says there is apparently no ap, and that system is communicating with card.

In my experience i've found out that applications like wifi-radar sometimes just refuse to work. I had a similar problem with my broadcom chip. You may want to consider taking a glance at the howto i wrote on the wiki. the procedure should work for you as long as you use the right drivers for your device

OK, that wiki was based on easuter's howto, which I have now followed as religiously as possible four times, and the wiki (not easuter's howto) seemed to be missing some things.

Have tried two paths each to get two different cards working, a Belkin which is not reported anywhere as working with Linux, and a D-Link as above which is reported multiple places including here in VL as working with Linux.

VASM would not configure either. Both a native Linux approach using the madwifi drivers, which turned out to be the same for both cards, ath_pci, and ndiswrapper failed to work with either card. All attempts have ended in the same result:the system recognizes the card, shows correct attributes for itiwlist xxxxxx scan produces "no scan results"dhcpcd does not connect but shows correct MAC address for the cardwifi-radar cannot obtain an IP address from the wireless router

Maybe the problem is not with the card, but with communicating with the router? How do I troubleshoot this? The madwifi developer told me that I do not have an Access Point associated with the interface, and I think I have confirmed that I am unable to do that with either VL or the cards I have tried. It is supposed to be setup to communicate with any Access Point (..... or it won't be portable!). The generic iwconfig for Linux shows options any and auto for iwconfig. In VL 5.8, "iwconfig wlan0 ap any" results in "Access Point:Not Associated""iwconfig ..... auto" results in "Access Point:Not Associated""iwconfig ..... "00:11:50:43:91:CF" .... router WLAN address .... results in "Access Point:Not Associated"

Router is open security, no WPA/WEP, no key. The only security is Mac address filtering, which is off for these tests.

Whatever, the card is not seeing the ap, and something is wrong that it appears that no ap can actually be configured as the last iwconfig command should result in seeing the router's mac address in iwconfig. According to what I am reading in various references for iwconfig, the last command having resulted in "Access Point:Not Associated" represents a problem.

("The little distro that grows on you." This experience reminds me of first dealing with home wireless network with Windows NT, which at least came with drivers, but required much "fiddling" of channels and parameters to get it to work! The "growing" is becoming very annoying!)

Which exact revision is your pcmcia card? Look on the label of the card for the "H/W: ##". It may be A1, B1, B2, B3, B4, B5. If you can't find a "H/W" section then at the end of the serial number look for "V.##"; it may be C0, C1, ...

From the sounds of it, I think you have the "H/W: A1" card but nailing it down exactly will help for the ndiswrapper method.

The H/W Rev is B5. Before using ndiswrapper (as I had previously done for the Belkin card as well 2 weeks ago), I looked the D-Link card up in ndiswrapper, and used the drivers from the CD which came with the card after checking to make sure they were up-to-date with those listed on the D-Link site. The drivers also corresponded to those on ndiswrapper site for the specific hardware revision.

The first card I tried, the Belkin, was just one I had laying around from another laptop .... but it did work in the Thinkpad 600E prior to installing VL. The second card I bought specifically because it was alleged to work "out of the box" with VL, and also found several references here and in other Linux forums that it worked with Linux, which was not true for the Belkin card.

Download and unzip the archive. You should find a 'Drivers' directory containing the required drivers; you should be fine to delete 'ar52119x.sys' since it's for win9x systems and you want the driver for winxp/nt systems.

Your pciid should be: 168c:0013 - this should be confirmed once you load the driver in ndiswrapper

If you don't have the latest ndiswrapper package from the repo then get it now, install it, and reboot (I think it's version 1.9).

Start by making sure that the hal daemon/service is stopped; in fact, if it's set to start with the system then please disable this service during this testing period.

Next, list the ndiswrapper drivers that are installed (as root, ndiswrapper -l). My natural expectation would be that this would list none (maybe some) drivers that you had tried in the past, however on my system it lists several that are installed by default which was not my expectation. At least you can see which drivers are already installed this way. Did the listing show many drivers?

Next, remove some ndiswrapper modules that may be loaded by default (as root, ndiswrapper -r <modulename>). Make sure that 'airplus', 'gplus', and 'netdlwl' are removed to help make sure there's not a conflict with a preloaded module trying to controlling your hardware. Were any of these listed as 'driver installed'? Just to ensure they're not installed anymore, re-list your ndiswrapper modules.

Next, clean up your /etc/modprobe.conf and /etc/ifplugd/ifplugd.conf files. Remove the alias for ath0/wlan0 from the former, and remove the atho/wlan0 interface name from the latter. This should leave your modprobe.conf file with a single alias entry for eth0, and it should leave your ifplugd.conf file with a single interface device name (eth0).

Now, list your ndiswrapper drivers again. You should see something to the effect of:net5211 : driver installeddevice (168c:0013) presentwithin the driver listing. Do you see this?

Next, have ndiswrapper insert the alias info for you (as root, ndiswrapper -m); use the standard 'wlan0' interface name for this test (not ath0). IIRC, this command exits with what seems to be an error statement; not a big deal. Open your /etc/modprobe.conf and /etc/ifplugd/ifplugd.conf files and make sure the correct information has been inserted for you; alias wlan0 ndiswrapper and INTERFACES="eth0 wlan0", respectively. IIRC, modprobe.conf looks good but you have to manually add the interface name to ifplugd.

Next, you need to restart the ifplugd server by issuing service ifplugd restart, or better yet just reboot.

If you're good up to this point then run depmod -aq as root, and wait a minute or so.

If you're good up to this point and you have not received any glaring errors/problems up to this point then you should insert the ndiswrapper module as root (modprobe ndiswrapper).

If you don't get any errors up to this point then you should have the drivers loaded for your wireless card and it should (theorhetically) function once it's connected to a network.

I know you've stated that you are supposed to use 'ath0'. If this test did not work correctly using wlan0 then start from scratch and substitute ath0 as the alias/interface name throughout - really, start from scratch (i.e. clean up the modprobe/ifplugd files, remove modules, etc.).

If it seems like you're good up to this point then go straight to wifi-radar. Delete any old profiles and start a new one; ssid name, managed network, auto channel, dhcp enabled, etc... Then try connecting to the newly created profile; give it a couple minutes to make a good attempt. If it doesn't seem to connect (indicated by iwconfig/ifconfig or your wifi card icon with green bars) then click disconnect - be sure to pay attention to see if the connection is made upon clicking 'disconnect'. If it does seem to connect on disconnect, then immediately click connect again and give it a few seconds to "level out". I only mention this odd behavious because my laptop (native driver) has this strangness, but my desktop (ndiswrapper driver) does not. The alternative to wifi-radar is to do it manually as you've been attempting on your previous attempts. I would certainly try wifi-radar first, and if you don't have success then try the manual method

I know this is all TOO familiar from all your other attempts but sometimes just having things listed differently helps.