hail,
I have Linksys USB200M working for some time on 1.2.3R, and now I'm
testing 2.0 BETA. I got my unit to run BETA3 and got this error:
da0: <HUAWEI MMC Storage 2.31> Removable Direct Access SCSI-2 device
da0: 1.000MB/s transfers
da0: Attempt to query device size failed: NOT READY, Medium not present
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored)
usbd_req_re_enumerate: getting device descriptor at addr 2 failed,
USB_ERR_TIMEO
UT
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored)
usbd_req_re_enumerate: getting device descriptor at addr 2 failed,
USB_ERR_TIMEO
UT
usb_alloc_device: Failure selecting configuration index 0:USB_ERR_TIMEOUT,
port
2, addr 2 (ignored)
ugen1.2: <vendor 0x13b1> at usbus1
vr0: link state changed to DOWN
ugen1.2: <vendor 0x13b1> at usbus1 (disconnected)
usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored)
usb_alloc_device: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored)
usbd_req_re_enumerate: getting device descriptor at addr 2 failed,
USB_ERR_TIMEO
UT
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored)
usbd_req_re_enumerate: getting device descriptor at addr 2 failed,
USB_ERR_TIMEO
UT
ugen1.2: <(null)> at usbus1 (disconnected)
uhub_reattach_port: could not allocate new device
usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored)
usb_alloc_device: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored)
usbd_req_re_enumerate: getting device descriptor at addr 2 failed,
USB_ERR_TIMEO
UT
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored)
usbd_req_re_enumerate: getting device descriptor at addr 2 failed,
USB_ERR_TIMEO
UT
ugen1.2: <(null)> at usbus1 (disconnected)
uhub_reattach_port: could not allocate new device
vr0: link state changed to UP
[2.0-beta4][ad...@pfsense.localdomain]/root(2):
so, I then decided to update to BETA4 and as you can see the same issue
happens. I imagine this is something for the FreeBSD part, then the
pfSense, but I had the same NIC running on 8.1R on same hardware and no
problem. so asking here first.
by the way, this unit has 4 usb ports, and this one where the usb nic is
and the one above it are useless until a reboot is issued. using the one
above the 3G modem is fine with the keyboard:
ugen0.1: <UHCI root HUB VIA> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=ON
ugen1.1: <UHCI root HUB VIA> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps)
pwr=ON
ugen2.1: <EHCI root HUB VIA> at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=ON
ugen0.2: <HUAWEI Mobile HUAWEI Technology> at usbus0, cfg=0 md=HOST
spd=FULL (12Mbps) pwr=ON
ugen0.3: <USB NetVista Full Width Keyboard CHICONY> at usbus0, cfg=0
md=HOST spd=LOW (1.5Mbps) pwr=ON
and using the nic there gets me the same error as above. after trying the
usb nic on the port above the 3G modem, the keyboard is useless on it,
returning me the same above error.
all tests now are on BETA4. anyone has any clue ?
this is a via mini itx crusoe based mobo.
thanks,
matheus
--
We will call you cygnus,
The God of balance you shall be
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
http://en.wikipedia.org/wiki/Posting_style
--
We will call you cygnus,
The God of balance you shall be
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
http://en.wikipedia.org/wiki/Posting_style
---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
