Replicant

Jorge,

I don't believe that this is currently working, but I would love to see support for this added.

It is likely that support for this will become much easier to add in the near future for the Note 2 and Galaxy S3 when they start running with the mainline linux kernel. I really have no idea how hard it would be to add this feature for the Galaxy Tab 2. I don't think that the Replicant devs have really looked into it yet.

I was also excited about this potential feature a number of months back when I saw the product that you linked to existed for the Note 2.

By the way, can you confirm that Replicant 6.0003 runs just fine on the Galaxy Tab 2 7.0 GT-P3113? Someone just asked about that exact model on the mailing list.

cordially,
kurtis

Jorge and Kurtis,

You both may have already noticed, but on this page, https://redmine.replicant.us/projects/replicant/wiki/ReplicantStatus#fn1 footnote-1 marks that SOME USB-WiFi-adapters, work with Replicant 6.0 (0003?), for all of the supported devices. (not sure about models x113. Like Kurtis referred to, I asked some thing about those models, on the mailing-list. Compatibility with Replicant 6.0 is still a question.)

https://redmine.replicant.us/projects/replicant/wiki/WifiAdapter has more details on using Replicant 6 with USB-WiFi, like (a) needing an OTG-cable, and (b) mentioning certain of the libre-friendly adapters from "ThinkPenguin" and "TechnoEthical".

If WiFi works that way on Replicant 6.0, then may-be wired (Ethernet) does too ??

Kurtis, does the Linux-kernel handle WiFi and Ethernet much differently?

Jorge, if you prefer wired, then https://www.thinkpenguin.com/gnu-linux/penguin-usb-20-hi-speed-10100-fast-ethernet-network-adapter MIGHT be more-likely to work than that adapter from Amazon, since "ThinkPenguin's" is said to be libre-compatible, and USB 2, and that company seems to strive to only sell devices with high-compatibility. You could ask "ThinkPenguin". If they have a Replicant-device available, they might gladly test for you (us) whether their USB-Ethernet-adapter works with Replicant. (Their adapter has 2 versions. Version 1 cost more and offered support for more systems. And Sales said that version 2 was good quality but that version 2 was even better quality.)

(If you are fine with wireless, then products from both "ThinkPenguin" and "TechnoEthical" are mentioned on that page regarding WiFi on Replicant.)

Yay for libre computing.
Sincerely, Chad.

Chad,

I'm almost positive that the x113 models work just fine with Replicant 6.0

WiFi with Replicant 6.0 works with RepWifi, but wired Ethernet does not. I've already tried. I don't know what is different about it in the code, I just know that it currently isn't supported.

https://tehnoetic.com/tehnoetic-wireless-adapter-gnu-linux-libre-tet-n150 is confirmed to work with RepWifi on Replicant 6.0

My hope is that the upcoming mainlining of the kernel for the S3 and Note 2 will make it fairly easy to add usb ethernet support in Replicant.

Cordially,
Kurtis

Hello Jorge,

We finally got a patch submitted to add support for usb ethernet on the Galaxy Tab 2 7.0! We have Roms available for testing as well. Any chance you still have that adapter? If so, can you test the Roms for us? Even if you don't, can you install our Roms and just verify that they boot? Further instructions are here: https://redmine.replicant.us/issues/1889#note-12

Cordially,
Kurtis

Hi Kurtis,

Unfortunately I have my Tab 2 7.0 back in the states in storage. I won't be able to get it until next year. If you still need help testing a new rom when I get back then I will be more than happy to.

If I am able to acquire it somehow before then I'll also let you know.

best regards,

Jorge

Hello Jorge,

Nice to chat with you again, by the way! Hope you're having a fun time on the other side of the pond. The need for testing of this Rom has fortunately already been done by two testers in the last day or two, so no worries there. If you are currently using a different Replicant device, we should have a new testing version available in a few days and an official 6.0 0004 release shortly after that.

In Solidarity,
Kurtis

Hi, today I upgraded Replicant(0004) on my S3. I am still unable to use USB Ethernet adapter. I've tried to restart device with plugged adapter at boot and without with no success.
Any idea?
I found this picture:
Could you please implement that in Replicant?
Best regards!

Hello trumpEt,

A user with a Note II device had what I think is a similar problem. They were able to resolve it by entered four lines into the terminal via a root shell by way of adb. https://redmine.replicant.us/boards/21/topics/15583?r=15590#message-15590

Our directions for getting a root shell via adb are here: https://redmine.replicant.us/projects/replicant/wiki/ADB#Accessing-root-shell

After you set that up, you would then type these four commands into the terminal:

ifconfig eth0 192.168.XXX.XXX netmask 255.255.XXX.XXX
busybox route add default gw 192.168.XXX.XXX dev eth0
ndc resolver setnetdns eth0 "" X.X.X.X X.X.X.X
ip rule add from all lookup main pref 99

Please let me know if you have any questions about this and whether or not this fixing your issue.

Cordially,
Kurtis

Hello Kurtis,
Thanks for the info.
Unfortunately it doesn't work.

root@i9300:/ # ifconfig eth0 X.X.X.X netmask 255.255.255.0
ifconfig: ioctl 8916: No such device

root@i9300:/ # ifconfig                                                        
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0 
          inet6 addr: ::1/128 Scope: Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:472 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:472 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:0 
          RX bytes:96641 TX bytes:96641 

p2p0      Link encap:Ethernet  HWaddr X:X:X:X:X:X
          inet6 addr: X::X:X:X:X/64 Scope: Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:0 TX bytes:0 

wlan0     Link encap:Ethernet  HWaddr X:X:X:X:X:X
          inet addr:X.X.X.X  Bcast:X.X.X.X  Mask:255.255.255.0 
          inet6 addr: X::X:X:X:X/64 Scope: Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:418 errors:0 dropped:9 overruns:0 frame:0 
          TX packets:399 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:140544 TX bytes:94246

Sorry to hear that!

A few questions... Which release candidate of Replicant 6.0 0004 are you running? Is it rc3?

What USB Ethernet Adapter are you using?

Also, is the picture you provided above a screenshot or picture of what you see on your screen? It wasn't clear to me if it was or not.

I would test this myself but I had lent my usb ethernet adapter to a friend. I'll ask them if I can get it back soon.

Hi,

All I did was add the drivers for several USB Ethernet adapters.

I tested (on the Galaxy Nexus if I recall well) with one working with the asix driver. It's a driver for a chip found in many USB 2.0 USB Ethernet adapters.

For some devices it didn't work out of the box (rebooting with the Ethernet plugged didn't give me an IP address).

However with the right adapter it's still supposed to show up in ifconfig.

Here some commands that could help:

ls -la /sys/class/net/

Here's an example of output on a laptop with an asix compatible USB Ethernet adapter:

total 0
drwxr-xr-x  2 root root 0 15 janv. 22:18 .
drwxr-xr-x 62 root root 0 15 janv. 22:18 ..
[...]
lrwxrwxrwx  1 root root 0 15 janv. 22:18 pe0 -> ../../devices/pci0000:00/0000:00:19.0/net/pe0
lrwxrwxrwx  1 root root 0 15 janv. 22:27 pw0 -> ../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/pw0
lrwxrwxrwx  1 root root 0 15 janv. 22:33 ue0 -> ../../devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5.1/1-5.1:1.0/net/ue0
lrwxrwxrwx  1 root root 0 15 janv. 22:27 virbr0 -> ../../devices/virtual/net/virbr0
[...]

So here the interface corresponding to the USB ethernet adapter is ue0.

lsusb

So here's the output of lsusb on my Galaxy SIII (GT-I9300):

Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 002: ID 1519:0020

In contrast here what I have on my laptop:

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 012: ID 0b95:772b ASIX Electronics Corp. AX88772B
Bus 001 Device 010: ID 17ef:1005 Lenovo ThinkPad X200 Ultrabase (42X4963 )
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[...]

So here we see that there are some Linux Foundation 2.0 root hub. I'm unsure what it corresponds to exactly, maybe it's an USB port, maybe a hub, but we can ignore it as it's not an USB peripheral.

Somehow 1d6b:0001 seems to correspond to USB1, 1d6b:0002 to USB2, 1d6b:0003 to USB3.

These appears on my smartphone too:

Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
[...]

So if we ignore these remains this one:

Bus 001 Device 002: ID 1519:0020

And it doesn't show more as I didn't have anything USB peripheral connected to it.

So an USB adapter compatible with the Asix driver might look a bit like that on your device:

 
Bus 001 Device 002: ID 0b95:772b

Instead of that on your laptop:

Bus 001 Device 012: ID 0b95:772b ASIX Electronics Corp. AX88772B

For instance you can identify it by connecting the adapter to your laptop, and writing down the IDs (here 0b95:772b) and looking at it on the smartphone too.

Back on my laptop I can also identify the driver of the ue0 network interface with this command:

ls -la /sys/class/net/ue0/device/driver

Which gives me that:

lrwxrwxrwx 1 root root 0 15 janv. 22:46 /sys/class/net/ue0/device/driver -> ../../../../../../../bus/usb/drivers/asix

It should also give something similar on your smartphone.

I hope that the above can help you debug the issue.

Hi!
@Kurtis
I've just upgraded to rc4.
My USB ethernet adapter: UCN3126-1
The picture I uploaded is the one I found in the internet. It would be great if Replicant had this kind of feature in gui.

@Denis
I can't connect my adapter to my computer - lack of USB-C or microUSB.

This is my S3 current output with connected adapter or without.

lsusb

Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 002: ID 1519:0020

Connection doesn't work.

When the system is ready the message appears:

Unfortunately, the process android.process.acore has stopped.

Regards