KNetworkmanager doesn't work

[Ben_Cook2]

I have this problem too. Coincidentally I also rebooted when I started to have problems, but that was under a different user.

Today, KNetworkManager appears to be totally useless, I am searching for a replacement. It could be D-Bus issues, likely permissions

[Ben_Cook2]

I did some searching on bugzilla, and found one that fits our problem(s)

https://bugzilla.novell.com/show_bug.cgi?id=444740

[essl]

Don't really know what fixed it, did two things:
Removed vmware networks.
Removed networkmanager-kde4 package (left the kde3 version).

[Ben_Cook2]

I found an instant solution: switch to ifup and install wicd

You can search for it at software.opensuse.org/search

Works beautifully for me and my WPA-PSK network, no more fighting with network manager any more.

[coomac]

If the kde3 knetworkmanager is not accepting clicks, it's because the kde4 version is installed and the two can't co-exist. Remove networkmanager-kde4 and the problem should be solved.

[indetek]

I have this same problem. Here is the work around I have been using.

Using KNetwork Manager, I select the wireless network that I want to connect to. When the status bar appears it goes to 28%. I have a manual on/off switch for my wirelss card on my laptop. I turn the power switch off and then right back on. The wireless card initializes and makes the connection.

I know this work around is cheezy but it works for me every time. It would be nice to have an actual fix for this but, well...

[lwfinger]

indetek wrote:
> I have this same problem. Here is the work around I have been using.
>
> Using KNetwork Manager, I select the wireless network that I want to
> connect to. When the status bar appears it goes to 28%. I have a manual
> on/off switch for my wirelss card on my laptop. I turn the power switch
> off and then right back on. The wireless card initializes and makes the
> connection.
>
> I know this work around is cheezy but it works for me every time. It
> would be nice to have an actual fix for this but, well...

When you do all of this, what is logged? The 'dmesg' command will dump the log.

Larry

[indetek]

How do I dump to txt file?

[indetek]

This is logged with the radio left on:

r8169: eth0: link down

This is logged with the radio turned off:

r8169: eth0: link down
ipw3945: Radio Frequency Kill Switch is On:
Kill switch must be turned off for wireless networking to work.
atkbd.c: Unknown key pressed (translated set 2, code 0xf1 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e071 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xf1 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e071 <keycode>' to make it known.
ipw3945: Error sending ADD_STA: time out after 500ms.
ipw3945: Error sending RATE_SCALE: time out after 500ms.
ipw3945: Error sending ADD_STA: time out after 500ms.
ipw3945: Error sending RATE_SCALE: time out after 500ms.


And this is logged with my work around:

r8169: eth0: link down
ipw3945: Radio Frequency Kill Switch is On:
Kill switch must be turned off for wireless networking to work.
atkbd.c: Unknown key pressed (translated set 2, code 0xf1 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e071 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xf1 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e071 <keycode>' to make it known.
ipw3945: Error sending ADD_STA: time out after 500ms.
ipw3945: Error sending RATE_SCALE: time out after 500ms.
ipw3945: Error sending ADD_STA: time out after 500ms.
ipw3945: Error sending RATE_SCALE: time out after 500ms.
atkbd.c: Unknown key pressed (translated set 2, code 0xf1 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e071 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xf1 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e071 <keycode>' to make it known.
ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels)
martian source 255.255.255.255 from 192.168.1.1, on dev eth1
ll header: ff:ff:ff:ff:ff:ff:00:0f:66:bc:40:8d:08:00
martian source 255.255.255.255 from 192.168.1.1, on dev eth1
ll header: ff:ff:ff:ff:ff:ff:00:0f:66:bc:40:8d:08:00

[lwfinger]

indetek wrote:
> This is logged with the radio left on:
>
> r8169: eth0: link down
>
> This is logged with the radio turned off:
>
> r8169: eth0: link down
> ipw3945: Radio Frequency Kill Switch is On:
> Kill switch must be turned off for wireless networking to work.
> atkbd.c: Unknown key pressed (translated set 2, code 0xf1 on
> isa0060/serio0).

The log says that your radio kill switch is on when the system starts. Why, I do
not know, but your workaround may be what you have to do. The other option is to
turn it off before booting, then on when the system starts.

Larry