[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: problems with deXlan (Intersil) wifi pcmcia card



Paolo wrote:

On Wed, Nov 05, 2008 at 01:11:19AM +0000, bd wrote:
...
orinoco_cs             15844  0
orinoco                36084  1 orinoco_cs
hermes                  7008  2 orinoco_cs,orinoco
hostap_cs              53652  3
hostap                 96580  1 hostap_cs
ieee80211_crypt         5952  1 hostap
...
hostap_cs: Registered netdevice wifi0
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.0
wifi0: STA: id=0x1f v1.4.9
wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
wifi0: registered netdevice wlan0
prism2: wlan0: operating mode changed 3 -> 2
wifi0: dropped unencrypted TX data frame (drop_unencrypted=1)
wifi0: dropped unencrypted TX data frame (drop_unencrypted=1)
***above two lines repeated eleven times ! ***
wlan0: Preferred AP (SIOCSIWAP) is used only in Managed mode when host_roaming is enabled

so hostap is taking the hardware; I guess you just want to connect to your
AP, ie act as client, so remove/don't load hostap*.

Very difficult to remove or don't load hostap. 'rmmod' says that 'hostap' being in use, I can't remove it, same for hostap_cs. There is a warning about using the --force option, which says that it may be very dangerous to force remove a module in use. I then searched for a modprobe.conf file, only to find '/etc/discover-modprobe.conf'. In this file, I added the following line :

skip="hostap hostap_cs"

I then rebooted. After reboot, the hostap modules did not appear in 'lsmod' output, but then it did not take long for me to realize that this module did not load at boot time, whether the skip line was there or not. The hostap modules load right after you have introduced the pcmcia wifi card in its slot. So, I don't really know how to get away with the hostap module, unless I perform a 'apt-get remove hostap' but then it might lead me into unexpected problems. In any case, in my /etc/network/interfaces file, I have tried replacing

wpa-driver wext

by wpa-driver orinoco

and then by

wpa-driver hostap

with no difference whatsoever as far as end results were concerned.

By the way, some more details of what exactly happen, with the interfaces file as follow:

auto lo
iface lo inet loopback
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid Livebox-46db
wpa-psk 7799........

#/etc/init.d/networking restart
Reconfiguring network interfaces...
wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wlan0/00:02:...
Sending on LPF/wlan0/00:02:...
Sending on Socket/fallback
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - Internet Systems Consortium DHCP Client V3.0.4
wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/wlan0/00:02:...
Sending on LPF/wlan0/00:02:...
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
No DHCPOFFERES received
No working leases in persistent database - sleeping
done.








Reply to: