elmar gerdes wrote:
> On Wed, 14 Jun 2006, Rui Santos wrote:
>
>   
>> Hi,
>>     
>
> Hi Rui,
>
>   
>>    D-Link DUB-E100 USB2.0 to Ethernet adapter has been working for a
>> long time ( H/W Ver up to A2 ). It contained a ASIX AX88172 chip and,
>> had a VendorID and ProductID of 0x2001 and 0x1a00, respectively.
>>
>>    Now, D-Link has a new ( I have one ), DUB-E100 H/W Ver: B1, that
>> uses a ASIX AX88772, and has a VendorID and ProductID of 0x07d1 and
>> 0x3c05, respectively. This new USB2.0 to ethernet adapter no longer
>> works with the usbnet/asix driver. I Tried to force that ProdID/VendorID
>> into the ax88772_info driver_info struct on drivers/usb/net/asix.c, and
>> it didn't work. It recognizes it as a network card, it appears on
>> ifconfig but, it just doesn't work. If i run ethtool eth0 I only get the
>> following output:
>> Settings for eth0:
>>   Current message level: 0x00000007 (7)
>>   Link detected: yes
>>
>>    Am I missing something? Is there anyone that is able to make ( or
>> help me ) a patch for it? The only thing I can do, is just compile and
>> test it...
>>
>> All my tests were done with a 2.6.16.20 Kernel.
>>
>> Thanks you.
>>
>> -- 
>> Rui Santos
>> http://www.ruisantos.com/
>>
>>     
>
> my DUB-E100 is H/W version A4, it definitely contains an AX88172 chip.
> Are you really sure your adaptor contains an ASIX AX88772 chip?  I'm sure
>   
You're right, I did opened the devices case and, the chip actually says
ASIX AX88772.
> you opened the box to find out.  Looks like people at GrupoPIE feel
> comfortable with open boxes around :-)
>   
Well, I did break a few clamps :-[
> Maybe you're experiencing that rubbish I had to go through with WLAN
> cards some time ago: looking for cards that are supported by Linux,
> buying one, finding out that it's a newer revision with a completely
> different chip on it that did not yet have a stable native Linux driver;
> buying another one, and the same thing happened again.
>
> The manufacturers didn't even bother giving the whole thing a new name
> when it needs a completely different driver.  Example: Netgear WG 311:
> Rev.A with Atheros chip, Rev.B with TI chip.
>
> Now here you are with something called H/W versions A2 (or A4), and B1.
>   
Totally agree with you. To make this worst, according to our suppliers
in Portugal, D-Link DUB-E100 H/W Ver: Ax are no longer sold, and have
been replaced for the Ver: Bx. This means that a driver/patch/quirk is
urgently needed for these devices to work from now on.
> I hope that I'm wrong and that someone can help you.
>   
Someone is already helping me on this. Thank you David Hollis.
> elmar
>   
Rui
>
>
> _______________________________________________
> linux-usb-devel@lists.sourceforge.net
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
>
>
>   


-- 
Rui Santos
http://www.ruisantos.com/




_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to