webentwicklung-frage-antwort-db.com.de

WIfi fallen Probleme in Lenovo Y520 Legion

Ich habe Probleme mit LENOVO Legion/Ideapad Y520 ...

Ich habe gerade den Laptop gekauft und die 64-Bit-Ubuntu-Version 17 installiert.

Ich habe WLAN aktiviert, indem ich den harten Block entfernt habe, aber selbst danach stellt mein WLAN eine Verbindung her und funktioniert für eine Weile. Dann wird die Verbindung unterbrochen und getrennt. Die Protokolle zeigen einige Probleme mit dem Paket wpa_supplicant, aber ich konnte es nicht beheben.

Ich habe versucht, Ubuntu und auch Kali Linux v2 (2017) neu zu installieren. Es gab das gleiche Problem.

Ich habe keine Ahnung, was los ist, ich habe versucht, die Treiber neu zu installieren, aber keinen Erfolg.

Hier ist mein Teil der Protokolldatei von /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

-------- EDITED ------------

Ich verwende gerade Ubuntu 16.04.3 und die Ausgabe des angeforderten Befehls ist:

[email protected]:~$ 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)

Die Fehler, die ich oben gemeldet habe, sind die gleichen wie bei Ubuntu, aber ich werde auch Ubuntu Syslog setzen, wenn es benötigt wird. (Es kann gelesen werden hier von vorher Neustart von network-manager und dort von später .)

2
deepsec

Sieht aus wie nach 2 Tagen des Kampfes fand ich einen Fix ..

Wenn jemand ein ähnliches Problem mit y520 Legion/Ideapad lenovo Laptop unter Ubuntu 16.04/17 haben wird, sollte er versuchen:

Zuerst musst du tun

Finden Sie heraus, welches Laufwerk Sie benötigen:

[email protected]:/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)

So war es für mich

RTL8821AE

Dann habe ich diesen Treiber von Github mit folgenden Befehlen installiert:

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

Die obige Lösung half mir bei einer Fehlerbehebung. Dann musste ich den Netzwerkmanager und pptp gnome entfernen und wicd (Alternative zum Netzwerkmanager) mit den folgenden Befehlen installieren:

Wicd installieren, Alternative für Netzwerkmanager:

[email protected]:/tools$ Sudo apt-get install wicd 
[email protected]:/tools$ Sudo apt-get install wicd-gtk 

Jetzt müssen wir die wicd zum obersten Icon hinzufügen, wie der Netzwerk-Manager (standardmäßig wird diese Option nicht angeboten).

Ubuntu 16.04+ und höher Lösung:

[email protected]:/tools$ Sudo apt-get install python-appindicator

Alle Versionen unter 16.04 Lösung:

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

Führen Sie nun einen Neustart durch und vergewissern Sie sich, dass oben rechts das WICD-Symbol angezeigt wird. Überprüfen Sie, ob WICD auch funktioniert und ob alle verfügbaren WIFI-Verbindungen gefunden werden können

Wenn alles in Ordnung ist, entfernen Sie den Netzwerkmanager:

[email protected]:/tools$ Sudo apt-get purge network-manager
[email protected]:/tools$ Sudo apt-get purge network-manager-pptp-gnome
[email protected]:/tools$ Sudo apt-get purge network-manager-pptp

Ich habe festgestellt, dass meine Verbindung nicht mehr als 48 Stunden unterbrochen wurde. Ich denke, es ist in Ordnung. Es gibt keine Fehler mehr, die ich oben gepostet habe.

1
deepsec