Difference between revisions of "Talk:Ipw2200"

From ThinkWiki
Jump to: navigation, search
Line 7: Line 7:
 
WiFi adapter must be turned on before using. In Windows software utility is executed by Fn+F5 keys. This utility turns WiFi and/or Bluetooth adpters on/off. In Linux Fn+F5 controls only Bluetooth adapter.
 
WiFi adapter must be turned on before using. In Windows software utility is executed by Fn+F5 keys. This utility turns WiFi and/or Bluetooth adpters on/off. In Linux Fn+F5 controls only Bluetooth adapter.
 
Unfortunately I can not find switch utility yet (10 Sep 2005).
 
Unfortunately I can not find switch utility yet (10 Sep 2005).
 +
 +
----
 +
 +
Try using the usual hotkey hooks to activate the power management features described in the article.
 +
--[[User:Thinker|Thinker]] 04:37, 18 Nov 2005 (CET)
 +
----
 +
 +
== Reliability problems ==
 +
 +
On a T43p ipw2200 v1.0.6 works well 95% of the time with WPA using wpa_supplicant.  However it seemingly randomly causes trouble and refuses to connect (it is not the router, as non-linux devices work.)  It always recovers with a killall wpa_supplicant, unloading the ipw2200 and ieee80211 modules, and reloading everything (you can even write a "netreset" script to do this for you automatically...) --[[User:Gsmenden|Gsmenden]]

Revision as of 05:37, 18 November 2005

The ipw2000 drivers loads clean on my t42 and the interface eth1 is accessible. However, the wireless-lan LED does not light and i cant connect. Havent figured out what this is.

Radio Switch utility needed

I have the same problem. WiFi adapter must be turned on before using. In Windows software utility is executed by Fn+F5 keys. This utility turns WiFi and/or Bluetooth adpters on/off. In Linux Fn+F5 controls only Bluetooth adapter. Unfortunately I can not find switch utility yet (10 Sep 2005).


Try using the usual hotkey hooks to activate the power management features described in the article. --Thinker 04:37, 18 Nov 2005 (CET)


Reliability problems

On a T43p ipw2200 v1.0.6 works well 95% of the time with WPA using wpa_supplicant. However it seemingly randomly causes trouble and refuses to connect (it is not the router, as non-linux devices work.) It always recovers with a killall wpa_supplicant, unloading the ipw2200 and ieee80211 modules, and reloading everything (you can even write a "netreset" script to do this for you automatically...) --Gsmenden