Re: USB3 install no workie
In message <6efb4a35-cdbf-c356-1f6d-3d6f0be5b...@selasky.org>, you wrote: >On 09/10/16 04:57, Ronald F. Guilmette wrote: >> Greetings, >> >> I've asked in the past why FreeBSD seems to have such problems with >> USB3 devices and controllers, in particular, and various people of >> good will and admirable patience have been kind enough to explain >> to me the difficulties of trying to write drivers for things where >> nobody actually follows the standards, however... > >Hi, > >Can you try a 10-stable kernel on your box and see if USB 3.0 is >reliably enumerating? I can, but it will have to wait till late next week. I'm crushed with other work right now. ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
USB3 install no workie
Greetings, I've asked in the past why FreeBSD seems to have such problems with USB3 devices and controllers, in particular, and various people of good will and admirable patience have been kind enough to explain to me the difficulties of trying to write drivers for things where nobody actually follows the standards, however... Just a day or two ago I downloaded the file: FreeBSD-10.3-RELEASE-amd64-memstick.img and then dd'ed it to a recent vintage Sandisk Flair USB 3.0 16GB stick, stuck that into one of the built-in USB 3 sockets on my Asus A78M-A and tried to boot so I could do a fresh install of 10.3-RELEASE. Long story short, after getting past most of the boot up process, the install that I had hoped to do crashed and burned. The first irrecoverable error message seemed to be this one: Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19. (Of course, I have no idea what "error 19" is. Is that ENODEV?) Anyway, I at least had the good sense to try again with the same USB stick, but this time with the thing plugged into one of the built-in USB 2 ports on the motherboard. That, worked, no problem, and I was able to complete the install. But this series of events leaves me worrying. In the past, I've had literally a ton of trouble getting anything USB3-ish to work reliably, ever, with FreeBSD. But the last time I even tried was a couple of years ago. I had sort-of vaguely hoped that things might have matured since then, and that at least there would be good support by now for common and widely used motherboard chipsets (in this case, AMD A78 FCH, Bolton D3) as well as widely used devices such as recent vintage Sandisk USB3 sticks. But as noted above, I was unable to even perform a simple install using this combination. And it wasn't like I was trying to install something ancient and crusty. I was trying to install 10.3-RELEASE. So, questions: 1) Where can I find a list of which USB3 chipsets are in fact supported by, for example, 10.3-RELEASE? 2) Where can I find a list of which USB3 devices are in fact supported by, for example, 10.3-RELEASE? 3) Why did my install crash and burn, and what the bleep is error 19? (If that signifies ENODEV in this context, then, I mean, what the bleep? Why would a UFS mount work fine when a given device is plugged into a USB2 port but _not_ when it is plugged into a USB3 port?) 4) Should I assume that the USB3 ports on my Asus A78M-A won't be working any more reliably _after_ the install of 10.3 than they appear to have done _during_ the install? Regards, rfg ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: Do _any_ USB 3.0 cards actually work?
In message alpine.bsf.2.00.1405261636170.85...@wonkity.com, Warren Block wbl...@wonkity.com wrote: On Mon, 26 May 2014, Julian H. Stacey wrote: Does FreeBSD *ever* work with *any* USB 3.0 equipment? Or is this Yes it works. Tue, 12 Jun 2012 I filed a success report: http://lists.freebsd.org/pipermail/freebsd-usb/2012-June/011283.html Jeesh, two years ago. I remember looking it up at the time, and this appears to be the same card from Newegg: www.newegg.com/Product/Product.aspx?Item=N82E16815158297 So are you guys telling me that I just shoulda bought that one? I can see right off the bat why I didn't. It looks like even now it still costs about twice as much as the ones that I did actually buy. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Do _any_ USB 3.0 cards actually work?
I have more than a little reason to be suspicious of the motheboard in my #2 desktop system, so I swapped the USB 3.0 PCIe add-in cards that I had here between my two system and then re-ran all of my tests. So now you can find all my test results in these five files: ftp://ftp.tristatelogic.com/pub/fbsd-usb3/desktop1+anker-varlogmessages.txt ftp://ftp.tristatelogic.com/pub/fbsd-usb3/desktop1+hootoo-varlogmessages.txt ftp://ftp.tristatelogic.com/pub/fbsd-usb3/desktop2+anker-varlogmessages.txt ftp://ftp.tristatelogic.com/pub/fbsd-usb3/desktop2+hootoo-varlogmessages.txt ftp://ftp.tristatelogic.com/pub/fbsd-usb3/htpc-varlogmessages.txt Predictably, perhaps, the problems did in fact follow the (older, and apparently not so great) Anker[tm] brand controller card, and _did not_ seem at all to depend on the motherboard. I learned one other thing also. As I mentioned earlier, the Anker card (which I purchased over a year ago) apparently contains a VL800-Q8. On the other hand I've now looked closely at the HooToo USB 3.0 PCIe card that I just purchased recently, and it sports a VL805-Q6. Based on the dates of the following press reports, the VL800 is indeed a much earlier (and, I am guessing, buggier) incarnation of the VL805: (VL800 - May 26, 2010) http://www.legitreviews.com/via-labs-vl800-usb-3-0-4-port-host-controller-announced_8134 (VL805 - November 22nd 2012) http://www.techpowerup.com/175936/via-labs-announces-two-new-usb-3-0-host-controllers-via-vl805-and-via-vl806.html So I guess it serves me right for trying to use an old card with an old version of FreeBSD. But then again, even a really very fresh version of FreeBSD doesn't seem to like the old card. But then again, perhaps that silicon was just plain BUGGY. Certainly the fact that it seems to disconnect and then reconnect an unrelated device when I plug in my Patriot Gaultlet2 would tend to support that view. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Test Results (was: Re: Do _any_ USB 3.0 cards actually work?)
As a result of Warren Block's suggestion, I decided to try a number of new and additional tests in order to try to further pin down and/or at least document the current set of USB 3.0 problems I've been grappling with. I have also gathered further information about which chips, specifically are contained within my various devices and controllers. I do hope that all of the following information will prove useful. I am fortunate to have here three (3) different (amd) x86-based systems which each contain a dual USB 3.0 interface card of one kind or another. I am also fortunate to also have several different kinds of USB 2.0 and USB 3.0 external devices that I can run tests with. First, in order to make sure that I am reporting _current_ issues relating tro USB support, today I downloaded the following image file and installed this onto a USB 2.0 stick I had lying around (i.e. a SanDisk Switch 8GB): FreeBSD-10.0-STABLE-amd64-20140506-r265408-memstick.img All test results reported below are from systems that were booted to the above FreeBSD image. The results I gathered are all in the form of copies of /var/log/messages files. (At first I was going to provide just output from dmesg(8), but then I noticed that those don't have date/time stamps, so I went back and re-did all of my tests and collected the /var/log/messags files instead.) The following files show the results of the numerous tests I did on the three different system I own that contain USB 3.0 interfaces: ftp://ftp.tristatelogic.com/pub/fbsd-usb3/desktop1-varlogmessages.txt ftp://ftp.tristatelogic.com/pub/fbsd-usb3/desktop2-varlogmessages.txt ftp://ftp.tristatelogic.com/pub/fbsd-usb3/htcp-varlogmessages.txt Please note that during my tests every time I performed some manual action, in particular plugging or unplugging a USD device, I used the logger(1) program to write a line starting with to the system log (/var/log/messages). This helps a lot to see what was really (physically) going on at each step during the tests. My desktop#1 system contains this dual port USB 3.0 PCIe interface card that I've already mentioned (VIA LV800 chipset): http://www.newegg.com/Product/Product.aspx?Item=17Z-0002-2 My desktop#2 system contains this Anker 2-port USB 3.0 PCIe card: http://www.amazon.com/Anker%C2%AE-Uspeed-Express-20-pin-Connector/dp/B007SJGGAE/ref=pd_cp_pc_2/181-8193670-6916000 I have just now checked that, and the big chip on that has written on the top of the chip VL800-Q8, so apparentlty this also contained the VIA[tm] VL 800 chipset. My HTPC system contains whatever the heck kind of USB 3.0 controller Foxconn elected in include on the board for this system: http://www.newegg.com/Product/Product.aspx?Item=N82E16856119070 For my tests, I used the following 4 external devices, which I list here (and which I tested) in what I believed might be incresing levels of probable non-working-ness: SanDisk Cruzer Blade 1.20 # USB 2.0 device http://www.amazon.com/SanDisk-Cruzer-Frustration-Free-Packaging-SDCZ50-004G-AFFP/dp/B007KFAG8O ADATA USB Flash Drive 1.00 # USB 3.0 device http://www.newegg.com/Product/Product.aspx?Item=N82E16820211572 http://www.amazon.com/ADATA-Superior-Series-Flash-AS102P-16G-RGY/dp/B005Y8C0H4 HitachiG ST # USB 3.0 device http://www.newegg.com/Product/Product.aspx?Item=N82E16822145582 http://www.amazon.com/HGST-Touro-Mobile-External-HTOLMX3NA5001ABB/dp/B0062FZ3PY Hitachi HTS541010A9E680 JA0O # USB 3.0 device http://www.newegg.com/Product/Product.aspx?Item=N82E16817826002 http://www.amazon.com/Patriot-PCGTII25S-Gauntlet-2/dp/B006ICNRUO Please note that the HitachiG ST device is a PERMANENTLY SEALED unit, so there is no way for me to find out what sort of interface chip is inside that. What I am listing here as Hitachi HTS541010A9E680 JA0O is actually a rather ordinary 2.5 1TB laptop drive which I have installed inside of a Patroit[tm] brand Gauntlet 2 external 2.5 USB 3.0 enclosure. (See links above for pictures and more technical information.) In the case of the Patriot[tm] Gauntlet2 2.5 USB 3.0 enclosure (aka Hitachi HTS541010A9E680 JA0O) I took the time to actually disassemble that so that I could look and see what sort of chip was in it. Written on the chip that is inside the Gauntlet2 is a set of three designators, the first of which is GL3310. Googling that plus up lots of relevant information. As a boot device on all 3 test systems I also used a USB 2.0 flash stick which is identified within the system logs as SanDisk Cruzer Switch 1.26. That was pulgged into a USB 2.0 port on all three test systems during boot up. My test procedure for all three systems was as follows: 1) Insert the SanDisk Cruzer Blade (USB 2.0) into one of the two USB 3.0 ports. 2) Insert the ADATA USB Flash Drive into the second USB 3.0 port and
Do _any_ USB 3.0 cards actually work?
I onw a 1TB HGST laptop drive. This has been installed into a Patroit[tm] brand Gauntlet II external USB 3.0 enclosure. This drive has had all built-in diagnostics run on it, and it is perfectly A-OK. It works compltely fine with no problems on multiple Linux systems I have here. The motherboard on my main FreeBSD system is an ASRock N68C-GC FX, and to that I have added one of these add-on USB 3.0 cards: http://www.newegg.com/Product/Product.aspx?Item=17Z-0002-2 Unfortunately, the drive is not working at all with this system or this card. When the device is plugged into one of the USB 3.0 ports I get these messages in /var/log/messages: May 23 22:45:04 segfault kernel: xhci_do_command: Command timeout! May 23 22:45:04 segfault kernel: usb_alloc_device: device init 3 failed (USB_ERR_TIMEOUT, ignored) May 23 22:45:04 segfault kernel: ugen2.3: Unknown at usbus2 (disconnected) May 23 22:45:04 segfault kernel: uhub_reattach_port: could not allocate new device No other messages appear in the log, and quite obviously, the drive is utterly inaccessible to FreeBSD. This is extraoordinarily annoying, as I spend good money to buy this add-in USB 3.0 card in the hopes that it would solve the problems that I previously had with FreeBSD and a different USB 3.0 card, and now it is all useless. Does FreeBSD support the VIA VL800 Chipset that this add-on card is alleged to contain? Does FreeBSD *ever* work with *any* USB 3.0 equipment? Or is this just a far off dream? P.S. I know that FreeBSD doesn't have nearly as many people working on it as Linux does, but I didn't really expect it to be quite this far behind in terms of driver support for USB 3.0. I mean how long has USB 3.0 been out now? Five+ years?? ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Do _any_ USB 3.0 cards actually work?
In message 5380eb10.9030...@selasky.org, Hans Petter Selasky h...@selasky.org wrote: On 05/24/14 20:43, Ronald F. Guilmette wrote: Does FreeBSD support the VIA VL800 Chipset that this add-on card is alleged to contain? Does FreeBSD *ever* work with *any* USB 3.0 equipment? Or is this just a far off dream? What version of FreeBSD are you running. 9.1-RELEASE Have you tried -stable? No, I have not. I did also try 10.0-RELEASE (LiveCD) and also again got a bunch of errors and the system refused to see the drive again. I tried that (10.0-RELEASE) with multiple different motherboard and multiple different USB 3.0 add-in PCIe controller cards. All tests failed, all of the time, with both systems. Yes, USB 3.0 _works_ with FreeBSD. Please can you be more specific? What host controller chipsets are supported, exactly? Please post the list. And specifically, is the VIA VL800 chipset supported? What controllers and what external USB 3.0 devices have you yourself actually _successfully_ tested, and which version of FreeBSD exactly did you use for those tests? I'm sorry if I seem to be aseking too many detailed questions about this, but I've previously also tried using external USB 3.0 hard drives attached to a totally different system, also running FreeBSD, with a different motherboard *and* a totally different USB 3.0 card in it and that experiment also ended in tears and utter failure. I really would like to know what specific USB 3.0 hardware was properly tested and qualified as working and fully supported *before* 10.0-RELEASE went out the door. Was there any? Or did USB 3.0 support only begin working properly post 10.0-RELEASE? P.S. To be clear, I am interested in finding out if FreeBSD actually has any support for any kind of *rotating* USB 3.0-attached external storage. Right at the moment, I don't really care if USB 3.0 flash sticks work. (Those are quite obviously going to be easier to make work.) P.P.S. Not all of use have the luxury of being able to run -STABLE. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Do _any_ USB 3.0 cards actually work?
In message 8021b607-b94b-4a2d-8b0a-a63a88094...@gsoft.com.au, you wrote: On 25 May 2014, at 4:13, Ronald F. Guilmette r...@tristatelogic.com = wrote: This is extraoordinarily annoying, as I spend good money to buy this add-in USB 3.0 card in the hopes that it would solve the problems that I previously had with FreeBSD and a different USB 3.0 card, and now it is all useless. =20 Does FreeBSD support the VIA VL800 Chipset that this add-on card is alleged to contain? =20 Does FreeBSD *ever* work with *any* USB 3.0 equipment? Or is this just a far off dream? I have 2 USB3 cards, one works and one doesn't, unfortunately I haven't been able to determine why as yet. What is the brand and model number of the one that works? What is the brand and model number of the one that doesn't? It would be helpful to know in both cases. Also, for the one that works, are you able to connect a device to that, disconnect it and then reconnect it again and have it work after that? (I had trouble with this in the past with my other 3.0 card, even when only using external 2.0 devices, if I am recalling correctly.) P.S. I know that FreeBSD doesn't have nearly as many people working on it as Linux does, but I didn't really expect it to be quite this far behind in terms of driver support for USB 3.0. I mean how long has USB 3.0 been out now? Five+ years?? This isn't a helpful thing to say when you're using a volunteer project. Sorry. Having invested in two different USB 3.0 PCIe cards and a couple of external 3.0 enclosures... all of which I had some hope would work, by now, on FreeBSD... and all of which *do* in fact work entirely well on Linux, I do hope that perhaps my level of frustration is understandable. There are about a thousand or so different ethernet chipsets, so I can well and truly understand why this or that ethernet controller isn't supported yet. But how many different USB chipsets are there? Maybe like ten, total, including both 3.0 and 2.0? And aren't all of these different USB chipsets *supposed* to present one standard programatic interface (to the driver) anyway? Anyway, ignoring the investment in MONEY I've already made... for naught, apparently... I've also invested at least a little time in trying to make this stuff work, and in keeping with the volunteer nature of FreeBSD I *am* willing to try to assist in further testing and debugging, e.g. of the USB drivers in, e.g. 10.0-STABLE if only someone will instruct me how how to install that, from scratch, on a fresh empty drive. I seriously do not know how to do this. I've been using FreeBSD for well over ten+ years and I've always and only used -RELEASE. The -RELEASE CDs are obviously quite helpful and make installation so simple that a cave man could do it. But at this moment I am sitting here looking at this directory: /pub/FreeBSD/snapshots/amd64/amd64/10.0-STABLE on one of the FreeBSD mirrors, and I haven't the vaguest idea what to do with that stuff in order to get it all installed onto an empty drive. If you or someone else tells me how to do that, then I will be happy to do so and then see if either of these 3.0 cards I have will work with that, and if not I'll try to help debug the problem(s). ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Do _any_ USB 3.0 cards actually work?
In message alpine.bsf.2.00.1405242010430.97...@wonkity.com, you wrote: On Sat, 24 May 2014, Ronald F. Guilmette wrote: Does FreeBSD support the VIA VL800 Chipset that this add-on card is alleged to contain? Sorry, no idea. Does FreeBSD *ever* work with *any* USB 3.0 equipment? Or is this just a far off dream? I used this card along with a USB 3 drive dock to copy a fair amount of data: http://www.newegg.com/Product/Product.aspx?Item=N82E16815287015 Thanks Warren! (I wish I had consulted with you two weeks ago before purchasing the 2+2 port HooToo card.) Admittedly, I'm a bit skeptical about USB 3 given how long USB 2 took to mature in the industry as a whole. As I've been saying, it all seems to work just fine on Linux. If possible, I'd prefer SATA/eSATA or Ethernet for transferring large amounts of data. Unfortunately, the HTPC I have in the livingroom doesn't have an eSATA port. (And there are no slots for any add-in cards or even space to put an eSATA socket/connector.) It does however have two (2) USB 3.0 built-in ports. P.S. Somebody on www.newegg.com said that that Vantec card contains a Renesas D720200A chipset. So I guess we can check that one off as supported. Wish I had known that the VIA VL800 isn't. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
RALINK RT3572 supported in 9.1-RELEASE ?
I have a Trendnet TEW-684UB wireless dual-band USB adapter. Googling around for awhile leads me to believe that this probably contains an Ralink RT3572 chipset. Further googling also leads me to believe that a version of the run(4) driver which should support this chipset was comitted some considerable time ago. Can anyone confirm either or both of these two impressions? Does the TEW-684UB contain an Ralink RT3572? Is support for that chipset present in 9.1-RELEASE? If the answer to both of the above is yes, then where might I find a HOW TO sort of doc which might help me to get this running? I've already added the following lines to /boot/loader.conf and rebooted: if_run_load=YES runfw_load=YES but apparently to no avail. After adding the above two lines to loader.conf and rebooting, shouldn't the device thenceforth appear in the output of ifconfig -a ? (Mine does not.) ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Help please... More problems with USB 3.0 (kernel freezes)
Back on March 11, I wrote here about the problems I was having with a new Anker[tm] 2-port USB 3.0 PCIe card. After Hans Petter Selasky kindly responded, I believed that I had isolated the problem to just one specific pairing of a specific device and my specific card. Well, it seems now that I was utterly wrong. (I have only just now realized this because since the 11th, I have been working on other things and haven't even touched any of the USB 3.0 stuff... at least not in conjunction with FreeBSD.) Anyway, the problem is back now, and with a vengence. In fact now, it is causing kernel freezes. (This is exceptionally serious in my book.) The problem is what it was before... the Anker[tm] card, together with the 9.1-RELEASE xhci driver, is refusing to properly connect a USB mass storage type device that has been plugged into the card. I have now reproduced this problem multiple times, both with external (non-powered) USB 3.0 drive enclosures (2 x Patriot Gauntlet2) and also even with a USB 3.0 flash thumb drive I have here (ADATA S102 16GB). It appears that once the drive+card gets into a mode (mood?) where it no longer wants to properly recognize any newly inserted USB mass storage type device it will, after that point in time, refuse to properly recognize _any_ USB mass storage device (3.0 or 2.0) that is plugged into the Anker card after that time. So far, this problem only seems to occur when I plug something in to the Anker card _after_ boot time. But since the problem appears to be somewhat random... sometimes failing, sometimes not... I cannot tell for sure if pre-boot-time versus post-boot-time device insertion is making any real difference to the problem. After boot time, about 50% of the time when I plug a device... apparently _any_ device... into the Anker card, I will get messages like the following in my /var/log/messages file: ... Mar 18 13:36:44 segfault kernel: xhci_do_command: Command timeout! Mar 18 13:36:44 segfault kernel: usb_alloc_device: set address 3 failed (USB_ERR_TIMEOUT, ignored) Mar 18 13:36:44 segfault kernel: xhci_do_command: Command timeout! Mar 18 13:36:58 segfault last message repeated 47 times Mar 18 13:36:58 segfault kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) Mar 18 13:36:59 segfault kernel: xhci_do_command: Command timeout! Mar 18 13:37:12 segfault last message repeated 41 times Mar 18 13:37:12 segfault kernel: usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) Mar 18 13:37:14 segfault kernel: xhci_do_command: Command timeout! Mar 18 13:37:25 segfault last message repeated 39 times Mar 18 13:37:25 segfault kernel: ugen0.3: Unknown at usbus0 (disconnected) Mar 18 13:37:25 segfault kernel: xhci_do_command: Command timeout! Mar 18 13:37:25 segfault kernel: uhub_reattach_port: could not allocate new device Mar 18 13:37:26 segfault kernel: xhci_do_command: Command timeout! ... In all cases where the set of /var/log/messages messages is exactly like what is shown above, after the final messages of the sequence (see above) the little blue power light on my Gauntlet2 box goes out and at that point the kernel absolutely freezes... there is no longer any response from key- board or mouse input, and the system in question then and henceforth refuses to respond even to pings from elsewhere on the same networtk. I have now seen these kernel freezes several times. They can and do happen regardless of whether or not X is running at the time. These kernel freezes are unambiguously linked to the physical act of me plugging in a device to the Anker card... they always happen very shortly thereafter, and only and immediately after the exact sequence of messages shown above are written to /var/log/messages. For the record, the card+driver is/are malfunctioning... specifically not completing the attach of a newly inserted mass storage device... regardless of whether the device just inserted is an external hard drive or an external flash drive, however I have only seen the kernel freezes occur when the device just inserted was an external (self-powered) hard drive. In due course, I will of course file appropriate formal PRs for these USB problems, however for now I am more focused on just getting these bloody things working. (I have already invested a fair amount of time and effort into this little project and I have nothing to show for it, other than some personal aggravation.) So anyway, for right now I just want to debug these problems, if possible, and get this equipment working properly. Along those lines, I have a few questions: 1) What is the best way to debug this? I have seen HPS suggest to others with USB problems that they either (a) use the usbdump(8) command to get more info about the problems or else (b) compile and install a new kernel in which the option USB_DEBUG has been defined. Which should I do, and how may I interpret the results in either case? 2) What are the
Help, please... USB 3.0 card won't attach again after first detach
I have a new PCIe USB 3.0 card. It is basically just like this one: http://www.amazon.com/Uspeed-Superspeed-Express-Connector-Desktops/dp/B005ARQV6U/ref=sr_1_2?ie=UTF8qid=1362999114sr=8-2keywords=anker+USB+3.0 except that mine is the 2 port version, rather than the 4 port version. (But it is the same brand/manufacturer.) Wnen I fire up the system, the card is recognized just fine. Then, I can plug in one of my USB 3.0 external drives, and the system properly notices that this has happened, and the system then creates an appropriate set of new /dev/da??? nodes. Then I can successfully mount one of those, e.g. onto /mnt. Later however, I umount the partition in question and then physically disconnect USB 3.0 drive from the USB 3.0 card. Later still, I try again to plug in the same USB 3.0 drive or a different USB 3.0 drive, also and again into one of the two ports on the USB 3.0 PCIe card. Now, all I get is grief and failure. Here is some probably relevant material from my /var/log/messages file: ... Mar 11 03:40:06 segfault kernel: pci3: ACPI PCI bus on pcib1 Mar 11 03:40:06 segfault kernel: xhci0: XHCI (generic) USB 3.0 controller mem 0xf600-0xf6000fff irq 16 at device 0.0 on pci3 Mar 11 03:40:06 segfault kernel: xhci0: 32 byte context size. Mar 11 03:40:06 segfault kernel: usbus0 on xhci0 ... ... Mar 11 03:40:06 segfault kernel: usbus0: 5.0Gbps Super Speed USB v3.0 Mar 11 03:40:06 segfault kernel: usbus1: 12Mbps Full Speed USB v1.0 Mar 11 03:40:06 segfault kernel: usbus2: 480Mbps High Speed USB v2.0 Mar 11 03:40:06 segfault kernel: ugen0.1: 0x1106 at usbus0 Mar 11 03:40:06 segfault kernel: uhub0: 0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1 on usbus0 Mar 11 03:40:06 segfault kernel: ugen1.1: nVidia at usbus1 Mar 11 03:40:06 segfault kernel: uhub1: nVidia OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus1 Mar 11 03:40:06 segfault kernel: ugen2.1: nVidia at usbus2 Mar 11 03:40:06 segfault kernel: uhub2: nVidia EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus2 Mar 11 03:40:06 segfault kernel: uhub1: 8 ports with 8 removable, self powered Mar 11 03:40:06 segfault kernel: uhub0: 5 ports with 4 removable, self powered Mar 11 03:40:06 segfault kernel: ugen0.2: vendor 0x2109 at usbus0 Mar 11 03:40:06 segfault kernel: uhub3: vendor 0x2109 USB2.0 Hub, class 9/0, rev 2.00/2.00, addr 1 on usbus0 Mar 11 03:40:06 segfault kernel: uhub3: 4 ports with 4 removable, self powered ... ... Mar 11 03:41:56 segfault kernel: ugen0.3: AFT at usbus0 Mar 11 03:41:56 segfault kernel: umass1: U3.0 on usbus0 Mar 11 03:41:56 segfault kernel: umass1: SCSI over Bulk-Only; quirks = 0x4100 Mar 11 03:41:56 segfault kernel: umass1:8:1:-1: Attached to scbus8 Mar 11 03:42:01 segfault kernel: (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 Mar 11 03:42:01 segfault kernel: (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error Mar 11 03:42:01 segfault kernel: (probe0:umass-sim1:1:0:0): Retrying command Mar 11 03:42:02 segfault kernel: da1 at umass-sim1 bus 1 scbus8 target 0 lun 0 Mar 11 03:42:02 segfault kernel: da1: Hitachi HTS541010A9E680 JA0O Fixed Direct Access SCSI-0 device Mar 11 03:42:02 segfault kernel: da1: 400.000MB/s transfers Mar 11 03:42:02 segfault kernel: da1: 953868MB (1953523051 512 byte sectors: 255H 63S/T 121601C) Mar 11 03:42:51 segfault ntfs-3g[1786]: Version 2012.1.15 external FUSE 29 Mar 11 03:42:51 segfault ntfs-3g[1786]: Mounted /dev/da1s1 (Read-Write, label Gauntlet2-1-Partition-0, NTFS 3.1) Mar 11 03:42:51 segfault ntfs-3g[1786]: Cmdline options: Mar 11 03:42:51 segfault ntfs-3g[1786]: Mount options: allow_other,nonempty,relatime,fsname=/dev/da1s1 Mar 11 03:42:51 segfault ntfs-3g[1786]: Ownership and permissions disabled, configuration type 1 ... Mar 11 03:44:15 segfault ntfs-3g[1786]: Unmounting /dev/da1s1 (Gauntlet2-1-Partition-0) Mar 11 03:44:51 segfault kernel: ugen0.3: AFT at usbus0 (disconnected) Mar 11 03:44:51 segfault kernel: umass1: at uhub0, port 4, addr 2 (disconnected) Mar 11 03:44:51 segfault kernel: (da1:umass-sim1:1:0:0): lost device - 0 outstanding, 1 refs Mar 11 03:44:51 segfault kernel: (pass5:umass-sim1:1:0:0): passdevgonecb: devfs entry is gone Mar 11 03:44:51 segfault kernel: (da1:umass-sim1:1:0:0): removing device entry Mar 11 03:45:05 segfault kernel: ugen0.3: HitachiGST at usbus0 Mar 11 03:45:05 segfault kernel: umass1: HitachiGST Touro Mobile 3.0, class 0/0, rev 3.00/0.00, addr 2 on usbus0 Mar 11 03:45:05 segfault kernel: umass1: SCSI over Bulk-Only; quirks = 0x0100 Mar 11 03:45:05 segfault kernel: umass1:8:1:-1: Attached to scbus8 Mar 11 03:45:05 segfault kernel: (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0 Mar 11 03:45:05 segfault kernel: (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an error Mar 11 03:45:05 segfault kernel: (probe0:umass-sim1:1:0:0): Retrying command Mar 11 03:45:05 segfault kernel: ugen0.3: HitachiGST at usbus0 (disconnected) Mar 11 03:45:05
Re: Help, please... USB 3.0 card won't attach again after first detach
In message 513dec7b.3080...@bitfrost.no, Hans Petter Selasky h...@bitfrost.no wrote: If you plug another USB device like a memory stick, does the same happen? Is your USB HDD self powered? Thank you very much for your questions. I am ashamed to admit that I simply did not stop to think that I should try various USB devices to see if any others would make a difference to this problem. Now I have done several tests, based on your questions, and the specific device being plugged in quite clearly _does_ make a difference. I am fortuante that I happen to have several USB memory sticks on hand, including both USB 2.0 and also USB 3.0 sticks, and I also have on hand three (3) different USB 3.0 external 2.5 inch (5400rpm) drives. I've tested all these now with my new Anker[tm] USB 3.0 PCIe card, and now I know what I did not know before... the problem I described is apparently limited to just one of my external USB 3.0 hard drives... which is indeed self-powered... although I'm not at all persuaded that that makes any difference. All of my USB 2.0 3.0 memory sticks work just fine with the Anker card. Of my USB 3.0 external hard drives, I have just the following three: 1) Hitachi Mobile Touro (Model 0S03452) 500GB 5400rpm (self-powered) 2) HGST 2.5 1TB/5400rpm drive (model 0s03508) mounted inside of a brand new Patriot[tm] Gauntlet2 external 2.5 USB 3.0 self-powered enclosure 3) identical to #2 above The latter two drives work just fine with the Anker PCIe card, with no problems whatsoever. From all my testing, it is now 100% clear that the only problem is with the Hitachi Mobile Touro drive. As noted above, this drive is self-powered, but then so are the other two external 2.5 drives that I have had complete success with, so I really don't think that this is a power issue. I should perhaps note also that I have used the Hitachi Mobile Touro also with my laptop (USB 2.0 port Windows 7), with another computer (USB 2.0 only, Windows 7 2000) and even with my LG Blu-ray player, and it has never before given me even a hint of trouble. But clearly, there is some incompatability between the Hitachi Mobile Touro and the Anker PCIe USB 3.0 card. I will inform the manufacturer. Thanks again for your questions and makeing me do my homework. I apologize for failing to have done it earlier. Regards, rfg P.S. For whatever it's worth I also don't believe that this problem has anything to do with power supply issues because (a) the little blue light on top of the Hitachi Mobile Touro does in fact come on when it is plugged in, and also, the Anker[tm] card _does_ have a place on it to attach a 4-pin molex power connector, from the system power supply, and I have of course done that. It seems that this card and this drive just do not like each other. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
