Network Manager only showing status - not allowing control

English Network/Internet
1

Just moved back to openSUSE 11.0 last night (tried that whole Gentoo thing, for a few weeks, but was too impatient for the compile times).

Installed from the DVD. As soon as the installer was done and a user (me) logged in, my wireless worked (as expected). So I go through and tell YaST to fetch the updates. If it matters, immediately afterwards I hooked up to the XOrg:X11 and Packman repositories and updated all that stuff as well.

Anyway, rebooted, now Network Manager (or at least KNetworkManager) is more or less useless. The globe turns green when I plug into the wired network, but if I right click on it, I get the following:

New Connection…
Deactivate Connection >
Configure Notifications
Edit Connections
Quit

If I click New Connection, absolutely nothing happens. Nothing.

Clicking Deactivate Connection only gives the option for switching to offline mode.

Going to Edit Connections shows the wifi setup from last night (my home network), but, once in there, if I tell it to connect to said saved connection, nothing happens.

For the past year or so, I’m used to having the network Just Work on this thing, and this is the only distro I’ve used with NetworkManager 0.7*, so I’m at a bit of a loss. Any help is appreciated.

dirty details:

software:
openSUSE 11.0 i686
2.6.25.11-0.1-default
NetworkManager-kde-0.7r821737-0.3
NetworkManager-0.7.0.r3685-7.1
NetworkManager-glib-0.7.0.r3685-7.2
iwl3945-ucode-2.14.1.5-50.1

hardware:
Lenovo Thinkpad T60 type 2007
Intel Pro/Wireless 3945 ABG
(yes, the wifi switch is on and has been)

Let me know what other information you need.

Oh, and, for the record, I didn’t throw this in the “Wireless” category since the applet won’t let me connect/disconnect from the wired network. Sometimes it connects by itself, sometimes I need to do “#ifconfig eth0 up”.

2

I don’t know how much it’ll help, but here’s some system output:

jeffro@jeffro-lappy:~> dmesg | grep wlan                                                                                                                               
ADDRCONF(NETDEV_UP): wlan0: link is not ready                                                                                                                          
wlan0: Initial auth_alg=0                                                                                                                                              
wlan0: authenticate with AP 00:16:01:84:2b:16                                                                                                                          
wlan0: RX authentication from 00:16:01:84:2b:16 (alg=0 transaction=2 status=0)                                                                                         
wlan0: authenticated                                                                                                                                                   
wlan0: associate with AP 00:16:01:84:2b:16                                                                                                                             
wlan0: authentication frame received from 00:16:01:84:2b:16, but not in authenticate state - ignored                                                                   
wlan0: RX AssocResp from 00:16:01:84:2b:16 (capab=0x401 status=0 aid=2)
wlan0: associated
wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: disassociate(reason=3)
wlan0: no IPv6 routers present
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: RX disassociation from 00:16:01:84:2b:16 (reason=7)
wlan0: associate with AP 00:16:01:84:2b:16
wlan0: RX ReassocResp from 00:16:01:84:2b:16 (capab=0x401 status=0 aid=2)
wlan0: associated
wlan0: disassociate(reason=3)
3

well, I’m even more confused now.

My brother’s laptop (an older Dell of some sort) also has openSUSE 11.0 on it. Aside from his wireless being referred to as eth0 and his ethernet port being eth1, his networking was fine out of the box, and did until the other day when he did a system-wide update.

Different laptop, different wireless card (ipw2200), different errors in dmesg (but still getting errors) but same symptoms as me.

I guess I’m just going to revert back to default install on the kernel, modules, NetworkManager, and all applets. Hopefully that’ll get me back to what worked, and I can try individual packages to see what broke it.

…unless someone has a better idea?

4

well, crap. I downgraded everything back to the versions from the normal OSS repo, but still no dice. Is there some other program in the network stack that I’m overlooking?

5

Decided to try something…

eth0 seems to work. Kinda. If it’s plugged in, it usually sets itself up. Should the network act up, I just do the following:

jeffro-lappy:/home/jeffro # ifconfig eth0 down
jeffro-lappy:/home/jeffro # ifup eth0
Network interface is managed from NetworkManager
NetworkManager will be advised to set up eth0
but it cannot be assured from here.
jeffro-lappy:/home/jeffro # ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:16:41:56:3C:9D
          inet addr:192.168.1.120  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5017 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3544 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:6173639 (5.8 Mb)  TX bytes:394809 (385.5 Kb)
          Memory:ee000000-ee020000

So, it looked to me like maybe it was on the client side, since the output of ifup eth0 says that it’ll tell NetworkManager to bring the interface up, and, sure enough, it does get brought up.

So I tried a couple different clients. Same results. Here’s my original (and persisting) condition:

http://img.photobucket.com/albums/v494/NotAnAvrageLoser/networkfail/knetworkmanagerfail.jpg

Here’s what happened when I tried Novell’s own KInternet

http://img.photobucket.com/albums/v494/NotAnAvrageLoser/networkfail/kinternetfail.jpg

For the heck of it, I tried KWiFiManager, and here’s what I got.

http://img.photobucket.com/albums/v494/NotAnAvrageLoser/networkfail/kwifimanagerfail.jpg

KWifiManager acknowledges the network interface. It even says that it connects to my wireless network. But it doesn’t get assigned an IP address.

I also put Gnome on here since I have disk space to burn to try out the networkmanager-gnome applet. But, I have no idea what I’m doing with that.

Either way, I’m at a loss. It seems like it’s a lower-level software problem/issue. Like I said in a previous post, my brother’s laptop is exhibiting the same symptoms a day after mine started acting up. His is a dual-boot with Windows XP, and everything works fine (well, as fine as it can) under that OS. Mine works fine with a Kubuntu 8.04.1 live cd popped in. It’s something openSUSE related, I’m just out of ideas.

6

Hi!

I’m having the exact same problem here. The kde update I did at the beginning of September broke KNetworkManager: There are no options anymore if I login as a user. However, if I login as root, all is normal.

So I thought it might be a permission problem. To check this, I created a new user and assigned it to all groups. But that didn’t help either.

So the workaround is: If I login as a user, I quit KNetworkManager, open a shell, su to root, start KNetworkManager as root, and close the shell. Then I have a working KNetworkManager.

Furthermore, there is an interesting difference between the output of KNetworkManager when I start it as root or as a user:

As user:
NMSettings::NMSettings
restore setting: ConnectionSetting_up0P8IJ1GCASGkjh_connection
restore setting: ConnectionSetting_up0P8IJ1GCASGkjh_ipv4
restore setting: ConnectionSetting_up0P8IJ1GCASGkjh_ppp
restore setting: ConnectionSetting_up0P8IJ1GCASGkjh_gsm
restore setting: ConnectionSetting_up0P8IJ1GCASGkjh_serial
restore secret: ConnectionSecrets_up0P8IJ1GCASGkjh_gsm

As root:

NMSettings::NMSettings
restore setting: ConnectionSetting_CfXQ3jHMm85XybzB_connection
restore setting: ConnectionSetting_CfXQ3jHMm85XybzB_ipv4
restore setting: ConnectionSetting_CfXQ3jHMm85XybzB_ppp
restore setting: ConnectionSetting_CfXQ3jHMm85XybzB_gsm
restore setting: ConnectionSetting_CfXQ3jHMm85XybzB_serial
restore secret: ConnectionSecrets_CfXQ3jHMm85XybzB_gsm
Connection::GetSettings, obj: /org/freedesktop/NetworkManagerSettings/Connection/0
Processing Setting ‘connection’
Attach setting ‘connection’
autoconnect: <bool>false</bool>
id: <string>mobile</string>
timestamp: <uint32>1221038656</uint32>
type: <string>gsm</string>
Processing Setting ‘ipv4’
Attach setting ‘ipv4’
method: <string>dhcp</string>
Processing Setting ‘ppp’
Attach setting ‘ppp’
baud: <uint32>0</uint32>
crtscts: <bool>false</bool>
lcp-echo-failure: <uint32>0</uint32>
lcp-echo-interval: <uint32>0</uint32>
mpppe-stateful: <bool>false</bool>
mru: <uint32>0</uint32>
mtu: <uint32>0</uint32>
no-vj-comp: <bool>false</bool>
noauth: <bool>false</bool>
nobsdcomp: <bool>false</bool>
nodeflate: <bool>false</bool>
refuse-chap: <bool>false</bool>
refuse-eap: <bool>false</bool>
refuse-mschap: <bool>false</bool>
refuse-pap: <bool>false</bool>
require-mppe: <bool>false</bool>
require-mppe-128: <bool>false</bool>
Processing Setting ‘gsm’
Attach setting ‘gsm’
band: <int32>0</int32>
network-type: <int32>0</int32>
number: <string>*99#</string>
Processing Setting ‘serial’
Attach setting ‘serial’
baud: <uint32>115200</uint32>
bits: <uint32>8</uint32>
parity: <byte>110</byte>
send-delay: <uint64>0</uint64>
stopbits: <uint32>1</uint32>
Connection::GetSettings, obj: /org/freedesktop/NetworkManagerSettings/Connection/0
Processing Setting ‘connection’
Attach setting ‘connection’
autoconnect: <bool>false</bool>
id: <string>mobile</string>
timestamp: <uint32>1221038656</uint32>
type: <string>gsm</string>
Processing Setting ‘ipv4’
Attach setting ‘ipv4’
method: <string>dhcp</string>
Processing Setting ‘ppp’
Attach setting ‘ppp’
baud: <uint32>0</uint32>
crtscts: <bool>false</bool>
lcp-echo-failure: <uint32>0</uint32>
lcp-echo-interval: <uint32>0</uint32>
mpppe-stateful: <bool>false</bool>
mru: <uint32>0</uint32>
mtu: <uint32>0</uint32>
no-vj-comp: <bool>false</bool>
noauth: <bool>false</bool>
nobsdcomp: <bool>false</bool>
nodeflate: <bool>false</bool>
refuse-chap: <bool>false</bool>
refuse-eap: <bool>false</bool>
refuse-mschap: <bool>false</bool>
refuse-pap: <bool>false</bool>
require-mppe: <bool>false</bool>
require-mppe-128: <bool>false</bool>
Processing Setting ‘gsm’
Attach setting ‘gsm’
band: <int32>0</int32>
network-type: <int32>0</int32>
number: <string>*99#</string>
Processing Setting ‘serial’
Attach setting ‘serial’
baud: <uint32>115200</uint32>
bits: <uint32>8</uint32>
parity: <byte>110</byte>
send-delay: <uint64>0</uint64>
stopbits: <uint32>1</uint32>

Any help is greatly appreciated. My versions:

yast2-network-2.16.48-3.1
NetworkManager-kde-0.7r821737-0.3
yast2-network-devel-doc-2.16.48-3.1
NetworkManager-glib-0.7.0.r3685-7.1
kdenetwork3-news-3.5.10-3.4
kdenetwork3-3.5.10-3.4
NetworkManager-0.7.0.r3685-7.1
NetworkManager-devel-0.7.0.r3685-7.1
kdenetwork3-InstantMessenger-3.5.10-3.4

(No, upgrading to NetworkManager-0.7.0.r3685-7.2 does not help, in contrary, it breaks my USB modem connection ability.)

7

Did you make sure that under network settings you have our cards set to “managed” and not “ifup”.

8

Yes, absolutely. It is not ifup, it is managed.

9

Same here. Both machines set to “user controlled via KInternet” rather than ifup.

And lotlorien, thanks for the heads up. I’ll try that in a little bit.

10

yep, invoking KNetworkManager as root does the trick. It’s kind of a crappy work-around, but it’ll get me through (hardly any ethernet ports on campus).

still… anyone know what’s causing this?

11

Hi again!

I made another interesting discovery: I can not play DVDs anymore as a normal user, only as root. There is some error message about possibly missing rights.

I once had created a new user and had it assigned to all groups with no success, but I’m almost sure by now that I’m missing something here…

Please help!

12

Hi,

Sorry to say it but I am happy that I am not alone with this problem…

It first occurred some point in August on my laptop and when my sister ran a much needed update (few days ago) it occurred on her’s.

Connections with ethernet or wireless (b43 driver) didn’t happen for some reason and I couldn’t be bothered to go out of my way to setup network login before kdm loads.

I tried this:

modifying my user groups/rights (no success)
new user with root access (other problems)
running knetworkmanager as root (variable success)
knetworkmanager is saving my passwords in ~/.kde somewhere (found out by removing)
logging in as root (worked, but insecure)
reinstalling the versions from the 11.0 disk (no success) (networkmanager and it’s dependencies)

I found a strange work around
Ctrl+Alt+F1, login
remove ~/.kde4 and log in through kdm(or equivalent)
I think a startup script is ‘fixing’ this problem temporarily but have no idea how it is as when I restart the problem returns.

This has been accompanied by my sisters sound breaking (no permission to access device)

I have my suspicions that somebody has been toying with user permissions (myself or a SuSE update) I can recommend my sister run as root as that offers her more freedom/reliability/speed than Vista, not vista trouncing, she hates it, not me.

I won’t run as root (paranoia) as I can run a prog as root or tolerate this ‘fix’ I found but my sister isn’t as technologically minded.

Thanks for any help anyone can suggest,

Rob

13

downloaded a bunch of updates yesterday and restarted this morning and wireless is gone.

I’ve read all the threads and tried everything in there. Ethernet works (wired) and right now I have networkmanager turned off.

Maybe this will be fixed in an update, but I’m disappointed that Suse would release updates that break wireless. I know they are doing this incrementally and something is bound to break (I’m talking about KDE4.1.1 thru factory) but is disappointing nonetheless.

I suppose this is the price for being cutting edge and I’m sure a later update will fix this.

I installed Gnome – impressed with the interface – just to see if that might install a fix for networkmanager but it fails there as well.

I followed the advice in another thread and turned off networkmanager to configure manually, but that only made things worse.

Will restart knetworkmanager in Yast and reconfigure by deleting current settings rebooting and starting fresh.

Not asking for help at this point but I wanted to keep this thread going for future reference.

I have an acer laptop with the broadcom 43xx chip. It is recognized.

14

I had this same problem and after hours and hours of digging I think I finally found some clues to the origin of it.

Audio, dvd, NetworkManager etc all depend on resmgrd (check out the manpage!) to track your login and give you ownership of the hardware devices and dbus permissions.
For some reason this seems to fail. To check that this is indeed the root of your problem look into /var/run/resmgr/classes when you are logged in as your user, if it’s empty (bad!), this post is for you.

How to fix it? You can use resmgr (note, no “d” at the end) to get resmgrd to do what it should have done when you logged in. Read the manpage, it has an example which should help you out. If you are of the more reckless persuasion and execute random code posted in forums, you could just type the following into a console:

sudo resmgr login username $DISPLAY

where you should replace “username” by your actual username.

In theory pam_resmgr should do this for you when you log in from kdm/gdm/… but for some strange reason this does not happen. If anybody figures out why that’s the case, I’d like to hear about it :slight_smile:

Note that you probably will have to repeat this after every login (this is assuming the logout is actually noticed by resmgrd). I haven’t tested that yet since I’m writing this post and have no intention of logging out anytime soon :wink:

15

Excellent that works. Now if someone could figure out why this has happened that would be great. For the moment though at we know a temporary fix. It should hopefully help find a way to fix the problem. :slight_smile:

16

Hi All!

Great news! Just right now I did an update and everything works again - NetworkManager, DVD, CD, etc.! I updated the following packages:

ffmpeg
gstreamer-0_10-plugins-good
libavcodec52
libavdevice52
libavformat52
libavutil49
libffmpeg0
libpostproc51
libswscale
x11-input-synaptics
x11-input-wacom
x11-input-wacom-tools
xkeyboard-config
xorg-x11
xorg-x11-Xvnc
xorg-x11-driver-input
xorg-x11-driver-video
xorg-x11-driver-video-radeonhd
xorg-x11-driver-video-unichrome
xorg-x11-fonts
xorg-x11-fonts-core
xorg-x11-libX11-ccache
xorg-x11-server
xorg-x11-server-extra
xterm

They were chosen automatically for update when I selected in Software Management to update all packages that have a later version. These updates have appeared in the last 24 hours. I have subscribed to about 15 software repositories (from the build services), among others XOrg.

When I see in one of the previous posts that something related to $DISPLAY fixes things, I suppose that some x11 updates in the past broke something, and now these packages have been fixed.

Apart from this, I also fixed that Amarok didn’t fade in and out. If you have the same issue, you have to install amarok-xine and use the xine engine, and not the yauap engine, in Amarok.

Have a good day!

17

Good deal. Thanks for posting this. Are you using the factory repos as well as buildservice? I was about to try the fix discussed above when I read your post about the updates today.

Can’t wait to get home and see if it fixed my machine.

18

Well the resmgr fixed things when I ran that.
(THANK YOU!!! :slight_smile: )

And after running a large update everything now seems to work properly.
(although I’m non the wiser what I broke and what the update might of)

Most of my other problems have now been fixed as well.

Yey for the SuSE developers!!! :smiley: :smiley:

19

Well, still not sure what broke, but it’s fixed. Did a global update a couple days ago and all’s well.

Well, I guess that’s what I get for being diligent on updates…

Either way, thanks devs!

20

I’m not willing to cheer them yet. Releasing an incomplete update or one with dependencies that cannot be resolved is a good way to run people back to Ubuntu or PCLinuxOS. :frowning: