This is a weird issue that I've had for years, except now I kind of need to be able to leave my LAN wire plugged in.
I have a Toshiba Satellite P755. I have a dual boot with Windows. This issue doesn't happen with Windows.
When I turn it on, if the cable is plugged in, the ethernet port won't even be recognized by Ubuntu. I've tried plugging the cable in and out, and nothing changes. If I unplug the wire, turn the computer off completely, and then boot up, the ethernet port will be there, and I can get a wired connection by just plugging it back.
I can plug it in without issues after the Mate logo goes away during bootup. At that point, it shows what looks like a console screen with a few short messages, saying that it's already loaded drivers and it's executing something like "script/init-premount". However, I can't leave it plugged in during shutdown.
This is the normal output of sudo lshw -C network:
Code:
*-network
description: Ethernet interface
product: RTL810xE PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:01:00.0
logical name: enp1s0
version: 05
serial: b8:70:f4:69:5b:4c
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=rtl_nic/rtl8105e-1.fw ip=192.168.0.54 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
resources: irq:16 ioport:e000(size=256) memory:f0004000-f0004fff memory:f0000000-f0003fff
*-network
description: Wireless interface
product: Centrino Wireless-N 1000 [Condor Peak]
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlp2s0
version: 00
serial: 74:e5:0b:06:f2:62
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-65-generic firmware=39.31.5.1 build 35138 ip=192.168.0.53 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:40 memory:f7e00000-f7e01fff
When it's failing, the output is the same for the Wireless interface, but the Ethernet block doesn't show up.
This looks to me like a driver issue, but I'm not sure. The Additional Drivers application doesn't show any new drivers, and "Install Firmware Package" didn't help either. Has anyone encountered this before? Is there a solution?
I'm hoping it can be solved with something like changing how or when the drivers are loaded, or adding a couple of lines to a script that runs during bootup. Any ideas to what that script is at the beginning?
Bookmarks