You are not logged in.

Pages: 1

#1 2020-07-13 19:42:35

bruh-i-use-arch-cow
Member
Registered: 2020-07-01
Posts: 46

[SOLVED] Wifi problems...

Ok so i have fully installed arch (with desktop enviroment and all that stuff), and i was never able to make Wifi work properly...
Problem is when i try to make netctl profile to automaticly start wifi interface every time i login, and doing that for some reason it takes REALLY long time to start up my system. Because of that -

"wpa_supplicant[530]: nl80211: kernel reports: Match already configured"

i keep runing into. I tried disabling/enabling wpa_supplincant and other network services, nothing worked.

Output from journal -x

note: this just loops like 10 times and journal output gets really long so dont waste your time reading all of the output

-- The job identifier is 359.
Jul 13 22:20:21 boringPC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher>
Jul 13 22:20:21 boringPC kernel: Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_b>
Jul 13 22:20:21 boringPC NetworkManager[527]: <info>  [1594668021.7849] device (wlp6s0): driver supports Access Point (AP) mode
Jul 13 22:20:21 boringPC NetworkManager[527]: <info>  [1594668021.7852] manager: (wlp6s0): new 802.11 Wi-Fi device (/org/freede>
Jul 13 22:20:21 boringPC NetworkManager[527]: <info>  [1594668021.7856] device (wlp6s0): state change: unmanaged -> unavailable>
Jul 13 22:20:21 boringPC kernel: r8169 0000:03:00.0 enp3s0: Link is Down
Jul 13 22:20:22 boringPC NetworkManager[527]: <info>  [1594668022.1682] device (wlp6s0): set-hw-addr: set MAC address to E6:7D:>
Jul 13 22:20:22 boringPC NetworkManager[527]: <info>  [1594668022.5524] ovsdb: Could not connect: No such file or directory
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: ctrl_iface exists and seems to be in use - cannot override it
Jul 13 22:20:22 boringPC wpa_supplicant[530]: Delete '/run/wpa_supplicant/wlp6s0' manually if it is not used anymore
Jul 13 22:20:22 boringPC wpa_supplicant[530]: Failed to initialize control interface '/run/wpa_supplicant'.
                                              You may have another wpa_supplicant process already running or the file was
                                              left by an unclean termination of wpa_supplicant in which case you will need
                                              to manually remove this file before starting wpa_supplicant again.
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0
Jul 13 22:20:22 boringPC NetworkManager[527]: <error> [1594668022.7227] device (wlp6s0): Couldn't initialize supplicant interfa>
Jul 13 22:20:23 boringPC systemd[1]: systemd-rfkill.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit systemd-rfkill.service has successfully entered the 'dead' state.
Jul 13 22:20:23 boringPC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="syste>
Jul 13 22:20:27 boringPC NetworkManager[527]: <info>  [1594668027.7870] manager: startup complete
Jul 13 22:20:32 boringPC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.
Jul 13 22:20:32 boringPC kernel: kauditd_printk_skb: 3 callbacks suppressed
Jul 13 22:20:32 boringPC kernel: audit: type=1131 audit(1594668032.172:30): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='uni>
Jul 13 22:20:32 boringPC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher >
Jul 13 22:20:33 boringPC NetworkManager[527]: <warn>  [1594668033.1676] device (wlp6s0): re-acquiring supplicant interface (#1).
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: ctrl_iface exists and seems to be in use - cannot override it
Jul 13 22:20:33 boringPC wpa_supplicant[530]: Delete '/run/wpa_supplicant/wlp6s0' manually if it is not used anymore
Jul 13 22:20:33 boringPC wpa_supplicant[530]: Failed to initialize control interface '/run/wpa_supplicant'.
                                              You may have another wpa_supplicant process already running or the file was
                                              left by an unclean termination of wpa_supplicant in which case you will need
                                              to manually remove this file before starting wpa_supplicant again.
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0
Jul 13 22:20:33 boringPC NetworkManager[527]: <error> [1594668033.3361] device (wlp6s0): Couldn't initialize supplicant interfa>
Jul 13 22:20:36 boringPC network[528]: WPA association/authentication failed for interface 'wlp6s0'
Jul 13 22:20:37 boringPC network[528]: Failed to bring the network up for profile 'cgate'
Jul 13 22:20:37 boringPC systemd[1]: netctl@cgate.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- An ExecStart= process belonging to unit netctl@cgate.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Jul 13 22:20:37 boringPC systemd[1]: netctl@cgate.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit netctl@cgate.service has entered the 'failed' state with result 'exit-code'.
Jul 13 22:20:37 boringPC systemd[1]: Failed to start Automatically generated profile by wifi-menu.
-- Subject: A start job for unit netctl@cgate.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit netctl@cgate.service has finished with a failure.
-- 
-- The job identifier is 86 and the job result is failed.
Jul 13 22:20:37 boringPC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@cgate comm="system>
Jul 13 22:20:37 boringPC kernel: audit: type=1130 audit(1594668037.586:31): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='uni>
Jul 13 22:20:43 boringPC NetworkManager[527]: <warn>  [1594668043.1685] device (wlp6s0): re-acquiring supplicant interface (#2).
Jul 13 22:20:43 boringPC NetworkManager[527]: <info>  [1594668043.6048] device (wlp6s0): supplicant interface state: internal-s>
Jul 13 22:20:43 boringPC NetworkManager[527]: <info>  [1594668043.6048] Wi-Fi P2P device controlled by interface wlp6s0 created
Jul 13 22:20:43 boringPC NetworkManager[527]: <info>  [1594668043.6050] manager: (p2p-dev-wlp6s0): new 802.11 Wi-Fi P2P device >
Jul 13 22:20:43 boringPC NetworkManager[527]: <info>  [1594668043.6052] device (p2p-dev-wlp6s0): state change: unmanaged -> una>
Jul 13 22:20:43 boringPC NetworkManager[527]: <warn>  [1594668043.6054] sup-iface[5204ba3514071fd7,0,wlp6s0]: call-p2p-cancel: >
Jul 13 22:20:43 boringPC NetworkManager[527]: <info>  [1594668043.6055] device (wlp6s0): state change: unavailable -> disconnec>
Jul 13 22:20:43 boringPC NetworkManager[527]: <info>  [1594668043.6059] device (p2p-dev-wlp6s0): state change: unavailable -> d>
Jul 13 22:20:51 boringPC systemd[1]: systemd-hostnamed.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit systemd-hostnamed.service has successfully entered the 'dead' state.
Jul 13 22:20:51 boringPC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="sy>
Jul 13 22:20:51 boringPC kernel: audit: type=1131 audit(1594668051.429:32): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='uni>
Jul 13 22:20:51 boringPC audit: BPF prog-id=10 op=UNLOAD
Jul 13 22:20:51 boringPC audit: BPF prog-id=9 op=UNLOAD
Jul 13 22:20:51 boringPC kernel: audit: type=1334 audit(1594668051.546:33): prog-id=10 op=UNLOAD
Jul 13 22:20:51 boringPC kernel: audit: type=1334 audit(1594668051.546:34): prog-id=9 op=UNLOAD
Jul 13 22:21:44 boringPC systemd[1]: sys-subsystem-net-devices-wlan0.device: Job sys-subsystem-net-devices-wlan0.device/start t>
Jul 13 22:21:44 boringPC systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/wlan0.
-- Subject: A start job for unit sys-subsystem-net-devices-wlan0.device has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit sys-subsystem-net-devices-wlan0.device has finished with a failure.
-- 
-- The job identifier is 80 and the job result is timeout.
Jul 13 22:21:44 boringPC systemd[1]: Dependency failed for Automatic wireless network connection using netctl profiles.
-- Subject: A start job for unit netctl-auto@wlan0.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit netctl-auto@wlan0.service has finished with a failure.
-- 
-- The job identifier is 81 and the job result is dependency.
Jul 13 22:21:44 boringPC systemd[1]: netctl-auto@wlan0.service: Job netctl-auto@wlan0.service/start failed with result 'depende>
Jul 13 22:21:44 boringPC systemd[1]: Dependency failed for Automatically generated profile by wifi-menu.
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: ctrl_iface exists and seems to be in use - cannot override it
Jul 13 22:20:33 boringPC wpa_supplicant[530]: Delete '/run/wpa_supplicant/wlp6s0' manually if it is not used anymore
Jul 13 22:20:33 boringPC wpa_supplicant[530]: Failed to initialize control interface '/run/wpa_supplicant'.
                                              You may have another wpa_supplicant process already running or the file was
                                              left by an unclean termination of wpa_supplicant in which case you will need
                                              to manually remove this file before starting wpa_supplicant again.
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0
Jul 13 22:20:33 boringPC NetworkManager[527]: <error> [1594668033.3361] device (wlp6s0): Couldn't initialize supplicant interfa>
Jul 13 22:20:36 boringPC network[528]: WPA association/authentication failed for interface 'wlp6s0'
Jul 13 22:20:37 boringPC network[528]: Failed to bring the network up for profile 'cgate'
Jul 13 22:20:37 boringPC systemd[1]: netctl@cgate.service: Main process exited, code=exited, status=1/FAILURE
lines 1850-1870
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:33 boringPC wpa_supplicant[530]: ctrl_iface exists and seems to be in use - cannot override it
Jul 13 22:20:33 boringPC wpa_supplicant[530]: Delete '/run/wpa_supplicant/wlp6s0' manually if it is not used anymore
Jul 13 22:20:33 boringPC wpa_supplicant[530]: Failed to initialize control interface '/run/wpa_supplicant'.
                                              You may have another wpa_supplicant process already running or the file was
                                              left by an unclean termination of wpa_supplicant in which case you will need
                                              to manually remove this file before starting wpa_supplicant again.
Jul 13 22:20:33 boringPC wpa_supplicant[530]: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0
Jul 13 22:20:33 boringPC NetworkManager[527]: <error> [1594668033.3361] device (wlp6s0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError>
Jul 13 22:20:36 boringPC network[528]: WPA association/authentication failed for interface 'wlp6s0'
Jul 13 22:20:37 boringPC network[528]: Failed to bring the network up for profile 'cgate'
Jul 13 22:20:37 boringPC systemd[1]: netctl@cgate.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited

any suggestions are appreciated smile

Last edited by bruh-i-use-arch-cow (2020-07-13 20:44:25)

Offline

#2 2020-07-13 19:47:42

loqs
Member
Registered: 2014-03-06
Posts: 18,382

Re: [SOLVED] Wifi problems...

Please provide the information requested from https://bbs.archlinux.org/viewtopic.php … 4#p1914884 including `journalctl -b`
Also the output of

find /etc/systemd -name \*.service -type l -a -xtype f -printf %f\\n

Offline

#3 2020-07-13 19:52:21

bruh-i-use-arch-cow
Member
Registered: 2020-07-01
Posts: 46

Re: [SOLVED] Wifi problems...

output form

find /etc/systemd -name \*.service -type l -a -xtype f -printf %f\\n

netctl-auto@wlan0.service
getty@tty1.service
dbus-org.freedesktop.nm-dispatcher.service
NetworkManager-wait-online.service
dbus-fi.w1.wpa_supplicant1.service
NetworkManager.service
wpa_supplicant.service
netctl@wlan0\x2dH.service
netctl@wlan0\x2dCgates_2514.service
netctl@cgate.service

output form:
journal -b

ul 13 22:20:22 boringPC NetworkManager[527]: <info>  [1594668022.1682] device (wlp6s0): set-hw-addr: set MAC address to E6:7D:0A:ED:6B:D0 (scanning)
Jul 13 22:20:22 boringPC NetworkManager[527]: <info>  [1594668022.5524] ovsdb: Could not connect: No such file or directory
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: nl80211: kernel reports: Match already configured
Jul 13 22:20:22 boringPC wpa_supplicant[530]: ctrl_iface exists and seems to be in use - cannot override it
Jul 13 22:20:22 boringPC wpa_supplicant[530]: Delete '/run/wpa_supplicant/wlp6s0' manually if it is not used anymore
Jul 13 22:20:22 boringPC wpa_supplicant[530]: Failed to initialize control interface '/run/wpa_supplicant'.
                                              You may have another wpa_supplicant process already running or the file was
                                              left by an unclean termination of wpa_supplicant in which case you will need
lines 1240-1281
Jul 13 22:20:21 boringPC NetworkManager[527]: <info>  [1594668021.6170] device (lo): ca>

Last edited by bruh-i-use-arch-cow (2020-07-13 19:54:08)

Offline

#4 2020-07-13 19:56:09

bruh-i-use-arch-cow
Member
Registered: 2020-07-01
Posts: 46

Re: [SOLVED] Wifi problems...

loqs wrote:

Please provide the information requested from https://bbs.archlinux.org/viewtopic.php … 4#p1914884 including `journalctl -b`
Also the output of

find /etc/systemd -name \*.service -type l -a -xtype f -printf %f\\n

btw ur responses are fast do you have business related to arch or something? (just asking}

Last edited by bruh-i-use-arch-cow (2020-07-13 19:56:48)

Offline

#5 2020-07-13 20:02:59

loqs
Member
Registered: 2014-03-06
Posts: 18,382

Re: [SOLVED] Wifi problems...

netctl-auto@wlan0.service
NetworkManager-wait-online.service
dbus-fi.w1.wpa_supplicant1.service
NetworkManager.service
wpa_supplicant.service
netctl@wlan0\x2dH.service
netctl@wlan0\x2dCgates_2514.service
netctl@cgate.service

Three different network management services NetworkManager,  netctl and wpa_supplicant all controlling the same interface.
Only one service should manage an interface.  Please pick one and stop and disable all services for the other two.

The `journalctl -b` output is truncated.  Please also post the output of `lspci -nnk` if the interface is PCI based or `lsusb` if it uses USB.

Offline

#6 2020-07-13 20:13:41

bruh-i-use-arch-cow
Member
Registered: 2020-07-01
Posts: 46

Re: [SOLVED] Wifi problems...

loqs wrote:
netctl-auto@wlan0.service
NetworkManager-wait-online.service
dbus-fi.w1.wpa_supplicant1.service
NetworkManager.service
wpa_supplicant.service
netctl@wlan0\x2dH.service
netctl@wlan0\x2dCgates_2514.service
netctl@cgate.service

Three different network management services NetworkManager,  netctl and wpa_supplicant all controlling the same interface.
Only one service should manage an interface.  Please pick one and stop and disable all services for the other two.

The `journalctl -b` output is truncated.  Please also post the output of `lspci -nnk` if the interface is PCI based or `lsusb` if it uses USB.

lspci -nnk

06:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8192CE PCIe Wireless Network Adapter [10ec:8178] (rev 01)
	Subsystem: Device [7392:7622]
	Kernel driver in use: rtl8192ce
	Kernel modules: rtl8192ce

also if you are still here which service do you suggest NetworkManager or wpa_supplicant?

Offline

#7 2020-07-13 20:29:48

bruh-i-use-arch-cow
Member
Registered: 2020-07-01
Posts: 46

Re: [SOLVED] Wifi problems...

loqs wrote:
netctl-auto@wlan0.service
NetworkManager-wait-online.service
dbus-fi.w1.wpa_supplicant1.service
NetworkManager.service
wpa_supplicant.service
netctl@wlan0\x2dH.service
netctl@wlan0\x2dCgates_2514.service
netctl@cgate.service

Three different network management services NetworkManager,  netctl and wpa_supplicant all controlling the same interface.
Only one service should manage an interface.  Please pick one and stop and disable all services for the other two.

The `journalctl -b` output is truncated.  Please also post the output of `lspci -nnk` if the interface is PCI based or `lsusb` if it uses USB.

ok this is so confusing so i did  "sudo systemctl disable wpa_supplicant.service"
find /etc/systemd -name \*.service -type l -a -xtype f -printf %f\\n
returns me this:

netctl-auto@wlan0.service
getty@tty1.service
dbus-org.freedesktop.nm-dispatcher.service
NetworkManager-wait-online.service
NetworkManager.service
netctl@wlan0\x2dH.service
netctl@wlan0\x2dCgates_2514.service
netctl@cgate.service

but i still get this:

-- The job identifier is 440.
Jul 13 23:22:46 boringPC wpa_supplicant[572]: Successfully initialized wpa_supplicant
Jul 13 23:22:46 boringPC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? add>
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC kernel: audit: type=1130 audit(1594671766.632:25): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=wpa_supplicant comm="systemd" exe="/usr/lib/syst>
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:46 boringPC wpa_supplicant[572]: ctrl_iface exists and seems to be in use - cannot override it
Jul 13 23:22:46 boringPC wpa_supplicant[572]: Delete '/run/wpa_supplicant/wlp6s0' manually if it is not used anymore
Jul 13 23:22:46 boringPC wpa_supplicant[572]: Failed to initialize control interface '/run/wpa_supplicant'.
                                              You may have another wpa_supplicant process already running or the file was
                                              left by an unclean termination of wpa_supplicant in which case you will need
                                              to manually remove this file before starting wpa_supplicant again.
Jul 13 23:22:46 boringPC wpa_supplicant[572]: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0
Jul 13 23:22:46 boringPC NetworkManager[523]: <error> [1594671766.8161] device (wlp6s0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError>
Jul 13 23:22:47 boringPC systemd[1]: systemd-rfkill.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: [url]https://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- The unit systemd-rfkill.service has successfully entered the 'dead' state.
Jul 13 23:22:47 boringPC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr>
Jul 13 23:22:47 boringPC kernel: audit: type=1131 audit(1594671767.872:26): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/syst>
Jul 13 23:22:51 boringPC NetworkManager[523]: <info>  [1594671771.8704] manager: startup complete
Jul 13 23:22:56 boringPC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: [url]https://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.
Jul 13 23:22:56 boringPC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" host>
Jul 13 23:22:56 boringPC kernel: audit: type=1131 audit(1594671776.222:27): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/u>
Jul 13 23:22:57 boringPC NetworkManager[523]: <warn>  [1594671777.1671] device (wlp6s0): re-acquiring supplicant interface (#1).
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: kernel reports: Match already configured
Jul 13 23:22:57 boringPC wpa_supplicant[572]: ctrl_iface exists and seems to be in use - cannot override it
Jul 13 23:22:57 boringPC wpa_supplicant[572]: Delete '/run/wpa_supplicant/wlp6s0' manually if it is not used anymore
Jul 13 23:22:57 boringPC wpa_supplicant[572]: Failed to initialize control interface '/run/wpa_supplicant'.
                                              You may have another wpa_supplicant process already running or the file was
                                              left by an unclean termination of wpa_supplicant in which case you will need
                                              to manually remove this file before starting wpa_supplicant again.
Jul 13 23:22:57 boringPC wpa_supplicant[572]: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0
Jul 13 23:22:57 boringPC NetworkManager[523]: <error> [1594671777.3360] device (wlp6s0): Couldn't initialize supplicant interface: GDBus.Error:fi.w1.wpa_supplicant1.UnknownError>
Jul 13 23:23:01 boringPC network[524]: WPA association/authentication failed for interface 'wlp6s0'
Jul 13 23:23:01 boringPC network[524]: Failed to bring the network up for profile 'cgate'
Jul 13 23:23:01 boringPC systemd[1]: netctl@cgate.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: [url]https://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- An ExecStart= process belonging to unit netctl@cgate.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Jul 13 23:23:01 boringPC systemd[1]: netctl@cgate.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: [url]https://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- 
-- The unit netctl@cgate.service has entered the 'failed' state with result 'exit-code'.
Jul 13 23:23:01 boringPC systemd[1]: Failed to start Automatically generated profile by wifi-menu.
-- Subject: A start job for unit netctl@cgate.service has failed
-- Defined-By: systemd

Last edited by bruh-i-use-arch-cow (2020-07-13 20:31:00)

Offline

#8 2020-07-13 20:31:13

loqs
Member
Registered: 2014-03-06
Posts: 18,382

Re: [SOLVED] Wifi problems...

NetworkManager will manage both the wireless connection and obtaining an IP address while wpa_supplicant only manages the former and you would need another service to obtain an IP address.
So either keep NetworkManager,  stop plus disable wpa_supplicant or stop plus disable NetworkManager and wpa_supplicant then see Dhcpcd#10-wpa_supplicant.
Edit:
https://wiki.archlinux.org/index.php/Sy … mmon_tasks e.g. to disable and stop the enabled netctl services:

# systemctl disable --now netctl-auto@wlan0.service
# systemctl disable --now netctl@wlan0\x2dH.service
# systemctl disable --now netctl@wlan0\x2dCgates_2514.service
# systemctl disable --now netctl@cgate.service

Last edited by loqs (2020-07-13 20:37:00)

Offline

#9 2020-07-13 20:36:41

bruh-i-use-arch-cow
Member
Registered: 2020-07-01
Posts: 46

Re: [SOLVED] Wifi problems...

loqs wrote:

NetworkManager will manage both the wireless connection and obtaining an IP address while wpa_supplicant only manages the former and you would need another service to obtain an IP address.
So either keep NetworkManager,  stop plus disable wpa_supplicant or stop plus disable NetworkManager and wpa_supplicant then see Dhcpcd#10-wpa_supplicant.

well i think i disabled wpa_supplicant and it wont work... why?

Offline

#10 2020-07-13 20:39:20

loqs
Member
Registered: 2014-03-06
Posts: 18,382

Re: [SOLVED] Wifi problems...

What services are enabled now?  Which ones of those are active?  What happened after you disabled wpa_supplicant?  Just disabling the service should have no effect until next reboot as it would still be active.

Offline

#11 2020-07-13 20:48:01

bruh-i-use-arch-cow
Member
Registered: 2020-07-01
Posts: 46

Re: [SOLVED] Wifi problems...

loqs wrote:

NetworkManager will manage both the wireless connection and obtaining an IP address while wpa_supplicant only manages the former and you would need another service to obtain an IP address.
So either keep NetworkManager,  stop plus disable wpa_supplicant or stop plus disable NetworkManager and wpa_supplicant then see Dhcpcd#10-wpa_supplicant.
Edit:
https://wiki.archlinux.org/index.php/Sy … mmon_tasks e.g. to disable and stop the enabled netctl services:

# systemctl disable --now netctl-auto@wlan0.service
# systemctl disable --now netctl@wlan0\x2dH.service
# systemctl disable --now netctl@wlan0\x2dCgates_2514.service
# systemctl disable --now netctl@cgate.service

yea that fixed things
seems like netctl is somehow realated with wpa_supplicant (i know they are both network manager but still why did i get wpa_supplicant error when netctl services was enabled). oh well. everything now works as intended~
thanks dude big_smile

Last edited by bruh-i-use-arch-cow (2020-07-13 20:48:24)

Offline

#12 2020-07-13 21:06:56

loqs
Member
Registered: 2014-03-06
Posts: 18,382

Re: [SOLVED] Wifi problems...

For a WPA secured connection wireless connection either wpa_supplicant or iwd need to be used to establish the secure connection.
After establishing the secure connection an IP address needs to be obtained either statically or dynamically assigned via DHCP which may use dhcpcd or dhclient,  NetworkManager has built in DHCP support.
A network management service (netctl, wpa_supplicant, dhcpcd, NetworkManager e.t.c.) calls the commands internally so you only need one management service active.

Offline

#13 2021-04-25 19:49:56

vronp
Member
Registered: 2021-04-25
Posts: 1

Re: [SOLVED] Wifi problems...

Hi all,

Noob question:

What is the way to definitively determine which of the services is calling wpa_supplicant?  I have this identical problem.

thanks

Offline

#14 2021-04-25 20:49:08

seth
Member
Registered: 2012-09-03
Posts: 62,032

Re: [SOLVED] Wifi problems...

https://bbs.archlinux.org/viewtopic.php … 5#p1915355
The problem isn't "which", it's "services".

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB