You are not logged in.
So I have an RTL8821CE wireless chip, and due to some connectivity problems I'm trying to switch to the rtl8821ce-dkms-git driver, as suggested in the wiki and elsewhere. The previous problems do indeed seem to have improved, but now I get ~3s ping spikes every 10s or so. I'm using connman and disabled background scanning in /etc/connman/main.conf, but noticed that suspending (kill -STOP) connmand removed the spikes (but DNS no longer works then ofc). And starting connmand with debug output enabled shows that scanning is still going on:
Nov 19 14:50:01 [redacted] connmand[9594]: src/technology.c:scan() technology 0x560def62f190 request from :1.19
Nov 19 14:50:01 [redacted] connmand[9594]: plugins/wifi.c:wifi_scan() device 0x560def631cb0 wifi 0x560def608af0 hidden ssid (null)
Nov 19 14:50:01 [redacted] connmand[9594]: plugins/wifi.c:wifi_scan() max ssids 9
Nov 19 14:50:01 [redacted] connmand[9594]: plugins/wifi.c:reset_autoscan()
Nov 19 14:50:01 [redacted] connmand[9594]: plugins/wifi.c:wifi_update_scanner_type()
Nov 19 14:50:01 [redacted] connmand[9594]: plugins/wifi.c:throw_wifi_scan() device 0x560def631cb0 0x560def608af0
Nov 19 14:50:01 [redacted] connmand[9594]: src/device.c:connman_device_ref_debug() 0x560def631cb0 ref 3 by plugins/wifi.c:1242:throw_wifi_scan()
Nov 19 14:50:01 [redacted] connmand[9594]: src/device.c:connman_device_set_scanning() device 0x560def631cb0 scanning 1
Nov 19 14:50:01 [redacted] connmand[9594]: src/technology.c:__connman_technology_scan_started() device 0x560def631cb0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def65f420 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def634bd0 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def5fc3f0 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def666840 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def637540 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def5fc240 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def64fe40 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def6462a0 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def64eff0 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def63f310 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def6578e0 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def651180 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def63adb0 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def643e70 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def651570 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def63bb10 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def636590 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def63c210 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def648f80 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def63d7c0 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def60b4a0 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def66be10 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def635420 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def655a00 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: src/network.c:connman_network_set_available() network 0x560def64aad0 available 0
Nov 19 14:50:01 [redacted] connmand[9594]: plugins/wifi.c:scan_started()Blocks like the above appear in journalctl, in sync with the ping spikes and followed by more verbose output shortly thereafter, relating to the result of the scan.
Any clues on how to stop this?
Last edited by sloth_ful (2023-11-19 15:47:46)
Offline
Alright, I figured out that the :1.19 in the log above refers to a dbus port and checked which process it belonged to. The culprit was flameshot, of all things. I am baffled as to why a screenshot utility would be requesting wifi scans, and also don't understand why this wasn't a problem with the previous driver. Killing the flameshot daemon resolves the issue.
Offline