Mailinglist Archive: opensuse-bugs (13049 mails)
| < Previous | Next > |
[Bug 469038] iwl3945 causing syslog errors related to LED lights
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Mon, 26 Jan 2009 11:37:44 -0700 (MST)
- Message-id: <20090126183744.52378CC7D4@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=469038
User hschaa@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=469038#c15
Helmut Schaa <hschaa@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|hschaa@xxxxxxxxxx |tambet@xxxxxxxxxx
--- Comment #15 from Helmut Schaa <hschaa@xxxxxxxxxx> 2009-01-26 11:37:43 MST
---
However the logs indicate that the wireless card is not really disassociating
and associating again and again. I assume this is only a bug in NetworkManager
when dealing with hidden networks.
Hence reassigning to Tambet.
Tambet, NM triggers a scan every once in a while. As this scan is a broadcast
scan it will not find the hidden AP and NM thinks the AP is gone. After that
wpa_supplicant also thinks the AP is gone and triggers a ssid scan which finds
the AP again. I'm not sure but maybe something like below might fix this issue.
diff --git a/src/nm-device-wifi.c b/src/nm-device-wifi.c
index 0e8555e..b0c4e75 100644
--- a/src/nm-device-wifi.c
+++ b/src/nm-device-wifi.c
@@ -809,7 +809,7 @@ periodic_update (NMDeviceWifi *self)
NMAccessPoint *new_ap;
guint32 new_rate;
- new_ap = get_active_ap (self, NULL, FALSE);
+ new_ap = get_active_ap (self, NULL, TRUE);
if (new_ap)
nm_device_wifi_update_signal_strength (self, new_ap);
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
User hschaa@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=469038#c15
Helmut Schaa <hschaa@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|hschaa@xxxxxxxxxx |tambet@xxxxxxxxxx
--- Comment #15 from Helmut Schaa <hschaa@xxxxxxxxxx> 2009-01-26 11:37:43 MST
---
However the logs indicate that the wireless card is not really disassociating
and associating again and again. I assume this is only a bug in NetworkManager
when dealing with hidden networks.
Hence reassigning to Tambet.
Tambet, NM triggers a scan every once in a while. As this scan is a broadcast
scan it will not find the hidden AP and NM thinks the AP is gone. After that
wpa_supplicant also thinks the AP is gone and triggers a ssid scan which finds
the AP again. I'm not sure but maybe something like below might fix this issue.
diff --git a/src/nm-device-wifi.c b/src/nm-device-wifi.c
index 0e8555e..b0c4e75 100644
--- a/src/nm-device-wifi.c
+++ b/src/nm-device-wifi.c
@@ -809,7 +809,7 @@ periodic_update (NMDeviceWifi *self)
NMAccessPoint *new_ap;
guint32 new_rate;
- new_ap = get_active_ap (self, NULL, FALSE);
+ new_ap = get_active_ap (self, NULL, TRUE);
if (new_ap)
nm_device_wifi_update_signal_strength (self, new_ap);
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |