NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Fwd: USB ethernet with axe not working

Whoops, forgot to send to list. :)

On 6 April 2010 17:08, <> wrote:

> Hi,
> according to the axe(4) manpage the D-Link DUB-E100 USB to ethernet
> adapter is supported. So i bought one.. But when i plug it in one of
> the USB ports i get an ugen device and nothing else:
> Apr  6 18:15:55 blackbox /netbsd: ugen0 at uhub1 port 6
> Apr  6 18:15:55 blackbox /netbsd: ugen0: vendor 0x2001 product 0x3c05,
> rev 2.00/0.01, addr 2
> According to config -x the axe driver is included in the GENERIC kernel:
> # config -x | grep axe
> axe*    at uhub? port ?         # ASIX AX88172 based adapters
> Tried with:
> NetBSD 5.0.2 (GENERIC) #0: Sat Feb  6 17:53:27 UTC 2010
> /home/builds/ab/netbsd-5-0-2-RELEASE/i386/201002061851Z-obj/home/builds/ab/netbsd-5-0-2-RELEASE/src/sys/arch/i386/compile/GENERIC
> i386
> So what's needed to get this thing working?
> It looks like there's 2 different versions of this device.  the axe driver
only seems to reference the older revision. I dunno if the hardware between
the two is similar enough for the new version to work, but you could try
changing the file '/usr/src/sys/dev/usb/if_axe.c', duplicate the line that

        { { USB_VENDOR_DLINK,           USB_PRODUCT_DLINK_DUBE100}, 0 },

and change it to USB_PRODUCT_DLINK_DUBE100B1, so you end up with:

        { { USB_VENDOR_DLINK,           USB_PRODUCT_DLINK_DUBE100}, 0 },
        { { USB_VENDOR_DLINK,           USB_PRODUCT_DLINK_DUBE100B1}, 0 },

then rebuild your kernel and see what happens. :) (I'm no expert but I've
had stuff like this help make things work before, if the hardware isn't that
different you should be okay.)

FWIW, I can't find USB_PRODUCT_DLINK_DUBE100B1 in any other driver, it's
only referenced in the header files, so I don't think it's a case of a
different driver.



Home | Main Index | Thread Index | Old Index