As atualizações do Ubuntu interrompem a conexão ethernet

0

Após realizar atualizações no meu recém-instalado Ubuntu 14.04 no Lenovo T440p, a conexão Ethernet pára de funcionar. Agora não tenho como conectá-lo à internet (o wi-fi nunca funcionou. Eu planejava lidar com isso em seguida). Como descubro o que está errado?

lspci

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM87 Express LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
02:00.0 VGA compatible controller: NVIDIA Corporation GK208M [GeForce GT 730M] (rev a1)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01)
04:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192EE PCIe Wireless Network Adapter

dmesg | grep -i eth

[    0.979465] e1000e 0000:00:19.0 eth0: registered PHC clock
[    0.979468] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 28:d2:44:bf:b3:3c
[    0.979469] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[    0.979498] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: 1000FF-0FF
[    1.451758] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    1.563023] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG_.VID_ handle
[    1.736366] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.484106] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    2.484325] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    4.203411] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[    4.203414] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[    4.203442] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

ifconfig

eth0      Link encap:Ethernet  HWaddr 28:d2:44:bf:b3:3c  
          inet6 addr: fe80::2ad2:44ff:febf:b33c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:13978 (13.9 KB)
          Interrupt:20 Memory:f1600000-f1620000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1184 (1.1 KB)  TX bytes:1184 (1.1 KB)
    
por dspyz 11.09.2014 / 23:48

1 resposta

1

Isso é um erro no driver e1000e, é discutido aqui: link

% bl0ck_qu0te%

Tenho certeza de que o uso do driver mais recente da Intel corrige seu problema .

    
por Jan 12.09.2014 / 09:06