Estoy corriendo
uname -r
4.10.6-1-ARCH
en mi dell XPS 13 Developer Edition (2014). Actualmente tengo problemas extraños con mi wifi (uso Networkamanger con nm-appletKDE):
1) en el nivel más superficial, observé que a veces funciona perfectamente: cuando inicio mi PC, ya se ha conectado al wifi, y a veces no se conecta de ninguna manera (el wifi es siempre el mismo);
2) Intento reiniciar NM: y el problema persiste. 3) A veces, si reinicio mi computadora portátil, funciona de nuevo, a veces no.
4) Traté de usar nmcli
nmcli connection up My-WiFi
entonces observo
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
siempre hay el mismo error. No sé cómo arreglarlo. Observe lo siguiente:
1) Mi PC es Linux Friedly (se vendió con Ubuntu), en particular
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) Todos los servicios necesarios están activos
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 uso un escudo etéreo con cable usb, puedo conectarme a NM sin problema;
4) Intenté también conectarme directamente wpa_supplicant, pero fue imposible debido a errores de autenticación, sin embargo , recalco que mi ID de usuario y mi contraseña son correctos, ya que a veces puedo conectarme sin ningún problema.
¿Qué tengo que hacer?
/lib/firmwareluego vuelva a cargar eliwlwifiRespuestas:
Veo que tienes NetworkManager y wpa_supplicant ejecutándose. Mi laptop (Inspiron 7590) con tarjeta wifi Intel 9560-ac tenía un problema similar. Después de reemplazar wpa_supplicant con NetworkManager, se resolvieron las cosas. Antes de eso, probé todas las sugerencias en Internet sin ningún éxito.
EDITAR: El problema era múltiples clientes dhcpcd. El sistema ahora también es estable con wpa_supplicant.
fuente