You are not logged in.
I can't get my machine to connect to any wifi-network anymore, all fail with a generic
Job for netctl@wlp3s0\x2dPython.service failed. See 'systemctl status netctl@wlp3s0\x2dPython.service' and 'journalctl -xn' for details.
(Yes the network is named Python)
Looking at the first option gives this:
systemctl status netctl@wlp3s0x2dPython.service ⏎
netctl@wlp3s0x2dPython.service - Networking for netctl profile wlp3s0x2dPython
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
Active: inactive (dead)
Docs: man:netctl.profile(5)
While the latter yields:
/e/netctl ❯❯❯ journalctl -xn
-- Logs begin at Sat 2013-08-17 06:33:44 EDT, end at Tue 2014-03-25 07:16:48 EDT. --
Mar 25 07:11:47 TuringMachine org.gtk.Private.UDisks2VolumeMonitor[843]: ### debug: Name owner ':1.34' vanished
Mar 25 07:11:47 TuringMachine org.gtk.Private.UDisks2VolumeMonitor[843]: ### debug: in handle_list
Mar 25 07:11:47 TuringMachine org.gtk.Private.UDisks2VolumeMonitor[843]: ### debug: in handle_supported
Mar 25 07:11:47 TuringMachine org.gtk.Private.UDisks2VolumeMonitor[843]: ### debug: Name owner ':1.37' vanished
Mar 25 07:11:47 TuringMachine org.gtk.Private.UDisks2VolumeMonitor[843]: ### debug: in handle_list
Mar 25 07:11:47 TuringMachine org.gtk.Private.UDisks2VolumeMonitor[843]: ### debug: in handle_supported
Mar 25 07:11:47 TuringMachine org.gtk.Private.UDisks2VolumeMonitor[843]: ### debug: Name owner ':1.40' vanished
Mar 25 07:11:47 TuringMachine org.gtk.Private.UDisks2VolumeMonitor[843]: ### debug: in handle_list
Mar 25 07:15:10 TuringMachine systemd[780]: Time has been changed
-- Subject: Time change
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
--
-- The system clock has been changed to REALTIME microseconds after January 1st, 1970.
Mar 25 07:16:48 TuringMachine org.gtk.Private.UDisks2VolumeMonitor[843]: ### debug: Name owner ':1.23' vanished
neither of which is particularly informative.
I'm not sure if netctl was updated recently and other people are affected as well, I'm on a X230 Thinkpad.
Perhaps I should downgrade netctl?
EDITED: Added code tags.
Last edited by algebr (2014-03-25 22:49:17)
Offline
Please use code tags when posting snippets.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
I'm not sure if netctl was updated recently and other people are affected as well, I'm on a X230 Thinkpad.
I have a fresh install of arch on an ASUS ROG laptop and am experiencing issues that look very similar. I'm using a Rosewill RNX-N150HG usb wifi adapter because the built in one is ac and not yet supported by any firmware I know of.
> sudo netctl start wlp0s20u4-edgewood
Job for netctl@wlp0s20u4\x2dedgewood.service failed. See 'systemctl status netctl@wlp0s20u4\x2dedgewood.service' and 'journalctl -xn' for details.
> systemctl status netctl@wlp0s20u4\x2dedgewood.service
netctl@wlp0s20u4x2dedgewood.service - Networking for netctl profile wlp0s20u4x2dedgewood
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
Active: inactive (dead)
Docs: man:netctl.profile(5)
> journalctl -xn
-- Logs begin at Sat 2014-03-22 11:33:20 CDT, end at Wed 2014-03-26 16:57:45 CDT. --
Mar 26 16:52:01 dailyalice systemd[650]: Starting Basic System.
-- 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 26 16:52:01 dailyalice systemd[650]: Reached target Basic System.
-- 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 26 16:52:01 dailyalice systemd[650]: 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 26 16:52:01 dailyalice systemd[650]: 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 26 16:52:01 dailyalice systemd[650]: Startup finished in 60ms.
-- 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 60246 microseconds.
Mar 26 16:57:45 dailyalice org.a11y.Bus[727]: Activating service name='org.a11y.atspi.Registry'
Mar 26 16:57:45 dailyalice org.a11y.Bus[727]: Successfully activated service 'org.a11y.atspi.Registry'
Mar 26 16:57:45 dailyalice org.a11y.atspi.Registry[2337]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Mar 26 16:57:45 dailyalice org.a11y.atspi.Registry[2337]: ** (at-spi2-registryd:2340): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.D
Mar 26 16:57:45 dailyalice org.a11y.atspi.Registry[2337]: ** (at-spi2-registryd:2340): WARNING **: Unable to register client with session manager
Additionally ip link reports the following:
> ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether d8:50:e6:05:dd:9e brd ff:ff:ff:ff:ff:ff
3: wlp0s20u4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 6c:fd:b9:09:3d:a0 brd ff:ff:ff:ff:ff:ff
Offline
*EDIT III* I am the biggest moron to ever walk the earth!! My apologies, but it seems that I actually hit the wireless function key when I was changing my screenbrightness in the dark before I turned my backlight on. Super sorry!!
I am also having a very similar issue with the Dell Inspiron 17R 7277 Special Edition. It literally just stopped last night and has not worked again since. I thought it may have been a hardware problem, but it seems that I was wrong. Its essentially the same exact situation as the poster of this thread.
*EDIT* mine seems to be an rf-kill problem, as trying to set the interface up gives me the operation not possible due to rfkill error. I have no idea how to go about fixing this, since I have tried adding unblock all to the rfkill config as par other instructions that I have read and enabling rfkill in rc.conf but nothing has worked. It just stopped randomly yesterday to not work and I have no idea why. I cannot do much trouble shooting because I have no internet access on the laptop and it is difficult to post configs and such.
*EDIT II* I have checked the diagnostic tool included in the firmware of this laptop, and it reports that the wireless switch is off and that Wireless LAN is disabled and Wireless WLAN is not installed. I may try flashing my bios this evening. I have tried "resetting" the card by disconnecting and reconnecting the card, but that has not worked either. I don not think that this is an arch problem, since this machine is notorious for its firmware issues. Will report back later.
Last edited by agahnim (2014-03-28 01:35:07)
Offline
Checked whether the wifi button was on, still no success.
Offline
EDIT II: My success appears to be entirely wicd. I've simply uninstalled netctl for now and will stick with wicd. I hope someone figures this problem out, though.
EDIT: After uninstalling wicd and network manager, it stopped working again. Upon installing them again, it works again. Not sure if this means wicd or networkmanager is taking over or if there's a dependency of one of them that netctl needs. Trying to figure it out now.
After playing around with other network managers, it finally occurred to me to simply delete all of my connection configurations and regenerate them. This worked right away for me. Have you tried this algebr?
*EDIT III* I am the biggest moron to ever walk the earth!! My apologies, but it seems that I actually hit the wireless function key when I was changing my screenbrightness in the dark before I turned my backlight on. Super sorry!!
Don't sweat it, happens to all of us
Last edited by nichdel (2014-03-30 20:47:04)
Offline
Unfortunately I'm still stuck with this issue, even tried wicd and that didn't help.
Offline