TP-Link - USB to Ethernet

[Martin Iturbide]

Hi

I just got my hands on a "TP-Link USB to Gigabit SuperSpeed UE300". HardwareID "2357:0601" Any idea on how I can find out if it will be compatible?

It is the first time I try an USB to Ethernet adapter  under ArcaOS (or OS/2). I guess I just need the USB drivers working and to put "USBMOS.OS2" on the "Adapter and Protocols".

Regards

[Martin Iturbide]

Hi

I just checked around for hardware id 2357:0601 and some databases says "UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153] ".

My chances do not look good.

Regards

[ivan]

Hi Martin,

It shouldn't matter what the network chip is since you are not connecting directly to that chip.  On the other hand it does matter what the USB chip is because that is what the USB network driver 'sees'.  Also, the unit you are talking about is a USB 3 unit and I don't know if the USB network stack has been updated to work with the XHCD driver.

[Martin Iturbide]

Hi Ivan

I'm tring this USB Ethernet adapter on a Thinkpad L420 without USB 3.0.  Since I have dual boot, I had run Windows 10 and it works there connected to USB 2.

I just tried in ArcaOS. lsusb see it:

[X:\]lsusb
Bus 001 Device 001: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 001 Device 002: ID 05c8:0317 Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 003: ID 147e:1002 Upek Biometric Touchchip/Touchstrip Fingerprint  Sensor
Bus 001 Device 004: ID 2357:0601 TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153]

I tried USBETHR.OS2 from ArcaOS (version 10.57) and Lar's (version 10.234) and both didn't work.

Regards

[Lars]

See this note from the USBETHR.OS2 usbether.txt:

USBETHR.OS2 driver is designed to work with any Kawasaki LSI KL5KUSB101
based USB Ethernet adapter, however specific vendor/device IDs must be
specified during installation.

and this:
2.1.6   Update vendor/device IDs card parameters dialog; use the following
          identification IDs:
+-----------------------------------------------------+---------+---------+
|                    Adapter                          |Vendor ID|Device ID|
+-----------------------------------------------------+---------+---------+
|3COM USB Network Interface (3C19250) *               |   0506  |  03E8   |
|D-Link Corp. USB Ethernet Adapter (DSB-650)          |   2001  |  4000   |
|ADS Technologies Inc. USB Ethernet Adapter (USB-10BT)|   06E1  |  0008   |
+-----------------------------------------------------+---------+---------+

I would think that this HW has long gone out of business.

[ivan]

Reading the Kawasaki LSI KL5KUSB101 data sheet it is only a USB 1 interface with a 16 Bit processor and a 10Mbit/sec ethernet interface - not very good by modern standards.

[Mathias]

2.1.6   Update vendor/device IDs card parameters dialog; use the following
          identification IDs:
+-----------------------------------------------------+---------+---------+
|                    Adapter                          |Vendor ID|Device ID|
+-----------------------------------------------------+---------+---------+
|3COM USB Network Interface (3C19250) *               |   0506  |  03E8   |
|D-Link Corp. USB Ethernet Adapter (DSB-650)          |   2001  |  4000   |
|ADS Technologies Inc. USB Ethernet Adapter (USB-10BT)|   06E1  |  0008   |
+-----------------------------------------------------+---------+---------+

I would think that this HW has long gone out of business.

Yes and misleading..
I've tried this driver with a current D-Link USB ethernet "card", which of course didn't work, EVEN THOUGH I've entered the correct hardware and vendor ID.
I thought when the driver is called "D-Link Corp. USB Ethernet Adapter", then it could work with mostly all of them, which wasn't the case. ; )

[Martin Iturbide]

Hi

I had tried these drivers without results:

- USBETHR.OS2 - (Lar's 10.234)
- USBMOS.OS2 - (AN 12.07)
- mcs7830.os2 - (1.14 - 15.02.2016)

I also included the hardwareID  (2357:0601) while using "USBETHR.OS2", like you told me, but it didn't work.

The USB ports are working, the USB driver are loaded (I have an USB Mouse attached.)
My test consist on adding the different driver on the "Adapter and Protocols", including the "TCPIP" protocol and rebooting. After that I try to ping anything on the network. Do you think I should do any other tests, maybe I'm doing something wrong, or just let this device to rest as unsupported?

Regards

[ivan]

Hi Martin,

It is not you with the problem, it is the old USB network drivers that do not recognise modern hardware.  They date from the turn of the century and the LSI chips are no longer being produced (you might find one in a old stock clearance sale).

What we need is a total revamping of the USB network drivers so they work with modern hardware.

[Alex Taylor]

The AN driver is current and should work well with supported chipsets (the Moschip controller).

Martin's problem is that the TP-Link uses a Realtek controller for which there is no OS/2 driver.

[ivan]

The LSI Moschip is an interesting device.  Not only is it a USB device but it includes a rudimentary ethernet section as well as being capable of driving a full ethernet chipset.  Its one failing is that, as it stands it is not gigabit network capable.