You are not logged in.
- Topics: Active | Unanswered
#1 2017-04-19 16:36:46
- excrement
- Member
- Registered: 2017-04-19
- Posts: 7
[Solved] wifi-menu now fails after last nights update.
I did a full update last night which had a kernel update; rebooted and now wireless isnt working..
i get this now.. 
Job for netctl@wlp112s0\x2dtest.service failed because the control process exited with error code.
See "systemctl status "netctl@wlp112s0\\x2dtest.service"" and "journalctl -xe" for details.
[root@nag ~]# journalctl -xn
-- Logs begin at Wed 2016-10-05 21:56:52 PDT, end at Wed 2017-04-19 09:30:38 PDT. --
Apr 19 09:27:47 nag su[8813]: (to root) root on pts/2
Apr 19 09:27:47 nag su[8813]: pam_unix(su-l:session): session opened for user root by (uid=0)
Apr 19 09:30:09 nag kernel: IPv6: ADDRCONF(NETDEV_UP): wlp112s0: link is not ready
Apr 19 09:30:38 nag systemd[1]: Starting Networking for netctl profile wlp112s0-test...
-- Subject: Unit netctl@wlp112s0\x2dtest.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@wlp112s0\x2dtest.service has begun starting up.
Apr 19 09:30:38 nag network[9092]: Starting network profile 'wlp112s0-test'...
Apr 19 09:30:38 nag network[9092]: The interface of network profile 'wlp112s0-test' is already up
Apr 19 09:30:38 nag systemd[1]: netctl@wlp112s0\x2dtest.service: Main process exited, code=exited, status=1/FAILURE
Apr 19 09:30:38 nag systemd[1]: Failed to start Networking for netctl profile wlp112s0-test.
-- Subject: Unit netctl@wlp112s0\x2dtest.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
--
-- Unit netctl@wlp112s0\x2dtest.service has failed.
--
-- The result is failed.
Apr 19 09:30:38 nag systemd[1]: netctl@wlp112s0\x2dtest.service: Unit entered failed state.
Apr 19 09:30:38 nag systemd[1]: netctl@wlp112s0\x2dtest.service: Failed with result 'exit-code'.
[root@nag ~]#
which leads me to believe the recent kernel update borked the wireless driver?.. It simply worked prior to today i never had any issues..
any help would be appreciated.
Last edited by excrement (2017-04-19 23:39:34)
Offline
#2 2017-04-19 16:46:36
- ewaller
- Administrator
- From: Pasadena, CA
- Registered: 2009-07-13
- Posts: 19,791
Re: [Solved] wifi-menu now fails after last nights update.
Sanity check: What are the output of uname -a and pacman -Q linux (Assuming you are running the stock kernel)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
#3 2017-04-19 16:50:22
- excrement
- Member
- Registered: 2017-04-19
- Posts: 7
Re: [Solved] wifi-menu now fails after last nights update.
[root@nag ~]# uname -a
Linux nag 4.10.10-1-ARCH #1 SMP PREEMPT Wed Apr 12 18:50:28 CEST 2017 x86_64 GNU/Linux
[root@nag ~]#
pacman -Q linux :: linux 4.10.10-1
Offline
#4 2017-04-19 17:03:01
- ewaller
- Administrator
- From: Pasadena, CA
- Registered: 2009-07-13
- Posts: 19,791
Re: [Solved] wifi-menu now fails after last nights update.
Okay, that is sane 
I was checking that the kernel could find its modules.
What are the output of ip link and (it will be long, be sure to use code tags) iw phy ?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
#5 2017-04-19 17:27:43
- excrement
- Member
- Registered: 2017-04-19
- Posts: 7
Re: [Solved] wifi-menu now fails after last nights update.
yea, i dont have a fancy kernel setup (old gentoo user) moved to arch about 6 months ago from gentoo..
So yea, basic.
ip link (i nulled out the mac addresses)
[root@nag ~]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp109s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether XXXXXXXXXXXX brd ff:ff:ff:ff:ff:ff
4: wlp112s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether XXXXXXXXXXXXXX brd ff:ff:ff:ff:ff:ff
[root@nag ~]# iw phy:
[root@nag ~]# iw phy
Wiphy phy1
max # scan SSIDs: 16
max scan IEs length: 195 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Device supports T-DLS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x19ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (no IR)
* 2472 MHz [13] (20.0 dBm) (no IR)
* 2484 MHz [14] (disabled)
Band 2:
Capabilities: 0x19ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x339071b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
SU Beamformee
MU Beamformee
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5180 MHz [36] (30.0 dBm) (no IR)
* 5200 MHz [40] (30.0 dBm) (no IR)
* 5220 MHz [44] (30.0 dBm) (no IR)
* 5240 MHz [48] (30.0 dBm)
* 5260 MHz [52] (30.0 dBm) (no IR, radar detection)
* 5280 MHz [56] (30.0 dBm) (no IR, radar detection)
* 5300 MHz [60] (30.0 dBm) (no IR, radar detection)
* 5320 MHz [64] (30.0 dBm) (no IR, radar detection)
* 5500 MHz [100] (30.0 dBm) (no IR, radar detection)
* 5520 MHz [104] (30.0 dBm) (no IR, radar detection)
* 5540 MHz [108] (30.0 dBm) (no IR, radar detection)
* 5560 MHz [112] (30.0 dBm) (no IR, radar detection)
* 5580 MHz [116] (30.0 dBm) (no IR, radar detection)
* 5600 MHz [120] (30.0 dBm) (no IR, radar detection)
* 5620 MHz [124] (30.0 dBm) (no IR, radar detection)
* 5640 MHz [128] (30.0 dBm) (no IR, radar detection)
* 5660 MHz [132] (30.0 dBm) (no IR, radar detection)
* 5680 MHz [136] (30.0 dBm) (no IR, radar detection)
* 5700 MHz [140] (30.0 dBm) (no IR, radar detection)
* 5720 MHz [144] (30.0 dBm) (no IR)
* 5745 MHz [149] (30.0 dBm) (no IR)
* 5765 MHz [153] (30.0 dBm) (no IR)
* 5785 MHz [157] (30.0 dBm) (no IR)
* 5805 MHz [161] (30.0 dBm) (no IR)
* 5825 MHz [165] (30.0 dBm) (no IR)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* tdls_mgmt
* tdls_oper
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* connect
* disconnect
* channel_switch
* set_qos_map
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
WoWLAN support:
* wake up on disconnect
* wake up on magic packet
* wake up on pattern match, up to 22 patterns of 1-148 bytes,
maximum packet offset 128 bytes
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed } <= 2, #{ AP, mesh point, P2P-client, P2P-GO } <= 2, #{ P2P-device } <= 1,
total <= 4, #channels <= 1
* #{ managed } <= 2, #{ P2P-client } <= 2, #{ AP, mesh point, P2P-GO } <= 1, #{ P2P-device } <= 1,
total <= 4, #channels <= 2
* #{ managed } <= 1, #{ IBSS } <= 1,
total <= 2, #channels <= 1
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports scan flush.
Device supports AP scan.
Device supports per-vif TX power setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
Device supports static SMPS
Device supports configuring vdev MAC-addr on create.
Device supports VHT-IBSS.
[root@nag ~]# Offline
#6 2017-04-19 17:31:38
- excrement
- Member
- Registered: 2017-04-19
- Posts: 7
Re: [Solved] wifi-menu now fails after last nights update.
not to add additional noise but from systemctl list-unit-files should there be some services enabled/static? im seeing some netctl services disabled ..
Offline
#7 2017-04-19 19:57:07
- excrement
- Member
- Registered: 2017-04-19
- Posts: 7
Re: [Solved] wifi-menu now fails after last nights update.
this post pretty much is the same as the issue im having..:
Offline
#8 2017-04-19 20:36:07
- excrement
- Member
- Registered: 2017-04-19
- Posts: 7
Re: [Solved] wifi-menu now fails after last nights update.
I think i fixed this..
added the following
ForceConnect=yesmy profile i created over in /etc/netctl
now sure why i had to add this now since prior i never had a problem..
Offline
#9 2017-04-19 22:06:15
- headkase
- Member
- Registered: 2011-12-06
- Posts: 1,976
Re: [Solved] wifi-menu now fails after last nights update.
I think i fixed this..
added the following
ForceConnect=yesmy profile i created over in /etc/netctl
now sure why i had to add this now since prior i never had a problem..
If your issue is fixed then don't forget to mark your thread as solved by editing the first post and prepending "[Solved]" to the title without the quotes.
Offline
#10 2017-04-19 23:42:06
- excrement
- Member
- Registered: 2017-04-19
- Posts: 7
Re: [Solved] wifi-menu now fails after last nights update.
If your issue is fixed then don't forget to mark your thread as solved by editing the first post and prepending "[Solved]" to the title without the quotes.
Yea, sorry about that..
Offline