Solid usb2.0 ethernet adapter to use?
-
Upgraded to 2.0 from 1.2.x, and finally 2 axe USB ethernets don't panic the box.
Sadly, what they don't do is work for any extended period.
http://www.freebsd.org/cgi/query-pr.cgi?pr=140883
And months later there seems to have been no real effort to fix it.
For those of you using USB 2.0 ethernet devices, what are you using?
-
Strange, I've used the D-Link USB-100 devices which are axe devices and are absolutely rock solid?
-
That PR is in regards to a GB adapter. I have used the DUB-E100 (which is a 10/100 USB 2.0 device) with only minor issues. If you need GB speeds, you shouldn't be using a USB adapter.
-
axe0: <vendor 2="" 0x13b1="" product="" 0x0018,="" rev="" 2.00="" 0.01,="" addr="">on usbus2
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, autoaxe1: <vendor 3="" 0x13b1="" product="" 0x0018,="" rev="" 2.00="" 0.01,="" addr="">on usbus2
ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, autoUSB200M v2, presumably not gig.
USB_ERR_TIMEOUT until a reset is forced after a large amount of data passes, e.g.
Jul 20 01:50:38 rtr kernel: axe_bulk_write_callback: transfer error, USB_ERR_TIMEOUT
Jul 20 01:50:48 rtr kernel: axe_bulk_write_callback: transfer error, USB_ERR_TIMEOUT
Jul 20 01:50:57 rtr kernel: axe_bulk_write_callback: transfer error, USB_ERR_TIMEOUT
Jul 20 01:51:01 rtr kernel: axe_bulk_read_callback: bulk read error, USB_ERR_CANCELLED
Jul 20 01:51:01 rtr kernel: axe_bulk_write_callback: transfer error, USB_ERR_CANCELLED
Jul 20 01:51:13 rtr kernel: axe_bulk_read_callback: bulk read error, USB_ERR_CANCELLEDand data continues to be able to be read after writing it fails.
Which matches that report; I suspect given the comment there that it's an 88178 based axe, and apparently this device id is one too, that the issue is 88178 and not gig.
Sadly, if you buy a USB200M now, this is what you get.</vendor></vendor>
-
That PR is in regards to a GB adapter. I have used the DUB-E100 (which is a 10/100 USB 2.0 device) with only minor issues. If you need GB speeds, you shouldn't be using a USB adapter.
and the referenced forum post includes folks complaining about the DUB-E100, presumably a later rev of the hardware. So 10/100-only doesn't help.