Network Manager non collega il laptop alla rete wifi dopo il passaggio a Fedora 37

Fedora Linux Configurazione
#1

Buongiorno, come da titolo ho fatto l’upgrade da F36 a F37 e KDE daemon mi chiede sempre la password (che inserisco ogni volta) senza collegarsi alla rete.

Ecco la situazione:

$ inxi -N
Network:
Device-1: Broadcom NetLink BCM57785 Gigabit Ethernet PCIe driver: tg3
Device-2: Qualcomm Atheros AR9485 Wireless Network Adapter driver: ath9k

$ dmesg | grep ath
[ 2.963477] systemd[1]: Started rngd.service - Hardware RNG Entropy Gatherer Daemon.
[ 19.677503] systemd[1]: /usr/lib/systemd/system/zoneminder.service:15: PIDFile= references a path below legacy directory /var/run/, updating /var/run/zoneminder/zm.pid → /run/zoneminder/zm.pid; please update the unit file accordingly.
[ 21.359695] systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of a failed condition check (ConditionPathExists=!/run/plymouth/pid).
[ 21.359810] systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
[ 21.380733] systemd[1]: multipathd.socket - multipathd control socket was skipped because of a failed condition check (ConditionPathExists=/etc/multipath.conf).
[ 21.402026] systemd[1]: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of a failed condition check (ConditionPathExists=/etc/krb5.keytab).
[ 21.834105] systemd[1]: multipathd.service - Device-Mapper Multipath Device Controller was skipped because of a failed condition check (ConditionPathExists=/etc/multipath.conf).
[ 29.661272] ath: phy0: Enable LNA combining
[ 29.662532] ath: phy0: ASPM enabled: 0x43
[ 29.662536] ath: EEPROM regdomain: 0x65
[ 29.662538] ath: EEPROM indicates we should expect a direct regpair map
[ 29.662540] ath: Country alpha2 being used: 00
[ 29.662541] ath: Regpair used: 0x65
[ 34.885553] ath9k 0000:03:00.0 wlp3s0: renamed from wlan0
[ 257.037744] ath: phy0: ASPM enabled: 0x43
[ 296.065355] ath: phy0: ASPM enabled: 0x43
[ 370.698638] ath: phy0: ASPM enabled: 0x43

Qualcuno mi puo’ aiutare? Grazie.

#2

Giusto per prova. Dai questo comando
sudo update-crypto-policies --set LEGACY
e riavvia.
Se non si collega lo stesso, non c’entra nulla e rimetti il default.
sudo update-crypto-policies --set DEFAULT

#3

Ho dato il comando e poi riavviato ma non è cambiato nulla.

#4

Il primo dei 2 comandi …

#5

Nei log ci hai guardato?
journalctl

#6

Questo riguarda il tentativo di accesso alla rete durante il boot di Fedora, non ho capito molto…

$ sudo journalctl -fu NetworkManager
mar 17 07:56:23 localhost.localdomain NetworkManager[1040]: [1679036183.3125] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> i
nactive
mar 17 07:56:24 localhost.localdomain NetworkManager[1040]: [1679036184.7640] device (wlp3s0): no secrets: User canceled the secrets request.
mar 17 07:56:24 localhost.localdomain NetworkManager[1040]: [1679036184.7641] device (wlp3s0): state change: need-auth -> failed (reason ‘no-secrets’, sys-ifac
e-state: ‘managed’)
mar 17 07:56:24 localhost.localdomain NetworkManager[1040]: [1679036184.7875] device (wlp3s0): set-hw-addr: set MAC address to 3E:8C:8C:7C:65:C3 (scanning)
mar 17 07:56:24 localhost.localdomain NetworkManager[1040]: [1679036184.8050] device (wlp3s0): Activation: failed for connection ‘TP-Link_7377’
mar 17 07:56:24 localhost.localdomain NetworkManager[1040]: [1679036184.8055] device (wlp3s0): supplicant interface state: inactive -> interface_disabled
mar 17 07:56:24 localhost.localdomain NetworkManager[1040]: [1679036184.8056] device (p2p-dev-wlp3s0): supplicant management interface state: inactive -> inter
face_disabled
mar 17 07:56:24 localhost.localdomain NetworkManager[1040]: [1679036184.8071] device (wlp3s0): state change: failed -> disconnected (reason ‘none’, sys-iface-s
tate: ‘managed’)
mar 17 07:56:24 localhost.localdomain NetworkManager[1040]: [1679036184.8141] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
mar 17 07:56:24 localhost.localdomain NetworkManager[1040]: [1679036184.8142] device (p2p-dev-wlp3s0): supplicant management interface state: interface_disable
d -> inactive

mar 17 08:03:17 localhost.localdomain NetworkManager[1040]: [1679036597.6645] device (wlp3s0): set-hw-addr: set MAC address to 3A:DD:D1:4E:48:C1 (scanning)
mar 17 08:03:17 localhost.localdomain NetworkManager[1040]: [1679036597.8643] device (wlp3s0): supplicant interface state: inactive -> disconnected
mar 17 08:03:17 localhost.localdomain NetworkManager[1040]: [1679036597.8644] device (p2p-dev-wlp3s0): supplicant management interface state: inactive -> disco
nnected
mar 17 08:03:17 localhost.localdomain NetworkManager[1040]: [1679036597.8752] device (wlp3s0): supplicant interface state: disconnected -> inactive
mar 17 08:03:17 localhost.localdomain NetworkManager[1040]: [1679036597.8753] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> i
nactive

Ho nuovamente richiesto l’accesso alla rete wifi e ho fornito la password … e questo è il nuovo log:

$ sudo journalctl -fu NetworkManager
mar 17 08:09:26 localhost.localdomain NetworkManager[1040]: [1679036966.7587] device (wlp3s0): supplicant interface state: associating -> associated
mar 17 08:09:26 localhost.localdomain NetworkManager[1040]: [1679036966.7588] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> associated
mar 17 08:09:26 localhost.localdomain NetworkManager[1040]: [1679036966.9055] device (wlp3s0): supplicant interface state: associated -> 4way_handshake
mar 17 08:09:26 localhost.localdomain NetworkManager[1040]: [1679036966.9056] device (p2p-dev-wlp3s0): supplicant management interface state: associated -> 4way_handshake
mar 17 08:09:33 localhost.localdomain NetworkManager[1040]: [1679036973.0297] device (wlp3s0): supplicant interface state: 4way_handshake -> disconnected
mar 17 08:09:33 localhost.localdomain NetworkManager[1040]: [1679036973.0299] device (wlp3s0): Activation: (wifi) disconnected during association, asking for new key
mar 17 08:09:33 localhost.localdomain NetworkManager[1040]: [1679036973.0302] device (wlp3s0): state change: config -> need-auth (reason ‘supplicant-disconnect’, sys-iface-state: ‘managed’)
mar 17 08:09:33 localhost.localdomain NetworkManager[1040]: [1679036973.0311] device (p2p-dev-wlp3s0): supplicant management interface state: 4way_handshake -> disconnected
mar 17 08:09:33 localhost.localdomain NetworkManager[1040]: [1679036973.1289] device (wlp3s0): supplicant interface state: disconnected -> inactive
mar 17 08:09:33 localhost.localdomain NetworkManager[1040]: [1679036973.1290] device (p2p-dev-wlp3s0): supplicant management interface state: disconnected -> inactive

#7

Rispetto ai precedenti aggiornamenti di Fedora, nel passaggio dalla 36 alla 37 ho dato il comando AUTOREMOVE. Potrei aver cancellato qualche pacchetto di troppo??
Ecco il log di DNF:

2023-03-15T16:45:52+0100 DDEBUG Base command: autoremove
2023-03-15T16:45:52+0100 DDEBUG Extra commands: [‘autoremove’]
2023-03-15T16:45:52+0100 DEBUG User-Agent: constructed: ‘libdnf (Fedora Linux 37; kde; Linux.x86_64)’
2023-03-15T16:46:27+0100 DEBUG repository: uso della cache per fedora
2023-03-15T16:46:28+0100 DEBUG fedora: usando metadati di sab 5 nov 2022, 09:04:38.
2023-03-15T16:46:28+0100 DEBUG repository: uso della cache per fedora-cisco-openh264
2023-03-15T16:46:28+0100 DEBUG fedora-cisco-openh264: usando metadati di gio 6 ott 2022, 13:01:40.
2023-03-15T16:46:28+0100 DEBUG repository: uso della cache per fedora-modular
2023-03-15T16:46:28+0100 DEBUG fedora-modular: usando metadati di sab 5 nov 2022, 08:58:03.
2023-03-15T16:46:29+0100 DEBUG repository: uso della cache per updates
2023-03-15T16:46:30+0100 DEBUG updates: usando metadati di mar 14 mar 2023, 01:48:26.
2023-03-15T16:46:30+0100 DEBUG repository: uso della cache per updates-modular
2023-03-15T16:46:30+0100 DEBUG updates-modular: usando metadati di mer 22 feb 2023, 12:28:37.
2023-03-15T16:46:30+0100 DEBUG repository: uso della cache per google-chrome
2023-03-15T16:46:30+0100 DEBUG google-chrome: usando metadati di gio 9 mar 2023, 20:19:55.
2023-03-15T16:46:30+0100 DEBUG repository: uso della cache per rpmfusion-free
2023-03-15T16:46:30+0100 DEBUG rpmfusion-free: usando metadati di ven 11 nov 2022, 17:54:42.
2023-03-15T16:46:30+0100 DEBUG repository: uso della cache per rpmfusion-free-updates
2023-03-15T16:46:30+0100 DEBUG rpmfusion-free-updates: usando metadati di lun 13 mar 2023, 12:48:40.
2023-03-15T16:46:30+0100 DEBUG repository: uso della cache per rpmfusion-nonfree
2023-03-15T16:46:30+0100 DEBUG rpmfusion-nonfree: usando metadati di ven 11 nov 2022, 18:25:12.
2023-03-15T16:46:30+0100 DEBUG repository: uso della cache per rpmfusion-nonfree-updates
2023-03-15T16:46:30+0100 DEBUG rpmfusion-nonfree-updates: usando metadati di lun 13 mar 2023, 13:49:01.
2023-03-15T16:46:30+0100 INFO Ultima verifica della scadenza dei metadati: 19:43:39 fa il mar 14 mar 2023, 21:02:51.
2023-03-15T16:46:31+0100 DDEBUG timer: sack setup: 39090 ms
2023-03-15T16:46:32+0100 DEBUG --> Inizio risoluzione dipendenze
2023-03-15T16:46:32+0100 DEBUG --> Finding unneeded leftover dependencies
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto NetworkManager-initscripts-ifcfg-rh.x86_64 1:1.40.10-1.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto NetworkManager-initscripts-updown.noarch 1:1.40.10-1.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto f35-backgrounds-base.noarch 35.0.1-4.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto f35-backgrounds-kde.noarch 35.0.1-4.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto f36-backgrounds-base.noarch 36.1.1-2.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto f36-backgrounds-kde.noarch 36.1.1-2.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto gcr.x86_64 3.92.0-1.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto geocode-glib.x86_64 3.26.4-1.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto iproute-tc.x86_64 5.18.0-2.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto java-11-openjdk-headless.x86_64 1:11.0.18.0.10-1.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto javascriptcoregtk4.0.x86_64 2.38.5-1.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto kf5-kalarmcal.x86_64 21.12.3-1.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto kf5-libksane.x86_64 22.12.3-1.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto libdmx.x86_64 1.1.4-13.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto libgdata.x86_64 0.18.1-6.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto libgweather.x86_64 40.0-4.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto libubsan.x86_64 12.2.1-4.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto lilv.x86_64 0.24.14-3.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto mozjs78.x86_64 78.15.0-7.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto mozjs91.x86_64 91.13.0-1.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto openldap-compat.x86_64 2.6.4-1.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto pcre-cpp.x86_64 8.45-1.fc37.2 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto pcre-devel.x86_64 8.45-1.fc37.2 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto pcre-utf16.x86_64 8.45-1.fc37.2 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto pcre-utf32.x86_64 8.45-1.fc37.2 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto podman-plugins.x86_64 5:4.4.2-2.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto python3-libxml2.x86_64 2.10.3-2.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG —> Il pacchetto webkit2gtk4.0.x86_64 2.38.5-1.fc37 sarà rimosso
2023-03-15T16:46:33+0100 DEBUG --> Risoluzione delle dipendenze completata
2023-03-15T16:46:33+0100 DDEBUG timer: depsolve: 360 ms
2023-03-15T16:46:33+0100 INFO Dipendenze risolte.

#8

Ovviamente i primi 2 li ho già reinstallati…