Re: USB 3 devices not reliably connecting at 5Gbps

2014-04-10 Thread Erich Dollansky
Hi, On Fri, 11 Apr 2014 14:03:19 +0930 Daniel O'Connor docon...@gsoft.com.au wrote: I have a FreeBSD 9.2 system on which I am developing a USB3 data acquisition card (based on the Cypress FX3) and I have found that it doesn't reliably connect at 5GBps - quite often it seems to only connect

Re: consistent, functional 1TB usb drive?

2014-03-04 Thread Erich Dollansky
Hi, just buy cheap USB cases and put any drive you want in. Of course, some of the cases are better and same are worse then other. But how much money will you lose. As you can use then drives which fit into your other hardware, you can even exchange them in case of a problem. Erich On Mon, 17

Re: consistent, functional 1TB usb drive?

2014-03-04 Thread Erich Dollansky
Hi, On Tue, 4 Mar 2014 07:37:34 -0800 (PST) Velcro Leaf velcrol...@rocketmail.com wrote: On Tue, 3/4/14, Erich Dollansky er...@alogt.com wrote: just buy cheap USB cases and put any drive you want in. Will this result in a quirkless installation, or will I just be moving the problem

Re: USB3 SATA enclosure

2012-12-10 Thread Erich Dollansky
Hi, On Mon, 10 Dec 2012 16:29:29 -0500 Mike Tancsa m...@sentex.net wrote: I picked up a USB3 sata enclosure and was surprised at the low speeds I was getting. I should probably just stick with eSata instead, but has anyone got any decent throughput on USB3 drives ? I have one. It achieves

Re: Device working on USB 2 but not on USB 3, best way to isolate the problem

2012-07-03 Thread Erich Dollansky
Hi Hans, On Tuesday, July 03, 2012 01:32:04 AM Hans Petter Selasky wrote: On Sunday 01 July 2012 02:02:03 Erich Dollansky wrote: Hi, On Saturday, June 30, 2012 10:02:21 PM Hans Petter Selasky wrote: On Saturday 30 June 2012 11:46:10 Erich Dollansky wrote: You can try to look

Re: Device working on USB 2 but not on USB 3, best way to isolate the problem

2012-07-03 Thread Erich Dollansky
Hi, On Tuesday, July 03, 2012 11:33:40 PM Hans Petter Selasky wrote: On Tuesday 03 July 2012 15:30:00 Erich Dollansky wrote: http://svn.freebsd.org/changeset/base/238078 http://svn.freebsd.org/changeset/base/238079 perfect. Erich ___ freebsd-usb

Re: Device working on USB 2 but not on USB 3, best way to isolate the problem

2012-07-01 Thread Erich Dollansky
I compile them into the kernel, it only works for the Toshiba device. Is there anything else I have to consider for a quirk which works from the command line? Erich On Sunday, July 01, 2012 07:02:03 AM Erich Dollansky wrote: Hi, On Saturday, June 30, 2012 10:02:21 PM Hans Petter Selasky

Re: Device working on USB 2 but not on USB 3, best way to isolate the problem

2012-07-01 Thread Erich Dollansky
Hi, On Saturday, June 30, 2012 10:02:21 PM Hans Petter Selasky wrote: On Saturday 30 June 2012 11:46:10 Erich Dollansky wrote: You can try to look at the Linux XHCI driver, and the port switching support they have. It appears that because many old OS'es does not support USB 3.0 out

Device working on USB 2 but not on USB 3, best way to isolate the problem

2012-06-30 Thread Erich Dollansky
Hi, I have here a several storage devices which all work in different FreeBSD machines on USB 2. Some of them also work on an USB 3 port but most fail. Even one USB 3 device works on USB 2 but not on USB 3. As at least two USB 2 devices work both on USB 2 and USB 3, I expect the USB 3 port

Freeze while USB hard disk died while calling umount

2011-11-26 Thread Erich Dollansky
Hi, I think that the following is just a note for the developers working on the USB section dealing with hard disks. I just have had a total freeze of a FreeBSD machine running on 8.2 from yesterday. How it happened: I got an old backup disk back. It was not used for more than a year. I

USB (ohci) on FreeBSD 8.0 not working with AcerLabs M5237

2010-01-15 Thread Erich Dollansky
Hi, I installed 8.0 after my hard disk died. I compiled 8.0 from last Saturday with the GENERIC configuration. It booted and hanged on the spot 7.2 gives this message: ohci0: AcerLabs M5237 (Aladdin-V) USB controller mem 0xe810-0xe8100fff irq 11 at device 2.0 on pci0 ohci0: [GIANT-LOCKED]