Using A-Link NA1GU, which uses ASIX 88772 chip, does not work with mainline kernel's asix driver. The driver detects the network interface correctly. However, when attempting to use the device, it does not send data frames at all. TX counters do increase, and tcpdump shows packets being sent - but they do not appear on the wire in reality. This applies to any and all packets - arps, DHCP requests, ICMP's, whatever. Receiving data works ok. This issue appeared at three separate computers, one of them an Alix router (Geode board) running Debian with kernel 2.6.26, one desktop computer (Ubuntu with kernel 2.6.28), and one laptop running Gentoo Linux and kernel 2.6.35. The driver code from the vendor, located at http://www.asix.com.tw/FrootAttach/driver/AX88772B_772A_760_772_178_LINUX2.6.32_Driver_v3.2.0_Source.tar.bz2 works ok and compiles against kernel sources 2.6.26 and 2.6.28 (Debian and Ubuntu variants). However, it does not compile against kernel 2.6.35 (tarball's readme says that tested until 2.6.32). Any chances of integrating the functional differences to the main tree?
Still not fixed in 2.6.36.
Looks like new version from vendor now compiles even with 2.6.36, so it's fixed from my point of view..
I can confirm the behaviour where the device won't actually send anything. This happens with two different machines, one running 2.6.34 or 2.6.36.2 and the other running 2.6.33.5. I was able to fix this on the other machine, running kernel 2.6.33.5, by using the vendor asix driver version 3.5.0. On the other machine this didn't help with either of the kernels. The device didn't work. The A-Link NA1GU has the ASIX AX88178 chipset.
This is still present in 2.6.37. Luckily the vendor's version still works.
http://asix.com.tw/FrootAttach/driver/AX88772B_772A_760_772_178_LINUX2.6.35_Driver_v3.5.0_Source.tar.bz2 Link to the working vendor-supplied driver.
I have like problem with D-Link Corp. DUB-E100 Fast Ethernet [asix]. The problem present on 2.6.38 and 2.6.39 kernel versions!
Closing as obsolete, please re-open if still present in modern kernels
*** This bug has been marked as a duplicate of bug 29082 ***