Bug 377560 - iwl3945, NetworkManager and NetworkManager-kde
Summary: iwl3945, NetworkManager and NetworkManager-kde
Status: RESOLVED DUPLICATE of bug 394333
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Network (show other bugs)
Version: Factory
Hardware: x86-64 openSUSE 11.0
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Helmut Schaa
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-07 07:01 UTC by Alexander Lavrinenko
Modified: 2008-05-29 09:55 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Lavrinenko 2008-04-07 07:01:09 UTC
After clean boot no wireless connection possible with NetworkManager and iwl3945-driven wi-fi card (intel/pro, laptop nc6400). NM's KDE applet shows wi-fi AP, but fails to connect to it. Only manual configuration works:
rcnetwork stop
rmmod iwl3945; modprobe iwl3945
ifconfig wlan0 X.X.X.X
iwconfig wlan0 essid <My AP's ESSID>
iwlist wlan0 scan <--- get AP's MAC here
iwconfig wlan0 ap <MAC obtained on previous step>
ip ro add default via Y.Y.Y.Y

My wi-fi setup has no encryption at all (access limited to several MACs), and IPs are assigned via DHCP by access point.
Comment 1 Alexander Lavrinenko 2008-04-11 07:20:04 UTC
Additional info (excerpt from /var/log/NetworkManager):
Apr 11 11:12:35 shark NetworkManager: <info>  User request for activation of wlan0.
Apr 11 11:12:35 shark NetworkManager: <info>  Activation (wlan0) starting connection 'OpenSoft'
Apr 11 11:12:35 shark NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 11 11:12:35 shark NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 11 11:12:35 shark NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 11 11:12:35 shark NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 11 11:12:35 shark NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 11 11:12:35 shark NetworkManager: <info>  Activation (wlan0/wireless): access point 'OpenSoft' has security, but secrets are required.
Apr 11 11:12:35 shark NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 11 11:12:35 shark NetworkManager: <WARN>  get_secrets_cb(): Couldn't get connection secrets: Requested setting is empty.
Apr 11 11:12:35 shark NetworkManager: <info>  Activation (wlan0) failed for access point (OpenSoft)
Apr 11 11:12:35 shark NetworkManager: <info>  Marking connection 'OpenSoft' invalid.
Apr 11 11:12:35 shark NetworkManager: <info>  Activation (wlan0) failed.
Apr 11 11:12:35 shark NetworkManager: <info>  Deactivating device wlan0.

The thing is, that "OpenSoft" AP does not have any security enabled (nor WEP, neither WPA/WPA2). This manual config works well:

[superuser@shark :: /var/log]rcnetwork stop
[superuser@shark :: /var/log]ifconfig wlan0 192.168.1.133
[superuser@shark :: /var/log]ip ro add default via 192.168.1.254
[superuser@shark :: /var/log]iwconfig wlan0 essid OpenSoft
[superuser@shark :: /var/log]iwconfig wlan0 ap 00:0F:EA:68:BF:72
[superuser@shark :: /var/log]iwconfig
wlan0     IEEE 802.11g  ESSID:"OpenSoft"
          Mode:Managed  Frequency:2.412 GHz  Access Point: 00:0F:EA:68:BF:72
          Bit Rate=54 Mb/s   Tx-Power=27 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B
          Encryption key:off
          Link Quality=82/100  Signal level=-54 dBm  Noise level=-87 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
[superuser@shark :: /var/log]ping www.ru
PING www.ru (194.87.0.50) 56(84) bytes of data.
64 bytes from www.ru (194.87.0.50): icmp_seq=1 ttl=56 time=6.00 ms
64 bytes from www.ru (194.87.0.50): icmp_seq=2 ttl=56 time=5.18 ms
^C
--- www.ru ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 5.185/5.595/6.005/0.410 ms
[superuser@shark :: /var/log]
Comment 2 Helmut Schaa 2008-04-17 15:48:36 UTC
Could you please try again with Beta1?
Comment 3 Helmut Schaa 2008-04-22 14:13:00 UTC
Fixed in Beta1.
Please reopen this report if the issue appears again.

Thanks for reporting :)
Comment 4 Alexander Lavrinenko 2008-04-24 03:49:47 UTC
Well, latest update has progress - now KNetworkManager tries to connect after booting and logon, but still fails. Reloading iwl3945 kmod does not help. Stopping network subsystem and manual config works. Here's dmesg part:

...<skipped>...
bootsplash: status on console 0 changed to on
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:0f:ea:68:bf:72
wlan0: RX authentication from 00:0f:ea:68:bf:72 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:0f:ea:68:bf:72
wlan0: RX AssocResp from 00:0f:ea:68:bf:72 (capab=0x421 status=0 aid=1)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:0f:ea:68:bf:72)
wlan0: disassociate(reason=3)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: deauthenticated
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: RX deauthentication from 00:0f:ea:68:bf:72 (reason=6)
wlan0: authenticate with AP 00:0f:ea:68:bf:72
wlan0: RX authentication from 00:0f:ea:68:bf:72 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:0f:ea:68:bf:72
wlan0: RX ReassocResp from 00:0f:ea:68:bf:72 (capab=0x421 status=0 aid=1)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:0f:ea:68:bf:72)
wlan0: disassociate(reason=3)
knetworkmanager[3052]: segfault at 7fff930a3ff8 ip 7ff88476543c sp 7fff930a4000 error 6 in libkdeinit_knetworkmanager.so[7ff884695000+ec000]

My current kernel is:
Linux shark 2.6.25-18-default #1 SMP 2008-04-19 12:46:18 +0200 x86_64 x86_64 x86_64 GNU/Linux
Comment 5 Alexander Lavrinenko 2008-05-28 07:19:37 UTC
Any progress with this? iwl3945 driver still works really unreliable (Beta3Plus), on fresh boot/after resume from STD(R) 'iwlist wlan0 scan' takes ages and sees AP that is 2 meters away two times from 20 (20 runs - only in 2 outputs AP is seen).
Comment 6 Helmut Schaa 2008-05-29 09:55:57 UTC
Duplicate of bug 394333.

Alexander, please write further comments to the bugreport 394333. Thanks.

*** This bug has been marked as a duplicate of bug 394333 ***