knetworkmanager not starting correctly

[1Daemon]

Hi all, I've gotten much useful information from this forum (thanks for the posts ) and I have finally decided to join.

Here's my first question:
Wherever since I have installed suse10.2 the knetworkmanager wasn't recognizing networks until I shut down the kde (init 3) and started it up again, after that it was working great.
I just recently got my wireless to work (with the help from this forum, thanks again!) but now I have to reload the kde after every reboot to use it.
Any ideas what the problem might be?


Cheers

[gatekeeper]

Yea i have noticed that happening to my system too. I have Suse 10.2 with everything updated, plus the updated version of ndiswrapper. An answer would interest me as well to that ...

[aliov]

I have an idea,

My problem what little bit similar but with glx,when i boot i can't use direct rendering unless i restart kde!, the problem was related to the permission.to see if your problem is as mine from the first boot go to the terminal and try to connect to internet from the command line as user first and the as root(to do it as root open a terminal a do su - and enter your password) .the commands are the following

iwconfig eth1 essid (the name of you network) mode managed
iwconfig eth1 key (your key can be off if you don't have a key)
dhcpcd eth1

eth1 is the name of your wireless it can be something else! to see simply type iwconfig and see wish interface is a wireless extension. if you can connect from the first boot only as root so the problem is related to the setup of the permissions during kde boot.

reply me to see what we can do


Hope this help.

[1Daemon]

Thank you for your reply aliov!

I tried to set up over command line but somehow it doesn't work.
After typing:
iwconfig eth1 essid (the name of you network) mode managed
and iwconfig again, it still shows
eth1 Auto ESSID: off/any

I tried to input the key (password) with
iwconfig eth1 key s:<pswd>
as described in man iwconfig but it's telling me "Invalid argument" (I'm using WPA TKIP encoding)
also, is there a way to display all available essids with iwconfig? Couldn't find anything in the manual...

Oh, one more thing... when I connect to the network via cable it connects even though knetworkmanager doesn't show a connection. After restarting kde it does show the connection... seems to be the same issue.

Cheers!

[aliov]

First to scan for the network wifi in range do:
iwlist eth1 scan.


for the iwconfig try to commit the arguments entered with.

iwconfig eth1 essid (.....) mode managed commit

Because some network need to save the changed configuration.

for setting the key try : invalid argument means that something is wrong in your command so simply try iwconfig eth1 key [................] without the s:.... ASCII strings. and tell me what will happen in this case,

Cheers,
Hope this help.

[1Daemon]

The commit parameter didn't do it either. Unless of course iwconfig only shows the essid when it's already connected...
I tried entering the key just as a string and with brackets but it didn't work. I think I need to setup WPA support first.

You said earlier it was a problem with permission, how do I resolve that? If I can get knetworkmanager to work right after reboot, I won't have to do it over command line anyway

Cheers.

[aliov]

My suggestion to connect fro the command line was only to see if you can connect without restart KDE. in any case please try from the first boot to login as a root and then try to connect via Knetworkmanager , and tell me about any news.

[1Daemon]

How do you log in from the very first login screen as root?

[aliov]

You should have the KDM, if not then it's seems that you'r login directly after the boot,so disable login automatically by using YaST (probably it's under the users configuration), and then reboot the system a try to login as a root.

Cheers,

[1Daemon]

Ok, I've logged in as root and knetworkmanager worked properly.
I've also found another way without rebooting the kde. I closed down the instance of knetworkmanager loaded up at the beginning and opened one from the console as root and it worked, so it's definately a permission issue. Now, how do I edit the permissions for processes loaded up at bootup?

Cheers.