You are not logged in.
Hello all,
I have a problem in using wifi-menu. When I invoke wifi-menu the system scans for networks but, before visualizing the blue menu thingy with networks, I get an "Aborted" (like when I press CTRL+C in the menu). Wifi-menu has always worked for me, and I did not update the system before the error appeared. If I connect through iwconfig (and dhclient), the connection works.
Revelant dmesg message, just after running wifi-menu:
[ 21.761334] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
ip link output, regarding the interface:
3: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 24:0a:64:c3:cb:85 brd ff:ff:ff:ff:ff:ff
I tried to set wlp3s0 up manually (sudo ip link set wlp3s0 up), output:
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 24:0a:64:c3:cb:85 brd ff:ff:ff:ff:ff:ff
Trying to run dmesg after using wifi-menu with this status gives me no dmesg output.
I've also tried to connect using netctl (sudo netctl start wlp3s0-interface). A classic job failed:
Job for netctl@wlp3s0\x2deigenNet.service failed. See "systemctl status 'netctl@wlp3s0\x2d***.service'" and "journalctl -xe" for details.
journalctl output:
-- Unit netctl@wlp3s0\x2deigenNet.service has begun starting up.
Apr 25 20:14:09 *** network[1174]: Starting network profile 'wlp3s0-***'...
Apr 25 20:14:09 *** network[1174]: The interface of network profile 'wlp3s0-***' is already up
Apr 25 20:14:09 *** systemd[1]: netctl@wlp3s0\x2d***.service: main process exited, code=exited, status=1/FAILURE
Apr 25 20:14:09 *** systemd[1]: Failed to start Networking for netctl profile wlp3s0-***.
-- Subject: Unit netctl@wlp3s0\x2d***.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@wlp3s0\x2d***.service has failed.
--
-- The result is failed.
Apr 25 20:14:09 *** systemd[1]: Unit netctl@wlp3s0\x2d***.service entered failed state.
Apr 25 20:14:09 *** systemd[1]: netctl@wlp3s0\x2d***.service failed.
Apr 25 20:14:09 *** sudo[1163]: pam_unix(sudo:session): session closed for user root
Apr 25 20:14:09 *** polkitd[678]: Unregistered Authentication Agent for unix-process:1168:60594 (system bus name :1.45, object path /org/freedesktop/Pol
systemctl status
netctl@wlp3s0\x2d***.service - Networking for netctl profile wlp3s0-***
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2015-04-25 20:15:11 CEST; 8s ago
Docs: man:netctl.profile(5)
Process: 1193 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 1193 (code=exited, status=1/FAILURE)
Apr 25 20:15:11 *** systemd[1]: Starting Networking for netctl profile wlp3s0-***...
Apr 25 20:15:11 *** network[1193]: Starting network profile 'wlp3s0-***'...
Apr 25 20:15:11 *** network[1193]: The interface of network profile 'wlp3s0-***' is already up
Apr 25 20:15:11 *** systemd[1]: netctl@wlp3s0\x2d***.service: main process exited, code=exited, status=1/FAILURE
Apr 25 20:15:11 *** systemd[1]: Failed to start Networking for netctl profile wlp3s0-***.
Apr 25 20:15:11 *** systemd[1]: Unit netctl@wlp3s0\x2d***.service entered failed state.
Apr 25 20:15:11 *** systemd[1]: netctl@wlp3s0\x2d***.service failed.
A bunch of random things. I have no idea about the error, as I repeat, wifi-menu was working fine until now and I made no updates.
My computer is an Asus X552C laptop.
Last edited by s.baldino (2015-04-26 02:24:33)
Offline
Hey s.baldino!
It looks like various people have been having some problems that are attributed to a recent update to wpa_supplicant.
if
pacman -Q | grep wpa_supplicant
returns version 2.4.1, then that may be your problem.
Check in /var/cache/pacman/pkg/ and look, if there is a file named "wpa_supplicant-2.3-1-x86_64.pkg.tar.xz". If so, type
pacman -U wpa_supplicant-2.3-1-x86_64.pkg.tar.xz
If you don't have it locally, I imagine you could download it from the repos on a working comp and then put it on a usb stick to get it over to the affected computer.
HTH,
Nick
sauce:http://www.reddit.com/r/archlinux/comments/33s2hk/wifimenu_and_netctl_not_working/
Offline
pacman -Q | grep wpa_supplicant
Ehmm...
pacman -Q wpa_supplicant
Offtopic how-to-use-pacman stuff, please continue with your netctl troubleshooting.
Offline
Inkdinky, are you sure about your solution? Why should wpa_supplicant influence wifi-menu? I'd like to be sure before executing a rollback.
About netctl, I've solved the problem: I have found that the interface needs to be down in order for netctl to work, and wifi-menu brings it up. All I had to do was to type
ip link set dev wlp3s0 down
to bring the interface down once and for all. Having done that, netctl works like a charm.
wifi-menu still doesn't work, but at least I can connect. But I'd like to solve this problem too.
Last edited by s.baldino (2015-04-25 20:45:03)
Offline
I was just offering what I found as a solution to the problem. I experienced the same problem on my Arch install with wifi-menu aborting. I used the solution listed above and it worked for me.
Your situation may be different, but it worked for me! If you want to read about other's experience take a look at the link I posted. That may give you the warm fuzzies that you are after.
Offline
It worked! So it really was a wpa_supplicant bug... I'll report it. Thanks, problem solved!
Offline
No, it's a netctl bug - other networking tools are not affected.
Offline
I had the same issue.
Oddly it started with netctl-auto not connecting to my usual profiles anymore. I had to stop netctl with systemctl in order to be able to manually select a connection within wifi-menu. Tonight nothing would work at all.
I connected with my cellphone using usb tethering with the following commands :
ip link set enp0s20u3 up
sudo dhcpcd enp0s20u3
Since I just cleared pacman cache this morning I didn't have the old packet for wpa_supplicant but it got downgraded yesterday so a simple update was enough :
Revert to version 2.3 due to issues with version 2.4:
- Segmentation fault when a P2P device interface is used. [1]
- Inability to connect to WPA2-Enterprise networks. [2]
Link : https://projects.archlinux.org/svntogit … e7791e18b5
And I also realized we just got the update to linux 4. Skynet is coming !
Last edited by yenda (2015-04-29 22:57:52)
Offline