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 actually work on the other computer, so something
important is wrong. The fact that the other machine silently fails is maybe
After many years in the USB game I feel a need to emphasize again, that many of
the mass storage related errors reported here are not a USB HOST problem. There
is a USB standard defined at www.usb.org, that we are trying to comply to.
I totally respect that, but all these devices work with other OSs (which shall
remain unnamed). There's intellectual purity and then there's getting the
freaking things to work. How do these other OSs deal with the quirks? Is it a
matter of downloading piles of drivers?
I do like the idea of a FreeBSD Seal of Approval. It would save us all a lot
Probably some that can be discussed at the next EuroBSDcon !
Any suggestion for fixing the problem? (Other than the long term, but probably
fruitless, suggestion of complaining to Western Digital?)
Could you try to look through the quirks list, using usbconfig and see
if your device is really quirked like it should. I know there has been
introduced an attempt to auto-detect quirks, and this is disabled if any
quirks are set manually.
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"