Arch Linux not connecting to Wifi anymore

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
14
down vote

favorite
7












I have been using Arch Linux over a month now. I have used wifi-menu to connect to my Wifi Network. I run the command every time I start my laptop.



wifi-menu always gives this error when I try to connect:



Job for netctl@HelloWorld.service failed. See 'systemctl status netctl@HelloWorld.service' and 'journalctl -xn' for details.


The problem was that my interface was up every time I started. So I put the interface down using this:



ip link set down wlp2s0


wlp2s0 is my interface's name and HelloWorld is my Wifi Network's SSID.




This time, it didn't connect to the network regardless of putting the interface down. It gives me the same error described above.



This is the output of systemctl status netctl@HelloWorld.service:



netctl@HelloWorld.service - Networking for netctl profile HelloWorld
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
Active: failed (Result: exit-code) since Mon 2014-03-24 02:32:35 IST; 2min 56s ago
Docs: man:netctl.profile(5)
Process: 8601 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 8601 (code=exited, status=1/FAILURE)

Mar 24 02:32:34 lenovo network[8601]: Starting network profile 'HelloWorld'...
Mar 24 02:32:35 lenovo network[8601]: chmod: cannot access ‘/run/dhcpcd-wlp2s0.pid’: No such file or directory
Mar 24 02:32:35 lenovo network[8601]: Failed to bring the network up for profile 'HelloWorld'
Mar 24 02:32:35 lenovo systemd[1]: netctl@HelloWorld.service: main process exited, code=exited, status=1/FAILURE
Mar 24 02:32:35 lenovo systemd[1]: Failed to start Networking for netctl profile HelloWorld.
Mar 24 02:32:35 lenovo systemd[1]: Unit netctl@HelloWorld.service entered failed state.



journalctl -xn gives me this output:



Mar 24 02:38:05 lenovo kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement)
Mar 24 02:38:05 lenovo kernel: cfg80211: Calling CRDA to update world regulatory domain
Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: carrier lost
Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: carrier acquired
Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: carrier lost
Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: waiting for carrier
Mar 24 02:38:05 lenovo network[8993]: Failed to bring the network up for profile 'HelloWorld'
Mar 24 02:38:05 lenovo systemd[1]: netctl@HelloWorld.service: main process exited, code=exited, status=1/FAILURE
Mar 24 02:38:05 lenovo systemd[1]: Failed to start Networking for netctl profile HelloWorld.
-- Subject: Unit netctl@HelloWorld.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@HelloWorld.service has failed.
--
-- The result is failed.
Mar 24 02:38:05 lenovo systemd[1]: Unit netctl@HelloWorld.service entered failed state.


systemctl gives the error that /run/dhcpcd-wlp2s0.pid doesn't exist, and it doesn't. Though a file named /run/dhcpcd.pid does exist.




This is the Network Controller output from lspci -k



02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
Subsystem: Broadcom Corporation Device 051b
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcma



I have tried a couple of things from around the Internet but haven't found a solution.



Is there a way to fix this problem? Or can I just reset everything related to networking in Arch Linux so that I can just use wifi-menu to connect to the network again?



Thanks!










share|improve this question

























    up vote
    14
    down vote

    favorite
    7












    I have been using Arch Linux over a month now. I have used wifi-menu to connect to my Wifi Network. I run the command every time I start my laptop.



    wifi-menu always gives this error when I try to connect:



    Job for netctl@HelloWorld.service failed. See 'systemctl status netctl@HelloWorld.service' and 'journalctl -xn' for details.


    The problem was that my interface was up every time I started. So I put the interface down using this:



    ip link set down wlp2s0


    wlp2s0 is my interface's name and HelloWorld is my Wifi Network's SSID.




    This time, it didn't connect to the network regardless of putting the interface down. It gives me the same error described above.



    This is the output of systemctl status netctl@HelloWorld.service:



    netctl@HelloWorld.service - Networking for netctl profile HelloWorld
    Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
    Active: failed (Result: exit-code) since Mon 2014-03-24 02:32:35 IST; 2min 56s ago
    Docs: man:netctl.profile(5)
    Process: 8601 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
    Main PID: 8601 (code=exited, status=1/FAILURE)

    Mar 24 02:32:34 lenovo network[8601]: Starting network profile 'HelloWorld'...
    Mar 24 02:32:35 lenovo network[8601]: chmod: cannot access ‘/run/dhcpcd-wlp2s0.pid’: No such file or directory
    Mar 24 02:32:35 lenovo network[8601]: Failed to bring the network up for profile 'HelloWorld'
    Mar 24 02:32:35 lenovo systemd[1]: netctl@HelloWorld.service: main process exited, code=exited, status=1/FAILURE
    Mar 24 02:32:35 lenovo systemd[1]: Failed to start Networking for netctl profile HelloWorld.
    Mar 24 02:32:35 lenovo systemd[1]: Unit netctl@HelloWorld.service entered failed state.



    journalctl -xn gives me this output:



    Mar 24 02:38:05 lenovo kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement)
    Mar 24 02:38:05 lenovo kernel: cfg80211: Calling CRDA to update world regulatory domain
    Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: carrier lost
    Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: carrier acquired
    Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: carrier lost
    Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: waiting for carrier
    Mar 24 02:38:05 lenovo network[8993]: Failed to bring the network up for profile 'HelloWorld'
    Mar 24 02:38:05 lenovo systemd[1]: netctl@HelloWorld.service: main process exited, code=exited, status=1/FAILURE
    Mar 24 02:38:05 lenovo systemd[1]: Failed to start Networking for netctl profile HelloWorld.
    -- Subject: Unit netctl@HelloWorld.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit netctl@HelloWorld.service has failed.
    --
    -- The result is failed.
    Mar 24 02:38:05 lenovo systemd[1]: Unit netctl@HelloWorld.service entered failed state.


    systemctl gives the error that /run/dhcpcd-wlp2s0.pid doesn't exist, and it doesn't. Though a file named /run/dhcpcd.pid does exist.




    This is the Network Controller output from lspci -k



    02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
    Subsystem: Broadcom Corporation Device 051b
    Kernel driver in use: bcma-pci-bridge
    Kernel modules: bcma



    I have tried a couple of things from around the Internet but haven't found a solution.



    Is there a way to fix this problem? Or can I just reset everything related to networking in Arch Linux so that I can just use wifi-menu to connect to the network again?



    Thanks!










    share|improve this question























      up vote
      14
      down vote

      favorite
      7









      up vote
      14
      down vote

      favorite
      7






      7





      I have been using Arch Linux over a month now. I have used wifi-menu to connect to my Wifi Network. I run the command every time I start my laptop.



      wifi-menu always gives this error when I try to connect:



      Job for netctl@HelloWorld.service failed. See 'systemctl status netctl@HelloWorld.service' and 'journalctl -xn' for details.


      The problem was that my interface was up every time I started. So I put the interface down using this:



      ip link set down wlp2s0


      wlp2s0 is my interface's name and HelloWorld is my Wifi Network's SSID.




      This time, it didn't connect to the network regardless of putting the interface down. It gives me the same error described above.



      This is the output of systemctl status netctl@HelloWorld.service:



      netctl@HelloWorld.service - Networking for netctl profile HelloWorld
      Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
      Active: failed (Result: exit-code) since Mon 2014-03-24 02:32:35 IST; 2min 56s ago
      Docs: man:netctl.profile(5)
      Process: 8601 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
      Main PID: 8601 (code=exited, status=1/FAILURE)

      Mar 24 02:32:34 lenovo network[8601]: Starting network profile 'HelloWorld'...
      Mar 24 02:32:35 lenovo network[8601]: chmod: cannot access ‘/run/dhcpcd-wlp2s0.pid’: No such file or directory
      Mar 24 02:32:35 lenovo network[8601]: Failed to bring the network up for profile 'HelloWorld'
      Mar 24 02:32:35 lenovo systemd[1]: netctl@HelloWorld.service: main process exited, code=exited, status=1/FAILURE
      Mar 24 02:32:35 lenovo systemd[1]: Failed to start Networking for netctl profile HelloWorld.
      Mar 24 02:32:35 lenovo systemd[1]: Unit netctl@HelloWorld.service entered failed state.



      journalctl -xn gives me this output:



      Mar 24 02:38:05 lenovo kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement)
      Mar 24 02:38:05 lenovo kernel: cfg80211: Calling CRDA to update world regulatory domain
      Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: carrier lost
      Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: carrier acquired
      Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: carrier lost
      Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: waiting for carrier
      Mar 24 02:38:05 lenovo network[8993]: Failed to bring the network up for profile 'HelloWorld'
      Mar 24 02:38:05 lenovo systemd[1]: netctl@HelloWorld.service: main process exited, code=exited, status=1/FAILURE
      Mar 24 02:38:05 lenovo systemd[1]: Failed to start Networking for netctl profile HelloWorld.
      -- Subject: Unit netctl@HelloWorld.service has failed
      -- Defined-By: systemd
      -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
      --
      -- Unit netctl@HelloWorld.service has failed.
      --
      -- The result is failed.
      Mar 24 02:38:05 lenovo systemd[1]: Unit netctl@HelloWorld.service entered failed state.


      systemctl gives the error that /run/dhcpcd-wlp2s0.pid doesn't exist, and it doesn't. Though a file named /run/dhcpcd.pid does exist.




      This is the Network Controller output from lspci -k



      02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
      Subsystem: Broadcom Corporation Device 051b
      Kernel driver in use: bcma-pci-bridge
      Kernel modules: bcma



      I have tried a couple of things from around the Internet but haven't found a solution.



      Is there a way to fix this problem? Or can I just reset everything related to networking in Arch Linux so that I can just use wifi-menu to connect to the network again?



      Thanks!










      share|improve this question













      I have been using Arch Linux over a month now. I have used wifi-menu to connect to my Wifi Network. I run the command every time I start my laptop.



      wifi-menu always gives this error when I try to connect:



      Job for netctl@HelloWorld.service failed. See 'systemctl status netctl@HelloWorld.service' and 'journalctl -xn' for details.


      The problem was that my interface was up every time I started. So I put the interface down using this:



      ip link set down wlp2s0


      wlp2s0 is my interface's name and HelloWorld is my Wifi Network's SSID.




      This time, it didn't connect to the network regardless of putting the interface down. It gives me the same error described above.



      This is the output of systemctl status netctl@HelloWorld.service:



      netctl@HelloWorld.service - Networking for netctl profile HelloWorld
      Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
      Active: failed (Result: exit-code) since Mon 2014-03-24 02:32:35 IST; 2min 56s ago
      Docs: man:netctl.profile(5)
      Process: 8601 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
      Main PID: 8601 (code=exited, status=1/FAILURE)

      Mar 24 02:32:34 lenovo network[8601]: Starting network profile 'HelloWorld'...
      Mar 24 02:32:35 lenovo network[8601]: chmod: cannot access ‘/run/dhcpcd-wlp2s0.pid’: No such file or directory
      Mar 24 02:32:35 lenovo network[8601]: Failed to bring the network up for profile 'HelloWorld'
      Mar 24 02:32:35 lenovo systemd[1]: netctl@HelloWorld.service: main process exited, code=exited, status=1/FAILURE
      Mar 24 02:32:35 lenovo systemd[1]: Failed to start Networking for netctl profile HelloWorld.
      Mar 24 02:32:35 lenovo systemd[1]: Unit netctl@HelloWorld.service entered failed state.



      journalctl -xn gives me this output:



      Mar 24 02:38:05 lenovo kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement)
      Mar 24 02:38:05 lenovo kernel: cfg80211: Calling CRDA to update world regulatory domain
      Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: carrier lost
      Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: carrier acquired
      Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: carrier lost
      Mar 24 02:38:05 lenovo dhcpcd[256]: wlp2s0: waiting for carrier
      Mar 24 02:38:05 lenovo network[8993]: Failed to bring the network up for profile 'HelloWorld'
      Mar 24 02:38:05 lenovo systemd[1]: netctl@HelloWorld.service: main process exited, code=exited, status=1/FAILURE
      Mar 24 02:38:05 lenovo systemd[1]: Failed to start Networking for netctl profile HelloWorld.
      -- Subject: Unit netctl@HelloWorld.service has failed
      -- Defined-By: systemd
      -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
      --
      -- Unit netctl@HelloWorld.service has failed.
      --
      -- The result is failed.
      Mar 24 02:38:05 lenovo systemd[1]: Unit netctl@HelloWorld.service entered failed state.


      systemctl gives the error that /run/dhcpcd-wlp2s0.pid doesn't exist, and it doesn't. Though a file named /run/dhcpcd.pid does exist.




      This is the Network Controller output from lspci -k



      02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
      Subsystem: Broadcom Corporation Device 051b
      Kernel driver in use: bcma-pci-bridge
      Kernel modules: bcma



      I have tried a couple of things from around the Internet but haven't found a solution.



      Is there a way to fix this problem? Or can I just reset everything related to networking in Arch Linux so that I can just use wifi-menu to connect to the network again?



      Thanks!







      networking arch-linux wifi






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 23 '14 at 21:14









      Arjun Bajaj

      171115




      171115




















          4 Answers
          4






          active

          oldest

          votes

















          up vote
          21
          down vote













          I had exactly the same problem. Have you killed the dhcpd?



          I completely killed dhcpd:



          $ sudo killall dhcpcd



          After I disabled my wireless interface ($ ip link set down $ should work too):



          $ sudo ifconfig wlp3s0 down



          and my wifi-menu is working again.






          share|improve this answer






















          • I ran the commands but now it's telling me that the interface is controlled by netctl-auto. I couldn't find a way to disable that in the wiki.
            – Arjun Bajaj
            Mar 24 '14 at 21:55










          • The Error is: Interface 'wlp2s0' is controlled by netctl-auto A profile already exists for SSID 'HelloWorld'
            – Arjun Bajaj
            Mar 24 '14 at 21:55










          • no need to call "up" again?
            – ã‚¢ãƒ¬ãƒƒã‚¯ã‚¹
            Jul 5 '14 at 2:36










          • Lol.. Killing DHCPCD really nailed it. Thanks a bunch
            – Gorilla Moe
            Oct 31 '14 at 10:20










          • yeeeaahhh, thanks for this. @Alex, no need to call up again.
            – ÐœÐ°Ñ‚и Тернер
            Jan 15 '15 at 19:49

















          up vote
          4
          down vote













          Why are you running wifi-menu each time you start? Unless you are constantly connecting to new wireless networks, you should simply use wifi-menu once to create a profile, then use netctl to automatically connect when you boot.






          share|improve this answer




















          • The changes I did because of this bug enabled the netctl-auto command to start wifi at boot. Now, it connects to the network at boot and I can use netctl-auto to reconnect. Thanks! :)
            – Arjun Bajaj
            Apr 12 '14 at 7:45

















          up vote
          2
          down vote













          Probably a very late answer, but you can restart the dhcpcd, with the device down. And it should work.



          $ ip link set dev wlp9s0b1 down



          $ wifi-menu



          if wifi-menu does not work, try installing networkmanager. and enabling it.



          # pacman -S networkmanager



          # systemctl enable NetworkManager.service



          and restart.






          share|improve this answer





























            up vote
            0
            down vote













            This worked for me, I used netctl enable [PROFILE] to enable my wifi profile.






            share|improve this answer




















              Your Answer







              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "106"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              convertImagesToLinks: false,
              noModals: false,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













               

              draft saved


              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f121060%2farch-linux-not-connecting-to-wifi-anymore%23new-answer', 'question_page');

              );

              Post as a guest






























              4 Answers
              4






              active

              oldest

              votes








              4 Answers
              4






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              21
              down vote













              I had exactly the same problem. Have you killed the dhcpd?



              I completely killed dhcpd:



              $ sudo killall dhcpcd



              After I disabled my wireless interface ($ ip link set down $ should work too):



              $ sudo ifconfig wlp3s0 down



              and my wifi-menu is working again.






              share|improve this answer






















              • I ran the commands but now it's telling me that the interface is controlled by netctl-auto. I couldn't find a way to disable that in the wiki.
                – Arjun Bajaj
                Mar 24 '14 at 21:55










              • The Error is: Interface 'wlp2s0' is controlled by netctl-auto A profile already exists for SSID 'HelloWorld'
                – Arjun Bajaj
                Mar 24 '14 at 21:55










              • no need to call "up" again?
                – ã‚¢ãƒ¬ãƒƒã‚¯ã‚¹
                Jul 5 '14 at 2:36










              • Lol.. Killing DHCPCD really nailed it. Thanks a bunch
                – Gorilla Moe
                Oct 31 '14 at 10:20










              • yeeeaahhh, thanks for this. @Alex, no need to call up again.
                – ÐœÐ°Ñ‚и Тернер
                Jan 15 '15 at 19:49














              up vote
              21
              down vote













              I had exactly the same problem. Have you killed the dhcpd?



              I completely killed dhcpd:



              $ sudo killall dhcpcd



              After I disabled my wireless interface ($ ip link set down $ should work too):



              $ sudo ifconfig wlp3s0 down



              and my wifi-menu is working again.






              share|improve this answer






















              • I ran the commands but now it's telling me that the interface is controlled by netctl-auto. I couldn't find a way to disable that in the wiki.
                – Arjun Bajaj
                Mar 24 '14 at 21:55










              • The Error is: Interface 'wlp2s0' is controlled by netctl-auto A profile already exists for SSID 'HelloWorld'
                – Arjun Bajaj
                Mar 24 '14 at 21:55










              • no need to call "up" again?
                – ã‚¢ãƒ¬ãƒƒã‚¯ã‚¹
                Jul 5 '14 at 2:36










              • Lol.. Killing DHCPCD really nailed it. Thanks a bunch
                – Gorilla Moe
                Oct 31 '14 at 10:20










              • yeeeaahhh, thanks for this. @Alex, no need to call up again.
                – ÐœÐ°Ñ‚и Тернер
                Jan 15 '15 at 19:49












              up vote
              21
              down vote










              up vote
              21
              down vote









              I had exactly the same problem. Have you killed the dhcpd?



              I completely killed dhcpd:



              $ sudo killall dhcpcd



              After I disabled my wireless interface ($ ip link set down $ should work too):



              $ sudo ifconfig wlp3s0 down



              and my wifi-menu is working again.






              share|improve this answer














              I had exactly the same problem. Have you killed the dhcpd?



              I completely killed dhcpd:



              $ sudo killall dhcpcd



              After I disabled my wireless interface ($ ip link set down $ should work too):



              $ sudo ifconfig wlp3s0 down



              and my wifi-menu is working again.







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Mar 24 '14 at 11:57









              Raphael Ahrens

              6,76752845




              6,76752845










              answered Mar 24 '14 at 10:02









              Seberm

              21112




              21112











              • I ran the commands but now it's telling me that the interface is controlled by netctl-auto. I couldn't find a way to disable that in the wiki.
                – Arjun Bajaj
                Mar 24 '14 at 21:55










              • The Error is: Interface 'wlp2s0' is controlled by netctl-auto A profile already exists for SSID 'HelloWorld'
                – Arjun Bajaj
                Mar 24 '14 at 21:55










              • no need to call "up" again?
                – ã‚¢ãƒ¬ãƒƒã‚¯ã‚¹
                Jul 5 '14 at 2:36










              • Lol.. Killing DHCPCD really nailed it. Thanks a bunch
                – Gorilla Moe
                Oct 31 '14 at 10:20










              • yeeeaahhh, thanks for this. @Alex, no need to call up again.
                – ÐœÐ°Ñ‚и Тернер
                Jan 15 '15 at 19:49
















              • I ran the commands but now it's telling me that the interface is controlled by netctl-auto. I couldn't find a way to disable that in the wiki.
                – Arjun Bajaj
                Mar 24 '14 at 21:55










              • The Error is: Interface 'wlp2s0' is controlled by netctl-auto A profile already exists for SSID 'HelloWorld'
                – Arjun Bajaj
                Mar 24 '14 at 21:55










              • no need to call "up" again?
                – ã‚¢ãƒ¬ãƒƒã‚¯ã‚¹
                Jul 5 '14 at 2:36










              • Lol.. Killing DHCPCD really nailed it. Thanks a bunch
                – Gorilla Moe
                Oct 31 '14 at 10:20










              • yeeeaahhh, thanks for this. @Alex, no need to call up again.
                – ÐœÐ°Ñ‚и Тернер
                Jan 15 '15 at 19:49















              I ran the commands but now it's telling me that the interface is controlled by netctl-auto. I couldn't find a way to disable that in the wiki.
              – Arjun Bajaj
              Mar 24 '14 at 21:55




              I ran the commands but now it's telling me that the interface is controlled by netctl-auto. I couldn't find a way to disable that in the wiki.
              – Arjun Bajaj
              Mar 24 '14 at 21:55












              The Error is: Interface 'wlp2s0' is controlled by netctl-auto A profile already exists for SSID 'HelloWorld'
              – Arjun Bajaj
              Mar 24 '14 at 21:55




              The Error is: Interface 'wlp2s0' is controlled by netctl-auto A profile already exists for SSID 'HelloWorld'
              – Arjun Bajaj
              Mar 24 '14 at 21:55












              no need to call "up" again?
              – ã‚¢ãƒ¬ãƒƒã‚¯ã‚¹
              Jul 5 '14 at 2:36




              no need to call "up" again?
              – ã‚¢ãƒ¬ãƒƒã‚¯ã‚¹
              Jul 5 '14 at 2:36












              Lol.. Killing DHCPCD really nailed it. Thanks a bunch
              – Gorilla Moe
              Oct 31 '14 at 10:20




              Lol.. Killing DHCPCD really nailed it. Thanks a bunch
              – Gorilla Moe
              Oct 31 '14 at 10:20












              yeeeaahhh, thanks for this. @Alex, no need to call up again.
              – ÐœÐ°Ñ‚и Тернер
              Jan 15 '15 at 19:49




              yeeeaahhh, thanks for this. @Alex, no need to call up again.
              – ÐœÐ°Ñ‚и Тернер
              Jan 15 '15 at 19:49












              up vote
              4
              down vote













              Why are you running wifi-menu each time you start? Unless you are constantly connecting to new wireless networks, you should simply use wifi-menu once to create a profile, then use netctl to automatically connect when you boot.






              share|improve this answer




















              • The changes I did because of this bug enabled the netctl-auto command to start wifi at boot. Now, it connects to the network at boot and I can use netctl-auto to reconnect. Thanks! :)
                – Arjun Bajaj
                Apr 12 '14 at 7:45














              up vote
              4
              down vote













              Why are you running wifi-menu each time you start? Unless you are constantly connecting to new wireless networks, you should simply use wifi-menu once to create a profile, then use netctl to automatically connect when you boot.






              share|improve this answer




















              • The changes I did because of this bug enabled the netctl-auto command to start wifi at boot. Now, it connects to the network at boot and I can use netctl-auto to reconnect. Thanks! :)
                – Arjun Bajaj
                Apr 12 '14 at 7:45












              up vote
              4
              down vote










              up vote
              4
              down vote









              Why are you running wifi-menu each time you start? Unless you are constantly connecting to new wireless networks, you should simply use wifi-menu once to create a profile, then use netctl to automatically connect when you boot.






              share|improve this answer












              Why are you running wifi-menu each time you start? Unless you are constantly connecting to new wireless networks, you should simply use wifi-menu once to create a profile, then use netctl to automatically connect when you boot.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Apr 5 '14 at 16:24









              Serge Canizares

              411




              411











              • The changes I did because of this bug enabled the netctl-auto command to start wifi at boot. Now, it connects to the network at boot and I can use netctl-auto to reconnect. Thanks! :)
                – Arjun Bajaj
                Apr 12 '14 at 7:45
















              • The changes I did because of this bug enabled the netctl-auto command to start wifi at boot. Now, it connects to the network at boot and I can use netctl-auto to reconnect. Thanks! :)
                – Arjun Bajaj
                Apr 12 '14 at 7:45















              The changes I did because of this bug enabled the netctl-auto command to start wifi at boot. Now, it connects to the network at boot and I can use netctl-auto to reconnect. Thanks! :)
              – Arjun Bajaj
              Apr 12 '14 at 7:45




              The changes I did because of this bug enabled the netctl-auto command to start wifi at boot. Now, it connects to the network at boot and I can use netctl-auto to reconnect. Thanks! :)
              – Arjun Bajaj
              Apr 12 '14 at 7:45










              up vote
              2
              down vote













              Probably a very late answer, but you can restart the dhcpcd, with the device down. And it should work.



              $ ip link set dev wlp9s0b1 down



              $ wifi-menu



              if wifi-menu does not work, try installing networkmanager. and enabling it.



              # pacman -S networkmanager



              # systemctl enable NetworkManager.service



              and restart.






              share|improve this answer


























                up vote
                2
                down vote













                Probably a very late answer, but you can restart the dhcpcd, with the device down. And it should work.



                $ ip link set dev wlp9s0b1 down



                $ wifi-menu



                if wifi-menu does not work, try installing networkmanager. and enabling it.



                # pacman -S networkmanager



                # systemctl enable NetworkManager.service



                and restart.






                share|improve this answer
























                  up vote
                  2
                  down vote










                  up vote
                  2
                  down vote









                  Probably a very late answer, but you can restart the dhcpcd, with the device down. And it should work.



                  $ ip link set dev wlp9s0b1 down



                  $ wifi-menu



                  if wifi-menu does not work, try installing networkmanager. and enabling it.



                  # pacman -S networkmanager



                  # systemctl enable NetworkManager.service



                  and restart.






                  share|improve this answer














                  Probably a very late answer, but you can restart the dhcpcd, with the device down. And it should work.



                  $ ip link set dev wlp9s0b1 down



                  $ wifi-menu



                  if wifi-menu does not work, try installing networkmanager. and enabling it.



                  # pacman -S networkmanager



                  # systemctl enable NetworkManager.service



                  and restart.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 13 mins ago

























                  answered Jan 11 at 12:11









                  sidharth arya

                  7314




                  7314




















                      up vote
                      0
                      down vote













                      This worked for me, I used netctl enable [PROFILE] to enable my wifi profile.






                      share|improve this answer
























                        up vote
                        0
                        down vote













                        This worked for me, I used netctl enable [PROFILE] to enable my wifi profile.






                        share|improve this answer






















                          up vote
                          0
                          down vote










                          up vote
                          0
                          down vote









                          This worked for me, I used netctl enable [PROFILE] to enable my wifi profile.






                          share|improve this answer












                          This worked for me, I used netctl enable [PROFILE] to enable my wifi profile.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Oct 17 '15 at 16:31









                          Tiberio de Oliveira

                          1




                          1



























                               

                              draft saved


                              draft discarded















































                               


                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f121060%2farch-linux-not-connecting-to-wifi-anymore%23new-answer', 'question_page');

                              );

                              Post as a guest













































































                              Popular posts from this blog

                              How to check contact read email or not when send email to Individual?

                              Displaying single band from multi-band raster using QGIS

                              How many registers does an x86_64 CPU actually have?