You are not logged in.
Hi!
I work now since a half year with my Samsung Series 9 Laptop. Since January I did not made many updates. So I mad a very huge update yesterday. When I started the laptop today, I could not connect to the WLAN any more.
I checked the state of the network manager using "systemctl status networkmanager" and got the following output:
networkmanager.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
Mar 13 21:04:05 rzi systemd[1]: networkmanager.service: control process exi...03
Mar 13 21:04:05 rzi NetworkManager[413]: <info> caught signal 15, shutting d....
Mar 13 21:04:05 rzi NetworkManager[413]: <info> (wlan0): canceled DHCP trans...4
Mar 13 21:04:05 rzi NetworkManager[413]: <info> (wlan0): now unmanaged
Mar 13 21:04:05 rzi NetworkManager[413]: <info> (wlan0): device state change...]
Mar 13 21:04:05 rzi NetworkManager[413]: <info> (wlan0): cleaning up...
Mar 13 21:04:05 rzi NetworkManager[413]: <info> (eth0): now unmanaged
Mar 13 21:04:05 rzi NetworkManager[413]: <info> (eth0): device state change:...]
Mar 13 21:04:05 rzi NetworkManager[413]: <info> (eth0): cleaning up...
Mar 13 21:04:05 rzi NetworkManager[413]: <info> (eth0): taking down device.
Mar 13 21:04:05 rzi systemd[1]: Stopped LEGACY unit for "networkmanager" rc...t.
Mar 13 21:04:05 rzi systemd[1]: Unit networkmanager.service entered failed state
Any Idea what it could be? Some thing is missing...is it the driver or so?
Cheers
Raphi
Last edited by raphiz (2013-03-18 16:10:11)
Offline
What is networkmanager.service? The one shipped with NM is NetworkManager.service. The line "Stopped LEGACY unit for "networkmanager" rc...t" makes me suspicious that it may be coming from rc.conf or something?
Online
I think it's the gnome Network manager... I think installed the system before sytemd or at least made configurations in the rc.conf...
Offline
I too was facing the same issue and on running "systemctl start NetworkManager", it said no unit found. Hence I resolved it by creating a networkmanager.service file in /etc/systemd/system/multi-user.target.wants/ .
Last edited by pareshverma91 (2013-03-14 23:51:08)
Offline
Well that sound reasonable! But what have you put into that file?
Offline
Doesn't sound reasonable to me. How about figuring out just what you're starting and from where first?
Online
How about trying the output of
systemctl status NetworkManager.service
LENOVO Y 580 IVYBRIDGE 660M NVIDIA
Unix is user-friendly. It just isn't promiscuous about which users it's friendly with. - Steven King
Offline
This is the output for systemctl status NetworkManager.service
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled)
Active: inactive (dead)
I started /usr/sbin/NetworkManager manually and it worked. So it seems to be a systemd issue.
Offline
I 'm not sure how you came to the conclusion.
Last edited by hadrons123 (2013-03-16 11:22:43)
LENOVO Y 580 IVYBRIDGE 660M NVIDIA
Unix is user-friendly. It just isn't promiscuous about which users it's friendly with. - Steven King
Offline
I ment it's not an issue with the networkManager itself...
Offline
Mh.. the service is disabled. Enable and start it?
You can see some log information with journalctl.
Last edited by gridcol (2013-03-16 12:27:00)
Offline
There is a regression created by this commit
http://cgit.freedesktop.org/NetworkMana … d1b7cc22f9
LENOVO Y 580 IVYBRIDGE 660M NVIDIA
Unix is user-friendly. It just isn't promiscuous about which users it's friendly with. - Steven King
Offline
Well that sound reasonable! But what have you put into that file?
I created a NetworkManager.service fiel myself. But it seems one can even link /usr/lib/systemd/system/NetworkManager.service and everything will be fine.
As far as my case was concerned (I landed on this page to find a solution), I was invoking the network manager from rc.conf, while I was under an impression that systemd was responsible for it. Finally, I removed networkmanager from the daemons list at rc.conf and enabled NetworkManager.service with systemctl.
Offline
raphiz wrote:Well that sound reasonable! But what have you put into that file?
I created a NetworkManager.service fiel myself. But it seems one can even link /usr/lib/systemd/system/NetworkManager.service and everything will be fine.
As far as my case was concerned (I landed on this page to find a solution), I was invoking the network manager from rc.conf, while I was under an impression that systemd was responsible for it. Finally, I removed networkmanager from the daemons list at rc.conf and enabled NetworkManager.service with systemctl.
Thank you ALL! The last suggestion actually worked!
Offline