I'll try it out soon, thanks!
-adrian
On 15 July 2013 14:35, Taku YAMAMOTO t...@tackymt.homeip.net wrote:
This reminds me of my local patch which I wrote and forgot about deep in
the git :)
This hack was required to have working USB ports on X61 after resume,
but I'm not sure whether it's
Got a new one of these with the same model number as the previous versions, but
still different behavior this time.
When you connect it, it says this:
usbd_setup_device_desc: getting device descriptor at addr 2 failed,
USB_ERR_STALLED
ugen1.2: Western Digital at usbus1
umass0: Western Digital
Hi,
The stalled messages has nothing to do with the mass storage part. It simply
indicates that some error happened during a USB control request. The USB stack
will re-try this particular message, so it is not directly dangerous.
After many years in the USB game I feel a need to emphasize
Nope, no such joy.
What else can I try?
-adrian
On 16 July 2013 02:16, Adrian Chadd adr...@freebsd.org wrote:
I'll try it out soon, thanks!
-adrian
On 15 July 2013 14:35, Taku YAMAMOTO t...@tackymt.homeip.net wrote:
This reminds me of my local patch which I wrote and forgot about deep
On Tue, Jul 16, 2013 at 12:06 PM, Hans Petter Selasky
hans.petter.sela...@bitfrost.no wrote:
I`ve been thinking that perhaps I should start selling certified USB hardware
that doesn`t have all of these caveats you guys report all the time :-) Would
you buy stuff if I opened up an USB shop?
The stalled messages has nothing to do with the mass storage part. It simply
indicates that some error happened during a USB control request.The USB stack
will re-try this particular message, so it is not directly dangerous.
Well, the drive doesn't actually work on the other computer, so
On 07/16/13 13:12, Velcro Leaf wrote:
The stalled messages has nothing to do with the mass storage part. It simply
indicates that some error happened during a USB control request.The USB stack
will re-try this particular message, so it is not directly dangerous.
Well, the drive doesn't
On Tue, 16 Jul 2013 03:14:38 -0700
Adrian Chadd adr...@freebsd.org wrote:
Nope, no such joy.
What else can I try?
Maybe sysctl dev.[uoex]hci.*.wake=1 works.
Other than that I have out of my ideas :(...
-adrian
On 16 July 2013 02:16, Adrian Chadd adr...@freebsd.org wrote:
I'll try it
