[Bug 406635] New: knetworkmanager fails to reconnect after suspend

bugzilla_noreply＠novell.com

6 Jul 2008 6 Jul '08

17:26

https://bugzilla.novell.com/show_bug.cgi?id=406635 Summary: knetworkmanager fails to reconnect after suspend Product: openSUSE 11.0 Version: Final Platform: i586 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dave@daveroyal.com QAContact: qa@suse.de Found By: Customer Created an attachment (id=226145) --> (https://bugzilla.novell.com/attachment.cgi?id=226145) knetworkmanager log - connect, suspect to ram, wakeup ALWAYS fails to reconnect after s2r or s2d. It uses WEP and hex key. Attached knetworkmanager log (innitial connect, suspect to ram, wakeup) Often it won't connect to wlan on startup, and requires several retries. -- 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.

Show replies by date

bugzilla_noreply＠novell.com

6 Jul 6 Jul

17:30

New subject: [Bug 406635] knetworkmanager fails to reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User dave@daveroyal.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c1 --- Comment #1 from David Royal 2008-07-06 11:30:48 MDT --- Created an attachment (id=226146) --> (https://bugzilla.novell.com/attachment.cgi?id=226146) hwinfo Attached hwinfo -- 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.

bugzilla_noreply＠novell.com

8 Jul 8 Jul

15:10

New subject: [Bug 406635] knetworkmanager fails to reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User clovisgladstone@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c2 Clovis Gladstone changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clovisgladstone@gmail.com --- Comment #2 from Clovis Gladstone 2008-07-08 09:10:34 MDT --- I have the same problem using a wpa key. Here's the relevant part of /var/log/NetworkManager if that helps : Jul 8 08:21:52 linux NetworkManager: <info> Waking up... Jul 8 08:21:52 linux NetworkManager: <info> (eth0): now managed Jul 8 08:21:52 linux NetworkManager: <info> (eth0): device state change: 1 -> 2 Jul 8 08:21:52 linux NetworkManager: <info> (eth0): bringing up device. Jul 8 08:21:52 linux NetworkManager: <info> (eth0): preparing device. Jul 8 08:21:52 linux NetworkManager: <info> (eth0): deactivating device. Jul 8 08:21:52 linux NetworkManager: <info> (wlan0): now managed Jul 8 08:21:53 linux NetworkManager: <info> (wlan0): device state change: 1 -> 2 Jul 8 08:21:53 linux NetworkManager: <info> (wlan0): bringing up device. Jul 8 08:21:53 linux NetworkManager: <info> (wlan0): preparing device. Jul 8 08:21:53 linux NetworkManager: <info> (wlan0): deactivating device. Jul 8 08:21:53 linux NetworkManager: <info> (wlan0): device state change: 2 -> 3 Jul 8 08:21:53 linux NetworkManager: <info> (wlan0): supplicant interface state change: 1 -> 2. Jul 8 08:21:54 linux NetworkManager: <info> Activation (wlan0) starting connection 'z00gl4d' Jul 8 08:21:54 linux NetworkManager: <info> (wlan0): device state change: 3 -> 4 Jul 8 08:21:54 linux NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jul 8 08:21:54 linux NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jul 8 08:21:54 linux NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jul 8 08:21:54 linux NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jul 8 08:21:54 linux NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jul 8 08:21:54 linux NetworkManager: <info> (wlan0): device state change: 4 -> 5 Jul 8 08:21:54 linux NetworkManager: <info> Activation (wlan0/wireless): access point 'z00gl4d' has security, but secrets are required. Jul 8 08:21:54 linux NetworkManager: <info> (wlan0): device state change: 5 -> 6 Jul 8 08:21:54 linux NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jul 8 08:21:55 linux NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jul 8 08:21:55 linux NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jul 8 08:21:55 linux NetworkManager: <info> (wlan0): device state change: 6 -> 4 Jul 8 08:21:55 linux NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jul 8 08:21:55 linux NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jul 8 08:21:55 linux NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jul 8 08:21:55 linux NetworkManager: <info> (wlan0): device state change: 4 -> 5 Jul 8 08:21:55 linux NetworkManager: <info> Activation (wlan0/wireless): connection 'z00gl4d' has security, and secrets exist. No new secrets needed. Jul 8 08:21:55 linux NetworkManager: <info> Config: added 'ssid' value 'z00gl4d' Jul 8 08:21:55 linux NetworkManager: <info> Config: added 'scan_ssid' value '1' Jul 8 08:21:55 linux NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK' Jul 8 08:21:55 linux NetworkManager: <info> Config: added 'psk' value '<omitted>' Jul 8 08:21:55 linux NetworkManager: <info> Config: added 'proto' value 'RSN' Jul 8 08:21:55 linux NetworkManager: <info> Config: added 'pairwise' value 'TKIP CCMP' Jul 8 08:21:55 linux NetworkManager: <info> Config: added 'group' value 'TKIP CCMP' Jul 8 08:21:55 linux NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jul 8 08:21:55 linux NetworkManager: <info> Config: set interface ap_scan to 1 Jul 8 08:21:55 linux NetworkManager: <info> (wlan0): supplicant connection state change: 1 -> 2 Jul 8 08:22:20 linux NetworkManager: <info> Activation (wlan0/wireless): association took too long. -- 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.

bugzilla_noreply＠novell.com

9 Jul 9 Jul

06:32

New subject: [Bug 406635] knetworkmanager fails to reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User dave@daveroyal.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c3 --- Comment #3 from David Royal 2008-07-09 00:32:16 MDT --- Created an attachment (id=226619) --> (https://bugzilla.novell.com/attachment.cgi?id=226619) knetworkmanagerlog for many attempted connections at bootup I think that this failure to reconnect after suspend is merely an example of a more general failure to connect to the wi-fi AP. Attached a log from this morning's boot up - half a dozen attempts to get it to connect followed by one successful one. (These attempts included me deactivating and reactivating wan0 using the tray menu in an attempt to get it to connect). These logs contain these lines: <info> Activation (wlan0/wireless): association took too long. <WARN> get_secrets_cb(): Couldn't get connection secrets: Requested setting is empty. knetworkmanager works fine with cable eth0 BTW. It's only wifi which works badly. -- 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.

bugzilla_noreply＠novell.com

07:48

New subject: [Bug 406635] knetworkmanager fails to reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 Stephan Binner changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |hschaa@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.

bugzilla_noreply＠novell.com

19:44

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User rprigan@insight.rr.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c4 Richard Prigan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rprigan@insight.rr.com Summary|knetworkmanager fails to reconnect after suspend|knetworkmanager fails to connect, or reconnect | |after suspend --- Comment #4 from Richard Prigan 2008-07-09 13:44:36 MDT --- Problem is not restricted to resume. It can also fail to connect on normal startup, timing out when attempting to connect. I can often make it connect by running YAST network device setup, or by /etc/inet.d/network restart Situation looks just as in as bug report in /var/log/NetworkManager: ...linux NetworkManager: <info> Activation (wlan0/wireless): association took too long. in /etc/sysconfig/network/config value is default 0 ... (it should keep trying!?) might try explicitly setting that to an interval? -- 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.

bugzilla_noreply＠novell.com

20 Aug 20 Aug

19:21

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User scheve@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c5 Stephan Scheve changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scheve@gmx.de --- Comment #5 from Stephan Scheve 2008-08-20 13:21:17 MDT --- Hello, I've got the same problem. Maybe the attached data may help a little bit: [code] collectNWData.sh V0.6.1-5 --- Welcher Netzwerkverbindungtyp soll getestet werden? --- (2) Kabellose Verbindung (WLAN) --- Welche Netzwerktopologie liegt vor? --- (3) WLAN access point <---> LinuxRouter <---> LinuxClient --- Auf welchem Rechner wird das Script ausgeführt? --- (1) LinuxClient !!! CND0300E: Keinen dhcp Server am Interface wlan0 gefunden --- 1 Fehler gefunden. --- Gehe zu http://www.linux-tips-and-tricks.de/CND um detailiertere Hinweise zu den Fehlermeldungen/Warnungen zu bekommen und wie die Fehler beseitigt werden könnenF. ================================================================================================================== ================================================================================================================== *** uname Linux limobi 2.6.25.11-0.1-default #1 SMP 2008-07-13 20:48:28 +0200 x86_64 x86_64 x86_64 GNU/Linux ================================================================================================================== *** SuSE release openSUSE 11.0 (X86-64) VERSION = 11.0 ================================================================================================================== *** /etc/resolv ================================================================================================================== *** /etc/hosts 127.0.0.1 localhost 127.0.0.2 limobi.scheve.heim limobi ================================================================================================================== *** route Kernel IP Routentabelle Ziel Router Genmask Flags Metric Ref Use Iface 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo ================================================================================================================== *** arp ================================================================================================================== *** ifconfig eth0 Link encap:Ethernet Hardware Adresse 00:1A:4B:66:2A:B1 inet6 Adresse: fe80::21a:4bff:fe66:2ab1/64 Gültigkeitsbereich:Verbindung UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:7960 errors:0 dropped:0 overruns:0 frame:0 TX packets:6047 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:1000 RX bytes:9380602 (8.9 Mb) TX bytes:1061324 (1.0 Mb) Interrupt:10 lo Link encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:742 errors:0 dropped:0 overruns:0 frame:0 TX packets:742 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:0 RX bytes:67632 (66.0 Kb) TX bytes:67632 (66.0 Kb) wlan0 Link encap:Ethernet Hardware Adresse 00:1A:73:8B:F5:BD UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:72 errors:0 dropped:0 overruns:0 frame:0 TX packets:106 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:1000 RX bytes:9996 (9.7 Kb) TX bytes:18411 (17.9 Kb) wmaster0 Link encap:UNSPEC Hardware Adresse 00-1A-73-8B-F5-BD-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) ================================================================================================================== *** ping tests connect: Network is unreachable Ping of 195.135.220.3 failed ping: unknown host www.suse.de Ping of www.suse.de failed ================================================================================================================== *** PCI devices 10:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM5906M Fast Ethernet PCI Express [14e4:1713] (rev 02) 30:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11a/b/g [14e4:4312] (rev 02) ================================================================================================================== *** USB devices Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ================================================================================================================== *** List of loaded modules | aes_generic | aes_x86_64 | af_packet | ahci | | arc4 | b43 | binfmt_misc | cdrom | | cfg80211 | crypto_blkcipher | dm_mod | dock | | ecb | edd | ehci_hcd | ext3 | | fglrx | firmware_class | fuse | i2c_core | | i2c_piix4 | input_polldev | ip6table_filter | ip6table_mangle | | ip6_tables | ip6t_LOG | ip6t_REJECT | iptable_filter | | iptable_mangle | iptable_nat | ip_tables | ipt_LOG | | ipt_REJECT | ipv6 | jbd | joydev | | k8temp | led_class | libata | loop | | mac80211 | mbcache | nf_conntrack | nf_conntrack_ipv4 | | nf_conntrack_ipv6 | nf_conntrack_netbios_ns | nf_nat | ohci_hcd | | pata_atiixp | pci_hotplug | pcmcia | pcmcia_core | | rfkill | rfkill_input | rsrc_nonstatic | scsi_mod | | sd_mod | serio_raw | sg | shpchp | | snd | snd_hda_intel | snd_hwdep | snd_mixer_oss | | snd_page_alloc | snd_pcm | snd_pcm_oss | snd_seq | | snd_seq_device | snd_timer | soundcore | sr_mod | | ssb | tg3 | usbcore | x_tables | | xt_limit | xt_pkttype | xt_state | xt_tcpudp | | yenta_socket | ================================================================================================================== *** cat /etc/sysconfig/network/ifcfg-[earwd]* | egrep -v ".*=''" ================================================================================================================== *** iwconfig lo no wireless extensions. eth0 no wireless extensions. wmaster0 no wireless extensions. wlan0 IEEE 802.11g ESSID:"" Mode:Managed Frequency:2.437 GHz Access Point: 00:1C:F0:5A:33:EB Bit Rate=9 Mb/s Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:off Link Quality=95/100 Signal level=-54 dBm Noise level=-69 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ================================================================================================================== *** grep -i radio /var/log/boot.msg ================================================================================================================== *** grep -i firmware /var/log/messages* Aug 20 13:51:11 limobi kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) Aug 20 13:59:28 limobi kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) Aug 20 16:41:27 limobi kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) Aug 20 16:47:27 limobi kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) Aug 20 18:03:23 limobi kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) ================================================================================================================== *** ls -ls /lib/firmware insgesamt 64 4 -rw-r--r-- 1 root root 137 6. Jun 23:59 3CCFEM556.cis 4 -rw-r--r-- 1 root root 134 6. Jun 23:59 3CXEM556.cis 4 drwxr-x--- 2 root root 4096 18. Aug 10:59 b43 4 drwxr-xr-x 2 root root 4096 18. Aug 10:59 b43legacy 4 -rw-r--r-- 1 root root 109 6. Jun 23:59 COMpad2.cis 4 -rw-r--r-- 1 root root 76 6. Jun 23:59 COMpad4.cis 4 -rw-r--r-- 1 root root 136 6. Jun 23:59 DP83903.cis 4 -rw-r--r-- 1 root root 53 6. Jun 23:59 E-CARD.cis 4 -rw-r--r-- 1 root root 253 6. Jun 23:59 LA-PCM.cis 4 -rw-r--r-- 1 root root 107 6. Jun 23:59 MT5634ZLX.cis 4 -rw-r--r-- 1 root root 54 6. Jun 23:59 NE2K.cis 4 -rw-r--r-- 1 root root 210 6. Jun 23:59 PCMLM28.cis 4 -rw-r--r-- 1 root root 68 6. Jun 23:59 PE-200.cis 4 -rw-r--r-- 1 root root 74 6. Jun 23:59 PE520.cis 4 -rw-r--r-- 1 root root 86 6. Jun 23:59 RS-COM-2P.cis 4 -rw-r--r-- 1 root root 85 6. Jun 23:59 tamarack.cis ================================================================================================================== *** ndiswrapper -l No ndiswrapper found ================================================================================================================== *** Active processes wpa_supplicant:YES knetworkmanager:YES nm-applet:NO ================================================================================================================== *** grep NETWORKMANAGER /etc/sysconfig/network/config NETWORKMANAGER="yes" ================================================================================================================== *** grep -i persistent /etc/sysconfig/network/config ================================================================================================================== *** grep 'eth|ath|wlan|ra' /etc/udev/rules.d/*net_persistent* /etc/udev/rules.d/70-persistent-net /usr/bin/egrep: /etc/udev/rules.d/*net_persistent*: Datei oder Verzeichnis nicht gefunden /etc/udev/rules.d/70-persistent-net.rules:SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1a:73:8b:f5:bd", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0" /etc/udev/rules.d/70-persistent-net.rules:SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1a:4b:66:2a:b1", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" ================================================================================================================== *** grep -r 'eth[0-10]|ath[0-10]|wlan[0-10]|ra[0-10]' /etc/modprobe.* /etc/modprobe.conf:install eth0 /bin/true /etc/modprobe.conf:install eth1 /bin/true ================================================================================================================== *** tail /var/log/messages* No firmware messages found ================================================================================================================== *** iwlist scanning ================================================================================================================== *** NWEliza states IF:eth0 IP: IM:1 IF:wlan0 IP: IM:2 DI:2 dI:1 NIC:1 cNiC:2:1 NI:2 cNI:2 NDIS:0 NIWL:0 KM:0 AP:1 [/code] With cable connection on eth0 there is no problem, only with wlan. Best regards, Stephan -- 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.

bugzilla_noreply＠novell.com

1 Oct 1 Oct

11:38

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |zoz@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.

bugzilla_noreply＠novell.com

7 Oct 7 Oct

21:18

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User b.a.koenig@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c7 Bernhard Koenig changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |b.a.koenig@googlemail.com --- Comment #7 from Bernhard Koenig 2008-10-07 15:18:17 MDT --- Can confirm this on my opensuse install. Still, as of October 2008. At times, I have to "connect" 3-4 in order to get into my wireless even though the signal is good 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.

bugzilla_noreply＠novell.com

21:25

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User b.a.koenig@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c8 --- Comment #8 from Bernhard Koenig 2008-10-07 15:25:45 MDT --- Just checked and my NetworkManager-kde is 07r821737-0.3. It is claimed in Bug #405631 that this version improves on a number of related problems but I still have trouble connecting. -- 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.

bugzilla_noreply＠novell.com

9 Oct 9 Oct

15:47

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User jbenc@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c9 Jiri Benc changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |dave@daveroyal.com --- Comment #9 from Jiri Benc 2008-10-09 09:47:54 MDT --- Could you please try to disable hw scanning: rmmod iwl3945 modprobe iwl3945 disable_hw_scan=1 (you may need to restart both NetworkManager and knetworkmanager afterwards) and report whether it changes anything? -- 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.

bugzilla_noreply＠novell.com

19:51

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User b.a.koenig@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c10 Bernhard Koenig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|dave@daveroyal.com | --- Comment #10 from Bernhard Koenig 2008-10-09 13:51:01 MDT --- The funny thing is that it always works much better if I quit the system tray Network applet and restart it in command-line with" knetworkmanager". If I do that, it always connects immediately. It often does not connect, however, when the Network applet is activated right after startup. So I'm not sure if the hw scanning is the problem. Btw, what is hw scanning? -- 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.

bugzilla_noreply＠novell.com

13 Oct 13 Oct

16:48

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User jbenc@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c11 --- Comment #11 from Jiri Benc 2008-10-13 10:48:24 MDT --- I managed to reproduce the problem on my test machine. It indeed behaves much better if knetworkmanager is restarted after KDE starts. Both nm-tool and iwlist scan list the networks correctly, so I confirm this is a knetworkmanager problem and I can do nothing here. No need to try to switch off hw scanning, it works correctly. (Hw scanning is done by the card itself with no software control over it. It uses a quite aggressive timing, so a possible culprit could be hw scanning not finding the network, which would lead to a similar behavior.) -- 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.

bugzilla_noreply＠novell.com

15 Oct 15 Oct

07:08

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User kojot350@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c12 kojot 350 changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kojot350@gmail.com --- Comment #12 from kojot 350 2008-10-15 01:08:16 MDT --- I confirm this bug on: openSUSE 11.0 (x86-64) Intel Corporation PRO/Wireless 4965 AG I don't use knetworkmanager(it's buggy an ugly), just networkmanager, and after every suspend I have to reconnect manually by /etc/init.d/network restart - it works every time. Does networkmanager can, on it's own, detect wi-fi after suspend? Any one know how to do workaround by executing automatically /etc/init.d/network restart after suspend? -- 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.

bugzilla_noreply＠novell.com

16 Oct 16 Oct

13:56

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 Christian Zoz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |helmut.schaa@gmail.com, wstephenson@novell.com AssignedTo|zoz@novell.com |anaumov@novell.com 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.

bugzilla_noreply＠novell.com

5 Nov 5 Nov

09:14

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User jbenc@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c13 Jiri Benc changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |listuser@peternixon.net --- Comment #13 from Jiri Benc 2008-11-05 02:14:57 MST --- *** Bug 416508 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=416508 -- 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.

bugzilla_noreply＠novell.com

10:05

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User dave@daveroyal.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c14 --- Comment #14 from David Royal 2008-11-05 03:05:23 MST --- I raised this bug as "knetworkmanager fails to connect, or reconnect after suspend" but I would now say "knetworkmanager fails to connect" I can usually get it to connect on startup by doing this: 1 sign on to kde 2 quit knetworkmanager 3 restart it 4 sit next to the wifi AP 5 click the ESSID in the tray icon 6 if it won't connect, repeat from 5 About 50% of the time this fails twice and succeeds on the 3rd attempt. If it doesn't, I repeat from step 2. Usually it connects within about 3 attempts but sometimes it takes a dozen attempts - I can usually connect it eventually. Same procedure after S2D (which I don't often do now!) I'm using NetworkManager-kde-0.7r826733-7.1 Everything else the same as OP -- 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.

bugzilla_noreply＠novell.com

13:46

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635

User jbenc@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=406635#c15





--- Comment #15 from Jiri Benc   2008-11-05 06:46:17 MST ---
Yes. And it is really the same issue as bug 416508. By the way, it is not
connected to iwl* drivers - I can reproduce it also on my laptop with ath5k
driver. It seems to happen more often with iwl* but it may be just a
coincidence.

>From what I know so far, it is caused by knetworkmanager not getting all
networks from NetworkManager. This has two consequences:
1. knetworkmanager doesn't show all wireless networks available, while nm-tool
does.
2. When connecting, NetworkManager asks knetworkmanager for keys, which are not
provided as knetworkmanager doesn't see the network. This results in
unsuccessful attempt to associate.

This also means that the reconnection fails after suspend - NetworkManager
tries to reassociate and asks knetworkmanager for keys, which fails.

Also, it seems it happens only after KDE is started or after a suspend. After
restarting knetworkmanager, everything works. In all cases nm-tool reports all
of the networks. (Please note we have probably another bug with iwl* driver
when the current network is not returned even by the driver - see bug 394333.
But that is not the same as this bug as the symptoms described here can be
observed with other drivers as well.)


-- 
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.

bugzilla_noreply＠novell.com

8 Dec 8 Dec

13:37

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 Christian Zoz changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Network |KDE3 -- 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.

bugzilla_noreply＠novell.com

12 Jan 12 Jan

10:59

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User vankan@kabelfoon.nl added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c16 Jos van Kan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vankan@kabelfoon.nl --- Comment #16 from Jos van Kan 2009-01-12 03:59:04 MST --- I don't use (k)networkmanager but traditional ifup/down and also have no connection to the AP on wakeup after suspend, but have to do rcnetwork restart from the CLI. This always works flawlessly. I'm using the new b43 drivers to the Broadcom wlan controller. -- 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.

bugzilla_noreply＠novell.com

11:05

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c17 Helmut Schaa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |dave@daveroyal.com --- Comment #17 from Helmut Schaa 2009-01-12 04:05:32 MST --- (In reply to comment #16)

...

I don't use (k)networkmanager but traditional ifup/down and also have no connection to the AP on wakeup after suspend, but have to do

As this bug is about KNetworkManager could you please open a new bug for this issue? Thanks. -- 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.

bugzilla_noreply＠novell.com

14:20

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User vankan@kabelfoon.nl added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c18 --- Comment #18 from Jos van Kan 2009-01-12 07:20:23 MST --- Why? I just was trying to show that the bug probably was not or not entirely a (k)networkmanager issue. Filing it as a different bug only will cloud the issue. -- 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.

bugzilla_noreply＠novell.com

14:31

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c19 --- Comment #19 from Helmut Schaa 2009-01-12 07:31:34 MST --- (In reply to comment #18)

...

Why? I just was trying to show that the bug probably was not or not entirely a (k)networkmanager issue.

You might have the same symptoms as in this bug report (wireless not working after resume) but it wouldn't surprise me if the real cause is something totally unrelated. At least you're using a different driver and a different method for connecting. Hence it is unlikely that both issues are related. If you create a new bug report we can still close it as a duplicate if we find out that both bugs suffer from the same 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.

bugzilla_noreply＠novell.com

16:00

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User scheve@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c20 --- Comment #20 from Stephan Scheve 2009-01-12 09:00:16 MST --- Hello, after istallation of opensuse 11.1 and the b43 firmware my laptop now works with Knetworkmanager. With update from sunday it failed again, but with last update from today, wlan connection works again. So my problem is solved... Best regards and many thanks for your hard work! I'm very happy with my laptop now working with wlan. Stephan -- 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.

bugzilla_noreply＠novell.com

24 Feb 24 Feb

16:47

New subject: [Bug 406635] knetworkmanager fails to connect, or reconnect after suspend

https://bugzilla.novell.com/show_bug.cgi?id=406635 User dave@daveroyal.com added comment https://bugzilla.novell.com/show_bug.cgi?id=406635#c21 --- Comment #21 from David Royal 2009-02-24 09:47:55 MST --- I've found a workaround for this bug. I no longer have to go through the rigmarole in comment #14 The machine still (nearly*) always fails to restore the wifi connection when I boot it up and login. So I now do this: 1 Click on the round knetworkmanager icon in the tray. 2 Click on the SSID to start connecting 3 Immediately hit alt-control-F2 4 No need to login - just wait 15 seconds or so 5 Hit alt-control-F7 to return to KDE 6 Voilà - I'm connected This has worked every morning for a fortnight. And it just worked when wakening from S2R. Perhaps this strange behaviour will help diagnose the problem. *On the _very_ few occasions that it reconnects automatically after reboot it doesn't show the signal strength meter in the tray - it shows the round icon. I can tell if it's connected or not by hovering over it. I'm still on 11.0 BTW. Does it work any better on 11.1? -- 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.

5546

Age (days ago)

5779

Last active (days ago)

List overview

Download

24 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 406635] New: knetworkmanager fails to reconnect after suspend

tags

participants (1)