[Bug 342183] New: NetworkManager: no connect to WPA AP, wpa_supplicant not started
https://bugzilla.novell.com/show_bug.cgi?id=342183 Summary: NetworkManager: no connect to WPA AP, wpa_supplicant not started Product: openSUSE 11.0 Version: unspecified Platform: x86 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: casualprogrammer@yahoo.com QAContact: qa@suse.de Found By: Beta-Customer On an FSC Amilo Si1520 running openSuSE 10.3.1 (GNOME) with Intel ipw3945 WLAN NetworkManager fails to connect after update from factory. dmesg has: [ 33.244982] wlan0 renamed to wlan0_rename while in fact it is renamed to wlan0_rename_re which might be the cause. Starting wpa_supplicant manually and connecting via wpa_gui connects, alas the connection can not be used as NetworkManager seems to prohibit binding. Not sure why NetworkManager is compulsory now, I had removed it in 10.3 and started wpa_supplicant during boot via a script. This seems no longer possible, as yast2 network insists on installing NetworkManager when configuring the network Card. cat /etc/SuSE-release openSUSE 10.3.1 (i586) Alpha0 VERSION = 10.3.1 rpm -qa | grep network yast2-network-2.16.7-2 rpm -qa | grep Network NetworkManager-0.6.5-36 NetworkManager-gnome-0.6.5-36 -- 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=342183 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=342183#c1 --- Comment #1 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-11-16 07:33:56 MST --- After turning off NetworkManager via yast2 sysconfig Network/General/NETWORKMANAGER = NO running service network restart returns service network restart Shutting down network interfaces: eth0 device: Intel Corporation PRO/100 VE Network Connectiondonev 02) wlan0_rename_re device: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) No configuration found for wlan0_rename_re Nevertheless the interface will be shut down. done Shutting down service network . . . . . . . . . . . . . done. Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: lo lo IP address: 127.0.0.1/8 Checking for network time protocol daemon (NTPD): doneed eth0 device: Intel Corporation PRO/100 VE Network Connection (rev 02) eth0 is controlled by ifplugd waiting wlan0_rename_re device: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) No configuration found for wlan0_rename_re unused Setting up service network . . . . . . . . . . . . . . done. after copying /etc/sysconfig/network/ifcfg-eth1 to ifcfg-wla0_rename_re running service network restart returns service network restart Shutting down network interfaces: eth0 device: Intel Corporation PRO/100 VE Network Connectiondonev 02) wlan0_rename_re device: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) done Shutting down service network . . . . . . . . . . . . . done. Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: lo lo IP address: 127.0.0.1/8 Checking for network time protocol daemon (NTPD): doneed eth0 device: Intel Corporation PRO/100 VE Network Connection (rev 02) eth0 is controlled by ifplugd waiting wlan0_rename_re device: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) command 'iwconfig wlan0_rename_re nick workstation6l' returned Error for wireless request "Set Nickname" (8B1C) : SET failed on device wlan0_rename_re ; Operation not supported. wlan0_rename_re (DHCP) . *** buffer overflow detected ***: /sbin/dhcpcd terminated ======= Backtrace: ========= /lib/libc.so.6(__chk_fail+0x41)[0xb7ec2301] /sbin/dhcpcd[0xb7f565af] /sbin/dhcpcd[0xb7f57668] /sbin/dhcpcd(main+0x20e)[0xb7f57c9e] /lib/libc.so.6(__libc_start_main+0xe6)[0xb7dfbfc6] /sbin/dhcpcd[0xb7f50461] ======= Memory map: ======== b7dd9000-b7de3000 r-xp 00000000 08:04 358427 /lib/libgcc_s.so.1 b7de3000-b7de5000 rw-p 00009000 08:04 358427 /lib/libgcc_s.so.1 b7de5000-b7de6000 rw-p b7de5000 00:00 0 b7de6000-b7f1b000 r-xp 00000000 08:04 358347 /lib/libc-2.6.1.so b7f1b000-b7f1d000 r--p 00135000 08:04 358347 /lib/libc-2.6.1.so b7f1d000-b7f1e000 rw-p 00137000 08:04 358347 /lib/libc-2.6.1.so b7f1e000-b7f22000 rw-p b7f1e000 00:00 0 b7f31000-b7f4c000 r-xp 00000000 08:04 361460 /lib/ld-2.6.1.so b7f4c000-b7f4d000 r--p 0001a000 08:04 361460 /lib/ld-2.6.1.so b7f4d000-b7f4e000 rw-p 0001b000 08:04 361460 /lib/ld-2.6.1.so b7f4e000-b7f5a000 r-xp 00000000 08:04 48899 /sbin/dhcpcd b7f5a000-b7f5b000 r--p 0000b000 08:04 48899 /sbin/dhcpcd b7f5b000-b7f5c000 rw-p 0000c000 08:04 48899 /sbin/dhcpcd b7f5c000-b7f5d000 rw-p b7f5c000 00:00 0 b8104000-b8125000 rw-p b8104000 00:00 0 [heap] bfcc2000-bfcd7000 rw-p bffeb000 00:00 0 [stack] ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso] . . . no IP address yet... backgrounding. waiting Setting up service network . . . . . . . . . . . . . . done. Looks like something is broken :-( -- 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=342183#c2 --- Comment #2 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-11-16 07:57:26 MST --- After fixing /etc/sysconfig/network/ifcfg-wlan0_rename_re ( the yast2 network card setup had put the psk in the WIRELESS_KEY field rather than WIRELESS_WPA_PSK and marked it as Hex value by prefixing h: for eth1 as well as set AUTH_MODE to open rather than psk) wpa_supplicant is started and connects to the AP ( you can verify that with wpa_gui ), yet no bind takes place, probably due to the above error. -- 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=342183#c3 --- Comment #3 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-11-16 07:59:04 MST --- P.S. uname-r 2.6.24-rc2-4-default -- 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=342183#c4 --- Comment #4 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-11-16 11:31:50 MST --- P.P.S. actually I missed out a dmesg entry [ 37.782697] wlan0_rename renamed to wlan0_rename_re Not sure what all this is needed for, but it surely looks impressive. -- 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=342183 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=342183#c5 Casual J. Programmer <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High --- Comment #5 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-12-10 06:57:18 MST --- Hardware: Notebook FSC Amilo Si1520 Graphics: Intel 945 GM, LCD 1280*800 Wireless: Intel ipw3945 Sound: Intel ICH7 Desktop: GNOME OS: openSUSE 11.0 (i586) Alpha0 VERSION = 11.0 Kernel: 2.6.24-rc4-git1-2-default rpm -qa | grep network yast2-network-2.16.14-2 Still broken :-( -- 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=342183 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=342183#c6 Casual J. Programmer <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Critical Component|GNOME |Kernel --- Comment #6 from Casual J. Programmer <casualprogrammer@yahoo.com> 2007-12-14 10:32:51 MST --- While this is probably related to Bug 309081, it seems that it is getting worse, although various claims have been put forward as to the issue having been fixed. This is ridiculous! While every effort is undertaken to establish a completely broken iwl3945 support at the same time the flawless working ipw3945 support gets crippled as well. As of todays update from factory ipw3945 is no longer installable, respectively gets removed when updating the Kernel. I think it's about time somebody gets this fixed ASAP. dmesg shows: wlan0_rename renamed to wlan0_rename_re IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk> powernow: This module only works with AMD K7 CPUs e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex iwl3945: Microcode SW error detected. Restarting 0x82000008. iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x000B ser 0x0000004B iwl3945: Error setting new configuration (-5). iwl3945: Can't stop Rx DMA. iwl3945: Microcode SW error detected. Restarting 0x82000008. iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x0000004B iwl3945: Error setting new configuration (-5). iwl3945: Can't stop Rx DMA. iwl3945: Microcode SW error detected. Restarting 0x82000008. iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x0000004B iwl3945: Error setting new configuration (-5). iwl3945: Can't stop Rx DMA. [drm] Initialized drm 1.1.0 20060810 iwl3945: Microcode SW error detected. Restarting 0x82000008. iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x0000004B iwl3945: Error setting new configuration (-5). iwl3945: Can't stop Rx DMA. ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 17 [drm] Initialized i915 1.6.0 20060119 on minor 0 audit(1197652688.006:2): audit_backlog_limit=320 old=64 by auid=4294967295 res=1 audit(1197652688.718:3): audit_pid=2780 old=0 by auid=4294967295 NET: Registered protocol family 17 ip6_tables: (C) 2000-2006 Netfilter Core Team ip_tables: (C) 2000-2006 Netfilter Core Team iwl3945: Microcode SW error detected. Restarting 0x82000008. iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x000B ser 0x0000004B iwl3945: Error setting new configuration (-5). iwl3945: Can't stop Rx DMA. iwl3945: Microcode SW error detected. Restarting 0x82000008. iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x0000004B iwl3945: Error setting new configuration (-5). iwl3945: Can't stop Rx DMA. iwl3945: Microcode SW error detected. Restarting 0x82000008. iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x0000004B iwl3945: Error setting new configuration (-5). iwl3945: Can't stop Rx DMA. iwl3945: Microcode SW error detected. Restarting 0x82000008. iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x0000004B iwl3945: Error setting new configuration (-5). iwl3945: Can't stop Rx DMA. kjournald starting. Commit interval 5 seconds EXT3-fs warning: checktime reached, running e2fsck is recommended EXT3 FS on sdb1, internal journal EXT3-fs: mounted filesystem with ordered data mode. iwl3945: Microcode SW error detected. Restarting 0x82000008. iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x000B ser 0x0000004B iwl3945: Error setting new configuration (-5). iwl3945: Can't stop Rx DMA. iwl3945: Microcode SW error detected. Restarting 0x82000008. iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x0000004B iwl3945: Error setting new configuration (-5). iwl3945: Can't stop Rx DMA. iwl3945: Microcode SW error detected. Restarting 0x82000008. iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x0000004B iwl3945: Error setting new configuration (-5). iwl3945: Can't stop Rx DMA. iwl3945: Microcode SW error detected. Restarting 0x82000008. iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x0000004B iwl3945: Error setting new configuration (-5). iwl3945: Can't stop Rx DMA. Hardware: Notebook FSC Amilo Si1520 Graphics: Intel 945 GM, LCD 1280*800 Wireless: Intel ipw3945 Sound: Intel ICH7 Desktop: GNOME OS: openSUSE 11.0 (i586) Alpha0 VERSION = 11.0 Kernel: 2.6.24-rc5-2-default Changing component from GNOME to Kernel, as this is probably caused by the screwed up drivers. Output from Smart on trying to install ipw3945: Can't install ipw3945d-1.7.22-19@i586: all packages providing ipw3945-kmp failed to install: Can't install ipw3945-kmp-pae-1.2.2_2.6.24_rc4_git6_2-4@i586: no package provides kernel(drivers_base) = 83d878b70135960d Can't install ipw3945-kmp-default-1.2.2_2.6.24_rc4_git6_2-4@i586: no package provides kernel(vmlinux) = 95a2a8427b0b5406 Can't install ipw3945-kmp-debug-1.2.2_2.6.24_rc4_git6_2-4@i586: no package provides kernel(drivers_base) = 7c04bfbfc08aeff0 -- 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=342183 User jpr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=342183#c7 JP Rosevear <jpr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |casualprogrammer@yahoo.com --- Comment #7 from JP Rosevear <jpr@novell.com> 2008-01-18 12:20:18 MST --- With NM 0.7, can you give an update CJP? -- 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=342183 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=342183#c8 Casual J. Programmer <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #8 from Casual J. Programmer <casualprogrammer@yahoo.com> 2008-01-18 17:07:54 MST --- See Bug 345147 -- 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=342183 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=342183#c10 Casual J. Programmer <casualprogrammer@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|casualprogrammer@yahoo.com | --- Comment #10 from Casual J. Programmer <casualprogrammer@yahoo.com> 2008-03-01 01:50:55 MST --- I am not sure what you should do with this bug. It's pretty old (opened 2007-11-16 ) and I switched back to ipw3945 since, which is working nicely for me. I think iwl3945 (AKA iwlwifi) is still not running properly but I am not going to waste more time on it. -- 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=342183 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=342183#c11 Tambet Ingo <tambet@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #11 from Tambet Ingo <tambet@novell.com> 2008-03-03 09:58:10 MST --- I'm going to close it then, in any case it's not a NetworkManager bug. If you strongly disagree with the decision to replace ipw3945 with iwl3945, you should open a bug for that, but there's nothing I can do. -- 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=342183 User casualprogrammer@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=342183#c12 --- Comment #12 from Casual J. Programmer <casualprogrammer@yahoo.com> 2008-03-03 10:16:36 MST --- That's OK with me, as long as both are provided. As I pointed out elsewhere already the intellinux project ( http://intellinuxwireless.org/?p=iwlwifi ) considers iwlwifi: "NOTE: The iwlwifi driver is a development driver. If you are looking for a fully validated and stable driver, please visit the Intel Customer Support download page." So, as far as I am concerned, there is no room for it in a final distribution. -- 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