Problems with connecting to wifi

webeseit · 2018-08-18 09:46:15

Hello. I've just set up arch linux with gnome and am trying to connect to the internet via NetworkManager.
I disabled and stopped all other services such as dhcpcd and netctl, enabled and started NetworkManager.
Wired connection works just fine, but I can't connect to wifi.
On Windows wifi works fine, so it isn't a problem of the wifi router.
I think it isn't a problem of NetworkManager because earlier I tried to connect to wifi via netctl but got this:

sudo netctl start slonik

Job for netctl@slonik.service failed because the control process exited with error code.
See "systemctl status netctl@slonik.service" and "journalctl -xe" for details.

sudo systemctl status netctl@slonik.service

● netctl@slonik.service - Networking for netctl profile slonik
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2018-08-18 12:15:18 MSK; 3min 46s ago
     Docs: man:netctl.profile(5)
  Process: 2901 ExecStart=/usr/lib/netctl/network start slonik (code=exited, status=1/FAILURE)
 Main PID: 2901 (code=exited, status=1/FAILURE)

Aug 18 12:15:00 evm systemd[1]: Starting Networking for netctl profile slonik...
Aug 18 12:15:00 evm network[2901]: Starting network profile 'slonik'...
Aug 18 12:15:18 evm network[2901]: WPA association/authentication failed for interface 'wlp2s0'
Aug 18 12:15:18 evm network[2901]: Failed to bring the network up for profile 'slonik'
Aug 18 12:15:18 evm systemd[1]: netctl@slonik.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 12:15:18 evm systemd[1]: netctl@slonik.service: Failed with result 'exit-code'.
Aug 18 12:15:18 evm systemd[1]: Failed to start Networking for netctl profile slonik.

sudo journalctl -xe

Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #8 0x7ffde6097c10 b   resource:///org/gnome/shell/ui/tweener.js:207 (0x7fd23c3cf5e8 @ 159)
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #9 0x7ffde6097c80 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd23c3b5de0 @ 71)
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #10 0x7ffde6097c80 I   resource:///org/gnome/shell/ui/tweener.js:182 (0x7fd23c3cf560 @ 15)
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: == Stack trace for context 0x557b362b4220 ==
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #0 0x7ffde6097690 b   resource:///org/gnome/shell/ui/tweener.js:80 (0x7fd23c3c8cd0 @ 82)
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #1 0x7ffde6097730 b   resource:///org/gnome/shell/ui/tweener.js:105 (0x7fd23c3c8f78 @ 36)
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #2 0x7ffde60977d0 b   resource:///org/gnome/shell/ui/tweener.js:92 (0x7fd23c3c8de0 @ 52)
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #3 0x7ffde6097850 I   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fd23c3d2918 @ 54)
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #4 0x7ffde60979a0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fd23c3d29a0 @ 162>
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #5 0x7ffde6097a50 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fd23c3d2a28 @ 100)
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #6 0x7ffde6097ae0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fd23c3d2ab0 @ 10)
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #7 0x7ffde6097b60 I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd23c3cff78 @ 386)
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #8 0x7ffde6097c10 b   resource:///org/gnome/shell/ui/tweener.js:207 (0x7fd23c3cf5e8 @ 159)
Aug 18 12:19:45 evm gnome-shell[649]: Object Meta.WindowActor (0x557b38e2db60), has been already finalized. Impossible to set any property to it.
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #9 0x7ffde6097c80 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd23c3b5de0 @ 71)
Aug 18 12:19:45 evm org.gnome.Shell.desktop[649]: #10 0x7ffde6097c80 I   resource:///org/gnome/shell/ui/tweener.js:182 (0x7fd23c3cf560 @ 15)
Aug 18 12:20:30 evm wpa_supplicant[329]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-100
Aug 18 12:20:36 evm kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=83598 end=83599) time 217 us, min 763, m>
Aug 18 12:20:50 evm gjs[1032]: JS LOG: could not get x11 server time (cause: TypeError: Object is of type GdkWaylandWindow - cannot convert to GdkX11W>
Aug 18 12:21:13 evm sudo[3416]:    danil : TTY=pts/0 ; PWD=/home/danil ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Aug 18 12:21:13 evm sudo[341

This is the output of ip a:

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 40:b0:34:97:fa:c1 brd ff:ff:ff:ff:ff:ff
    inet 10.56.11.56/24 brd 10.56.11.255 scope global dynamic noprefixroute enp3s0
       valid_lft 84757sec preferred_lft 84757sec
    inet6 fe80::4a91:fc86:2d4d:e4a4/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether f2:fd:28:09:ff:b0 brd ff:ff:ff:ff:ff:ff

My wifi interface is wlp2s0, I should notice that before when I created wifi profile /etc/netctl/slonik:

Description='A simple WPA encrypted wireless connection'
Interface=wlp2s0
Connection=wireless

Security=wpa
IP=dhcp

ESSID='slonik'
# Prepend hexadecimal keys with \"
# If your key starts with ", write it as '""<key>"'
# See also: the section on special quoting rules in netctl.profile(5)
Key='my password is here'
# Uncomment this if your ssid is hidden
#Hidden=yes
# Set a priority for automatic profile selection
#Priority=10

dhcpcd wlp2s0 command didn't get the ip adress for wlp2s0.

I should also noticed that the wifi router is connected to my university network and needs the authentication via its website. When I connect to the network with a cable, browser invites me to the login page but nothing happens when I'm trying to do the same thing via wifi, networkmanager just requires a password for wifi, then it's trying to connect but the after the 30 seconds delay it says that connection failed.

I also tried to connect to the open public wifi network but networkmanager couldn't connect it aswell.

I was googling it yesterday but have found nothing that helped me.
If anyone knows how can I fix it or where can I be looking for more logs information, I'll appreciate that. I'll be adding additional information here if I find something.
----------
Here are NetworkManager logs:

-- Logs begin at Thu 2018-08-16 19:33:49 MSK, end at Sat 2018-08-18 12:57:58 MSK. --
Aug 17 17:50:57 evm systemd[1]: Starting Network Manager...
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.1932] NetworkManager (version 1.12.3dev+1+g0a3755c17-1) is starting... (for the first ti>
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.1933] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Aug 17 17:50:57 evm systemd[1]: Started Network Manager.
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.2183] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.2199] manager[0x558e5891e000]: monitoring kernel firmware directory '/usr/lib/firmware'.
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.7443] hostname: hostname: using hostnamed
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.7445] hostname: hostname changed from (none) to "evm"
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.7454] dns-mgr[0x558e58929130]: init: dns=default, rc-manager=symlink
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.7512] rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.2/0000>
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.7522] manager[0x558e5891e000]: rfkill: WiFi hardware radio set enabled
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.7524] manager[0x558e5891e000]: rfkill: WWAN hardware radio set enabled
Aug 17 17:50:57 evm NetworkManager[1324]: <error> [1534517457.8390] dispatcher: could not get dispatcher proxy! Error calling StartServiceByName for o>
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.8396] settings: Loaded settings plugin: NMSKeyfilePlugin (internal)
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.8950] settings: Loaded settings plugin: NMSIbftPlugin (/usr/lib/NetworkManager/1.12.3dev>
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.9021] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.9027] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.9033] manager: Networking is enabled by state file
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.9036] dhcp-init: Using DHCP client 'internal'
Aug 17 17:50:57 evm NetworkManager[1324]: <info>  [1534517457.9166] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.12.3dev+1+g0a3755c17>

g 18 15:25:09 evm NetworkManager[323]: <info>  [1534595109.9122] device (enp3s0): state change: secondaries -> activated (reason 'none', sys-iface-s>
Aug 18 15:25:10 evm NetworkManager[323]: <info>  [1534595110.0114] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 18 15:25:10 evm NetworkManager[323]: <info>  [1534595110.0118] policy: set 'Wired connection 1' (enp3s0) as default for IPv4 routing and DNS
Aug 18 15:25:10 evm NetworkManager[323]: <info>  [1534595110.0471] device (enp3s0): Activation: successful, device activated.
Aug 18 15:25:22 evm NetworkManager[323]: <warn>  [1534595122.5753] device (wlp2s0): Activation: (wifi) association took too long
Aug 18 15:25:22 evm NetworkManager[323]: <info>  [1534595122.5755] device (wlp2s0): state change: config -> failed (reason 'no-secrets', sys-iface-sta>
Aug 18 15:25:22 evm NetworkManager[323]: <warn>  [1534595122.5814] device (wlp2s0): Activation: failed for connection 'slonik 3'
Aug 18 15:25:22 evm NetworkManager[323]: <info>  [1534595122.5823] device (wlp2s0): state change: failed -> disconnected (reason 'none', sys-iface-sta>
Aug 18 15:25:22 evm NetworkManager[323]: <info>  [1534595122.5952] device (wlp2s0): set-hw-addr: set MAC address to 66:9C:54:A0:60:43 (scanning)
Aug 18 15:25:23 evm NetworkManager[323]: <info>  [1534595123.2178] device (wlp2s0): supplicant interface state: scanning -> disconnected
Aug 18 15:25:23 evm NetworkManager[323]: <info>  [1534595123.2243] device (wlp2s0): supplicant interface state: disconnected -> inactive
Aug 18 15:25:26 evm NetworkManager[323]: <info>  [1534595126.0343] device (wlp2s0): supplicant interface state: inactive -> disconnected
Aug 18 15:25:36 evm NetworkManager[323]: <info>  [1534595136.0427] device (wlp2s0): supplicant interface state: disconnected -> inactive
Aug 18 15:26:17 evm NetworkManager[323]: <info>  [1534595177.8114] device (wlp2s0): Activation: starting connection 'slonik 3' (e5de2898-c3e7-456c-829>
Aug 18 15:26:17 evm NetworkManager[323]: <info>  [1534595177.8120] audit: op="connection-activate" uuid="e5de2898-c3e7-456c-8294-af22740c8c5e" name="s>
Aug 18 15:26:17 evm NetworkManager[323]: <info>  [1534595177.8124] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-st>
Aug 18 15:26:17 evm NetworkManager[323]: <info>  [1534595177.8186] device (wlp2s0): set-hw-addr: reset MAC address to 3C:A0:67:DA:6F:41 (preserve)
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3248] device (wlp2s0): supplicant interface state: inactive -> disabled
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3251] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: '>
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3264] device (wlp2s0): Activation: (wifi) access point 'slonik 3' has security, but secre>
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3265] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state:>
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3270] sup-iface[0x55872031b220,wlp2s0]: wps: type pbc start...
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3325] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state>
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3335] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: '>
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3348] device (wlp2s0): Activation: (wifi) connection 'slonik 3' has security, and secrets>
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3349] Config: added 'ssid' value 'slonik'
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3349] Config: added 'scan_ssid' value '1'
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3349] Config: added 'bgscan' value 'simple:30:-80:86400'
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3350] Config: added 'key_mgmt' value 'WPA-PSK'
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3350] Config: added 'auth_alg' value 'OPEN'
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.3350] Config: added 'psk' value '<hidden>'
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.4269] device (wlp2s0): supplicant interface state: disabled -> inactive
Aug 18 15:26:18 evm NetworkManager[323]: <info>  [1534595178.4500] device (wlp2s0): supplicant interface state: inactive -> scanning
Aug 18 15:26:20 evm NetworkManager[323]: <info>  [1534595180.9176] device (wlp2s0): supplicant interface state: scanning -> authenticating
Aug 18 15:26:20 evm NetworkManager[323]: <info>  [1534595180.9380] device (wlp2s0): supplicant interface state: authenticating -> associating
Aug 18 15:26:20 evm NetworkManager[323]: <info>  [1534595180.9664] device (wlp2s0): supplicant interface state: associating -> associated
Aug 18 15:26:20 evm NetworkManager[323]: <warn>  [1534595180.9750] sup-iface[0x55872031b220,wlp2s0]: connection disconnected (reason -3)
Aug 18 15:26:20 evm NetworkManager[323]: <info>  [1534595180.9779] device (wlp2s0): supplicant interface state: associated -> disconnected
Aug 18 15:26:22 evm NetworkManager[323]: <info>  [1534595182.0804] device (wlp2s0): supplicant interface state: disconnected -> scanning
Aug 18 15:26:32 evm NetworkManager[323]: <info>  [1534595192.7474] device (wlp2s0): supplicant interface state: scanning -> authenticating
Aug 18 15:26:33 evm NetworkManager[323]: <info>  [1534595193.1510] device (wlp2s0): supplicant interface state: authenticating -> disconnected
Aug 18 15:26:43 evm NetworkManager[323]: <warn>  [1534595203.5746] device (wlp2s0): Activation: (wifi) association took too long
Aug 18 15:26:43 evm NetworkManager[323]: <info>  [1534595203.5747] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state:>
Aug 18 15:26:43 evm NetworkManager[323]: <warn>  [1534595203.5801] device (wlp2s0): Activation: (wifi) asking for new secrets
Aug 18 15:26:44 evm NetworkManager[323]: <info>  [1534595204.1624] device (wlp2s0): supplicant interface state: disconnected -> inactive
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.7067] settings-connection[0x558720377380,e5de2898-c3e7-456c-8294-af22740c8c5e]: write: su>
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.7077] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state>
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.7300] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: '>
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.7315] device (wlp2s0): Activation: (wifi) connection 'slonik 3' has security, and secrets>
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.7316] Config: added 'ssid' value 'slonik'
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.7316] Config: added 'scan_ssid' value '1'
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.7317] Config: added 'bgscan' value 'simple:30:-80:86400'
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.7317] Config: added 'key_mgmt' value 'WPA-PSK'
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.7317] Config: added 'auth_alg' value 'OPEN'
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.7318] Config: added 'psk' value '<hidden>'
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.7647] device (wlp2s0): supplicant interface state: inactive -> authenticating
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.7783] device (wlp2s0): supplicant interface state: authenticating -> associating
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.9272] device (wlp2s0): supplicant interface state: associating -> associated
Aug 18 15:26:45 evm NetworkManager[323]: <warn>  [1534595205.9350] sup-iface[0x55872031b220,wlp2s0]: connection disconnected (reason -3)
Aug 18 15:26:45 evm NetworkManager[323]: <info>  [1534595205.9415] device (wlp2s0): supplicant interface state: associated -> disconnected
Aug 18 15:26:46 evm NetworkManager[323]: <info>  [1534595206.0416] device (wlp2s0): supplicant interface state: disconnected -> scanning

Here is the output of sudo systemctl status "netctl@wlp2s0\\x2dMoscow_WiFi_Free.service", Moscow_Wifi_Free is the open public network which I tryied to connect to:

● netctl@wlp2s0\x2dMoscow_WiFi_Free.service - Networking for netctl profile wlp2s0-Moscow_WiFi_Free
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2018-08-18 13:11:03 MSK; 28s ago
     Docs: man:netctl.profile(5)
  Process: 6823 ExecStart=/usr/lib/netctl/network start wlp2s0-Moscow_WiFi_Free (code=exited, status=1/FAILURE)
 Main PID: 6823 (code=exited, status=1/FAILURE)

Aug 18 13:10:45 evm systemd[1]: Starting Networking for netctl profile wlp2s0-Moscow_WiFi_Free...
Aug 18 13:10:45 evm network[6823]: Starting network profile 'wlp2s0-Moscow_WiFi_Free'...
Aug 18 13:11:03 evm network[6823]: WPA association/authentication failed for interface 'wlp2s0'
Aug 18 13:11:03 evm network[6823]: Failed to bring the network up for profile 'wlp2s0-Moscow_WiFi_Free'
Aug 18 13:11:03 evm systemd[1]: netctl@wlp2s0\x2dMoscow_WiFi_Free.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 13:11:03 evm systemd[1]: netctl@wlp2s0\x2dMoscow_WiFi_Free.service: Failed with result 'exit-code'.
Aug 18 13:11:03 evm systemd[1]: Failed to start Networking for netctl profile wlp2s0-Moscow_WiFi_Free.

Last edited by webeseit (2018-08-18 12:28:21)

seth · 2018-08-18 12:47:01

According to theis post, networkmanager, netctl and dhcpcd seem to be running at the same time?

systemctl list-units | grep -iE '(net|dhcp|conn|wicd)'
systemctl list-unit-files --state=enabled

Stop them all and attempt to connect manually, https://wiki.archlinux.org/index.php?ti … management

webeseit · 2018-08-18 14:25:50

so I disabled all those services before started NetworkManager.
I went to the link to connect manually but when I did the command

wpa_supplicant -B -i interface -c <(wpa_passphrase MYSSID passphrase)

using my ssid and passphrase I got this:

wpa_supplicant -B -i wlp2s0 -c <(wpa_passphrase slonik n18i22a7)
Successfully initialized wpa_supplicant
nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
wlp2s0: Failed to initialize driver interface

could it be the driver's problem?

Last edited by webeseit (2018-08-18 14:26:09)

seth · 2018-08-18 14:30:07

so I disabled all those services before started NetworkManager.

Leaving aside that this sounds as if NM is still running, did you also stop them?

seth wrote:

systemctl list-units | grep -iE '(net|dhcp|conn|wicd)'
systemctl list-unit-files --state=enabled

webeseit · 2018-08-18 14:39:02

yes, I stopped it before I tried to connect manually

systemctl list-units | grep -iE '(net|dhcp|conn|wicd)'

  sys-devices-pci0000:00-0000:00:1c.2-0000:02:00.0-net-wlp2s0.device                          loaded active plugged   RTL8723BE PCIe Wireless Network Adapter                                                    
  sys-devices-pci0000:00-0000:00:1c.3-0000:03:00.0-net-enp3s0.device                          loaded active plugged   RTL810xE PCI Express Fast Ethernet controller                                              
  sys-subsystem-net-devices-enp3s0.device                                                     loaded active plugged   RTL810xE PCI Express Fast Ethernet controller                                              
  sys-subsystem-net-devices-wlp2s0.device                                                     loaded active plugged   RTL8723BE PCIe Wireless Network Adapter                                                    
  sys-fs-fuse-connections.mount                                                               loaded active mounted   FUSE Control File System                                                                   
● netctl@wlp2s0\x2dslonik.service                                                             loaded failed failed    Networking for netctl profile wlp2s0-slonik                                                
  network-wireless@wlp2s0.service                                                             loaded active exited    Wireless network connectivity (wlp2s0)                                                     
  system-netctl.slice                                                                         loaded active active    system-netctl.slice                                                                        
  system-network\x2dwireless.slice                                                            loaded active active    system-network\x2dwireless.slice                                                           
  network.target                                                                              loaded active active    Network

systemctl list-unit-files --state=enabled

autovt@.service                    enabled
dbus-fi.w1.wpa_supplicant1.service enabled
display-manager.service            enabled
gdm.service                        enabled
getty@.service                     enabled
sshd.service                       enabled
wpa_supplicant.service             enabled
remote-fs.target                   enabled

ewaller · 2018-08-18 14:39:20

report_by_webeseit wrote:

yes, I stopped it before I tried to connect manually

And the code block that came with it:

systemctl list-units | grep -iE '(net|dhcp|conn|wicd)'

sys-devices-pci0000:00-0000:00:1c.2-0000:02:00.0-net-wlp2s0.device loaded active plugged RTL8723BE PCIe Wireless Network Adapter
sys-devices-pci0000:00-0000:00:1c.3-0000:03:00.0-net-enp3s0.device loaded active plugged RTL810xE PCI Express Fast Ethernet controller
sys-subsystem-net-devices-enp3s0.device loaded active plugged RTL810xE PCI Express Fast Ethernet controller
sys-subsystem-net-devices-wlp2s0.device loaded active plugged RTL8723BE PCIe Wireless Network Adapter
sys-fs-fuse-connections.mount loaded active mounted FUSE Control File System
● netctl@wlp2s0\x2dslonik.service loaded failed failed Networking for netctl profile wlp2s0-slonik
network-wireless@wlp2s0.service loaded active exited Wireless network connectivity (wlp2s0)
system-netctl.slice loaded active active system-netctl.slice
system-network\x2dwireless.slice loaded active active system-network\x2dwireless.slice
network.target loaded active active Network

systemctl list-unit-files --state=enabled

autovt@.service enabled
dbus-fi.w1.wpa_supplicant1.service enabled
display-manager.service enabled
gdm.service enabled
getty@.service enabled
sshd.service enabled
wpa_supplicant.service enabled
remote-fs.target enabled

If you were wondering where your post went, I think you hit the report link, not the reply link

Edit: I see you re-posted while I was posting.
Edit 2: I see it happened twice

Last edited by ewaller (2018-08-18 14:41:25)

webeseit · 2018-08-18 14:48:43

oh, sorry, I missclicked

seth · 2018-08-19 12:48:29

The wpa_supplicant service is still enabeld, "systemctl list-units | grep -i wpa"?
(The error strongly suggests sth. else™ is trying to operate the device)

Arch Linux

#1 2018-08-18 09:46:15

Problems with connecting to wifi

#2 2018-08-18 12:47:01

Re: Problems with connecting to wifi

#3 2018-08-18 14:25:50

Re: Problems with connecting to wifi

#4 2018-08-18 14:30:07

Re: Problems with connecting to wifi

#5 2018-08-18 14:39:02

Re: Problems with connecting to wifi

#6 2018-08-18 14:39:20

Re: Problems with connecting to wifi

#7 2018-08-18 14:48:43

Re: Problems with connecting to wifi

#8 2018-08-19 12:48:29

Re: Problems with connecting to wifi

Board footer