[driverloader] Unable to associate, using Intel 2200BG
marc at linuxant.com
Mon Jul 19 10:04:37 EDT 2004
It seems that Intel's 2200BG driver has trouble with explicit selection
of APs (causing the driverloader: ndisSetInformation: 802_11_BSSID
st=FAILURE), and there was a compatibility issue with WPA.
To fix the latter, please upgrade to
or a newer release version >= 1.74 if available.
The driverloader: ndisSetInformation: 802_11_BSSID st=FAILURE message
will still occur since it is caused by Intel's driver but the card
should nonetheless work fine with WPA (btw there is now a new
wpa_supplicant available from our web-site).
If you want to experiment without encryption, I would recommend using
"iwconfig eth1 essid <your_essid>" instead of "iwconfig eth1 ap ..." to
choose the access point.
Let us know the results..
On Jun 2, 2004, at 6:26 AM, Byron Darrah wrote:
> driverloader seems to find the device just fine, and defines it as
> However, when trying to set the access point, I get an error, and I
> hope someone can help.
> wpa_supplicant says it's trying to associate with my AP, and prints
> the correct BSSID, SSID, and frequency. Then it outputs:
> ioctl[SIOCSIWAP]: Input/output error
> And this shows up in syslog:
> driverloader: ndisSetInformation: 802_11_BSSID st=FAILURE W=0 N=0
> I also get a similar error when attempting iwconfig eth1 ap <mac
> SET failed on device eth1 ; Input/output error.
> (If I turn off the encryption security at the AP, I still get the
> same error).
> I'm using:
> generic kernel 2.4.25 with wireless extensions enabled.
> WAP: Dell TrueMobile 2300.
> chipset: Intel 2200BG
> driverloader 1.71
> libdnet 1.8
> libpcap 0.8.3
> wireless tools 26
> ndis driver: w22n51.sys for Windows XP
> I really hope this looks familiar to someone.
> driverloader mailing list
> driverloader at lists.linuxant.com
More information about the driverloader