-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kai Ponte wrote: > On Saturday 22 September 2007 23:09, Andrés Cosa wrote: >> Hi, I installed open suse 10.3 beta 3. After a week I managed to have >> the wireless working. Yesterday gnome update downloaded heaps of updates > > <snip> > >> WIRELESS_MODE='Managed' > > Isn't this stating that you have Network Manager doing your dirty work? > IIRC, "managed" means you're not using ifup and ifdown. Or is that 'ad_hoc' > setting? > > >> WIRELESS_WPA_PASSWORD='' >> WIRELESS_WPA_PSK='pskkey' > > I wonder if this might be an issue, too? > >
I dont think WIRELESS_MODE has anything to do with network manager. I think 'Managed' is a synonym for what is called 'Infrastructure' mode. I do not use network manager, and I have these settings. (My experiments with network manager did not impress me with it). WIRELESS_WPA_PSK is correct if pskkey is the ahared key, and the there is nothing wrong with the other setting. These settings are used only if the authorisation mode is set to a mode which requires them (which is kind of handy). The error messages seem to indicate a problem with wpa_supplicant, rather than the device driver, I would ifdown then ifup to test this, a previously broken connection can cause problems. A likely issue is that from some reason wpa_supplicant is either being passed the wrong device info, or is broken for that device, It is also possible the device driver WPA support is broken. I would be a bit worried the device being identified as 'Intel LAN Controller' rather than a specific piece of hardware e.g. "Intel PRO/Wireless 2200BG" (this could suggest use of a generic driver rather than a specific driver). If it is possible I would try and isolate wpa_supplicant as the problem from the device driver. My experience with wpa_supplicant suggests that it can be very twitchy about hardware. I would look a bit more closely at what driver is in use. You may find that you have to create your own load script to get a working configuration. (I do not have your Intel wireless hardware, but I do have intel hardware). In my case I use hwup in a script to initially load my WiFi. (and use ifup, ifdown, ifconfig, iwconfig etc thereafter). The problem was with all these tools to work was that the network device name has to be assigned, and hwup forced the assignment of the device name that was not being assigned on boot which was one of my problems. (9.3 did load OK but before the days of udev I never knew which device name was being associated with which bit of hardware). - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG93WwasN0sSnLmgIRAtDqAJ9nmcDiXhwtdtN2VBmekYXyFv98UgCgsK2M 30gTMmxG5nGbepYT0VPdqSU= =A7zv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
