Any truth to the ehci(4) having stability problems in >= 6.0-RC1 ? Or has this only been a problem in 5.4-RELEASE or earlier? -------- Original Message -------- Subject: Re: USB 2.0 Support (re-post, more info) Date: Tue, 8 Nov 2005 09:46:20 -0500 From: Bob Johnson <fbsdlists_at_gmail.com> To: Nathan Vidican <nvidican_at_wmptl.com> CC: questions_at_freebsd.org References: <4370B124.1010103_at_wmptl.com> On 11/8/05, Nathan Vidican <nvidican_at_wmptl.com> wrote: > I tried plugging the device in to all four ports on the USB 2.0 PCI Card, to > no > avail, no device/event is registered. I read the manpage on usbd, and it > appears > to be monitoring/watching for devices. I connect the device to one of the > two > ports on the mainboard, and I get this: > > > uhub3: device problem (SET_ADDR_FAILED), disabling port 1 > umass0: Cypress Semiconductor USB2.0 Storage Device, rev 2.00/0.01, addr 2 > umass0: Get Max Lun not supported (STALLED) > umass0: at uhub0 port 1 (addr 2) disconnected > umass0: detached > umass0: Cypress Semiconductor USB2.0 Storage Device, rev 2.00/0.01, addr 2 > umass0: Get Max Lun not supported (STALLED) > da1 at umass-sim0 bus 0 target 0 lun 0 > da1: <WDC WD16 00JB-98GVA0 \\0000\\0000> Fixed Direct Access SCSI-0 device > da1: 1.000MB/s transfers > da1: 152627MB (312581808 512 byte sectors: 255H 63S/T 19457C) > > Yet again, my transfer speed is limited to the USB 1.1 specification of this > > controller, and it's terribly slow to be pulling 100GB tar files off of :( USB 2.0 support is provided by the ehci(4) driver, which is not in a default install. It is also buggy, at least in 5.4-R. I use Firewire for large external drives. - Bob -- Nathan Vidican nvidican_at_wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/Received on Tue Nov 08 2005 - 15:24:48 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:47 UTC