WIfi soltando problemas na legião do Lenovo Y520

2

Eu tenho problemas com LENOVO legion / Ideapad Y520 ...

Acabei de comprar o laptop e instalei a última versão do Ubuntu de 64 bits.

Eu habilitei wifi removendo o bloco de disco rígido, mas mesmo depois disso, meu wifi conecta e funciona por um tempo, depois cai, desconecta. Os logs mostram alguns problemas com wpa_supplicant package, mas não consegui corrigi-lo.

Eu tentei reinstalar o Ubuntu e também o Kali Linux v2 (2017). Houve o mesmo problema.

Eu não tenho ideia do que está acontecendo, tentei reinstalar os drivers, mas não tive sucesso.

Aqui está minha parte do arquivo de log 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

-------- EDITADO ------------

Estou usando o Ubuntu 16.04.3 agora e a saída do comando solicitado é:

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)

Os erros que eu enviei acima são os mesmos que no Ubuntu, mas vou colocar também o syslog do Ubuntu se for necessário. (Pode ser lido aqui de antes reiniciando network-manager e lá de depois .)

    
por deepsec 20.09.2017 / 18:31

1 resposta

1

Parece que depois de 2 dias de luta encontrei uma correção ...

Se alguém tiver um problema semelhante com o laptop y520 Legion / Ideapad lenovo sob o Ubuntu 16.04 / 17, tente:

Primeiro, o que você precisa fazer é

Descubra exatamente o que você precisa de unidade:

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)

Então, para mim, foi

RTL8821AE

Então eu instalei este driver do github, usando os seguintes comandos:

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

A solução acima me ajudou em uma correção de erro, então eu tive que remover o network-manager e o pptp gnome, e instalar o wicd (alternativa ao network-manager) usando os seguintes comandos:

Instalando o wicd, alternativa para o gerenciador de rede:

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

Agora temos que adicionar o wicd ao ícone do topo, como o network-manager (por padrão, você não terá essa opção)

Ubuntu 16.04+ e solução acima:

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

Toda a versão abaixo da solução 16.04:

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

Agora faça uma reinicialização e tenha certeza de que você tem o ícone wicd no corrnet superior direito, verifique se o wicd também está funcionando e vc pode verificar todas as conexões wifi disponíveis

Se tudo estiver bem, remova o gerenciador de rede:

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

Eu notei que minha conexão não caiu por mais de 48 horas, então acho que está tudo bem, não há mais erros que eu postei acima.

    
por deepsec 20.09.2017 / 23:33