Issues with wireless connection

Ask Fedora
1

Changed my Dell XPS 15 9500 for a new Lenovo Thinkpad Z16 gen2 and every 5 minutes, the WIFI reconnects and loose 4 to 8 pings. This only happens in Feroda(39 and 40), Ubuntu and Arch works without problems. I think in the Fedora LiveCD doesn’t happens.

keep getting:

Apr 13 01:22:12 molepad systemd[2122]: Started app-gnome-org.mozilla.firefox-32625.scope - Application launched by gnome-shell.
Apr 13 01:22:12 molepad gnome-shell[2363]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Apr 13 01:22:15 molepad systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Apr 13 01:22:15 molepad audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 13 01:22:15 molepad audit: BPF prog-id=146 op=UNLOAD
Apr 13 01:22:15 molepad audit: BPF prog-id=145 op=UNLOAD
Apr 13 01:22:15 molepad audit: BPF prog-id=144 op=UNLOAD
Apr 13 01:22:50 molepad systemd[2122]: app-gnome-org.mozilla.firefox-5957.scope: Consumed 5min 41.988s CPU time.
Apr 13 01:22:50 molepad wpa_supplicant[1716]: wlp1s0: SME: Trying to authenticate with fc:34:97:af:73:68 (SSID='Emilia' freq=5580 MHz)
Apr 13 01:22:51 molepad kernel: wlp1s0: disconnect from AP fc:34:97:af:73:60 for new auth to fc:34:97:af:73:68
Apr 13 01:22:51 molepad kernel: wlp1s0: authenticate with fc:34:97:af:73:68 (local address=fc:b0:de:16:d9:61)
Apr 13 01:22:51 molepad NetworkManager[32243]: <info>  [1712985771.2710] device (wlp1s0): supplicant interface state: completed -> authenticating
Apr 13 01:22:51 molepad kernel: wlp1s0: send auth to fc:34:97:af:73:68 (try 1/3)
Apr 13 01:22:51 molepad NetworkManager[32243]: <info>  [1712985771.2712] device (p2p-dev-wlp1s0): supplicant management interface state: completed -> authenticating
Apr 13 01:22:51 molepad kernel: wlp1s0: authenticated
Apr 13 01:22:51 molepad wpa_supplicant[1716]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Apr 13 01:22:51 molepad wpa_supplicant[1716]: wlp1s0: Trying to associate with fc:34:97:af:73:68 (SSID='Emilia' freq=5580 MHz)
Apr 13 01:22:51 molepad wpa_supplicant[1716]: wlp1s0: SME: Association request to the driver failed
Apr 13 01:22:51 molepad wpa_supplicant[1716]: BSSID fc:34:97:af:73:68 ignore list count incremented to 3, ignoring for 60 seconds
Apr 13 01:22:51 molepad wpa_supplicant[1716]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=CL
Apr 13 01:22:51 molepad NetworkManager[32243]: <info>  [1712985771.3413] device (wlp1s0): supplicant interface state: authenticating -> disconnected
Apr 13 01:22:51 molepad NetworkManager[32243]: <info>  [1712985771.3414] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> disconnected
Apr 13 01:22:51 molepad NetworkManager[32243]: <info>  [1712985771.4469] device (wlp1s0): supplicant interface state: disconnected -> scanning
Apr 13 01:22:51 molepad NetworkManager[32243]: <info>  [1712985771.4469] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> scanning
Apr 13 01:22:53 molepad wpa_supplicant[1716]: wlp1s0: SME: Trying to authenticate with fc:34:97:af:73:64 (SSID='Emilia' freq=5220 MHz)
Apr 13 01:22:53 molepad kernel: wlp1s0: authenticate with fc:34:97:af:73:64 (local address=fc:b0:de:16:d9:61)
Apr 13 01:22:53 molepad kernel: wlp1s0: send auth to fc:34:97:af:73:64 (try 1/3)
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.3318] device (wlp1s0): supplicant interface state: scanning -> authenticating
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.3319] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> authenticating
Apr 13 01:22:53 molepad wpa_supplicant[1716]: wlp1s0: Trying to associate with fc:34:97:af:73:64 (SSID='Emilia' freq=5220 MHz)
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.3338] device (wlp1s0): supplicant interface state: authenticating -> associating
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.3338] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating
Apr 13 01:22:53 molepad kernel: wlp1s0: authenticated
Apr 13 01:22:53 molepad kernel: wlp1s0: associate with fc:34:97:af:73:64 (try 1/3)
Apr 13 01:22:53 molepad kernel: wlp1s0: RX ReassocResp from fc:34:97:af:73:64 (capab=0x1011 status=0 aid=17)
Apr 13 01:22:53 molepad kernel: wlp1s0: associated
Apr 13 01:22:53 molepad wpa_supplicant[1716]: wlp1s0: Associated with fc:34:97:af:73:64
Apr 13 01:22:53 molepad wpa_supplicant[1716]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 13 01:22:53 molepad wpa_supplicant[1716]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
Apr 13 01:22:53 molepad wpa_supplicant[1716]: wlp1s0: WPA: Key negotiation completed with fc:34:97:af:73:64 [PTK=CCMP GTK=CCMP]
Apr 13 01:22:53 molepad wpa_supplicant[1716]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:af:73:64 completed [id=0 id_str=]
Apr 13 01:22:53 molepad wpa_supplicant[1716]: bgscan simple: Failed to enable signal strength monitoring
Apr 13 01:22:53 molepad kernel: wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:34:97:af:73:64
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.4990] device (wlp1s0): supplicant interface state: associating -> completed
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.4992] device (wlp1s0): ip:dhcp4: restarting
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.4992] dhcp4 (wlp1s0): canceled DHCP transaction
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.4992] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.4992] dhcp4 (wlp1s0): state changed no lease
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.4992] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.4994] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> completed
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.4994] device (wlp1s0): ip:dhcp4: restarting
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.4994] dhcp4 (wlp1s0): canceled DHCP transaction
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.4994] dhcp4 (wlp1s0): state changed no lease
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.4994] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.5089] dhcp4 (wlp1s0): state changed new lease, address=192.168.50.60, acd pending
Apr 13 01:22:53 molepad NetworkManager[32243]: <info>  [1712985773.5089] dhcp4 (wlp1s0): state changed new lease, address=192.168.50.60
Apr 13 01:22:53 molepad systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Apr 13 01:22:53 molepad systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Apr 13 01:22:53 molepad audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re>
Apr 13 01:22:54 molepad geoclue[1759]: Failed to query location: Could not connect to location.services.mozilla.com: No route to host
Apr 13 01:23:03 molepad systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Apr 13 01:23:03 molepad audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res>
Apr 13 01:23:12 molepad gnome-terminal-[3614]: void terminal_screen_shell_preexec(VteTerminal*): assertion '!priv->between_preexec_and_precmd' failed
smaceda@molepad:~$ journalctl
Apr 12 23:12:39 fedora kernel: Linux version 6.8.0-0.rc6.49.fc40.x86_64 (mockbuild@87dce2383d594b42805279115548046e) (gcc (GCC) 14.0.1 20240217 (Red Hat 14.0.1-0), GNU ld version 2.41-34.fc40) #1 SMP PREEMPT_DYNAMIC Mon Feb 26 18:38:52 U>
Apr 12 23:12:39 fedora kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.8.0-0.rc6.49.fc40.x86_64 root=UUID=f0eac8ef-dd81-48d6-ba31-f09d2b508dab ro rootflags=subvol=root00 rhgb quiet
Apr 12 23:12:39 fedora kernel: BIOS-provided physical RAM map:
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009bfffff] usable
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x0000000009c00000-0x0000000009dd0fff] reserved
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x0000000009dd1000-0x0000000009efffff] usable
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x0000000009f00000-0x0000000009f3bfff] ACPI NVS
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x0000000009f3c000-0x000000001ad10fff] usable
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x000000001ad11000-0x000000001bd10fff] ACPI NVS
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x000000001bd11000-0x000000001bd90fff] ACPI data
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x000000001bd91000-0x0000000020e80fff] reserved
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x0000000020e81000-0x0000000053480fff] usable
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x0000000053481000-0x00000000581fdfff] reserved
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x00000000581fe000-0x0000000059fe8fff] usable
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x0000000059fe9000-0x0000000059fecfff] reserved
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x0000000059fed000-0x0000000059feefff] usable
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x0000000059fef000-0x000000005bffffff] reserved
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x000000005d790000-0x000000005d7effff] reserved
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x000000005d7f5000-0x000000005fffffff] reserved
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x00000000c0300000-0x00000000c03fffff] reserved
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed80fff] reserved
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x0000000100000000-0x000000085e2fffff] usable
Apr 12 23:12:39 fedora kernel: BIOS-e820: [mem 0x000000085f340000-0x00000008c01fffff] reserved
Apr 12 23:12:39 fedora kernel: NX (Execute Disable) protection: active
Apr 12 23:12:39 fedora kernel: APIC: Static calls initialized
Apr 12 23:12:39 fedora kernel: e820: update [mem 0x1a498018-0x1a49b057] usable ==> usable
Apr 12 23:12:39 fedora kernel: e820: update [mem 0x1a498018-0x1a49b057] usable ==> usable
Apr 12 23:12:39 fedora kernel: extended physical RAM map:
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x0000000000100000-0x0000000009bfffff] usable
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x0000000009c00000-0x0000000009dd0fff] reserved
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x0000000009dd1000-0x0000000009efffff] usable
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x0000000009f00000-0x0000000009f3bfff] ACPI NVS
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x0000000009f3c000-0x000000001a498017] usable
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x000000001a498018-0x000000001a49b057] usable
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x000000001a49b058-0x000000001ad10fff] usable
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x000000001ad11000-0x000000001bd10fff] ACPI NVS
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x000000001bd11000-0x000000001bd90fff] ACPI data
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x000000001bd91000-0x0000000020e80fff] reserved
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x0000000020e81000-0x0000000053480fff] usable
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x0000000053481000-0x00000000581fdfff] reserved
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x00000000581fe000-0x0000000059fe8fff] usable
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x0000000059fe9000-0x0000000059fecfff] reserved
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x0000000059fed000-0x0000000059feefff] usable
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x0000000059fef000-0x000000005bffffff] reserved
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x000000005d790000-0x000000005d7effff] reserved
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x000000005d7f5000-0x000000005fffffff] reserved
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x00000000c0300000-0x00000000c03fffff] reserved
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x00000000fed80000-0x00000000fed80fff] reserved
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x0000000100000000-0x000000085e2fffff] usable
Apr 12 23:12:39 fedora kernel: reserve setup_data: [mem 0x000000085f340000-0x00000008c01fffff] reserved
Apr 12 23:12:39 fedora kernel: efi: EFI v2.7 by Lenovo
Apr 12 23:12:39 fedora kernel: efi: ACPI=0x1bd90000 ACPI 2.0=0x1bd90014 SMBIOS=0x20b6a000 SMBIOS 3.0=0x20b5d000 TPMFinalLog=0x1bce8000 MEMATTR=0x4dd6f018 ESRT=0x4ddbad18 MOKvar=0x20b9a000 RNG=0x1bd8f018 TPMEventLog=0x1a49c018 
Apr 12 23:12:39 fedora kernel: random: crng init done
Apr 12 23:12:39 fedora kernel: efi: Remove mem69: MMIO range=[0xc0300000-0xc03fffff] (1MB) from e820 map
Apr 12 23:12:39 fedora kernel: e820: remove [mem 0xc0300000-0xc03fffff] reserved
Apr 12 23:12:39 fedora kernel: efi: Not removing mem71: MMIO range=[0xfed80000-0xfed80fff] (4KB) from e820 map
Apr 12 23:12:39 fedora kernel: efi: Remove mem73: MMIO range=[0x8a0000000-0x8c01fffff] (514MB) from e820 map
Apr 12 23:12:39 fedora kernel: e820: remove [mem 0x8a0000000-0x8c01fffff] reserved
Apr 12 23:12:39 fedora kernel: secureboot: Secure boot disabled
Apr 12 23:12:39 fedora kernel: SMBIOS 3.3.0 present.
Apr 12 23:12:39 fedora kernel: DMI: LENOVO 21JYCTO1WW/21JYCTO1WW, BIOS N41ET38W (1.15 ) 01/10/2024
Apr 12 23:12:39 fedora kernel: tsc: Fast TSC calibration using PIT
Apr 12 23:12:39 fedora kernel: tsc: Detected 3793.043 MHz processor
Apr 12 23:12:39 fedora kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Apr 12 23:12:39 fedora kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Apr 12 23:12:39 fedora kernel: last_pfn = 0x85e300 max_arch_pfn = 0x400000000
Apr 12 23:12:39 fedora kernel: MTRR map: 7 entries (3 fixed + 4 variable; max 20), built from 9 variable MTRRs
Apr 12 23:12:39 fedora kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Apr 12 23:12:39 fedora kernel: last_pfn = 0x59fef max_arch_pfn = 0x400000000
Apr 12 23:12:39 fedora kernel: esrt: Reserving ESRT space from 0x000000004ddbad18 to 0x000000004ddbae40.
Apr 12 23:12:39 fedora kernel: e820: update [mem 0x4ddba000-0x4ddbafff] usable ==> reserved
Apr 12 23:12:39 fedora kernel: Using GB pages for direct mapping
Apr 12 23:12:39 fedora kernel: secureboot: Secure boot disabled
Apr 12 23:12:39 fedora kernel: RAMDISK: [mem 0x149e4000-0x18312fff]
Apr 12 23:12:39 fedora kernel: ACPI: Early table checksum verification disabled
Apr 12 23:12:39 fedora kernel: ACPI: RSDP 0x000000001BD90014 000024 (v02 LENOVO)
Apr 12 23:12:39 fedora kernel: ACPI: XSDT 0x000000001BD8E188 000164 (v01 LENOVO TP-N41   00001150 PTEC 00000002)
Apr 12 23:12:39 fedora kernel: ACPI: FACP 0x000000001C85F000 000114 (v06 LENOVO TP-N41   00001150 PTEC 00000002)
...skipping...
Apr 13 01:28:12 molepad NetworkManager[32243]: <info>  [1712986092.0002] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> disconnected
Apr 13 01:28:12 molepad NetworkManager[32243]: <info>  [1712986092.1053] device (wlp1s0): supplicant interface state: disconnected -> scanning
Apr 13 01:28:12 molepad NetworkManager[32243]: <info>  [1712986092.1054] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> scanning
Apr 13 01:28:13 molepad wpa_supplicant[1716]: wlp1s0: SME: Trying to authenticate with fc:34:97:af:73:64 (SSID='Emilia' freq=5220 MHz)
Apr 13 01:28:13 molepad kernel: wlp1s0: authenticate with fc:34:97:af:73:64 (local address=fc:b0:de:16:d9:61)
Apr 13 01:28:13 molepad NetworkManager[32243]: <info>  [1712986093.9940] device (wlp1s0): supplicant interface state: scanning -> authenticating
Apr 13 01:28:13 molepad kernel: wlp1s0: send auth to fc:34:97:af:73:64 (try 1/3)
Apr 13 01:28:13 molepad NetworkManager[32243]: <info>  [1712986093.9940] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> authenticating
Apr 13 01:28:13 molepad wpa_supplicant[1716]: wlp1s0: Trying to associate with fc:34:97:af:73:64 (SSID='Emilia' freq=5220 MHz)
Apr 13 01:28:13 molepad NetworkManager[32243]: <info>  [1712986093.9962] device (wlp1s0): supplicant interface state: authenticating -> associating
Apr 13 01:28:13 molepad NetworkManager[32243]: <info>  [1712986093.9962] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating
Apr 13 01:28:13 molepad kernel: wlp1s0: authenticated
Apr 13 01:28:13 molepad kernel: wlp1s0: associate with fc:34:97:af:73:64 (try 1/3)
Apr 13 01:28:14 molepad kernel: wlp1s0: RX ReassocResp from fc:34:97:af:73:64 (capab=0x1011 status=30 aid=17)
Apr 13 01:28:14 molepad kernel: wlp1s0: fc:34:97:af:73:64 rejected association temporarily; comeback duration 981 TU (1004 ms)
Apr 13 01:28:14 molepad geoclue[1759]: Failed to query location: Could not connect to location.services.mozilla.com: No route to host
Apr 13 01:28:15 molepad kernel: wlp1s0: associate with fc:34:97:af:73:64 (try 2/3)
Apr 13 01:28:15 molepad kernel: wlp1s0: RX ReassocResp from fc:34:97:af:73:64 (capab=0x1011 status=30 aid=17)
Apr 13 01:28:15 molepad kernel: wlp1s0: fc:34:97:af:73:64 rejected association temporarily; comeback duration 981 TU (1004 ms)
Apr 13 01:28:16 molepad kernel: wlp1s0: associate with fc:34:97:af:73:64 (try 3/3)
Apr 13 01:28:16 molepad kernel: wlp1s0: deauthenticated from fc:34:97:af:73:64 while associating (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
Apr 13 01:28:16 molepad wpa_supplicant[1716]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=fc:34:97:af:73:64 reason=6
Apr 13 01:28:16 molepad wpa_supplicant[1716]: BSSID fc:34:97:af:73:64 ignore list count incremented to 2, ignoring for 10 seconds
Apr 13 01:28:16 molepad NetworkManager[32243]: <info>  [1712986096.1278] device (wlp1s0): supplicant interface state: associating -> disconnected
Apr 13 01:28:16 molepad NetworkManager[32243]: <info>  [1712986096.1279] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> disconnected
Apr 13 01:28:16 molepad NetworkManager[32243]: <info>  [1712986096.2275] device (wlp1s0): supplicant interface state: disconnected -> scanning
Apr 13 01:28:16 molepad NetworkManager[32243]: <info>  [1712986096.2276] device (p2p-dev-wlp1s0): supplicant management interface state: disconnected -> scanning
Apr 13 01:28:17 molepad wpa_supplicant[1716]: wlp1s0: SME: Trying to authenticate with fc:34:97:af:73:60 (SSID='Emilia' freq=2457 MHz)
Apr 13 01:28:17 molepad kernel: wlp1s0: 80 MHz not supported, disabling VHT
Apr 13 01:28:17 molepad kernel: wlp1s0: authenticate with fc:34:97:af:73:60 (local address=fc:b0:de:16:d9:61)
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.4001] device (wlp1s0): supplicant interface state: scanning -> authenticating
Apr 13 01:28:17 molepad kernel: wlp1s0: send auth to fc:34:97:af:73:60 (try 1/3)
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.4002] device (p2p-dev-wlp1s0): supplicant management interface state: scanning -> authenticating
Apr 13 01:28:17 molepad wpa_supplicant[1716]: wlp1s0: Trying to associate with fc:34:97:af:73:60 (SSID='Emilia' freq=2457 MHz)
Apr 13 01:28:17 molepad kernel: wlp1s0: authenticated
Apr 13 01:28:17 molepad kernel: wlp1s0: associate with fc:34:97:af:73:60 (try 1/3)
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.4115] device (wlp1s0): supplicant interface state: authenticating -> associating
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.4115] device (p2p-dev-wlp1s0): supplicant management interface state: authenticating -> associating
Apr 13 01:28:17 molepad kernel: wlp1s0: RX AssocResp from fc:34:97:af:73:60 (capab=0x1411 status=0 aid=33)
Apr 13 01:28:17 molepad kernel: wlp1s0: associated
Apr 13 01:28:17 molepad wpa_supplicant[1716]: wlp1s0: Associated with fc:34:97:af:73:60
Apr 13 01:28:17 molepad wpa_supplicant[1716]: wlp1s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr 13 01:28:17 molepad wpa_supplicant[1716]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.5213] device (wlp1s0): supplicant interface state: associating -> 4way_handshake
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.5213] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> 4way_handshake
Apr 13 01:28:17 molepad kernel: wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:34:97:af:73:60
Apr 13 01:28:17 molepad wpa_supplicant[1716]: wlp1s0: WPA: Key negotiation completed with fc:34:97:af:73:60 [PTK=CCMP GTK=CCMP]
Apr 13 01:28:17 molepad wpa_supplicant[1716]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to fc:34:97:af:73:60 completed [id=0 id_str=]
Apr 13 01:28:17 molepad wpa_supplicant[1716]: bgscan simple: Failed to enable signal strength monitoring
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.5814] device (wlp1s0): supplicant interface state: 4way_handshake -> completed
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.5816] device (wlp1s0): ip:dhcp4: restarting
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.5817] dhcp4 (wlp1s0): canceled DHCP transaction
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.5817] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.5817] dhcp4 (wlp1s0): state changed no lease
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.5817] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Apr 13 01:28:17 molepad NetworkManager[32243]: <info>  [1712986097.5819] device (p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> completed
Apr 13 01:28:17 molepad geoclue[1759]: Failed to query location: Could not connect to location.services.mozilla.com: No route to host
Apr 13 01:28:19 molepad NetworkManager[32243]: <info>  [1712986099.6040] dhcp4 (wlp1s0): state changed new lease, address=192.168.50.60, acd pending
Apr 13 01:28:19 molepad NetworkManager[32243]: <info>  [1712986099.6041] dhcp4 (wlp1s0): state changed new lease, address=192.168.50.60
Apr 13 01:28:19 molepad systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Apr 13 01:28:19 molepad systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Apr 13 01:28:19 molepad audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re>
Apr 13 01:28:23 molepad gnome-terminal-[3614]: void terminal_screen_shell_preexec(VteTerminal*): assertion '!priv->between_preexec_and_precmd' failed
Apr 13 01:28:29 molepad systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Apr 13 01:28:29 molepad audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res>

PS: Let me know if some more information is needed.

Please help!!!

2

Can you try journalctl -k | grep -iE 'wlp1s0|wpa_supplicant|NetworkManager|authentication|association' and see what that brings up?

Also try : dmesg | grep -iE 'wlp1s0|wpa_supplicant|NetworkManager|authentication|association'

Let’s see what that brings back.

3

In addition to the requested details from journalctl and dmesg, please make sure the system (both Fedora and Lenovo BIOS/firmware) are updated so you aren’t chasing a problem that has already been fixed.

4

It seems that the connection roams between various channels:

Apr 13 01:28:13 molepad wpa_supplicant[1716]: wlp1s0: Trying to associate with fc:34:97:af:73:64 (SSID='Emilia' freq=5220 MHz)

... snip ...

Apr 13 01:28:17 molepad wpa_supplicant[1716]: wlp1s0: Trying to associate with fc:34:97:af:73:60 (SSID='Emilia' freq=2457 MHz)

This is indeed annoying behavior and I had to enable (on my router) only some channels for my device. Not sure if that is due to varying signal quality or what is the reason for this :confused:

1 Like
5

It is possible within the fedora settings to lock the device to use only the 5G or the 2.4G channels.
Quite possibly the system prefers the 5G connection but it may be marginal on signal strength so drops and has to be reconnected.

The router can usually also be configured to use only one of those bands for connections. The 2.4G band usually is better for longer distances but is a little slower in data transfer speeds.

The info you post seems to indicate the same SSID is used for both bands and thus leaves the automatic negotiation up to the system instead of selected by the user.

6

The requested information:

journalctl -k | grep -iE ‘wlp1s0|wpa_supplicant|NetworkManager|authentication|association’

smaceda@fedora:~$ journalctl -k | grep -iE 'wlp1s0|wpa_supplicant|NetworkManager|authentication|association'
Apr 17 08:24:26 fedora kernel: mt7921e 0000:01:00.0 wlp1s0: renamed from wlan0
Apr 17 08:25:08 fedora kernel: wlp1s0: authenticate with fc:34:97:af:73:64 (local address=3e:b8:d9:cc:c1:c2)
Apr 17 08:25:08 fedora kernel: wlp1s0: send auth to fc:34:97:af:73:64 (try 1/3)
Apr 17 08:25:08 fedora kernel: wlp1s0: authenticated
Apr 17 08:25:08 fedora kernel: wlp1s0: associate with fc:34:97:af:73:64 (try 1/3)
Apr 17 08:25:08 fedora kernel: wlp1s0: RX AssocResp from fc:34:97:af:73:64 (capab=0x1011 status=0 aid=20)
Apr 17 08:25:08 fedora kernel: wlp1s0: associated
Apr 17 08:25:08 fedora kernel: wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:34:97:af:73:64
Apr 17 08:31:08 fedora kernel: wlp1s0: disconnect from AP fc:34:97:af:73:64 for new auth to fc:34:97:af:73:68
Apr 17 08:31:08 fedora kernel: wlp1s0: authenticate with fc:34:97:af:73:68 (local address=3e:b8:d9:cc:c1:c2)
Apr 17 08:31:09 fedora kernel: wlp1s0: send auth to fc:34:97:af:73:68 (try 1/3)
Apr 17 08:31:09 fedora kernel: wlp1s0: authenticated
Apr 17 08:31:09 fedora kernel: wlp1s0: authenticate with fc:34:97:af:73:64 (local address=3e:b8:d9:cc:c1:c2)
Apr 17 08:31:09 fedora kernel: wlp1s0: send auth to fc:34:97:af:73:64 (try 1/3)
Apr 17 08:31:09 fedora kernel: wlp1s0: authenticated
Apr 17 08:31:09 fedora kernel: wlp1s0: associate with fc:34:97:af:73:64 (try 1/3)
Apr 17 08:31:09 fedora kernel: wlp1s0: RX ReassocResp from fc:34:97:af:73:64 (capab=0x1011 status=30 aid=20)
Apr 17 08:31:09 fedora kernel: wlp1s0: fc:34:97:af:73:64 rejected association temporarily; comeback duration 981 TU (1004 ms)
Apr 17 08:31:10 fedora kernel: wlp1s0: associate with fc:34:97:af:73:64 (try 2/3)
Apr 17 08:31:10 fedora kernel: wlp1s0: RX ReassocResp from fc:34:97:af:73:64 (capab=0x1011 status=30 aid=20)
Apr 17 08:31:10 fedora kernel: wlp1s0: fc:34:97:af:73:64 rejected association temporarily; comeback duration 981 TU (1004 ms)
Apr 17 08:31:11 fedora kernel: wlp1s0: associate with fc:34:97:af:73:64 (try 3/3)
Apr 17 08:31:11 fedora kernel: wlp1s0: deauthenticated from fc:34:97:af:73:64 while associating (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
Apr 17 08:31:13 fedora kernel: wlp1s0: 80 MHz not supported, disabling VHT
Apr 17 08:31:13 fedora kernel: wlp1s0: authenticate with fc:34:97:af:73:60 (local address=3e:b8:d9:cc:c1:c2)
Apr 17 08:31:13 fedora kernel: wlp1s0: send auth to fc:34:97:af:73:60 (try 1/3)
Apr 17 08:31:13 fedora kernel: wlp1s0: authenticated
Apr 17 08:31:13 fedora kernel: wlp1s0: associate with fc:34:97:af:73:60 (try 1/3)
Apr 17 08:31:13 fedora kernel: wlp1s0: RX AssocResp from fc:34:97:af:73:60 (capab=0x1411 status=0 aid=34)
Apr 17 08:31:13 fedora kernel: wlp1s0: associated
Apr 17 08:31:13 fedora kernel: wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:34:97:af:73:60
Apr 17 08:31:17 fedora kernel: wlp1s0: deauthenticated from fc:34:97:af:73:60 (Reason: 2=PREV_AUTH_NOT_VALID)
Apr 17 08:31:18 fedora kernel: wlp1s0: 80 MHz not supported, disabling VHT
Apr 17 08:31:18 fedora kernel: wlp1s0: authenticate with fc:34:97:ae:d7:e1 (local address=3e:b8:d9:cc:c1:c2)
Apr 17 08:31:18 fedora kernel: wlp1s0: send auth to fc:34:97:ae:d7:e1 (try 1/3)
Apr 17 08:31:18 fedora kernel: wlp1s0: authenticated
Apr 17 08:31:18 fedora kernel: wlp1s0: associate with fc:34:97:ae:d7:e1 (try 1/3)
Apr 17 08:31:18 fedora kernel: wlp1s0: RX AssocResp from fc:34:97:ae:d7:e1 (capab=0x1411 status=0 aid=26)
Apr 17 08:31:18 fedora kernel: wlp1s0: associated
Apr 17 08:31:18 fedora kernel: wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:34:97:ae:d7:e1
Apr 17 08:36:37 fedora kernel: wlp1s0: disconnect from AP fc:34:97:ae:d7:e1 for new auth to fc:34:97:af:73:68
Apr 17 08:36:37 fedora kernel: wlp1s0: authenticate with fc:34:97:af:73:68 (local address=3e:b8:d9:cc:c1:c2)
Apr 17 08:36:37 fedora kernel: wlp1s0: send auth to fc:34:97:af:73:68 (try 1/3)
Apr 17 08:36:37 fedora kernel: wlp1s0: authenticated
Apr 17 08:36:39 fedora kernel: wlp1s0: authenticate with fc:34:97:af:73:64 (local address=3e:b8:d9:cc:c1:c2)
Apr 17 08:36:39 fedora kernel: wlp1s0: send auth to fc:34:97:af:73:64 (try 1/3)
Apr 17 08:36:39 fedora kernel: wlp1s0: authenticated
Apr 17 08:36:39 fedora kernel: wlp1s0: associate with fc:34:97:af:73:64 (try 1/3)
Apr 17 08:36:39 fedora kernel: wlp1s0: RX ReassocResp from fc:34:97:af:73:64 (capab=0x1011 status=0 aid=22)
Apr 17 08:36:39 fedora kernel: wlp1s0: associated
Apr 17 08:36:39 fedora kernel: wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:34:97:af:73:64
smaceda@fedora:~$

sudo dmesg | grep -iE ‘wlp1s0|wpa_supplicant|NetworkManager|authentication|association’

[   27.774673] mt7921e 0000:01:00.0 wlp1s0: renamed from wlan0
[   69.876273] wlp1s0: authenticate with fc:34:97:af:73:64 (local address=3e:b8:d9:cc:c1:c2)
[   70.353947] wlp1s0: send auth to fc:34:97:af:73:64 (try 1/3)
[   70.356539] wlp1s0: authenticated
[   70.357101] wlp1s0: associate with fc:34:97:af:73:64 (try 1/3)
[   70.369208] wlp1s0: RX AssocResp from fc:34:97:af:73:64 (capab=0x1011 status=0 aid=20)
[   70.398478] wlp1s0: associated
[   70.641995] wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:34:97:af:73:64
[  429.355870] wlp1s0: disconnect from AP fc:34:97:af:73:64 for new auth to fc:34:97:af:73:68
[  429.576590] wlp1s0: authenticate with fc:34:97:af:73:68 (local address=3e:b8:d9:cc:c1:c2)
[  430.053823] wlp1s0: send auth to fc:34:97:af:73:68 (try 1/3)
[  430.056535] wlp1s0: authenticated
[  430.590362] wlp1s0: authenticate with fc:34:97:af:73:64 (local address=3e:b8:d9:cc:c1:c2)
[  430.605000] wlp1s0: send auth to fc:34:97:af:73:64 (try 1/3)
[  430.607552] wlp1s0: authenticated
[  430.608298] wlp1s0: associate with fc:34:97:af:73:64 (try 1/3)
[  430.619707] wlp1s0: RX ReassocResp from fc:34:97:af:73:64 (capab=0x1011 status=30 aid=20)
[  430.619714] wlp1s0: fc:34:97:af:73:64 rejected association temporarily; comeback duration 981 TU (1004 ms)
[  431.633407] wlp1s0: associate with fc:34:97:af:73:64 (try 2/3)
[  431.640701] wlp1s0: RX ReassocResp from fc:34:97:af:73:64 (capab=0x1011 status=30 aid=20)
[  431.640738] wlp1s0: fc:34:97:af:73:64 rejected association temporarily; comeback duration 981 TU (1004 ms)
[  432.657774] wlp1s0: associate with fc:34:97:af:73:64 (try 3/3)
[  432.662857] wlp1s0: deauthenticated from fc:34:97:af:73:64 while associating (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
[  433.928677] wlp1s0: 80 MHz not supported, disabling VHT
[  433.964323] wlp1s0: authenticate with fc:34:97:af:73:60 (local address=3e:b8:d9:cc:c1:c2)
[  434.126118] wlp1s0: send auth to fc:34:97:af:73:60 (try 1/3)
[  434.132377] wlp1s0: authenticated
[  434.133177] wlp1s0: associate with fc:34:97:af:73:60 (try 1/3)
[  434.152131] wlp1s0: RX AssocResp from fc:34:97:af:73:60 (capab=0x1411 status=0 aid=34)
[  434.194613] wlp1s0: associated
[  434.194715] wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:34:97:af:73:60
[  438.593848] wlp1s0: deauthenticated from fc:34:97:af:73:60 (Reason: 2=PREV_AUTH_NOT_VALID)
[  439.119647] wlp1s0: 80 MHz not supported, disabling VHT
[  439.155361] wlp1s0: authenticate with fc:34:97:ae:d7:e1 (local address=3e:b8:d9:cc:c1:c2)
[  439.166910] wlp1s0: send auth to fc:34:97:ae:d7:e1 (try 1/3)
[  439.171819] wlp1s0: authenticated
[  439.172008] wlp1s0: associate with fc:34:97:ae:d7:e1 (try 1/3)
[  439.208246] wlp1s0: RX AssocResp from fc:34:97:ae:d7:e1 (capab=0x1411 status=0 aid=26)
[  439.246555] wlp1s0: associated
[  439.469699] wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:34:97:ae:d7:e1
[  758.411333] wlp1s0: disconnect from AP fc:34:97:ae:d7:e1 for new auth to fc:34:97:af:73:68
[  758.654304] wlp1s0: authenticate with fc:34:97:af:73:68 (local address=3e:b8:d9:cc:c1:c2)
[  758.670882] wlp1s0: send auth to fc:34:97:af:73:68 (try 1/3)
[  758.678711] wlp1s0: authenticated
[  760.711052] wlp1s0: authenticate with fc:34:97:af:73:64 (local address=3e:b8:d9:cc:c1:c2)
[  760.725726] wlp1s0: send auth to fc:34:97:af:73:64 (try 1/3)
[  760.728378] wlp1s0: authenticated
[  760.729119] wlp1s0: associate with fc:34:97:af:73:64 (try 1/3)
[  760.741296] wlp1s0: RX ReassocResp from fc:34:97:af:73:64 (capab=0x1011 status=0 aid=22)
[  760.781167] wlp1s0: associated
[  760.820115] wlp1s0: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:34:97:af:73:64
9

It seems like the device is constantly switching between access points and encountering authentication issues, leading to disconnections. You may need to investigate the authentication settings and stability of the Wi-Fi network, as well as ensure that the access points are correctly configured.

Is it possible to reboot or unplug the Router, Access Point ???

10

I have seen similar negotiation issues when the router only supported IPv4 and the host was trying to configure both IPv4 and IPv6 connections. Maybe try with disabling IPv6 on the host and see what happens.?

1 Like
11

Router unpluged and still have the same problem.

12

IPv6 is disabled already

13

I’m sorry, but i do not know what else to do here.

14

Thanks for the help anyway! I believe I will must stick to Ubuntu or Arch.

15

After some time I found the problem and a workaround…

I have a Asus ZenWIFI xt8 mesh system, and when I configure it with a wired back-haul it uses the 3 frequencies for clients: 2.4ghz, 5ghz and another 5ghz. and fedora for an strange reason, doesn’t undestand that is the same AP and reconnect every 5 minutes.

The solution: Change the mesh system to use one of the 5ghz frecuencies dedicated for backhaul and the problem is resolved.

Anyway… this is a poor implementation of networking from Fedora side, and also tried to report the problem by other channels and have no Luck.

Thanks to all that try to help here, I am switching to ARCH, hopping to get a more active community!

1 Like
16

Your problem is understandable.
Improvements can only be made if the developers know of the problem and that requires feedback from users in the form of a bug report.
https://bugzilla.redhat.com/

17

Hey I’m just a volunteer, I don’t work or am affiliated with Fedora. I tried my best and could only provide help to the OS to the best of my ability and experience.

either way here are some things you “could” try. . .

  • You could try assigning a static IP address to your Fedora machine
  • Instead of relying on NetworkManager’s automatic connection management, you could try manually configuring the connection settings for your WiFi network. This may involve specifying the SSID, security type, and possibly even the BSSID, to ensure that your Fedora machine always connects to the same access point.
  • You could potentially create custom scripts or use automation tools to monitor your network connection and automatically reconnect if it drops.
18

@hamrheadcorvette thanks for your help! you are awesome!!! I will create a Bug just for you, to try to contribute for a better distro for you. But like a said… I will try another distro.

1 Like
19

Basic functions like networking are largely from linux.org. Distros may differ in the user facing tools, but those also come from other large projects like Gnome and KDE. Fedora does use newer versions than most distros, and many bug fixes from Fedora users end up benefiting all distros. Failure to provide a good bug report may mean the problem will reappear in other distros after Fedora has started to use the upstream fixes. If you can’t afford to wait for a fix, you should consider keeping Fedora (external USB-C SSD’s work well for such purposes if you can turn off secure boot) so you can check that the issue has been fixed.