[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
This assume you have open a terminal window in your TAB3 and Using Terminal executed a Ubuntu chrooted as explained in previous post or similar.

Please not that if you need you could be working just in a Linux PC Desktop to test your adapter.

So I am in fact in a linux desktop running Ubuntu. Because it easier to type in the keyboard. So for testing I have my TAB3 and desktop connected to my WIFI. I know about your problem. Use TAB3 terminal or just put all as far as you can for know if using WIFI.

In Dektop Open a Terminal [CTRL] [ALT]ENTER and type

user@user-PC:~$ [COLOR="Red"]ssh ubuntu@192.168.3.33[/COLOR]
ubuntu@192.168.3.33's password:
Welcome to Ubuntu 14.04 LTS (GNU/Linux 3.4.34-850131 i686)

* Documentation: https://help.ubuntu.com/
ubuntu@localhost:~$

Now lets test if lsusb is installed

ubuntu@localhost:~$ [COLOR="Red"]lsusb -V[/COLOR]
lsusb (usbutils) 007

Note: lsusb is part of UBUNTU. if for any reason does not show just do

$sudo apt-get install usbutils

Lets continue. lsusb show nothing if nothing is attached to tab3 usb port.

ubuntu@localhost:~$ lsusb
ubuntu@localhost:~$

Now is where the

[IMG="Samsung OTG"]http://thumbs4.ebaystatic.com/d/l225/m/m0ND9kIAnqj_mbykTCo8yvA.jpg[/IMG]

Micro USB Host Cable Male to USB Female OTG Adapter For Samsung LG HTC Nexus 7

comes handy.

Hook the OTG Adapter and try again.

ubuntu@localhost:~$ lsusb
[COLOR="Blue"]Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub[/COLOR]
ubuntu@localhost:~$

So as you see we know should have Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub.

Now lets do

ubuntu@localhost:~$ [COLOR="Red"]sudo dmesg | tail -20[/COLOR]
[ 962.156210] C0 [ kworker/u:1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 962.156228] C0 [ kworker/u:1] usb usb1: Product: EHCI Host Controller
[ 962.156243] C0 [ kworker/u:1] usb usb1: Manufacturer: Linux 3.4.34-850131 ehci_hcd
[ 962.156258] C0 [ kworker/u:1] usb usb1: SerialNumber: 0000:00:02.3
[ 962.157717] C0 [ kworker/u:1] hub 1-0:1.0: USB hub found
[ 962.157766] C0 [ kworker/u:1] hub 1-0:1.0: 1 port detected
[ 962.158471] C2 [irq/318-mxt1188] mxt1188s_ts 2-004a: Calibration is on going !!
[ 962.185034] C2 [irq/318-mxt1188] mxt1188s_ts 2-004a: Normal mode
[ 962.194799] C2 [irq/318-mxt1188] mxt1188s_ts 2-004a: T46 TA config write
[ 962.233016] C2 [irq/318-mxt1188] mxt1188s_ts 2-004a: Calibration is on going !!
[ 962.248608] C2 [irq/318-mxt1188] mxt1188s_ts 2-004a: Normal mode
[ 962.286071] C0 [ kworker/u:1] penwell_otg 0000:00:02.3: new state = a_wait_bcon
[ 964.886381] C3 [ sh] Cannot change disksize for initialized device
[ 964.966078] C3 [ kworker/3:0] usb_otg_suspend OTG HNP update suspend
[ 964.966141] C3 [ kworker/3:0] penwell_otg 0000:00:02.3: penwell_otg_runtime_idle --->
[ 964.966168] C3 [ kworker/3:0] penwell_otg 0000:00:02.3: penwell_otg_runtime_suspend --->
[ 964.995258] C3 [ kworker/3:0] penwell_otg 0000:00:02.3: penwell_otg_phy_low_power ---> on
[ 969.827071] C3 [ sh] Cannot change disksize for initialized device
[ 974.825937] C2 [ watchdog] !@Sync 32
[ 974.886446] C3 [ sh] Cannot change disksize for initialized device
ubuntu@localhost:~$

NOW IMPORTANT. I do not have your Ethernet Adapter. So I will going to do the steps with a USB_to_Serial Adapter instead so that you can see whats going on. Also in Android "dmesg" is tricky because to many post from sec-battery and sensors!! So to see the difference dmesg has to be perform quickly after reattachment of adapters.

Hook the Adapter and quickly inspect dmesg

ubuntu@localhost:~$ sudo dmesg | tail -20
[ 1115.614908] C0 [ UI] [psb:0x08:mdfld_adjust_display_fifo] gfx_hdmi_setting: MI_ARB = 0x0
[ 1115.621159] C1 [ kworker/1:2] [psb:0x08:psb_runtime_idle]
[ 1115.621180] C1 [ kworker/1:2] [psb:0x08:mid_hdmi_audio_suspend] mid_hdmi_audio_suspend: hdmi_state 0
[ 1115.621193] C1 [ kworker/1:2] [psb:0x08:ospm_suspend_display]
[ 1115.621211] C1 [ kworker/1:2] [psb:0x08:mdfld_save_display_registers]
[ 1115.621224] C1 [ kworker/1:2] [psb:0x08:mdfld_disable_crtc] pipe = 0
[ 1115.710947] C1 [ sh] Cannot change disksize for initialized device
[ 1118.292570] C2 [ khubd] usb 1-1: USB disconnect, device number 2
[ 1118.295133] C0 [ kworker/u:2] penwell_otg 0000:00:02.3: old state = a_host
[ 1118.295168] C0 [ kworker/u:2] penwell_otg 0000:00:02.3: new state = a_wait_bcon
[COLOR="Blue"][ 1120.509879] C0 [ khubd] usb 1-1: new full-speed USB device number 3 using penwell_otg
[ 1120.664870] C3 [ khubd] usb 1-1: New USB device found, idVendor=1a86, idProduct=7523
[ 1120.664895] C3 [ khubd] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 1120.664915] C3 [ khubd] usb 1-1: Product: USB2.0-Ser![/COLOR]
[ 1120.668854] C0 [ kworker/u:2] penwell_otg 0000:00:02.3: old state = a_wait_bcon
[ 1120.668889] C0 [ kworker/u:2] penwell_otg 0000:00:02.3: new state = a_host
[ 1120.821631] C1 [ sh] Cannot change disksize for initialized device
[ 1121.145528] C2 [ swapper/2] intel_scu_watchdog: intel_scu_watchdog: Expected SW WDT warning irq received
[ 1121.145567] C2 [ swapper/2] intel_scu_watchdog: intel_scu_watchdog: interrupt tasklet body start
[ 1121.145654] C3 [ ia_watchdog] intel_scu_watchdog: intel_scu_watchdog: watchdog_keepalive
ubuntu@localhost:~$

So as you can see dmesg show that a new devices is hook. This is Parcialy good. But it does not show that the devices was asigned a new Port like "/dev/ttyUSB0"?? This means my Ubuntu/Android have no driver for it. Now lets ee lsusb

ubuntu@localhost:~$ lsusb
[COLOR="Blue"]Bus 001 Device 002: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter[/COLOR]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ubuntu@localhost:~$

as you see now I can see my Bus 001 Device 002: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter.

Againg this is Parcialy good. It means it has been detected. But lets look deeper

ubuntu@localhost:~$[COLOR="Red"] lsusb -t[/COLOR]
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=penwell_otg/1p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class,[COLOR="Purple"] Driver=, 12M[/COLOR]
ubuntu@localhost:~$

As you see lsusb -t report that NO driver has been install . If Installed we should have seen a new line showing something. For example this is what I see when I hook the Serial adapter to my Ubuntu Desktop

ruser@user-PC:~/$[COLOR="Red"] lsusb -t[/COLOR]
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M
[COLOR="Blue"]/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
|__ Port 2: Dev 14, If 0, Class=Vendor Specific Class, Driver=ch341, 12M[/COLOR]
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 4, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 2: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 2: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
user@user--PC:~$ \

As you see my Desktop shows

/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M

|__ Port 2: Dev 14, If 0, Class=Vendor Specific Class, Driver=ch341, 12M

Driver=ch341 is the driver used in desktop.

Now that I know what is the driver I can do

user@user-PC:~/Desktop/galaxyliedetector $ [COLOR="Red"]modinfo ch341[/COLOR]
[COLOR="Purple"]filename: /lib/modules/3.16.0-23-generic/kernel/drivers/usb/serial/ch341.ko[/COLOR]
license: GPL
srcversion: 0040753E6672CB27E750458
alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in*
depends: usbserial
intree: Y
vermagic: 3.16.0-23-generic SMP mod_unload modversions 686
signer: Magrathea: Glacier signing key
sig_key: 61:C0:C7:65:8F:DB:5B:DE:6B:B6:E0:6E:F0:89:A8:B1:BF:B1:AE:32
sig_hashalgo: sha512
user@user-PC:~/Desktop/galaxyliedetector $

Now I see that the driver for my ch341 is inside my PC in

filename: /lib/modules/3.16.0-23-generic/kernel/drivers/usb/serial/ch341.ko

So it is now time to compile that ch341.ko for my Kernel. This is the asigmen you need to do. So go ahead and do your test as I did. And PLEASE Post your results as I did. Yes it took me about 3 hours to do this tutorial! It is time you do your share.

Now since I am in a 32bit Linux system I could try to test that ch341.ko in my Ubuntu! Just a test! Who knows if it works!.