You are not logged in.
Hello guys.
I have a problem with ntctl and I'm not sure it's normal or no.
Everytime I boot my laptop I have start job running as shown below
https://s21.postimg.org/6n6cz3s93/14971 … 6061_n.jpg
When I disable every netctl profiles (I'm using 2) problem dissapeard but then my wifi connection won't start automattically.
Is it normal netctl need this job at boot or may I fix it somehow?
Thanks for any reply.
Last edited by nowakpawel (2017-03-29 20:45:42)
Offline
Don't post images of text, paste the actual text. If you do post an image, read the Code of Conduct and only post thumbnails http://wiki.archlinux.org/index.php/Cod … s_and_code
Include details of the profiles you are using, configs etc.
Moving to NC...
Offline
Check your journalctl to see where netctl fails.
Take a look at netctl's interface configuration.
Offline
When I grep journalctl I have several times line :
Mar 22 00:27:28 archlinux systemd[1]: netctl@Gimbus.service: Main process exited, code=exited, status=1/FAILURE
[EDIT]
I found small misstatement on Archwiki, this page: https://wiki.archlinux.org/index.php/netctl:
For wireless interfaces, install package wpa_actiond: After starting and enabling netctl-auto@interface.service profiles are started/stopped automatically as you move from the range of one network into the range of another network (roaming).
Shouldn't it be
systemctl enable netctl-auto@interface.service
?
We know it means services enabling by systemctl but for new users it can be missunderstood.
Last edited by nowakpawel (2017-03-22 00:16:01)
Offline
So read the journal for that service and see why it is failing.
Also, paste the output of:
systemctl list-unit-files --state enabled
Offline
Ok it looks like thread is expired. This problem I had on my previous Arch installation so I don' remember excaxtly where was the problem.
On my current I had something similar when I booted Linux there was a start is job running for network I randomly my network interfaces did not up., but I found out I had two services enabled:
netctl-auto@interface.service
and
netctl@my_netwokrkname.service
So i disabled the second one and it looks good now.
Marking as SOLVED
Offline