Hi
Since two week the knetworkmanager needs 3 minutes after login to start and connect. On an other computer (x86) it works fine. What could be the reason for this? I use opensuse 11.3 x64 and yes i need the network manager. Ifup isn’t practicable for me.
I have read in some thread to start the networkmanager at boot time and as root, but i don’t think this is necessary.
I would be glad if someone has any suggestions?
regards odesu
Use ifup and WICD, set WICD to run at boot in runlevels. Uninstall networkmanager.
Thanks! Wicd is fine but doesn’t support vpn connections.
Any other suggestions?
regards odesu
Hi there,
just to understand: What do you mean by this ? Does it need 3 minutes to get connected after you clicked on your Wireless Network in the control-panel-app-menu ?
Regards, user2304.
There is a way to manually get knetworkmanager started early. Must say though it’s a hack that’s gone on each KDE update to a next version.
Here it is:
Open a terminal window, and do:
su -c 'cp /usr/bin/startkde ~/Desktop/OLDSTARTKDE
kdesu kwrite /usr/bin/startkde
FIrt line asks for the rootpassword, then makes of copy of the file to edit to your Desktop folder.
The second asks for the rootpassword, then shows you kwrite (with rootpermissions) with /usr/bin/startkde opened for editing
Now change the next line:
LD_BIND_NOW=true /usr/lib64/kde4/libexec/start_kdeinit_wrapper +kcminit_startup
to:
LD_BIND_NOW=true /usr/lib64/kde4/libexec/start_kdeinit_wrapper +kcminit_startup +knetworkmanager
On my laptop the connection to a known wireless network is established before the systemtray even shows up. If I’m lucky I’ll see the notification fade away as a first sign of the desktop.
Hope this helps you. But it may very well be some problem with VPN as well. Please let us know.
Hi user2304,
thanks for you question.
No, after i login with my username and after all other programms shown in my task window are loaded, i click on the knetworkmanager icon with the mouse. Then a menu with the message ‘Network is deactivated’ pops up and there is nothing else to select or click on. Now i have to wait for about three minutes and then the knetworkmanager become active, begins to search for a connection and connect to my cable connection.
Sorry for my poor english, but i hope the problem is now clear enough.
regards, odesu
Some additional to the problem:
It doesn’t matter if i connect to a wireless or cable network. After the knetworkmanager is running switching the connection works without the delay.
Why are there always problems with the knetworkmanager? Since i use opensuse 11.2 the problems with it go on and off. Earlier i used Ubuntu with the gnome networkmanager and i could not remember any problems with it.
again regards, odesu
@ Knurpht
Thanks for the possible way to fix this. I will try it at weekend and will post my results.
regards, odesu
Hi
Sorry for my really late response.
@ Knurpht: I tried your recommendation with ‘+knetworkmanager’ but it don’t made a difference.
So it try some things, but without success:
Test with a new user account. The equal behaviour. So I think it hasn’t anything to do with the user settings.
Having a look on dmesg:
34.833746] nvidia: module license 'NVIDIA' taints kernel.
34.833749] Disabling lock debugging due to kernel taint
35.294217] RPC: Registered udp transport module.
35.294219] RPC: Registered tcp transport module.
35.294220] RPC: Registered tcp NFSv4.1 backchannel transport module.
35.301255] Slow work thread pool: Starting up
35.301295] Slow work thread pool: Ready
35.301312] FS-Cache: Loaded
35.312712] FS-Cache: Netfs 'nfs' registered for caching
35.529337] nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
35.529351] nvidia 0000:01:00.0: setting latency timer to 64
35.529362] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
35.529712] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 256.53 Fri Aug 27 20:27:48 PDT 2010
35.715630] ACPI Warning for \_SB_.PCI0.PEGP.DGFX.MXMI: Excess arguments - needs 1, found 2 (20100121/nspredef-319)
35.715676] ACPI Warning for \_SB_.PCI0.PEGP.DGFX.MXMS: Excess arguments - needs 1, found 2 (20100121/nspredef-319)
215.827679] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
216.233363] e1000e 0000:00:19.0: irq 30 for MSI/MSI-X
216.284196] e1000e 0000:00:19.0: irq 30 for MSI/MSI-X
216.284650] ADDRCONF(NETDEV_UP): eth0: link is not ready
216.373331] iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio.
216.641770] ADDRCONF(NETDEV_UP): wlan0: link is not ready
216.737193] NET: Registered protocol family 17
217.897334] iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio.
217.936022] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
217.936025] 0000:00:19.0: eth0: 10/100 speed: disabling TSO
217.936371] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
You can see there is the delay between 35… to 215… which prevents the network from starting. At 35… everything else is loaded an I am logged in and on my Desktop.
After reading the messages before and after the time jump I searched the net after them. But I haven’t found any usefull.
I tried to boot with eed=off because of
215.827679] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
or acpi=off
35.715630] ACPI Warning for \_SB_.PCI0.PEGP.DGFX.MXMI: Excess arguments - needs 1, found 2 (20100121/nspredef-319)
35.715676] ACPI Warning for \_SB_.PCI0.PEGP.DGFX.MXMS: Excess arguments - needs 1, found 2 (20100121/nspredef-319)
But again no difference. The delay is still present.
Perhaps anyone here has an idea to this messages?
regards, odesu
I think i figured out the problem. When i switch the wifi on the notebook off before login the knetworkmanager connects immediately.
Here the dmesg:
32.231078] FS-Cache: Loaded
32.242396] FS-Cache: Netfs 'nfs' registered for caching
32.462976] nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
32.462983] nvidia 0000:01:00.0: setting latency timer to 64
32.462988] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
32.463291] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 260.19.12 Fri Oct 8 11:17:08 PDT 2010
32.709790] ACPI Warning for \_SB_.PCI0.PEGP.DGFX.MXMI: Excess arguments - needs 1, found 2 (20100121/nspredef-319)
32.709841] ACPI Warning for \_SB_.PCI0.PEGP.DGFX.MXMS: Excess arguments - needs 1, found 2 (20100121/nspredef-319)
34.814022] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
36.107501] e1000e 0000:00:19.0: irq 30 for MSI/MSI-X
36.158260] e1000e 0000:00:19.0: irq 30 for MSI/MSI-X
36.158864] ADDRCONF(NETDEV_UP): eth0: link is not ready
37.985814] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
37.985822] 0000:00:19.0: eth0: 10/100 speed: disabling TSO
37.986944] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
38.069078] NET: Registered protocol family 17
48.326008] eth0: no IPv6 routers present
No wifi probing in this situation.
But when wifi button is on and a cable connection is present I am wondering that wifi probing is going to be done. Why do not connect first to the cable connection and search after for wifi connections?
regards, odesu
Now it works with wifi switched on too. I did a zypper up and in one of the lots of updates there must have been the solution.
Thanks for help.
regards
Seems that it was the equal problem to: e1000e in openSUSE 11.3 driver failure