Boa tarde a todos.
Ontem (11 de outubro) à meia-noite, meu laptop perdeu a conexão com a internet via cabo Ethernet. Ainda consigo me conectar via wifi.
Eu tenho um segundo laptop, com inicialização dupla com o Xubuntu 19.04 e o Windows 10. Este segundo laptop ainda pode se conectar à Ethernet no Windows 10 e no Xubuntu 19.04, portanto, não é um problema de modem/roteador.
Consegui restaurar a Ethernet excluindo as configurações do auto eth0 e reconfigurando, mas agora isso também parou de funcionar (e não consigo restaurar o auto eth0!).
Alguém pode me ajudar a solucionar esse problema, por favor?
@heynnema: as informações que você solicitou.
dkms status
digimend, 8, 5.0.0-29-generic, x86_64: installed
digimend, 8, 5.0.0-31-generic, x86_64: installed
sudo lshw -C network
[sudo] password for bac:
*-network
description: Ethernet interface
product: RTL810xE PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:07:00.0
logical name: enp7s0
version: 07
serial: b0:5a:da:c9:aa:2a
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical
configuration: broadcast=yes driver=r8169 latency=0 multicast=yes
resources: irq:18 ioport:4000(size=256) memory:b4000000-b4000fff memory:b4800000-b4803fff
*-network
description: Wireless interface
product: Wireless 3165
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0d:00.0
logical name: wlp13s0
version: 81
serial: 94:65:9c:b9:9a:ba
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-31-generic firmware=29.1044073957.0 ip=192.168.1.114 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:44 memory:b2000000-b2001fff
cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
cat /etc/netplan/*.yaml
cat: '/etc/netplan/*.yaml': No such file or directory
@heynnema: A segunda execução na rede sudo lshw -C:
*-network
description: Ethernet interface
product: RTL810xE PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:07:00.0
logical name: enp7s0
version: 07
serial: b0:5a:da:c9:aa:2a
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical
configuration: broadcast=yes driver=r8169 latency=0 multicast=yes
resources: irq:18 ioport:4000(size=256) memory:b4000000-b4000fff memory:b4800000-b4803fff
*-network
description: Wireless interface
product: Wireless 3165
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0d:00.0
logical name: wlp13s0
version: 81
serial: 94:65:9c:b9:9a:ba
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-31-generic firmware=29.1044073957.0 latency=0 link=no multicast=yes wireless=IEEE 802.11
resources: irq:44 memory:b2000000-b2001fff
@heynnema: Terceira vez mais charme!
sudo lshw -C network
*-network
description: Ethernet interface
product: RTL810xE PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:07:00.0
logical name: enp7s0
version: 07
serial: b0:5a:da:c9:aa:2a
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical
configuration: broadcast=yes driver=r8169 latency=0 multicast=yes
resources: irq:18 ioport:4000(size=256) memory:b4000000-b4000fff memory:b4800000-b4803fff
*-network
description: Wireless interface
product: Wireless 3165
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0d:00.0
logical name: wlp13s0
version: 81
serial: 94:65:9c:b9:9a:ba
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-31-generic firmware=29.1044073957.0 latency=0 link=no multicast=yes wireless=IEEE 802.11
resources: irq:43 memory:b2000000-b2001fff
Mas ainda não há auto eth0. Como posso saber se tenho um cabo cat5 ou cat6?
@heynnema: Esperamos que este seja o último:
sudo lshw -C network
*-network
description: Ethernet interface
product: RTL810xE PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:07:00.0
logical name: enp7s0
version: 07
serial: b0:5a:da:c9:aa:2a
size: 100Mbit/s
capacity: 100Mbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8106e-1_0.0.1 06/29/12 ip=192.168.1.195 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
resources: irq:18 ioport:4000(size=256) memory:b4000000-b4000fff memory:b4800000-b4803fff
*-network DISABLED
description: Wireless interface
product: Wireless 3165
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0d:00.0
logical name: wlp13s0
version: 81
serial: 94:65:9c:b9:9a:ba
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-31-generic firmware=29.1044073957.0 latency=0 link=no multicast=yes wireless=IEEE 802.11
resources: irq:43 memory:b2000000-b2001fff
Responder1
Dos comentários...
Após uma longa solução de problemas usando o sudo lshw -C networkcomando, parecia que nenhum cabo estava conectado ao computador ou o cabo estava com defeito (o usuário não estava usando um cabo cat 5e ou cat 6) ou o switch/hub/roteador/modem não estava conectado .
Foi determinado que o computador realmente viu um dispositivo Ethernet enp7s0, não um dispositivo eth0. Ao criar um novo script de conexão GUI do NetworkManager usando enp7s0 e testar com os kernels -29, -30 e -31, tudo parece funcionar novamente. Os scripts de conexão antigos que usavam eth0 foram excluídos.
Se falhar novamente, você precisará inicializar um Ubuntu Live DVD/USB e testar novamente a interface de rede Ethernet.