web-dev-qa-db-fra.com

WIFI laisse tomber les problèmes dans la légion de Lenovo Y520

J'ai des problèmes avec LENOVO legion/Ideapad Y520 ...

Je viens d'acheter l'ordinateur portable et d'installer la dernière version 17 d'Ubuntu 64 bits.

J'ai activé le wifi en retirant le bloc dur, mais même après cela, mon wifi se connecte et fonctionne pendant un moment, puis il tombe, se déconnecte. Les journaux montrent quelques problèmes avec le paquet wpa_supplicant, mais je n’ai pas pu le résoudre.

J'ai essayé de réinstaller Ubuntu ainsi que Kali Linux v2 (2017). Il y avait le même problème.

Je n'ai aucune idée de ce qui se passe, j'ai essayé de réinstaller les pilotes, mais sans succès.

Voici ma partie du fichier journal de /var/log/syslog:

Sep 20 17:59:32 pentesting NetworkManager[579]: <info> [1505923172.3868] device (wlan0): state change: ip-check -> secondaries (reason 'none', internal state 'managed')
Sep 20 17:59:32 pentesting NetworkManager[579]: <info> [1505923172.3890] device (wlan0): state change: secondaries -> activated (reason 'none', internal state 'managed')
Sep 20 17:59:32 pentesting NetworkManager[579]: <info> [1505923172.3895] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 20 17:59:32 pentesting dhclient[6534]: bound to 192.168.100.133 -- renewal in 271856 seconds.
Sep 20 17:59:32 pentesting NetworkManager[579]: <info> [1505923172.3970] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 20 17:59:32 pentesting NetworkManager[579]: <info> [1505923172.3972] policy: set 'everwifi' (wlan0) as default for IPv4 routing and DNS
Sep 20 17:59:32 pentesting NetworkManager[579]: <info> [1505923172.3979] device (wlan0): Activation: successful, device activated.
Sep 20 17:59:32 pentesting nm-dispatcher: req:3 'up' [wlan0]: new request (2 scripts)
Sep 20 17:59:32 pentesting nm-dispatcher: req:3 'up' [wlan0]: start running ordered scripts...
Sep 20 17:59:32 pentesting nm-dispatcher: req:4 'connectivity-change': new request (2 scripts)
Sep 20 17:59:32 pentesting nm-dispatcher: req:4 'connectivity-change': start running ordered scripts...
Sep 20 18:00:48 pentesting gnome-terminal-[1612]: Allocating size to GtkScrollbar 0x561ab6b5c730 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Sep 20 18:00:48 pentesting gnome-terminal-[1612]: Allocating size to GtkScrollbar 0x561ab6b5c730 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Sep 20 18:00:48 pentesting gnome-terminal-[1612]: Allocating size to GtkScrollbar 0x561ab6b5c730 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Sep 20 18:00:48 pentesting gnome-terminal-[1612]: Allocating size to GtkScrollbar 0x561ab6b5c730 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Sep 20 18:00:48 pentesting gnome-terminal-[1612]: Allocating size to GtkScrollbar 0x561ab6b5c730 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Sep 20 18:00:48 pentesting gnome-terminal-[1612]: Allocating size to GtkScrollbar 0x561ab6b5c730 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Sep 20 18:00:48 pentesting gnome-terminal-[1612]: Allocating size to GtkScrollbar 0x561ab6b5c730 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Sep 20 18:00:48 pentesting gnome-terminal-[1612]: Allocating size to GtkScrollbar 0x561ab6b5c730 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Sep 20 18:01:36 pentesting systemd-timesyncd[503]: Synchronized to time server MailScanner warning: numerical links are often malicious: 193.238.191.249:123 (0.debian.pool.ntp.org).
Sep 20 18:01:40 pentesting dbus-daemon[994]: Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service'
Sep 20 18:01:40 pentesting systemd[982]: Starting Virtual filesystem metadata service...
Sep 20 18:01:40 pentesting dbus-daemon[994]: Successfully activated service 'org.gtk.vfs.Metadata'
Sep 20 18:01:40 pentesting systemd[982]: Started Virtual filesystem metadata service.
Sep 20 18:02:12 pentesting wpa_supplicant[638]: wlan0: SME: Trying to authenticate with f0:5c:19:19:de:81 (SSID='everwifi' freq=2462 MHz)
Sep 20 18:02:12 pentesting kernel: [ 694.527193] wlan0: disconnect from AP f0:5c:19:19:de:91 for new auth to f0:5c:19:19:de:81
Sep 20 18:02:12 pentesting kernel: [ 694.530958] wlan0: authenticate with f0:5c:19:19:de:81
Sep 20 18:02:12 pentesting kernel: [ 694.533869] wlan0: send auth to f0:5c:19:19:de:81 (try 1/3)
Sep 20 18:02:12 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Sep 20 18:02:12 pentesting NetworkManager[579]: <info> [1505923332.9412] device (wlan0): supplicant interface state: completed -> authenticating
Sep 20 18:02:12 pentesting wpa_supplicant[638]: wlan0: Trying to associate with f0:5c:19:19:de:81 (SSID='everwifi' freq=2462 MHz)
Sep 20 18:02:12 pentesting kernel: [ 694.537653] wlan0: authenticated
Sep 20 18:02:12 pentesting kernel: [ 694.539718] wlan0: associate with f0:5c:19:19:de:81 (try 1/3)
Sep 20 18:02:12 pentesting NetworkManager[579]: <info> [1505923332.9471] device (wlan0): supplicant interface state: authenticating -> associating
Sep 20 18:02:12 pentesting wpa_supplicant[638]: wlan0: Associated with f0:5c:19:19:de:81
Sep 20 18:02:12 pentesting kernel: [ 694.548816] wlan0: RX AssocResp from f0:5c:19:19:de:81 (capab=0x431 status=0 aid=2)
Sep 20 18:02:12 pentesting kernel: [ 694.549402] wlan0: associated
Sep 20 18:02:12 pentesting NetworkManager[579]: <info> [1505923332.9666] device (wlan0): supplicant interface state: associating -> 4-way handshake
Sep 20 18:02:12 pentesting wpa_supplicant[638]: wlan0: WPA: Key negotiation completed with f0:5c:19:19:de:81 [PTK=CCMP GTK=CCMP]
Sep 20 18:02:12 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-CONNECTED - Connection to f0:5c:19:19:de:81 completed [id=0 id_str=]
Sep 20 18:02:12 pentesting NetworkManager[579]: <info> [1505923332.9762] device (wlan0): supplicant interface state: 4-way handshake -> completed
Sep 20 18:05:01 pentesting CRON[6889]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Sep 20 18:05:07 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:08 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:09 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:10 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:11 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:12 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:13 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:14 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:15 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:16 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:17 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:18 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:19 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:20 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:21 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:22 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:23 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:24 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:25 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:26 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:27 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:28 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:29 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:30 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:31 pentesting systemd-timesyncd[503]: Timed out waiting for reply from MailScanner warning: numerical links are often malicious: 193.238.191.249:123 (0.debian.pool.ntp.org).
Sep 20 18:05:31 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:32 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:33 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:34 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:35 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:36 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:37 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:38 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:39 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:40 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:41 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:41 pentesting systemd-timesyncd[503]: Timed out waiting for reply from MailScanner warning: numerical links are often malicious: 46.175.224.7:123 (0.debian.pool.ntp.org).
Sep 20 18:05:41 pentesting systemd[1]: Starting Cleanup of Temporary Directories...
Sep 20 18:05:41 pentesting systemd[1]: Started Cleanup of Temporary Directories.
Sep 20 18:05:42 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:43 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:44 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:45 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:46 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:47 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:48 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:49 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:50 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:51 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:51 pentesting systemd-timesyncd[503]: Timed out waiting for reply from MailScanner warning: numerical links are often malicious: 91.212.242.21:123 (0.debian.pool.ntp.org).
Sep 20 18:05:52 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:53 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:54 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:55 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:56 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:57 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:58 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:05:59 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:06:00 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:06:01 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:06:01 pentesting systemd-timesyncd[503]: Timed out waiting for reply from MailScanner warning: numerical links are often malicious: 193.219.28.2:123 (0.debian.pool.ntp.org).
Sep 20 18:06:02 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:06:03 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:06:04 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:06:05 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:06:06 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:06:07 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:06:08 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:06:09 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Sep 20 18:06:10 pentesting wpa_supplicant[638]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1

-------- ÉDITÉ ------------

J'utilise actuellement Ubuntu 16.04.3 et le résultat de la commande demandée est:

user@home:~$ Sudo lspci -knn | grep Net -A3
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter [10ec:8821]
Subsystem: Lenovo RTL8821AE 802.11ac PCIe Wireless Network Adapter [17aa:a814]
Kernel driver in use: rtl8821ae
Kernel modules: rtl8821ae
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10)

Les erreurs que j'ai soumises ci-dessus sont les mêmes que sur Ubuntu, mais je vais aussi mettre syslog Ubuntu si nécessaire. (Il peut être lu ici depuis avant redémarrer network-manager et là après .)

wirelesslenovodisconnect
2
deepsec

On dirait qu'après 2 jours de combat, j'ai trouvé une solution.

Si quelqu'un a un problème similaire avec un ordinateur portable y520 Legion/Ideapad lenovo sous Ubuntu 16.04/17, essayez:

Tout d'abord, que devez-vous faire?

Découvrez exactement ce dont vous avez besoin:

deepsec@deepnetwork:/tools$ Sudo lspci -knn | grep Net -A3 
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. 
RTL8821AE 802.11ac PCIe Wireless Network Adapter [10ec:8821] 
Subsystem: Lenovo RTL8821AE 802.11ac PCIe Wireless Network Adapter 
[17aa:a814] Kernel driver in use: rtl8821ae Kernel modules: rtl8821ae 
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10)

Donc pour moi c'était

RTL8821AE

Ensuite, j'ai installé ce pilote à partir de github, en utilisant les commandes suivantes:

deepsec@deepnetwork:/tools$ cd /tmp
deepsec@deepnetwork:/tmp$ Sudo apt-get install build-essential linux-headers-generic git dkms
deepsec@deepnetwork:/tmp$ git clone http://github.com/lwfinger/rtlwifi_new.git
deepsec@deepnetwork:/tmp$ cd /tmp/rtlwifi_new
deepsec@deepnetwork:/tmp$ make
deepsec@deepnetwork:/tmp$ Sudo modprobe -rv rtl8821ae
deepsec@deepnetwork:/tmp$ Sudo make install
deepsec@deepnetwork:/tmp$ Sudo modprobe -v rtl8821ae

La solution ci-dessus m'a aidé à corriger une erreur, puis j'ai dû supprimer le gestionnaire de réseau et le gnome de pptp, et installer wicd (une alternative au gestionnaire de réseau) en utilisant les commandes suivantes:

Installation de wicd, alternative pour network-manager:

deepsec@deepnetwork:/tools$ Sudo apt-get install wicd 
deepsec@deepnetwork:/tools$ Sudo apt-get install wicd-gtk

Maintenant, nous devons ajouter le wicd à l’icône du haut comme network-manager (par défaut, cette option ne sera pas disponible)

Solution Ubuntu 16.04+ et supérieure:

deepsec@deepnetwork:/tools$ Sudo apt-get install python-appindicator

Toutes les versions ci-dessous 16.04 solution:

https://askubuntu.com/questions/69005/wicd-tray-icon-doesnt-show

Maintenant, faites un redémarrage et assurez-vous que vous avez l'icône de wicd en haut à droite corrnet, vérifiez si wicd fonctionne également et vous pouvez rechercher toutes les connexions wifi disponibles

Si tout va bien, supprimez Network-Manager:

deepsec@deepnetwork:/tools$ Sudo apt-get purge network-manager
deepsec@deepnetwork:/tools$ Sudo apt-get purge network-manager-pptp-gnome
deepsec@deepnetwork:/tools$ Sudo apt-get purge network-manager-pptp

J'ai remarqué que ma connexion didint a chuté pendant plus de 48 heures, donc je suppose que c'est bien, il n'y a plus d'erreur que j'ai postée ci-dessus.

1
deepsec