16.04 Problemas Wifi / ethernet depois de atualizar a partir de 14.04

Question

16.04 Problemas Wifi / ethernet depois de atualizar a partir de 14.04

#1 resposta do chili555 (1 votos)
#2 resposta do Elder Geek (1 votos)
#3 resposta do Jeremy31 (1 votos)

4

Depois de atualizar o Ubuntu de 14.04 para 16.04, estou tendo alguns problemas com minha conexão wifi.

Verifique isso, a partir de uma conexão com fio (preste atenção no atraso da resposta).

leo@nelson:~$ ping facebook.com
PING facebook.com (66.220.158.68) 56(84) bytes of data.
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=1 ttl=75 time=154 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=2 ttl=75 time=155 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=3 ttl=75 time=155 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=4 ttl=75 time=154 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=5 ttl=75 time=155 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=6 ttl=75 time=155 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=7 ttl=75 time=155 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=8 ttl=75 time=156 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=9 ttl=75 time=156 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=10 ttl=75 time=162 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=11 ttl=75 time=154 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=12 ttl=75 time=154 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=13 ttl=75 time=155 ms
^C
--- facebook.com ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12001ms
rtt min/avg/max/mdev = 154.211/155.791/162.531/2.067 ms

Mas quando mudo para WiFi:

leo@nelson:~$ ping facebook.com
PING facebook.com (66.220.158.68) 56(84) bytes of data.
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=1 ttl=79 time=323 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=2 ttl=79 time=361 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=3 ttl=79 time=1008 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=4 ttl=79 time=652 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=5 ttl=79 time=999 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=6 ttl=79 time=1010 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=7 ttl=79 time=1003 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=8 ttl=79 time=1008 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=9 ttl=79 time=420 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=10 ttl=79 time=266 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=11 ttl=79 time=168 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=12 ttl=79 time=1009 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=13 ttl=79 time=1005 ms
64 bytes from edge-star-mini-shv-07-frc3.facebook.com (66.220.158.68): icmp_seq=14 ttl=79 time=471 ms
^C
--- facebook.com ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 13028ms
rtt min/avg/max/mdev = 168.777/693.596/1010.408/329.180 ms, pipe 2

Eu tenho dois provedores de internet diferentes com dois roteadores diferentes no mesmo lugar. Acontece o mesmo nas duas conexões. Eu também tentei com outro computador com o Ubuntu 12.04 e funciona como um encanto.

Estou com este problema desde que instalei o 16.04

Informação adicional: Eu tenho usado uma conexão com fio para funcionar porque é inutilizável por wifi ... MAS de vez em quando (a cada ~ 20-30 minutos) a conexão com fio é desconectada (acontece com os dois roteadores de diferentes ISPs eu tenho).

Informações do cartão sem fio Mi:

leo@nelson:~$ sudo lshw -class network
sudo: imposible resolver el anfitrión nelson
[sudo] password for leo: 
  *-network               
       descripción: Ethernet interface
       producto: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       fabricante: Realtek Semiconductor Co., Ltd.
       id físico: 0
       información del bus: pci@0000:01:00.0
       nombre lógico: eth0
       versión: 06
       serie: 4c:72:b9:58:9c:95
       tamaño: 100Mbit/s
       capacidad: 1Gbit/s
       anchura: 64 bits
       reloj: 33MHz
       capacidades: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuración: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168e-3_0.0.4 03/27/12 ip=192.168.0.18 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
       recursos: irq:28 ioport:e000(size=256) memoria:d0004000-d0004fff memoria:d0000000-d0003fff
  *-network
       descripción: Interfaz inalámbrica
       producto: RT5390 Wireless 802.11n 1T/1R PCIe
       fabricante: Ralink corp.
       id físico: 0
       información del bus: pci@0000:02:00.0
       nombre lógico: wlan0
       versión: 00
       serie: 20:10:7a:8e:3d:66
       anchura: 32 bits
       reloj: 33MHz
       capacidades: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuración: broadcast=yes driver=rt2800pci driverversion=4.4.0-34-generic firmware=0.34 ip=192.168.1.157 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn
       recursos: irq:17 memoria:fea00000-fea0ffff

Como @ chili555 perguntou, aqui está a saída "dmesg | grep rt2"

leo@nelson:~$ dmesg | grep rt2
[   14.104800] rt2800pci 0000:02:00.0: enabling device (0000 -> 0002)
[   14.105008] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5390, rev 0502 detected
[   14.109544] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5390 detected
[   78.812904] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
[   79.015681] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.34
[  105.903521] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  106.351522] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  106.799553] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  107.247543] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  107.759574] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  108.211584] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  108.727599] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  109.555615] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  148.965666] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  149.413726] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  149.925810] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  150.777953] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  367.323945] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  368.171986] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  368.944044] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  369.448049] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  469.630931] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  470.478973] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  470.931053] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  471.387076] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  471.843081] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  472.291140] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  472.739165] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  473.191144] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  473.691199] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[  474.191255] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 1191.044092] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 1191.816158] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 1192.316182] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 4549.926258] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 5030.979039] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 5031.427145] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 5031.883092] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 5032.655142] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 7430.737637] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 7431.185659] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 7432.033748] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 7432.497744] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 7432.997769] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 7433.497799] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[10551.963800] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush

Adicionado o iwconfig solicitado por Jeremy31

nelson@nelson:~$ iwconfig
lo        no wireless extensions.

eno1      no wireless extensions.

enp0s19f2u5  no wireless extensions.

wlp2s0    IEEE 802.11bgn  ESSID:"Liit"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: 54:BE:F7:61:84:25   
          Bit Rate=11 Mb/s   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=43/70  Signal level=-67 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1637  Invalid misc:528   Missed beacon:0

wireless 16.04 lts

por Nelson Galdeman Graziano 23.08.2016 / 19:44

3 respostas

Tags wireless 16.04 lts

Como mostro uma janela de progresso? Captura 22: python-pillow e python-pil apt-get conflict

score 1 · Answer 1

Sugiro que você tente um parâmetro de driver. Do terminal:

sudo -i
echo "options rt2800pci nohwcrypt=Y"  >  /etc/modprobe.d/rt2800pci.conf
exit.

Reinicie. Alguma melhoria? Verifique o log de mensagens:

dmesg | grep rt2

Os erros, avisos, etc., como os que você postou acima, são melhores, iguais ou piores?

Se você deseja tentar compilar backports , sugiro:

cd ~/Downloads/backports-4.2.2-1

Ou onde quer que tenha baixado o pacote, se não for Downloads.

make defconfig-wifi
make
sudo make install

O comando 'make' leva muito tempo nesta instância. Por favor, seja paciente. Reinicie. Alguma melhoria? Verifique o log de mensagens:

dmesg | grep rt2

score 1 · Answer 2

Você pode ter que colocar o driver r8169 na lista negra e tentar instalar o driver r8168 r8168-dkms do repositório universe. Detalhes do pacote

Se isso não resolver seus problemas de conexão com fio, tente substituir o cabo de patch, pois ele pode ter um curto intermitente.

No que diz respeito à conexão sem fio, você deve tentar 2011_1007_RT5390_RT5392_Linux_STA_V2.5.0.3_DPO atualizado para funcionar com o kernel Linux 3.8 e posterior. As instruções de instalação estão na mesma página. Eu vou replicá-los aqui se você vir valor nisso.

Editar: Conforme relatado por @Nelson Galdeman Graziano, parece que uma atualização recente resolveu esse problema. Então, a primeira coisa a tentar é sudo apt update seguido por sudo apt upgrade

Fonte:

link

score 1 · Answer 3

O gerenciamento de energia está ativado no cartão sem fio. Para desativar na inicialização

sudo -H gedit /lib/systemd/system/wifi-power-management-off.service

Digite o seguinte

[Unit]
Description=Disable power management for wlan0
Requires=sys-subsystem-net-devices-wlan0.device
After=network.target

[Service]
Type=oneshot
ExecStartPre= /bin/sleep 25
ExecStart=/sbin/iwconfig wlan0 power off

[Install]
WantedBy=multi-user.target

Salve o arquivo, saia do gedit e depois

systemctl enable wifi-power-management-off.service

Isso pode solicitar sua senha duas vezes, Reiniciar

Se você tiver problemas depois de suspender / dormir, também precisará

sudo -H gedit /etc/systemd/system/root-resume.service

Entrar

[Unit]
Description=Turn off wlan power management
After=suspend.target

[Service]
Type=simple
ExecStartPre= /bin/sleep 25
ExecStart= /sbin/iwconfig wlan0 power off

[Install]
WantedBy=suspend.target

E ative com

sudo systemctl enable root-resume

A origem da correção de suspensão / suspensão é link