je suis entrain de courir
uname -r
4.10.6-1-ARCH
sur mon dell XPS 13 developer edition (2014). J'ai actuellement des problèmes étranges avec mon wifi (j'utilise Networkamanger avec nm-appletpour KDE):
1) au niveau le plus superficiel, j'ai observé que parfois cela fonctionne parfaitement: lorsque je démarre mon PC, il est déjà connecté au wifi, et parfois il ne se connecte en aucune manière (le wifi est toujours le même);
2) J'essaie de redémarrer NM: et le problème persiste. 3) Parfois, si je redémarre mon ordinateur portable, cela fonctionne à nouveau, parfois non.
4) J'ai essayé d'utiliser nmcli
nmcli connection up My-WiFi
alors j'observe
dmesg
[ 250.165837] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[ 250.255882] wlp2s0: Limiting TX power to 14 dBm as advertised by 00:3a:9a:32:62:d3
[ 272.004204] wlp2s0: deauthenticating from 00:3a:9a:32:62:d3 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 275.432861] wlp2s0: authenticate with 00:3a:9a:32:62:d3
[ 275.435513] wlp2s0: send auth to 00:3a:9a:32:62:d3 (try 1/3)
[ 275.440164] wlp2s0: 00:3a:9a:32:62:d3 unexpected authentication state: alg 0 (expected 0) transact 256 (expected 2)
[ 275.538092] wlp2s0: send auth to 00:3a:9a:32:62:d3 (try 2/3)
[ 275.540879] wlp2s0: authenticated
[ 275.544662] wlp2s0: associate with 00:3a:9a:32:62:d3 (try 1/3)
[ 275.546811] wlp2s0: RX AssocResp from 00:3a:9a:32:62:d3 (capab=0x431 status=0 aid=4)
[ 275.548267] wlp2s0: associated
[ 275.653364] wlp2s0: Limiting TX power to 14 dBm as advertised by 00:3a:9a:32:62:d3
[ 297.004547] wlp2s0: deauthenticating from 00:3a:9a:32:62:d3 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 300.433810] wlp2s0: authenticate with 00:3a:9a:32:62:d3
[ 300.437019] wlp2s0: send auth to 00:3a:9a:32:62:d3 (try 1/3)
[ 300.438771] wlp2s0: authenticated
[ 300.441086] wlp2s0: associate with 00:3a:9a:32:62:d3 (try 1/3)
[ 300.443198] wlp2s0: RX AssocResp from 00:3a:9a:32:62:d3 (capab=0x431 status=0 aid=4)
[ 300.444175] wlp2s0: associated
[ 300.530232] wlp2s0: Limiting TX power to 14 dBm as advertised by 00:3a:9a:32:62:d3
[ 322.003946] wlp2s0: deauthenticating from 00:3a:9a:32:62:d3 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 325.430498] wlp2s0: authenticate with 00:3a:9a:32:62:d3
[ 325.433405] wlp2s0: send auth to 00:3a:9a:32:62:d3 (try 1/3)
[ 325.435168] wlp2s0: authenticated
[ 325.437533] wlp2s0: associate with 00:3a:9a:32:62:d3 (try 1/3)
[ 325.439710] wlp2s0: RX AssocResp from 00:3a:9a:32:62:d3 (capab=0x431 status=0 aid=4)
[ 325.440978] wlp2s0: associated
[ 325.618536] wlp2s0: Limiting TX power to 14 dBm as advertised by 00:3a:9a:32:62:d3
[ 347.007641] wlp2s0: deauthenticating from 00:3a:9a:32:62:d3 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 347.023798] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 347.025937] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 692.002060] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
il y a toujours la même erreur. Je ne sais pas comment réparer. Remarquez ce qui suit:
1) Mon pc est linux friably (a été vendu avec ubuntu), en particulier
lspci -k
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
2) Tous les services nécessaires sont actifs
systemctl --type=service
UNIT LOAD ACTIVE SUB DESCRIPTION
dbus.service loaded active running D-Bus System Message Bus
gssproxy.service loaded active running GSSAPI Proxy Daemon
kmod-static-nodes.service loaded active exited Create list of required static device nodes fo
lm_sensors.service loaded active exited Initialize hardware monitoring sensors
NetworkManager.service loaded active running Network Manager
ntpd.service loaded active running Network Time Service
polkit.service loaded active running Authorization Manager
rtkit-daemon.service loaded active running RealtimeKit Scheduling Policy Service
sddm.service loaded active running Simple Desktop Display Manager
systemd-backlight@backlight:intel_backlight.service loaded active exited Load/Save Screen Backlight Brightness of backl
systemd-backlight@leds:dell::kbd_backlight.service loaded active exited Load/Save Screen Backlight Brightness of leds:
systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
systemd-user-sessions.service loaded active exited Permit User Sessions
udisks2.service loaded active running Disk Manager
upower.service loaded active running Daemon for power management
[email protected] loaded active running User Manager for UID 1000
wpa_supplicant.service loaded active running WPA supplicant
3) Si j'utilise un blindage eth filaire USB, je peux me connecter avec NM sans problème;
4) J'ai également essayé de me connecter directement wpa_supplicant, mais cela a été impossible, en raison d'erreurs d'authentification, mais je souligne que mon ID utilisateur et pwd sont corrects car parfois je peux me connecter sans problème
Que devrais-je faire?
/lib/firmwarepuis rechargez leiwlwifiRéponses:
Je vois que vous avez à la fois NetworkManager et wpa_supplicant en cours d'exécution. Mon ordinateur portable (Inspiron 7590) avec carte wifi Intel 9560-ac a eu un problème similaire. Après avoir remplacé wpa_supplicant par NetworkManager, les choses ont été résolues. Avant cela, j'ai essayé toutes les suggestions sur Internet sans succès.
EDIT: Le problème était plusieurs clients dhcpcd. Le système est désormais également stable avec wpa_supplicant.
la source