[Solved] Cannot connect to wireless

Question

So I'm trying to connect to wireless but I'm having trouble. It seems to happen no matter what wireless network I try to connect to. I open up wifi-menu and select the network I want to connect to, but I get an error:
Job for netctl@wlp1s0\x2dTSC.service failed. See 'systemctl status netctl@wlp1s0\x2dTSC.service' and 'journalctl -xn' for details
However, looking at those seems to not really give an indication as to what's going on. Here they are:
systemctl status netctl@wlp1s0\x2dTSC.service:
* [email protected] - Networking for netctl profile wlp1s0x2dTSC
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
Active: inactive (dead)
Docs: man:netctl.profile(5)
journalctl -xn:
-- Logs begin at Tue 2013-08-27 08:59:38 EDT, end at Thu 2014-03-27 15:26:00 EDT. --
Mar 27 15:20:44 dave-lappy systemd[562]: Starting Default.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has begun starting up.
Mar 27 15:20:44 dave-lappy systemd[562]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has finished starting up.
-- The start-up result is done.
Mar 27 15:20:44 dave-lappy systemd[562]: Startup finished in 158ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- Kernel start-up required KERNEL_USEC microseconds.
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- Userspace start-up required 158066 microseconds.
Mar 27 15:23:44 dave-lappy su[913]: (to root) dave on pts/0
Mar 27 15:23:44 dave-lappy su[913]: pam_unix(su:session): session opened for user root by (uid=1000)
Mar 27 15:24:19 dave-lappy su[913]: pam_unix(su:session): session closed for user root
Mar 27 15:24:25 dave-lappy su[1069]: (to root) dave on pts/0
Mar 27 15:24:25 dave-lappy su[1069]: pam_unix(su:session): session opened for user root by (uid=1000)
Mar 27 15:24:24 dave-lappy systemd[562]: Time has been changed
-- Subject: Time change
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- The system clock has been changed to REALTIME microseconds after January 1st, 1970.
Mar 27 15:26:00 dave-lappy su[1069]: pam_unix(su:session): session closed for user root
I did a pacman -Syu last night. There wasn't any news on the website that mentioned any updates that might affect the wireless. Otherwise, everything was working fine previously. I can't think of any other changes I've made.
So I'm really not sure what's going on. Any thoughts?
Last edited by arbulus (2014-03-27 21:19:26)

Answer 1

So I decided to just go down the docs in the wiki step by step regarding wireless and netctl. From the netctl page, I did:
systemctl enable [email protected]
and then it started working again. I don't know why it stopped working, but it appears to be up and running now.
Last edited by arbulus (2014-03-27 21:20:38)