Date: Sun, 17 Dec 2006 16:24:21 -0500 From: "Dan Frohlich" <dan.frohlich@gmail.com> To: freebsd-usb@freebsd.org Subject: making the linksys 200m work... Message-ID: <a8a1e6750612171324n1094aca1o6528f38bf0059ada@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Here is what I did to try to get the linksys 200m running:
in if_axe.c:
/* product LINKSYS2 USB200M 0x2226 USB 2.0 10/100 ethernet */
product LINKSYS4 USB200M 0x0018 USB 2.0 10/100 ethernet rev 2.00
/0.01
in usbdevs:
/* { USB_VENDOR_LINKSYS2, USB_PRODUCT_LINKSYS2_USB200M },*/
{ USB_VENDOR_LINKSYS4, USB_PRODUCT_LINKSYS4_USB200M },
When I plug in my linksys usb dongle I see this at the console:
axe0: vendor 0x13b1 product 0x0018, rev 2.00/0.01, addr 2
axe0: MII without any PHY!
device_attach: axe0 attach returned 6
The cable is plugged in, but the link LEDs are all dark. :(
Any help would be appreciated.
-Dan
On 12/16/06, Dan Frohlich <dan.frohlich@gmail.com> wrote:
>
> Hi all,
> I've been using freebsd for about 6 months now and I'm trying to set up a
> network switch/gateway. I need to use several usb ethernet adapters since
> the box has only 1 NIC and no more expansion space.
>
> I pickup up a dlink dub-e100 and a linksys usb200m. They both come up as
> ugen devices. After hacking the usbdevs file and rebuilding, I was able to
> get the system to recognize the linksys as an axe device, but ifconfig does
> not show the interface. :( I have not tried this with the dlink yet.
>
> Is anyone working on a fix for this? If so is there any way I can assist?
> I saw that there was a low priority defect for the dlink filed, but I do not
> see a defect listed for the linksys. Are there any usb ethernet devices
> currently on the market which do work with 6.2rc1 ?
>
> Please help!
>
> -Dan
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a8a1e6750612171324n1094aca1o6528f38bf0059ada>