[Bug 269747] New: NetworkManager slow to start Wifi
https://bugzilla.novell.com/show_bug.cgi?id=269747 Summary: NetworkManager slow to start Wifi Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: o.wise.1@bigpond.com QAContact: qa@suse.de I am running SUSE10.2 on a Dell laptop (Inspirion 8200) with a Belkin wireless card. Networking works fine .... once it gets going (bit like me in the morning). If I use ifup the card starts OK during boot. If I use the Networkmanager tool the card takes a long time to start up and get an IP address. Networkmanager also tries stating the built in wired eth0 connection even though there is no cable connected (does not appear to support sensing cable connection). Setting the wired connection to manual does not change behaviour. Looking at networkmanager log there is a message about request_and_convert_scan_results(): card took too much time scanning. Get a better one." It appears that networkmanager may not be waiting long enough for this card to pickup a signal? log output from var/log/networkmanager follows: Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.034292] nm_system_device_get_system_config(): found config '/etc/sysconfig/network/ifcfg-wlan-id-00:30:bd:d2:6a:61' for interface 'eth1' Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186370] nm_system_device_get_system_config(): BOOTPROTO=dhcp Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186677] nm_system_device_get_system_config(): Adding 'WLAN' to the list of trusted networks Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186747] nm_system_device_get_system_config(): ------ Config (eth1) Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186782] nm_system_device_get_system_config(): dhcp=1 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186854] nm_system_device_get_system_config(): addr=0.0.0.0 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186886] nm_system_device_get_system_config(): gw=0.0.0.0 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186915] nm_system_device_get_system_config(): mask=0.0.0.0 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.186950] nm_system_device_get_system_config(): --------------------- Apr 27 19:07:53 laptop NetworkManager: <info> eth1: Device is fully-supported using driver 'atmel_cs'. Apr 27 19:07:53 laptop NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start Apr 27 19:07:53 laptop NetworkManager: <info> nm_device_init(): device's worker thread started, continuing. Apr 27 19:07:53 laptop NetworkManager: <info> Now managing wireless (802.11) device 'eth1'. Apr 27 19:07:53 laptop NetworkManager: <info> Deactivating device eth1. Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.466229] nm_system_device_get_system_config(): found config '/etc/sysconfig/network/ifcfg-eth-id-00:0b:db:16:6a:1b' for interface 'eth0' Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.466543] nm_system_device_get_system_config(): BOOTPROTO=dhcp Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.466664] nm_system_device_get_system_config(): ------ Config (eth0) Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.466762] nm_system_device_get_system_config(): dhcp=1 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.466856] nm_system_device_get_system_config(): addr=0.0.0.0 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.466948] nm_system_device_get_system_config(): gw=0.0.0.0 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.467039] nm_system_device_get_system_config(): mask=0.0.0.0 Apr 27 19:07:53 laptop NetworkManager: <debug> [1177664873.467127] nm_system_device_get_system_config(): --------------------- Apr 27 19:07:53 laptop NetworkManager: <info> eth0: Device is fully-supported using driver '3c59x'. Apr 27 19:07:53 laptop NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start Apr 27 19:07:53 laptop NetworkManager: <info> nm_device_init(): device's worker thread started, continuing. Apr 27 19:07:53 laptop NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'. Apr 27 19:07:53 laptop NetworkManager: <info> Deactivating device eth0. Apr 27 19:07:53 laptop NetworkManager: <info> Will activate wired connection 'eth0' because it now has a link. Apr 27 19:07:53 laptop NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'. Apr 27 19:07:53 laptop NetworkManager: <info> Will activate connection 'eth0'. Apr 27 19:07:53 laptop NetworkManager: <info> Device eth0 activation scheduled... Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) started... Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. Apr 27 19:07:53 laptop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Apr 27 19:07:54 laptop NetworkManager: <info> Activation (eth0) Beginning DHCP transaction. Apr 27 19:07:55 laptop NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Apr 27 19:07:55 laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth0 Apr 27 19:07:55 laptop NetworkManager: <info> Old device 'eth0' activating, won't change. Apr 27 19:07:57 laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth0 Apr 27 19:08:03 laptop NetworkManager: <info> Old device 'eth0' activating, won't change. Apr 27 19:08:33 laptop NetworkManager: <info> Old device 'eth0' activating, won't change. Apr 27 19:08:40 laptop NetworkManager: <info> Deactivating device eth1. Apr 27 19:08:40 laptop NetworkManager: <info> Updating allowed wireless network lists. Apr 27 19:08:40 laptop NetworkManager: <info> Old device 'eth0' activating, won't change. Apr 27 19:08:40 laptop NetworkManager: <info> Device 'eth0' DHCP transaction took too long (>45s), stopping it. Apr 27 19:08:41 laptop NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled... Apr 27 19:08:41 laptop NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface eth0 Apr 27 19:08:41 laptop NetworkManager: <info> DHCP daemon state is now 11 (unknown) for interface eth0 Apr 27 19:08:41 laptop NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface eth0 Apr 27 19:08:41 laptop NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started... Apr 27 19:08:41 laptop NetworkManager: <info> No DHCP reply received. Automatically obtaining IP via Zeroconf. Apr 27 19:08:41 laptop NetworkManager: <info> autoip: Sending probe #0 for IP address 169.254.74.81. Apr 27 19:08:41 laptop NetworkManager: <info> autoip: Waiting for reply... Apr 27 19:08:41 laptop NetworkManager: <info> Old device 'eth0' activating, won't change. Apr 27 19:08:43 laptop NetworkManager: <info> autoip: Sending probe #1 for IP address 169.254.74.81. Apr 27 19:08:43 laptop NetworkManager: <info> autoip: Waiting for reply... Apr 27 19:08:45 laptop NetworkManager: <info> autoip: Sending probe #2 for IP address 169.254.74.81. Apr 27 19:08:45 laptop NetworkManager: <info> autoip: Waiting for reply... Apr 27 19:08:47 laptop NetworkManager: <info> autoip: Sending announce #0 for IP address 169.254.74.81. Apr 27 19:08:47 laptop NetworkManager: <info> autoip: Waiting for reply... Apr 27 19:08:50 laptop NetworkManager: <info> autoip: Sending announce #1 for IP address 169.254.74.81. Apr 27 19:08:50 laptop NetworkManager: <info> autoip: Waiting for reply... Apr 27 19:08:52 laptop NetworkManager: <info> Old device 'eth0' activating, won't change. Apr 27 19:08:53 laptop NetworkManager: <info> autoip: Sending announce #2 for IP address 169.254.74.81. Apr 27 19:08:53 laptop NetworkManager: <info> autoip: Waiting for reply... Apr 27 19:08:56 laptop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Apr 27 19:08:56 laptop NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Timeout) complete. Apr 27 19:08:56 laptop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... Apr 27 19:08:57 laptop NetworkManager: <info> Clearing nscd hosts cache. Apr 27 19:08:57 laptop NetworkManager: <info> Activation (eth0) successful, device activated. Apr 27 19:08:57 laptop NetworkManager: <info> Activation (eth0) Finish handler scheduled. Apr 27 19:08:57 laptop NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. Apr 27 19:09:03 laptop NetworkManager: <debug> [1177664943.028429] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'WLAN' Apr 27 19:09:03 laptop NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/eth1 / WLAN Apr 27 19:09:03 laptop NetworkManager: <info> Deactivating device eth1. Apr 27 19:09:03 laptop NetworkManager: <info> Device eth1 activation scheduled... Apr 27 19:09:03 laptop NetworkManager: <info> Deactivating device eth0. Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) started... Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started... Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting... Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1/wireless): access point 'WLAN' is unencrypted, no key needed. Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD eth1 wext /var/run/wpa_supplicant ' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was 'OK' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was 'OK' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was '0' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 574c414e' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was 'OK' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 scan_ssid 1' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was 'OK' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was 'OK' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0' Apr 27 19:09:03 laptop NetworkManager: <info> SUP: response was 'OK' Apr 27 19:09:03 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete. Apr 27 19:09:04 laptop NetworkManager: <info> Old device 'eth1' activating, won't change. Apr 27 19:09:20 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:27 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:32 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:37 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:41 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:45 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:50 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:50 laptop NetworkManager: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'WLAN'. Apr 27 19:09:50 laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled. Apr 27 19:09:54 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:09:58 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:02 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:07 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:11 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:15 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:20 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:24 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:28 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:33 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:37 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:41 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:46 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:50 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one. Apr 27 19:10:50 laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started... Apr 27 19:10:51 laptop NetworkManager: <info> Activation (eth1) Beginning DHCP transaction. Apr 27 19:10:52 laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete. Apr 27 19:10:52 laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth1 Apr 27 19:10:52 laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth1 Apr 27 19:10:57 laptop NetworkManager: <info> DHCP daemon state is now 2 (bound) for interface eth1 Apr 27 19:10:57 laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled... Apr 27 19:10:57 laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) started... Apr 27 19:10:57 laptop NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon: Apr 27 19:10:57 laptop NetworkManager: <info> address 192.168.2.58 Apr 27 19:10:57 laptop NetworkManager: <info> netmask 255.255.255.0 Apr 27 19:10:57 laptop NetworkManager: <info> broadcast 255.255.255.255 Apr 27 19:10:57 laptop NetworkManager: <info> gateway 192.168.2.1 Apr 27 19:10:57 laptop NetworkManager: <info> nameserver 192.168.2.1 Apr 27 19:10:57 laptop NetworkManager: <info> domain name 'Belkin' Apr 27 19:10:57 laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled... Apr 27 19:10:57 laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) complete. Apr 27 19:10:57 laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started... Apr 27 19:10:58 laptop NetworkManager: <info> Clearing nscd hosts cache. Apr 27 19:10:58 laptop NetworkManager: <info> Activation (eth1) successful, device activated. Apr 27 19:10:58 laptop NetworkManager: <info> Activation (eth1) Finish handler scheduled. Apr 27 19:10:58 laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=269747 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |bnc-team-gnome@forge.provo.novell.com |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=269747 ------- Comment #1 from kibana@gmail.com 2007-06-07 05:49 MST ------- (In reply to comment #0)
I am running SUSE10.2 on a Dell laptop (Inspirion 8200) with a Belkin wireless card. Networking works fine .... once it gets going (bit like me in the morning). If I use ifup the card starts OK during boot. If I use the Networkmanager tool the card takes a long time to start up and get an IP address. Networkmanager also tries stating the built in wired eth0 connection even though there is no cable connected (does not appear to support sensing cable connection). Setting the wired connection to manual does not change behaviour. Looking at networkmanager log there is a message about request_and_convert_scan_results(): card took too much time scanning. Get a better one.
Could you tell me which driver do you use? If you use ndiswrapper, tell me the INF file you use. I have Dell Inspiron 5150 and I get the same error when I use bcmwl5.inf but everything works ok with bcmwl5a.inf. I know it's a work around but let's try that until NetworkManager matures enough. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=269747 ------- Comment #2 from o.wise.1@bigpond.com 2007-06-10 20:37 MST ------- (In reply to comment #1)
(In reply to comment #0)
I am running SUSE10.2 on a Dell laptop (Inspirion 8200) with a Belkin wireless card.
Could you tell me which driver do you use? If you use ndiswrapper, tell me the .INF file you use. I have Dell Inspiron 5150 and I get the same error when I use bcmwl5.inf but everything works ok with bcmwl5a.inf. I know it's a work around but let's try that until NetworkManager matures enough.
Hi - I am using the Atmel driver as detected by YAST under Suse10.2. Extract from the log above "Apr 27 19:07:53 laptop NetworkManager: <info> eth1: Device is fully-supported using driver 'atmel_cs'" Had a problem with Suse10.1 where the firmwear was not installed during OS installation. Worked a treat with networkmanager after install. I have stopped using networkmanager at the moment as it is so slow - traditional method results in network valability as soon as KDE desktop opens. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=269747#c3 --- Comment #3 from David Wise <o.wise.1@bigpond.com> 2007-08-15 15:12:18 MST --- I am travelling interstate next month and wanted the ease of connectivity so had another fiddle with this problem. It appeared that there was a timeout issue as the /var/log/networkmanager contains a lot of the following errors "Aug 14 10:39:21 laptop NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one." I tied again with WEP enabled and after getting past the WEP dialog (tried both passphrase and hex keys) I now get a "hang" at 28%. There is continuous string of the above warning messages. This time the card does not connect at all. Just a long delay then a return to the WEP dialog. Looking for a timeout problem, I found that there is a timeout parameter in etc/sysconfig/network/config - NM_ONLINE_TIMEOUT="0". I have tried changing this using the sysconfig edit tool but there is no way of changing it via the GUI so I edited it manually. There is no guide as to what the interger represents so tried "1" then "5". Restarted the network after each change with no noticeable difference. The config for the card in etc/sysconfig/network/ does not appear to have any parameters for any timeout settings. The traditional ifup works like a charm with the WEP keys /passphrase - just inconvenient on the road. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747#c4 --- Comment #4 from David Wise <o.wise.1@bigpond.com> 2007-08-26 00:13:52 MST --- Hi again, I have had a look through the source code for networkmanager and I suspect that not enough time is being allowed for my particular card to respond. In the get_scan_results section of nm-device-802-11-wireless.c of NM0.40 (the version on this build of SUSE10.2) the folowing snip of code appears to be the generator of the warning messages I am getting during the card startup: if (tries > 20 * SCAN_SLEEP_CENTISECONDS) { nm_warning ("get_scan_results(): card took too much time scanning. Get a better one."); break; } g_usleep (G_USEC_PER_SEC / SCAN_SLEEP_CENTISECONDS); tries++; I note that in the later version of NetworkManager 0.60 that the number of tries is dramatically reduced from 20 to 4. I suspect that version would give me more grief! The code is somewhat different so not sure of the actual effect. Given that if have no experience with C, I am not able to try out my theory and change the time. I just hope that my feedback assist in some way to later versions. Cheers Will live with this for now. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747 JP Rosevear <jpr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-gnome@forge.provo.novell.com |tambet@novell.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=269747#c5 Tambet Ingo <tambet@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #5 from Tambet Ingo <tambet@novell.com> 2008-05-23 07:50:36 MST --- The algorithms for scanning are rewritten in NetworkManager 0.7 (opensuse 11.0), so hopefully this bug is fixed too. If not, please reopen. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747 User korossy.p@freemail.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=269747#c6 Paul Korossy <korossy.p@freemail.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |korossy.p@freemail.hu Resolution|FIXED | --- Comment #6 from Paul Korossy <korossy.p@freemail.hu> 2009-01-18 13:15:54 MST --- This bug is still present for me in OpenSUSE 11.0 and 11.1 I use the iwl3945 driver. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747 User o.wise.1@bigpond.com added comment https://bugzilla.novell.com/show_bug.cgi?id=269747#c7 --- Comment #7 from David Wise <o.wise.1@bigpond.com> 2009-01-18 14:12:57 MST --- I originally posted the bug for SUSE10.2 . I have since changed my wireless card from a belkin card to a Avaya. The belikin requires ndiswrapper and the Avaya uses linux drivers. No problem with the Avaya card. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=269747#c8 Tambet Ingo <tambet@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |korossy.p@freemail.hu --- Comment #8 from Tambet Ingo <tambet@novell.com> 2009-01-19 00:56:17 MST --- Can you please try to explain a bit what exactly is the problem for you? I seriously doubt your problem is the same as the original bug here (the description line here is a bit broad, a bug with "NM doesn't work perfectly" would match all networking bugs), so please describe your bug and attach /var/log/NetworkManager log file here. It contains time stamps, so please let me know the time when you do something that takes too long time. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747 Tambet Ingo <tambet@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747 User korossy.p@freemail.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=269747#c9 --- Comment #9 from Paul Korossy <korossy.p@freemail.hu> 2009-01-21 16:34:25 MST --- Created an attachment (id=266703) --> (https://bugzilla.novell.com/attachment.cgi?id=266703) /var/log/Networkmanager -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747 User korossy.p@freemail.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=269747#c10 Paul Korossy <korossy.p@freemail.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|korossy.p@freemail.hu | --- Comment #10 from Paul Korossy <korossy.p@freemail.hu> 2009-01-21 16:39:47 MST --- You might be right, after scanning my NM logfile I can't find the line 'card took too much time scanning. Get a better one.' in it so my problem might be caused by another thing. I'm really sorry for not being thorough enough, I thought my problem might be the same. I'm only a simple SuSE user and I have neither time nor special knowledge to correctly locate the problem. What I've experienced: In most of the cases NM works well but sometimes it takes about one minute to connect, sometimes I simply cannot connect to my wifi network 'network60' or to other wireless networks using networkmanager. It usually works for a few days/weeks without problems but suddenly it doesn't. Rebooting doesn't help either. Because of this unreliable behavior I try to avoid using NM but it's not an easy thing to live with ifup/ifdown on a notebook. :-) Traditional ifup/ifdown method works like a charm. I've attached /var/log/NetworkManager log file here and I would appreciate if anybody could help to locate the problem. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747 User o.wise.1@bigpond.com added comment https://bugzilla.novell.com/show_bug.cgi?id=269747#c11 --- Comment #11 from David Wise <o.wise.1@bigpond.com> 2009-01-21 23:55:38 MST --- Paul, I had the same problem - see my earlier posts. I changed cards and NM worked fine from then on. You can get secondhand cards pretty cheap and this might save you the frustration. That was on a laptop running the now unsupported 10.2. The machine that I use everyday runs 11.0 with a netgear USB wifi device. Runs perfectly with the rt73usb driver. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=269747#c12 Tambet Ingo <tambet@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |korossy.p@freemail.hu --- Comment #12 from Tambet Ingo <tambet@novell.com> 2009-01-22 01:09:38 MST --- The iwl3945 driver is one of the most used drivers these days, so there's absolutely no point in replacing it. Both NetworkManager and ifup use the same application, wpa_supplicant, to associate with wireless AP. I need to see it's log file with debugging enabled to see why it sometimes fails. Paul, please follow the instructions from http://en.opensuse.org/Tracking_down_wireless_problems to turn on wpa_supplicant debugging and when you get the failure, let us know the exact time when it happened and attach your /var/log/NetworkManager and /var/log/wpa_supplicant.log files here. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747 User korossy.p@freemail.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=269747#c13 Paul Korossy <korossy.p@freemail.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|korossy.p@freemail.hu | --- Comment #13 from Paul Korossy <korossy.p@freemail.hu> 2009-01-24 14:41:49 MST --- After changing Network setup method in Yast from ifup/ifdown to NM I get error message: 'Network service is not running' Than I'm trying to connect to my wifi network using KNetworkmanager (KDE3). content of /var/log/NetworkManager: Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) starting connection 'network60' Jan 24 22:28:00 lpt NetworkManager: <info> (wlan0): device state change: 3 -> 4 Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 24 22:28:00 lpt NetworkManager: <info> (wlan0): device state change: 4 -> 5 Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0/wireless): access point 'network60' has security, but secrets are required. Jan 24 22:28:00 lpt NetworkManager: <info> (wlan0): device state change: 5 -> 6 Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jan 24 22:28:00 lpt NetworkManager: <info> (wlan0): device state change: 6 -> 4 Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 24 22:28:00 lpt NetworkManager: <info> (wlan0): device state change: 4 -> 5 Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0/wireless): connection 'network60' has security, and secrets exist. No new secrets needed. Jan 24 22:28:00 lpt NetworkManager: <info> Config: added 'ssid' value 'network60' Jan 24 22:28:00 lpt NetworkManager: <info> Config: added 'scan_ssid' value '1' Jan 24 22:28:00 lpt NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK' Jan 24 22:28:00 lpt NetworkManager: <info> Config: added 'psk' value '<omitted>' Jan 24 22:28:00 lpt NetworkManager: <info> Config: added 'proto' value 'RSN' Jan 24 22:28:00 lpt NetworkManager: <info> Config: added 'pairwise' value 'TKIP CCMP' Jan 24 22:28:00 lpt NetworkManager: <info> Config: added 'group' value 'TKIP CCMP' Jan 24 22:28:00 lpt NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jan 24 22:28:00 lpt NetworkManager: <info> Config: set interface ap_scan to 1 Jan 24 22:28:00 lpt NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected Jan 24 22:28:00 lpt NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning Jan 24 22:28:15 lpt NetworkManager: <info> wlan0: link timed out. Jan 24 22:28:25 lpt NetworkManager: <info> Activation (wlan0/wireless): association took too long. Jan 24 22:28:25 lpt NetworkManager: <info> (wlan0): device state change: 5 -> 6 Jan 24 22:28:25 lpt NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets Jan 24 22:28:25 lpt NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected Jan 24 22:28:25 lpt NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: Requested setting is empty. Jan 24 22:28:25 lpt NetworkManager: <info> (wlan0): device state change: 6 -> 9 Jan 24 22:28:25 lpt NetworkManager: <info> Activation (wlan0) failed for access point (network60) Jan 24 22:28:25 lpt NetworkManager: <info> Marking connection 'network60' invalid. Jan 24 22:28:25 lpt NetworkManager: <info> Activation (wlan0) failed. Jan 24 22:28:25 lpt NetworkManager: <info> (wlan0): device state change: 9 -> 3 Jan 24 22:28:25 lpt NetworkManager: <info> (wlan0): deactivating device (reason: 0). I've attached /var/log/wpa_supplicant.log -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=269747 User korossy.p@freemail.hu added comment https://bugzilla.novell.com/show_bug.cgi?id=269747#c14 Paul Korossy <korossy.p@freemail.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #266703|0 |1 is obsolete| | --- Comment #14 from Paul Korossy <korossy.p@freemail.hu> 2009-01-24 14:44:46 MST --- Created an attachment (id=267478) --> (https://bugzilla.novell.com/attachment.cgi?id=267478) wpa_supplicant.log -- 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.
participants (1)
-
bugzilla_noreply＠novell.com