O gerenciador de rede descarta a conexão com fio

0

Estou executando o Ubuntu 16.04 no Lenovo E530. Meu gerenciador de rede desconecta a conexão com fio após alguns segundos. Wifi funciona bem. Como isso pode ser corrigido?

Minhas placas de rede:

03:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
0c:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

Atualização # 1

Depois de configurar o endereço IP estático, conecte o cabo e execute o comando

sudo ethtool enp12s0

O resultado é:

Settings for enp12s0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full 
                        100baseT/Half 100baseT/Full 
                        1000baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
                        100baseT/Half 100baseT/Full 
                        1000baseT/Full 
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Speed: 10Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
               drv probe ifdown ifup
Link detected: no

Depois de desconectar:

Settings for enp12s0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full 
                        100baseT/Half 100baseT/Full 
                        1000baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
                        100baseT/Half 100baseT/Full 
                        1000baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Half
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
               drv probe ifdown ifup
Link detected: no
    
por gedO 20.09.2016 / 20:20

1 resposta

0

Instale outro driver pelo fornecedor. Executar

sudo apt install r8168-dkms

e reinicie.

    
por Pilot6 20.09.2016 / 20:32