netdev - Re: Linksys Gigabit USB2.0 adapter (asix) regression

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 22 Jun 2007 10:37:00 -0400
From:	David Hollis <dhollis@...ehollis.com>
To:	Erik Slagter <erik@...gter.name>
Cc:	netdev@...r.kernel.org
Subject: Re: Linksys Gigabit USB2.0 adapter (asix) regression

On Wed, 2007-06-20 at 13:56 +0200, Erik Slagter wrote:

> To rule out the possibility of the nic being defective, I connected the
> USB nic to a windows computer. There it works, although the ethernet
> connection is a bit flaky (just like it seems...).
> 
> Then I did a diff on the respective kernel sources of 2.6.20.3 and
> 2.6.22-rc2 (asix.c and usbnet.c), I found a few changes, but they do not
> seem to be related to my problem.
> 
> I am the and of my repertoire here, can anyone please do some
> suggestions for further testing or even better, fix it ;-)

You wouldn't happen to know what PHY that device is using?  The AX88178
(Gigabit USB Ethernet) support in the driver currently only supports the
Marvell PHY, which is the only one I've actually encountered to-date.
If you can rebuild the driver from your kernel sources but with DEBUG
enabled (uncomment it at the top of asix.c)

You can build the driver out-of-tree by creating a Makefile with these
contents:

obj-m   += asix.o

EXTRA_CFLAGS += -DDEBUG

all:
        make -C /lib/modules/`uname -r`/build SUBDIRS=`pwd`

clean:
        make -C /lib/modules/`uname -r`/build SUBDIRS=`pwd` clean

(You'll also need to copy usbnet.h into that directory)

After you build the module, load it with insmod ./asix.ko, plug in your
device and send me the dmesg output.  I'm particularly interested in the
PHYID=0x12345678 line.  That will tell me what PHY chip is being used in
that device and if I need to add support for it.

-- 
David Hollis <dhollis@...ehollis.com>

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html