Hoi!
I am trying to get an TP-Link UE300 USB3.0 to GigaBit ethernet adpater running as a full 3.0 device on an ubuntu 16.04 server.
In principle it works, but for some reason it is claimed by the cdc_driver and used as an USB 2.0 device. That results in a very limited bandwidth and the cdc_driver really doesn't know how to handle the device:
root@ff-payload:~# lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 2357:0601
Bus 001 Device 003: ID 2357:0601
Bus 001 Device 002: ID 2357:0601
Bus 001 Device 005: ID 0b05:1825 ASUSTek Computer, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 1 devices 2 to 3 are three of these adaptors. The TP-Link homepage claims that the UE300 uses a realtek RTL8153 chipset but for some reason none of 16.04 kernels realtek drivers feel responsible for the usb device.
Has anybody got a UE300 running as GB ethernet on 16.04 server?
blue skies Jan Albiez
P.S.: This is the output of a journalctl | grep eth:
Sep 14 13:43:45 ff-payload kernel: cdc_ether 1-6:2.0 eth0: register 'cdc_ether' at usb-0000:00:14.0-6, CDC Ethernet Device, f4:f2:6d:18:1f:82
Sep 14 13:43:45 ff-payload kernel: cdc_ether 1-7:2.0 eth1: register 'cdc_ether' at usb-0000:00:14.0-7, CDC Ethernet Device, f4:f2:6d:18:1e:6d
Sep 14 13:43:45 ff-payload kernel: cdc_ether 1-8:2.0 eth2: register 'cdc_ether' at usb-0000:00:14.0-8, CDC Ethernet Device, f4:f2:6d:14:06:13
Sep 14 13:43:45 ff-payload kernel: usbcore: registered new interface driver cdc_ether
Sep 14 13:43:45 ff-payload kernel: cdc_ether 1-6:2.0 enxf4f26d181f82: renamed from eth0
Sep 14 13:43:45 ff-payload kernel: cdc_ether 1-7:2.0 enxf4f26d181e6d: renamed from eth1
Sep 14 13:43:45 ff-payload kernel: cdc_ether 1-8:2.0 enxf4f26d140613: renamed from eth2
and: lsmod | grep r8:
r8152 49152 0
mii 16384 2 r8152,usbnet