NetworkManager won't even try to connect - why?

On my 11.1 system (all latest patches) every time I log in I have to click on the network manager icon in the tray and manually start my wireless connection. Even though in the edited settings for the connection I have the boxed checked off for “Autoconnect”.

Is it a bug in NetworkManager or am I missing something?

If the former, is there a workaround?

Thanks,
Chuck

Getting Your Wireless to Work - openSUSE Forums

could we get you caf to tell us exactly which line of this post

Getting Your Wireless to Work - openSUSE Forums

contains what chuckcintron asks for?

Really that will depend on the wireless device @chuckcintron has?!
Larry’s wireless post should help a user at least provide info we can work with (even if they can’t reslove the issue themselves), simply saying something does not work, gives us, ‘not a right lot to go on’.

@chuckcintron
You should check the settings in Yast - Network devices and see if you are using Networkmanager there to manage the connection.

lspci
lspci -k

will tell us about your device and if a kernel module is in use (assuming it’s not a usb device) otherwise use lsusb

Tell us if you are using WPA or WEP.

thanks caf;

I guess my sense as I read the post

every time I log in I have to click on the network manager icon in the tray and manually start my wireless connection

was that chuckcintron could log on; he was surprised it did NOT autoconnect

Even though in the edited settings for the connection I have the boxed checked off for “Autoconnect”

… that was the way I read it; I am happy to be corrected; I couldn’t see where in Larry’s very comprehensive post it described that feature …

@pdc_2
I see what you mean.
If he wants to auto connect then it should be checked

Appreciate the pointer to the sticky, and yes I have been through this in depth having now become an accidental “expert” on wireless connectivity through my recent experience in getting the T30 laptop to talk to my router with WPA(2) encryption. Many hours of reading, helpful pointers here, and a switch from an older Cisco mini-PCI card to an Intel card (along with a BIOS patch) finally did the trick. I have robust connectivity now, no problems at all with that part.

Yes, in YAST it is telling me that I am definitely using NetworkManager, it’s not a USB device and yes WPA(2) is the protocol…which works fine.

So, the simple question is: "Why, even though autoconnect is clearly selected with an ‘x’ in the box, is NetworkManager not even attempting to connect upon logging in?"

Thanks!
-Chuck

Well all I can say is mine does. Using kde4 BTW not Gnome (not sure what you are)
Just try deleting it and add new
connect and save

Sure, I will try that tonight when I get home from work.

I’m using KDE 3.5

-Chuck

I seem to recall this behavior in 3.5
But it’s a snip to just click, click and your done.
oldcpu uses kde3 and has been extolling the virtues of Linux wireless v. XP - I wonder if he spots this he can comment?

right, it is easy to manually connect every time – but this laptop will be turned over to my right-brained wife as the primary user…I’d like to have a shot at getting it to be as easy to use as possible for her.

For my NetworkManager to work with WPA, I have to first get kwallet running. I don’t like it, but that’s what works.

Well, I tried deleting and re-specifying the wireless connection. No real change, it still doesn’t autoconnect. In fact, it now seems to be intermittent – sometimes it will autoconnect and sometimes it won’t.

I started KDEWallet, but wasn’t really sure how to configure it.

I think this is simply a bug in NetworkManager so will probably have to just live with it.

-Chuck

I have exactly the same issue as Chuck. Clean, fresh opensuse install.

As do I.

kde 3.5

Model: “Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection”

I’ve seen a few different things on this:

cat /etc/modules |grep -i ndiswrapper

if no out put

echo “ndiswrapper” >> /etc/module

Didn’t do it for me.

NetworkManager is buggy with this chipset, turn it off.

Didn’t do it.

Select “AutoConnect” in NetworkManager under Edit Connections for your wireless interface.

It won’t save.

I’m looking for 11.1 kde 3.5 to automagically connect, optimally upon boot,but upon logging in would be acceptable.

I’ll install third party software or rig scripts if necessary, but it should work out of the box, or at least with a little system specific tweaking.

I have a Toshiba Satellite u305-s5107. I just installed 11.1 and got the latest updates.

Linux linux-jtgs 2.6.27.25-0.1-pae #1 SMP 2009-07-01 15:37:09 +0200 i686 i686 i386 GNU/Linux

mpemba wrote:
> As do I.
>
> kde 3.5
>
> Model: “Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection”
>
> I’ve seen a few different things on this:
>
> cat /etc/modules |grep -i ndiswrapper
>
> if no out put
>
> echo “ndiswrapper” >> /etc/module
>
> Didn’t do it for me.
>
> NetworkManager is buggy with this chipset, turn it off.
>
> Didn’t do it.
>
> Select “AutoConnect” in NetworkManager under Edit Connections for your
> wireless interface.
>
> It won’t save.
>
> I’m looking for 11.1 kde 3.5 to automagically connect, optimally upon
> boot,but upon logging in would be acceptable.
>
> I’ll install third party software or rig scripts if necessary, but it
> should work out of the box, or at least with a little system specific
> tweaking.
>
> I have a Toshiba Satellite u305-s5107. I just installed 11.1 and got
> the latest updates.
>
> Linux linux-jtgs 2.6.27.25-0.1-pae #1 SMP 2009-07-01 15:37:09 +0200
> i686 i686 i386 GNU/Linux

The answer to the question in the subject is that it doesn’t see your
AP. To find out why, post the output of


dmesg | egrep "firmware|4965"
/usr/sbin/iwconfig
sudo /usr/sbin/iwlist scan

If all else fails, you might need to add the repository at

http://download.opensuse.org/repositories/home:/Akoellh/openSUSE_11.1_Update/

and add the wireless-compat package for your kernel.

Thank you for responding to my question, any and all help is much appreciated.

dmesg | egrep “firmware|4965”
iwlagn: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
firmware: requesting iwlwifi-4965-2.ucode

Having a little trouble posting the rest of the output.
I keep getting “you are trying to post seven images”.
I’ve tried putting it through text editors to strip out any weird control characters, but it won’t let me. I’m going to try and peicemeal it one command at a time.

/usr/sbin/iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11abgn ESSID:“MidnightLanding”
Mode:Managed Frequency:2.412 GHz Access Point: 00:1F:90:DB:6D:C8
Bit Rate=54 Mb/s Tx-Power=14 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Power Management:off
Link Quality=62/100 Signal level:-67 dBm Noise level=-92 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

aha, it’s the stupid smileys

sudo /usr/sbin/iwlist scan
lo Interface doesn’t support scanning.

eth0 Interface doesn’t support scanning.

wmaster0 Interface doesn’t support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1F:90:DB:6D:C8
ESSID:""
Mode:Master
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=55/100 Signal level:-70 dBm Noise level=-92 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000026b5b78181
Extra: Last beacon: 44ms ago
Cell 02 - Address: 00:1A:70:DB:9C:3C
ESSID:“linksys_SES_38596”
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=52/100 Signal level:-77 dBm Noise level=-127 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=00000026b6c776db
Extra: Last beacon: 2904ms ago