Olinuxino Maxi and USB to Ethernet AX88772B adapter.

[Rubid]

Hi,
can anyone who has the Olinuxino Maxi board and USB to ethernet AX88772B adapter (https://www.olimex.com/Products/USB-Modules/USB-ETHERNET-AX88772B/) check if the adapter works as expected?

Can somebody post the output of ifconfig command? Do both ethernet connections work with sufficient speed when connected at the same time?

I've tested the adapter with Olinuxino Micro and it works, but I wanted to know if LAN9512 and AX88772B are working when connected together.

Regards,
Maciej

[lambda]

Sorry I can't test this. Perhaps it is easier if you just post the ifconfig output you get if you think something is wrong with that ...

I do expect that your scenario *should* work, but of course both devices will share one bus, so you might get some speed drop.

[Rubid]

Hi lambda,
I don't have Olinuxino Maxi, thats why I'm asking if anyone who has the Maxi board can do this for me. I'm not saying that it won't work, just wondering if it will, and if yes what will be network connection like (stable, unstable, fast, slow, etc.).

Regards.

[mbergmann]

Hi Maciej,

I have both, the Maxi board and an AX88772B adapter, but I do not have a recent Linux image for the Maxi board with drivers and configuration for both adapters, because I use my own board which is slightly different (RAM, UART), so my images don't work on Olimex boards out of the box.

If you give me a download link to a proper configured OLinuxIno-Maxi Linux image I'll give it a try.

Regards

Mike

[Rubid]

Mike,
can you use the official Olimex linux image with 2.6.35 kernel?
https://docs.google.com/open?id=0B-bAEPML8fwlYUUxaUtsNkZrRk0

Maciej

[mbergmann]

I already tried with the 2.6.35-8-ARCH+, lsusb is listing the ASIX adapter but ifconfig is not showing the corresponding eth.

I assume there is no asix driver available or the asix driver is not loaded properly. I'm not using the adapter sold by Olimex, but my one is based on AX88772, too.

I tried with the imx233_debian_3_11 image, too. With this image both adapters are listed on startup:

Code Select Expand


[    3.340000] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-ci_hdrc.0-1.1, smsc95xx USB 2.0 Ethernet, 82:4a:7b:f1:98:ff
...
[    3.970000] asix 1-1.2:1.0 eth1: register 'asix' at usb-ci_hdrc.0-1.2, ASIX AX88772 USB 2.0 Ethernet, b8:8d:12:54:a7:93


but ifconfig only shows the smsc95xx one, what seems to be a configuration issue.

So, if you can provide me either a configured image, or the configuration files for the debian-3.11 image (/etc/network/interfaces,  /etc/udev/rules.d/70-persistent-net.rules, anything else?) I'll give it another try.

Regards

Mike

[MBR]

The ifconfig shows only the devices in the "up" state. Try looking into /proc/net/dev by someting like

Code Select Expand

cat /proc/net/dev
Probably the new device is not configured yet in the /etc/network/interfaces, so is not brought up automatically. Also look at the already mentioned /etc/udev/rules.d/70-persistent-net.rules, you may need to edit it.

[lambda]

ifconfig -a
should show all devices, whether up or not.

HTH,
Harald

[mbergmann]

Thanks Harald
Thanks MBR

the adapter was listed in /proc/net/dev as eth2. I brought it up and now it is listed within ifconfig:

Code Select Expand


eth0      Link encap:Ethernet  HWaddr c6:c9:82:6b:75:db
          inet addr:192.168.1.36  Bcast:255.255.255.255  Mask:255.255.255.0
          inet6 addr: fe80::c4c9:82ff:fe6b:75db/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1560 errors:0 dropped:0 overruns:0 frame:0
          TX packets:241 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:106384 (103.8 KiB)  TX bytes:24164 (23.5 KiB)

eth2      Link encap:Ethernet  HWaddr b8:8d:12:54:a7:93
          inet addr:192.168.0.100  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::ba8d:12ff:fe54:a793/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:67 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:7038 (6.8 KiB)  TX bytes:8492 (8.2 KiB)


Transfer is working on both adapters (tested with ssh from each network):

Code Select Expand


root@arm:~# cat /proc/net/dev
Inter-|   Receive                                                |  Transmit
face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
  eth2:    7038      67    0    0    0     0          0         0     8492       0    0    0    0     0       0          0
  eth0:  106384    1560    0    0    0     0          0         0    24164     241    0    0    0     0       0          0


I'll do some speed test the next time I have some spare minutes.

Question:

Any idea why the ASIX adapter is registered as eth1 on startup but later listed as eth2 in /proc/net/dev?

Code Select Expand


asix 1-1.2:1.0 eth1: register 'asix' at usb-ci_hdrc.0-1.2, ASIX AX88772 USB 2.0 Ethernet, b8:8d:12:54:a7:93


Regards

Mike

[MBR]

The udev can rename network devices by the file /etc/udev/rules.d/70-persistent-net.rules to make they names consistent on the system (so the name is not dependent on plug-in order), but sometimes a device is not recognised properly and regarded as a new one. Most of the time, all that you need is to remove duplicate records from the /etc/udev/rules.d/70-persistent-net.rules.