https://bugzilla.novell.com/show_bug.cgi?id=372878
User gfarrell@netspeed.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=372878#c41
Geoff Farrell changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gfarrell@netspeed.com.au
--- Comment #41 from Geoff Farrell 2008-06-15 06:34:30 MDT ---
This particular combination (Dell 1720, Intel PRO/Wireless 3945ABG) has not
been able to connect under 10.3, or openSUSE11.0-RC1-KDE4-LiveCD-i386, until
11.0-RC1 was updated from the 'oss' and 'non-oss' repositories. The relevant
packages were updated to:
kernel-default-2.6.25.5-1.1
NetworkManager-0.7.0-r3685-5
NetworkManager-glib-0.7.0-r3685-5
NetworkManager-kde-0.7-r815970-3
iwl3945-ucode-2.14.1.5-50
The kernel-default was updated first, by itself, then the computer was
re-booted. As soon as KDE became established, the wireless tray icon identified
a successful connection, without any action by the user. There were three
separate icons in the tray regarding network connections (as was the case with
the standard 11.0-RC1 packages. Then the NetworkManager and iwl3945-ucode
packages were updated. Immediately, the wireless connection was lost, and
couldn't be regained just by re-booting or restarting NetworkManager. The
following sequence shows the steps taken in troubleshooting the wireless
connection. 'Item' numbers refer to paragraph numbers in the attachment.
Overall summary, in sequence:
1. Initial attempt at connection on first boot did not connect wlan0 to WAP
(Item 6).
2. First attempt at connection using 'KNetworkManager tray icon-> Connect to
other network-> FarNet' did not work. It seems that exchange of 'connection
secrets' was unsuccessful (Item 7).
3. Next attempt at connection using 'KNetworkManager tray icon-> Edit
Connections-> FarNet-> Edit Connection, completing info, then-> Connect & Save'
worked. This was probably because the correct WPA passphrase was entered
instead of the existing 64-char hex string (Item 8). Despite this, subsequent
entry into this dialog showed the same 64-char hex string (Item 10). This did
not prove to be a barrier to future connections.
4. Selecting 'KNetworkManager tray icon-> Deactivate connection-> FarNet
(wlan0)' did not deactivate the connection (Item 11).
5. Selecting 'KNetworkManager tray icon-> Deactivate connection-> Disable
wireless' did disable the connection (Item 12).
6. Selecting 'KNetworkManager tray icon-> Deactivate connection-> Enable
wireless' successfully re-started the connection (Item 14).
7. Selecting 'KNetworkManager tray icon-> Connect to other network-> FarNet'
successfully stopped/started the connection (Item 16).
8. Selecting 'KNetworkManager tray icon-> Edit Connections-> FarNet-> Edit
Connection, completing info, then-> Connect & Save' - leaving Shared Key at the
64-character version - successfully stopped/started the connection (Item 18).
9. After re-booting the computer, the connection was established automatically,
very quickly after KDE started; no user intervention was required (Item 20).
*** Observations.
1. The 'FarNet' Shared Key had been entered with the original
11.0-RC1-KDE4-LiveCD-i386 version of KNetworkManager (NetworkManager-kde),
before the updated version was installed from the 'oss' repository
(NetworkManager-kde-0.7r815970-3). It probably had to be re-entered before the
new version stored it correctly, or could access it correctly. After this,
wireless connections performed without fault.
2. Regardless of 1a, it is confusing to the user to see the 'wrong' Shared Key
in that dialog. This seems to be a regression from 10.3, which showed this
behaviour. The original 11.0-RC1 version distributed in the LiveCD showed the
'correct' ASCII Shared Key (in the user's eyes, at least). This behaviour could
have been introduced in the bringing together of the tray icons, which was
mentioned in the ChangeLog for the updated version.
3. The default location of 'wpa_supplicant.conf' (at
/etc/wpa_supplicant/wpa_supplicant.conf') is probably wrong. NetworkManager
works correctly in the traditional /etc/wpa_supplicant.conf location.
4. Correct operation of NetworkManager in connecting to an Intel PRO/Wireless
3945ABG device has been confirmed.
--
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.