Talk:Ipw2200 - Revision history

VincentP: /* Radio Switch utility needed */

2008-08-06T22:02:44Z

‎Radio Switch utility needed

Hmh: /* Correct!? path? */ indeed, /usr/lib/hotplug/firmware is broken

2007-02-08T11:36:32Z

‎Correct!? path?: indeed, /usr/lib/hotplug/firmware is broken

Zhenech at 08:19, 8 February 2007

2007-02-08T08:19:49Z

B.Steinbrink: /* Enhanced power saving with set_power 5 */

2006-12-02T01:01:10Z

‎Enhanced power saving with set_power 5

Thinker: /* Enhanced power saving with set_power 5 */

2006-12-01T23:43:27Z

‎Enhanced power saving with set_power 5

B.Steinbrink: Added a question about "iwpriv set_power"

2006-12-01T23:00:31Z

Added a question about "iwpriv set_power"

Gsmenden: Sudden breakage... resolved!

2006-01-31T19:10:36Z

Sudden breakage... resolved!

Gsmenden: ipw2200 problems

2006-01-31T04:45:47Z

ipw2200 problems

Gsmenden: ipw2200 stopped working...

2006-01-31T04:44:39Z

ipw2200 stopped working...

Xoby: /* Reliability problems */

2006-01-19T10:16:56Z

‎Reliability problems

@@ Line 1: / Line 1: @@
 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 ==

← Older revision		Revision as of 11:36, 8 February 2007
Line 79:		Line 79:
	Why /usr/lib/hotplug/firmware is better than /lib/firmware? Hotplug is deprecated, so is /usr/lib/hotplug/firmware.		Why /usr/lib/hotplug/firmware is better than /lib/firmware? Hotplug is deprecated, so is /usr/lib/hotplug/firmware.
	--[[User:Zhenech\|Zhenech]] 09:19, 8 February 2007 (CET)		--[[User:Zhenech\|Zhenech]] 09:19, 8 February 2007 (CET)
		+
		+	I have no idea, as firmware in /usr will be unavailable during early boot if /usr is a separate partition... in fact, I'd say it was a Bad Idea to use /usr/<anything>/firmware in the first place.
		+
		+	I have added /lib/firmware back. Anyone that can actually read and follow instructions, either Intel's or the ones in the rest of the page, won't need that comment, anyway.
		+	--[[User:Hmh\|hmh]] 12:36, 8 February 2007 (CET)

← Older revision		Revision as of 08:19, 8 February 2007
Line 75:		Line 75:

	Yeah, I saw 7 being the same as 3, that's why I tried 5. But with the first bigger download I noticed that my connection speed dropped along with the power consumption. I only got 64kbit/s out of the 1MBit/s the DSL line I'm currently using can shuffle around, switching back to 7 made the speed jump up to about 950kbit/s again. So that regular event kicking in was pretty important it seems ;) --B.Steinbrink 01:55, 2 December 2006 (CET)		Yeah, I saw 7 being the same as 3, that's why I tried 5. But with the first bigger download I noticed that my connection speed dropped along with the power consumption. I only got 64kbit/s out of the 1MBit/s the DSL line I'm currently using can shuffle around, switching back to 7 made the speed jump up to about 950kbit/s again. So that regular event kicking in was pretty important it seems ;) --B.Steinbrink 01:55, 2 December 2006 (CET)
		+
		+	== Correct!? path? ==
		+	Why /usr/lib/hotplug/firmware is better than /lib/firmware? Hotplug is deprecated, so is /usr/lib/hotplug/firmware.
		+	--[[User:Zhenech\|Zhenech]] 09:19, 8 February 2007 (CET)

← Older revision		Revision as of 01:01, 2 December 2006
Line 73:		Line 73:

	Odd. The only difference between 7 (which is the same as 3, BTW), and 5 is the timeouts; on an idle connection, the radio will be turned off most of the time with both of these. And 1.5W is roughly the full difference between radio on and radio off. Maybe you have some regular event kicking in at just the right intervals to make a difference. --[[User:Thinker\|Thinker]] 00:43, 2 December 2006 (CET)		Odd. The only difference between 7 (which is the same as 3, BTW), and 5 is the timeouts; on an idle connection, the radio will be turned off most of the time with both of these. And 1.5W is roughly the full difference between radio on and radio off. Maybe you have some regular event kicking in at just the right intervals to make a difference. --[[User:Thinker\|Thinker]] 00:43, 2 December 2006 (CET)
		+
		+	Yeah, I saw 7 being the same as 3, that's why I tried 5. But with the first bigger download I noticed that my connection speed dropped along with the power consumption. I only got 64kbit/s out of the 1MBit/s the DSL line I'm currently using can shuffle around, switching back to 7 made the speed jump up to about 950kbit/s again. So that regular event kicking in was pretty important it seems ;) --B.Steinbrink 01:55, 2 December 2006 (CET)

← Older revision		Revision as of 23:43, 1 December 2006
Line 70:		Line 70:
	== Enhanced power saving with set_power 5 ==		== Enhanced power saving with set_power 5 ==

−	Using "set_power 5" instead of "set_power 7" reduces power consumption in idle times (i.e. no network traffic) by about 1.5 watts on my T43, which is pretty good if you just want to keep your irc or im client running. Does anyone have a clue why that happens? Are there any drawbacks to this? (23:55, 1 December 2006 (CET))	+	Using "set_power 5" instead of "set_power 7" reduces power consumption in idle times (i.e. no network traffic) by about 1.5 watts on my T43, which is pretty good if you just want to keep your irc or im client running. Does anyone have a clue why that happens? Are there any drawbacks to this? --B.Steinbrink (23:55, 1 December 2006 (CET))
		+
		+	Odd. The only difference between 7 (which is the same as 3, BTW), and 5 is the timeouts; on an idle connection, the radio will be turned off most of the time with both of these. And 1.5W is roughly the full difference between radio on and radio off. Maybe you have some regular event kicking in at just the right intervals to make a difference. --[[User:Thinker\|Thinker]] 00:43, 2 December 2006 (CET)

← Older revision		Revision as of 23:00, 1 December 2006
Line 67:		Line 67:

	[[User:gsmenden\|gsmenden]] 13:55, 30 January 2006 (EST)		[[User:gsmenden\|gsmenden]] 13:55, 30 January 2006 (EST)
		+
		+	== Enhanced power saving with set_power 5 ==
		+
		+	Using "set_power 5" instead of "set_power 7" reduces power consumption in idle times (i.e. no network traffic) by about 1.5 watts on my T43, which is pretty good if you just want to keep your irc or im client running. Does anyone have a clue why that happens? Are there any drawbacks to this? (23:55, 1 December 2006 (CET))

← Older revision		Revision as of 19:10, 31 January 2006
Line 56:		Line 56:

	I'm running 2.6.14.6, but my 2.6.15.1 build also suddenly displays identical behavior... [[User:gsmenden\|gsmenden]] 11:30, 30 January 2006 (EST)		I'm running 2.6.14.6, but my 2.6.15.1 build also suddenly displays identical behavior... [[User:gsmenden\|gsmenden]] 11:30, 30 January 2006 (EST)
		+
		+	--------------
		+	Bizarre. Delving through the ipw2200-devel archives reveals several users having similar non-detection issues due to trouble loading the firmware. In the /etc/hotplug area one person solved a similar issue by removing firmware.agent file, which did not work for me.
		+
		+	I decided to completely remove the hotplug system
		+
		+	: apt-get remove --purge hotplug
		+
		+	followed by re-apt-getting hotplug. Voila, everything works as before. Sometimes Debian sid is as flaky as a baklava - an ill-timed "apt-get upgrade" can effectively destroy your system when running unstable, yet "stable" is far, far too behind the times for me... :(
		+
		+	[[User:gsmenden\|gsmenden]] 13:55, 30 January 2006 (EST)

@@ Line 42: / Line 42: @@
 Have any of you had recent problems while running debian sid with ipw2200-1.0.10 and ieee80211-1.1.9 on a t43p?  All of a sudden since 2d ago my wireless initialization gives the following error report:
-Error for wireless request "Set Encode" (8B2A) :
+    Error for wireless request "Set Encode" (8B2A) :
-    SET failed on device eth1 ; No such device.
+        SET failed on device eth1 ; No such device.
-Error for wireless request "Set ESSID" (8B1A) :
+    Error for wireless request "Set ESSID" (8B1A) :
-    SET failed on device eth1 ; No such device.
+        SET failed on device eth1 ; No such device.
-SIOCSIFADDR: No such device
+    SIOCSIFADDR: No such device
-eth1: ERROR while getting interface flags: No such device
+    eth1: ERROR while getting interface flags: No such device
-SIOCSIFNETMASK: No such device
+    SIOCSIFNETMASK: No such device
-eth1: ERROR while getting interface flags: No such device
+    eth1: ERROR while getting interface flags: No such device
 I can load the modules without complaint, but can not use the device.  I have tried everything obvious to fix it:  reinstalling via module-assistant the ipw2200 and ieee80211 drivers, downgrading to old versions, manually installing from sources without module-assistant, disabling then re-enabling the adapter in the BIOS, etc.  I have the 2.3 and 2.4 version firmware in the appropriate directory.

← Older revision		Revision as of 04:44, 31 January 2006
Line 38:		Line 38:

	And successfully transfered more than 5 Gb without any problem--[[User:Xoby\|Xoby]] 11:16, 19 January 2006 (CET)		And successfully transfered more than 5 Gb without any problem--[[User:Xoby\|Xoby]] 11:16, 19 January 2006 (CET)
		+
		+	== Sudden breakage... ==
		+	Have any of you had recent problems while running debian sid with ipw2200-1.0.10 and ieee80211-1.1.9 on a t43p? All of a sudden since 2d ago my wireless initialization gives the following error report:
		+
		+	Error for wireless request "Set Encode" (8B2A) :
		+	SET failed on device eth1 ; No such device.
		+	Error for wireless request "Set ESSID" (8B1A) :
		+	SET failed on device eth1 ; No such device.
		+	SIOCSIFADDR: No such device
		+	eth1: ERROR while getting interface flags: No such device
		+	SIOCSIFNETMASK: No such device
		+	eth1: ERROR while getting interface flags: No such device
		+
		+	I can load the modules without complaint, but can not use the device. I have tried everything obvious to fix it: reinstalling via module-assistant the ipw2200 and ieee80211 drivers, downgrading to old versions, manually installing from sources without module-assistant, disabling then re-enabling the adapter in the BIOS, etc. I have the 2.3 and 2.4 version firmware in the appropriate directory.
		+
		+	I was ready to dismiss this as a hardware problem, but when I boot up knoppix or suse-live-dvd, the wireless works consistently! ??? Odd that this suddenly break - I can not think of anything that triggered this, but I do "apt-get upgrade" approximately daily.
		+
		+	I'm running 2.6.14.6, but my 2.6.15.1 build also suddenly displays identical behavior... [[User:gsmenden\|gsmenden]] 11:30, 30 January 2006 (EST)

← Older revision		Revision as of 10:16, 19 January 2006
Line 20:		Line 20:
	It's frustrating, because this is so un-"linux-like" to have intermittent unreliability. Usually things work 100% or 0% of the time on my linux system. Note, I have not used the 2.6.15-rc kernel version nor 1.0.8 with WPA yet, this problem might be fixed. Can anybody verify? --[[User:Gsmenden\|Gsmenden]]		It's frustrating, because this is so un-"linux-like" to have intermittent unreliability. Usually things work 100% or 0% of the time on my linux system. Note, I have not used the 2.6.15-rc kernel version nor 1.0.8 with WPA yet, this problem might be fixed. Can anybody verify? --[[User:Gsmenden\|Gsmenden]]
	: Same problem here with a Linksys router and WPA, no problem with other routers ... I'll try the new kernel and ipw2200--[[User:Xoby\|Xoby]] 18:35, 15 January 2006 (CET)		: Same problem here with a Linksys router and WPA, no problem with other routers ... I'll try the new kernel and ipw2200--[[User:Xoby\|Xoby]] 18:35, 15 January 2006 (CET)
		+	:: I've tried and still had problems, I also edited my wpa_supplicant file to:
		+	ctrl_interface=/var/run/wpa_supplicant
		+	ctrl_interface_group=0
		+	eapol_version=1
		+	ap_scan=1
		+	fast_reauth=1
		+	### Associate with any open access point
		+	### Scans/ESSID changes can be done with wpa_cli
		+	network={
		+	ssid="myssid"
		+	psk="mypass"
		+	priority=1
		+	proto=WPA
		+	key_mgmt=WPA-PSK
		+	pairwise=TKIP CCMP
		+	}
		+
		+	And successfully transfered more than 5 Gb without any problem--[[User:Xoby\|Xoby]] 11:16, 19 January 2006 (CET)