Network adapter issues in Ubuntu 17.04

Operating Systems & Open Source Linux
1

Hello there!

So I was finally able to get my hands on a 1700 and an X370 Taichi and decided to finally make the jump to Linux. It's all well so far and I absolutely love it - except that for some reason, I'm having issues with my Ethernet. WiFi works just fine and is quite speedy too, but the wired connection is way slower than it should be. After doing some digging, I found some commands to check the 'status' of the LAN-Adapter with ethtools eth0 and this is what I get as a result:
Settings for eth0:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available

Using ifconfig outputs this:

enp11s0: flags=4099 mtu 1500
** ether 70:85:c2:40:cc:61 txqueuelen 1000 (Ethernet)**
** RX packets 0 bytes 0 (0.0 B)**
** RX errors 0 dropped 0 overruns 0 frame 0**
** TX packets 0 bytes 0 (0.0 B)**
** TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0**
** device memory 0xfd200000-fd21ffff **

lo: flags=73 mtu 65536
** inet 127.0.0.1 netmask 255.0.0.0**
** inet6 ::1 prefixlen 128 scopeid 0x10**
** loop txqueuelen 1000 (Local Loopback)**
** RX packets 68 bytes 5070 (5.0 KB)**
** RX errors 0 dropped 0 overruns 0 frame 0**
** TX packets 68 bytes 5070 (5.0 KB)**
** TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0**

wlp9s0: flags=4163 mtu 1500
** inet 192.168.2.119 netmask 255.255.255.0 broadcast 192.168.2.255**
** inet6 2003:d4:3e7:b443:248c:7ffa:8997:4bb7 prefixlen 64 scopeid 0x0**
** inet6 2003:d4:3e7:b443:e868:ebe8:f9ef:39e2 prefixlen 64 scopeid 0x0**
** inet6 fe80::fd24:9b44:7151:6141 prefixlen 64 scopeid 0x20**
** ether 10:f0:05:c6:69:66 txqueuelen 1000 (Ethernet)**
** RX packets 65571 bytes 69420550 (69.4 MB)**
** RX errors 0 dropped 0 overruns 0 frame 0**
** TX packets 23779 bytes 3677692 (3.6 MB)**
** TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0**

To be honest, I have no clue what any of these things mean, which is why I'm turning to you guys here for help.
I could just use WiFi sure, but it buggs me that the wired connection isn't working for me, especially because nobody else seems to have this problem with this board.

I hope somebody here can help me!

Thanks a lot in advance!

PS: I'll be at work for the next couple of hours so I won't be able to provide any more terminal 'results' or screenshots, only respond.

EDIT: It seems to be working now. It literally took 10 minutes for the LAN to connect though, so I still think that there's something wrong somehow. Mind you, this is also still the first time that it connected through wired at all.

2

It isn't usual for the wire connection to take from anywhere between 10 min to 20 min to resolve its self. I would keep an eye on it, if it starts acting slow or stops working update this post.

3

Well your ENP is your ethernet and you WLP is supposed to be your wireless.

4

No such device

17.04 Ubuntu uses the new naming scheme for network devices. In the past you used eth0, eth1, wifi2, wifi,4, etc, you get the idea. Back then the names where assigned the in the order the devices showed up. This can mean that you configured your firewall for eth0, but somehow devices initialised in another order and now everything for eth0 is really used as eth1.

The new naming scheme defines names by connection type and slot number etc. Read this nice explanation at askubuntu

1 Like
5

Okay, it's working now. I reset the BIOS, flashed the latest version, reset it again (for good measure) and wiped my Ubuntu drive, reinstalling it from a freshly set up USB drive. I have no clue which one of the steps actually fixed it but for now I'm just glad it's working again. Thank's to everyone who responded, I seriously appreciate it!