Sorry, I think that this question has been posted not long ago. It’s late and I haven’t been able to find it.
I have upgraded to KDE 4.3.4. Network manager now works but whenever I reboot or tun the computer on I have to start it manually. I have added it in “system settings > autostart”, but it has made no difference.
Can anyone point me in the right direction here?
Thanks.
On 12/09/2009 05:06 AM, asarge wrote:
>
> Sorry, I think that this question has been posted not long ago. It’s
> late and I haven’t been able to find it.
> I have upgraded to KDE 4.3.4. Network manager now works but whenever I
> reboot or tun the computer on I have to start it manually. I have added
> it in “system settings > autostart”, but it has made no difference.
> Can anyone point me in the right direction here?
> Thanks.
It is started by /etc/init.d/network through the link at
/etc/init.d/rc5.d/S02network.
Ok, I have had a bit of a quick look at both of the files.
They look the same to me. Is there something in them that would give a clue as to what is going on or do I need to modify them?
On 12/09/2009 01:36 PM, asarge wrote:
>
> Ok, I have had a bit of a quick look at both of the files.
> They look the same to me. Is there something in them that would give a
> clue as to what is going on or do I need to modify them?
You should not modify them. They are, in fact, the same file. The
entry in /etc/init.d/rc.5/ is a link to the file in /etc/init.d/. What
the system does is execute all the “files” that start with “S” in
/etc/init.d/rc.5/ in alphabetical order when level 5 starts. Get the
drift?
The presence of S02network in /etc/init.d/rc5/ means that the system
is trying to start NetworkManager. You might get an indication of what
is failing by entering the command
sudo /etc/init.d/network start
just after you boot. Otherwise look in the files /var/log/messages or
/var/log/NetworkManager to see if anything is logged there. You will
need to be root to view those files. The command
sudo less /var/log/messages
will work. If you are not familiar with less, then ‘man less’ will
help. If present, the info you want will be near the end of the file.
I just typed
sudo /etc/init.d/network start
after booting and it tells me that Knetwork manager is running.
There is no icon in the panel and I have no internet.
I then typed
sudo less /var/log/messages
Wow… I don’t know where to start there :shame:
On 12/10/2009 12:26 AM, asarge wrote:
>
> I just typed
> sudo /etc/init.d/network start
> after booting and it tells me that Knetwork manager is running.
> There is no icon in the panel and I have no internet.
>
> I then typed
> sudo less /var/log/messages
>
> Wow… I don’t know where to start there :shame:
As I told you, look near the bottom of the file. What you are looking
for is more likely to be in the NetworkManager log file.
Have you checked the process list? What does ‘ps ax | grep etwork’ show?
Can I search “Network Manager” in sudo /etc/init.d/network start?
This is some of the file
Dec 10 05:44:08 linux-sarge kernel: 247.100981] wlan0: authenticate with AP 00:24:d2:ce:a3:89
Dec 10 05:44:08 linux-sarge kernel: 247.103854] wlan0: authenticated
Dec 10 05:44:08 linux-sarge kernel: 247.103859] wlan0: associate with AP 00:24:d2:ce:a3:89
Dec 10 05:44:08 linux-sarge kernel: 247.106283] wlan0: RX AssocResp from 00:24:d2:ce:a3:89 (capab=0x411 status=0 aid=1)
Dec 10 05:44:08 linux-sarge kernel: 247.106288] wlan0: associated
Dec 10 05:44:08 linux-sarge kernel: 247.108734] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec 10 05:44:08 linux-sarge dhclient: Internet Systems Consortium DHCP Client V3.1.2p1
Dec 10 05:44:08 linux-sarge dhclient: Copyright 2004-2009 Internet Systems Consortium.
Dec 10 05:44:08 linux-sarge dhclient:
Dec 10 05:44:08 linux-sarge dhclient: Listening on LPF/wlan0/00:21:5d:a0:b3:4a
Dec 10 05:44:08 linux-sarge dhclient: Sending on LPF/wlan0/00:21:5d:a0:b3:4a
Dec 10 05:44:08 linux-sarge dhclient: Sending on Socket/fallback
Dec 10 05:44:09 linux-sarge avahi-daemon[1693]: Registering new address record for fe80::221:5dff:fea0:b34a on wlan0.*.
Dec 10 05:44:11 linux-sarge dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Dec 10 05:44:11 linux-sarge dhclient: DHCPOFFER from 192.168.1.1
Dec 10 05:44:16 linux-sarge dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 10 05:44:16 linux-sarge dhclient: DHCPACK from 192.168.1.1
Dec 10 05:44:16 linux-sarge avahi-daemon[1693]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.3.
Dec 10 05:44:16 linux-sarge avahi-daemon[1693]: New relevant interface wlan0.IPv4 for mDNS.
Dec 10 05:44:16 linux-sarge avahi-daemon[1693]: Registering new address record for 192.168.1.3 on wlan0.IPv4.
Dec 10 05:44:16 linux-sarge dhclient: bound to 192.168.1.3 -- renewal in 1760 seconds.
Dec 10 05:44:17 linux-sarge dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
Dec 10 05:44:17 linux-sarge dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Dec 10 05:44:17 linux-sarge SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 …
Dec 10 16:39:38 linux-sarge network: Starting the NetworkManager
Dec 10 21:37:17 linux-sarge dhclient:
Dec 10 21:37:17 linux-sarge dhclient: Listening on LPF/wlan0/00:21:5d:a0:b3:4a
Dec 10 21:37:17 linux-sarge dhclient: Sending on LPF/wlan0/00:21:5d:a0:b3:4a
Dec 10 21:37:17 linux-sarge dhclient: Sending on Socket/fallback
Dec 10 21:37:18 linux-sarge avahi-daemon[1733]: Registering new address record for fe80::221:5dff:fea0:b34a on wlan0.*.
Dec 10 21:37:20 linux-sarge dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Dec 10 21:37:20 linux-sarge dhclient: DHCPOFFER from 192.168.1.1
Dec 10 21:37:25 linux-sarge dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 10 21:37:25 linux-sarge dhclient: DHCPACK from 192.168.1.1
Dec 10 21:37:25 linux-sarge dhclient: bound to 192.168.1.3 -- renewal in 1723 seconds.
Dec 10 21:37:25 linux-sarge avahi-daemon[1733]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.3.
Dec 10 21:37:25 linux-sarge avahi-daemon[1733]: New relevant interface wlan0.IPv4 for mDNS.
Dec 10 21:37:25 linux-sarge avahi-daemon[1733]: Registering new address record for 192.168.1.3 on wlan0.IPv4.
Dec 10 21:37:26 linux-sarge dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
Dec 10 21:37:26 linux-sarge dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Dec 10 21:37:26 linux-sarge SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Dec 10 21:37:26 linux-sarge SuSEfirewall2: using default zone 'ext' for interface eth0
Dec 10 21:37:26 linux-sarge SuSEfirewall2: using default zone 'ext' for interface pan0
Dec 10 21:37:26 linux-sarge SuSEfirewall2: using default zone 'ext' for interface wmaster0
Dec 10 21:37:26 linux-sarge SuSEfirewall2: batch committing...
Dec 10 21:37:26 linux-sarge SuSEfirewall2: Firewall rules successfully set
Dec 10 21:37:27 linux-sarge kernel: 98.994283] RPC: Registered udp transport module.
Dec 10 21:37:27 linux-sarge kernel: 98.994294] RPC: Registered tcp transport module.
Dec 10 21:37:27 linux-sarge kernel: 99.033697] Slow work thread pool: Starting up
Dec 10 21:37:27 linux-sarge kernel: 99.034038] Slow work thread pool: Ready
Dec 10 21:37:27 linux-sarge kernel: 99.034107] FS-Cache: Loaded
Dec 10 21:37:27 linux-sarge kernel: 99.089267] FS-Cache: Netfs 'nfs' registered for caching
Dec 10 21:37:27 linux-sarge sm-notify[2755]: Already notifying clients; Exiting!
Dec 10 21:37:27 linux-sarge kernel: 99.541028] wlan0: no IPv6 routers present
Dec 10 21:37:30 linux-sarge kernel: 102.041530] process `skype' is using obsolete setsockopt SO_BSDCOMPAT
And here is the outpu of “ps ax | grep etwork”
1696 ? Ssl 0:00 /usr/sbin/NetworkManager
1713 ? S 0:00 /usr/sbin/nm-system-settings --config /etc/NetworkManager/nm-system-settings.conf
24238 pts/1 S+ 0:00 grep etwork
Looks to me like networkmanager is running - you have an IP:
Dec 10 21:37:25 linux-sarge dhclient: bound to 192.168.1.3 -- renewal in 1723 seconds
This line here says that dhcp IS NOT going to update your resolv.conf (used for namservers and stuff)
Dec 10 21:37:26 linux-sarge dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
Dec 10 21:37:26 linux-sarge dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Unless you have meant to do this (ie setting your own, static, nameservers) you can do this (as root) to fix it:
cp /etc/resolv.conf.netconfig /etc/resolv.conf
The tray icon you’re missing is knetworkmanager - KDE’s gui for networkmanager. You could try running knetworkmanager from a terminal as your user, see if that brings up the trayicon (I’m not sure that it is called knetworkmanager, I’m not at home so I can’t check, but it is something like that)
Also, it is worth checking in the network configuration in YaST. Specifically, have a look at the section that deals with icons (I think it is the ‘Other’ tab). Make sure you do have an ‘icon’ and make sure all the options listed are underneath it
If I type knetworkmanager I in a terminal I get the following message.
sarge@linux-sarge:~> knetworkmanager
QLayout: Attempting to add QLayout "" to InterfaceConnectionItem "", which already has a layout
Object::disconnect: Unexpected null parameter
sarge@linux-sarge:~>
But it brings up the tray icon and I then have the internet.
I have tried
cp /etc/resolv.conf.netconfig /etc/resolv.conf
but nothing has changed.
I haven’t been able to find the “other” tab yet… still looking
I have this issue now as well. OpenSUSE 11.2. After installing some updates and rebooting, knetworkmanager does not automatically start. I have no internet until I open a terminal and run knetworkmanager manually. I get the same error:
$knetworkmanager
QLayout: Attempting to add QLayout "" to InterfaceConnectionItem "", which already has a layout
QLayout: Attempting to add QLayout "" to InterfaceConnectionItem "", which already has a layout
But even with the error, knetworkmanager starts and my internet comes up. I’m getting tired of manually starting knetworkmanager now every time I reboot. Anyone have a solution to this?
Brandon