On Tue, 2010-06-29 at 07:35 +0200, ing. Barry B.F. de Graaff (debian) wrote: [...] > On Sun, Jun 27, 2010 at 7:40 PM, Ben Hutchings <ben@decadent.org.uk> wrote: > > OK, and for comparison, can you repeat that while using the original > > driver? (Temporarily remove the driver you got from the manufacturer.) [...] > [ 428.084108] eth2: register 'asix' at usb-0000:00:1d.7-7, ASIX AX88178 USB 2.0 Ethernet, 00:0e:c6:88:09:28 > [ 428.084137] usbcore: registered new interface driver asix > [ 493.600293] b44: eth0: powering down PHY > [ 493.704834] eth2: link down > [ 493.707183] ADDRCONF(NETDEV_UP): eth2: link is not ready > [ 503.123908] ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready > [ 503.126016] eth2: link up, 1000Mbps, full-duplex, lpa 0xCDE1 > [ 513.272023] eth2: no IPv6 routers present > [ 560.087747] eth2: link up, 1000Mbps, full-duplex, lpa 0xCDE1 > [ 563.511322] ADDRCONF(NETDEV_UP): eth0: link is not ready > [ 570.622539] b44: eth0: powering down PHY > [ 570.704834] eth2: link up, 1000Mbps, full-duplex, lpa 0xCDE1 > [ 581.576024] eth2: no IPv6 routers present So, it reported link up... [...] > *** Device statistics: > Inter-| Receive | Transmit > face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed > lo: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > eth1: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > eth0: 502382 809 0 0 0 0 0 64 128514 786 0 0 0 0 0 0 > eth2: 736 16 0 0 0 0 0 0 9860 43 0 0 0 0 0 0 [...] and apparently it was able to send and receive packets without errors. So what is your basis for saying it can't transfer data? How are you testing it? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part