Never mind, I plugged the adapter into a windows machine once more
(another one) and now it acts exactly like it's plugged into my linux
laptop, so I guess it's actually broken. I will send it back for repair.
Thanks for your effort and I apologise for being a pain ;-)
-
To unsubscribe from this
On Mon, 2007-08-20 at 18:23 +0200, Erik Slagter wrote:
/*
if ((eeprom 8) != 1) {
asix_write_gpio(dev, 0x003c, 30);
asix_write_gpio(dev, 0x001c, 300);
asix_write_gpio(dev, 0x003c, 30);
} else {
*/
David Hollis wrote:
It's a bit of a longshot, but I notice that EEPROM index 0x17 returns
0x580 for you, 0x180 for my devices. Based on that, my devices go
through the gpio phymode == 1 path GPIO init sequence, and yours goes
through the other path ( if ((eeprom 8) != 1) { ). Comment out
David Hollis wrote:
They are either garbled are they are not passed on the wire. The
transmitted packets are shown by tshark, but a tshark run on the other
end of the line does not show them.
Platform is indeed x86, to be precise: fedora 7, kernel 2.6.22-rc6, cpu
pentium M, dell laptop
David Hollis wrote:
On Mon, 2007-06-25 at 19:05 +0200, Erik Slagter wrote:
drivers/net/usb/asix.c: PHYID=0x01410cc2
Ok, it is using a Marvell PHY so that part should be fine. You
mentioned that it looks like the packets are being transmitted, but are
garbled in some way. The device does
On Mon, 2007-07-30 at 11:27 +0200, Erik Slagter wrote:
They are either garbled are they are not passed on the wire. The
transmitted packets are shown by tshark, but a tshark run on the other
end of the line does not show them.
Platform is indeed x86, to be precise: fedora 7, kernel
On Mon, 2007-06-25 at 19:05 +0200, Erik Slagter wrote:
drivers/net/usb/asix.c: PHYID=0x01410cc2
Ok, it is using a Marvell PHY so that part should be fine. You
mentioned that it looks like the packets are being transmitted, but are
garbled in some way. The device does prepend a 'header' to
David Hollis wrote:
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.
I'll quote a few of strings that are spewed that I assume
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
David Hollis 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
Hi,
I have kind of a difficult problem with my USB network adapter. It used
to work using kernel 2.6.20.3, more or less, I needed to insert and
remove the network cable from the device frequently to get it working,
but then, at least, it worked.
Now, using 2.6.22-rc2 it's not working anymore, at
11 matches
Mail list logo
