On Tuesday 04 March 2003 10:37 am, Irvine Short wrote: > Hi All > > There's a pile of pretty neat USB attached gadgets out there. > > We just got a USB 2.0 external case with a 2.5" notebook drive in it. > It's a Datafab MD2-USB2A.
USB 2.0 is not supported at all yet in FreeBSD as far as I last heard, so if this device works it will be in falling back to 1.0. > On my machine running 4-STABLE as of this afternoon with USB 1.0 ports > whenever I try to access it I get this: > gopak# disklabel -w -r da0 auto > disklabel: /dev/da0c: Input/output error any reason you need to put a new disklabel on it? Why not just try mounting it if it the drive already has a windows disklabel or whatever. > and in /var/log/messages I get this: > Mar 4 17:31:32 gopak /kernel: da0: reading primary partition table: > error reading fsbn 0 > > > On a 5.0 machine (5.0-RELEASE-p3) with USB 2.0 ports (Intel 845 based > motherboard) I get this: > > [EMAIL PROTECTED]:~$ disklabel -wr da0 auto > disklabel: /dev/da0: Input/output error > > and in /var/log/messages: > Mar 4 12:00:52 fusion kernel: umass0: vendor 0x07c4 USB 2.0 Storage > Device, rev 2.00/1.04, addr 2 > Mar 4 12:00:52 fusion kernel: umass0: Residue incorrect, was 0, > should've been 219 > Mar 4 12:00:52 fusion last message repeated 4 times > Mar 4 12:00:52 fusion kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > Mar 4 12:00:52 fusion kernel: da0: <USB 2.0 Storage Device 0100> > Fixed Direct Access SCSI-0 device > Mar 4 12:00:52 fusion kernel: da0: 1.000MB/s transfers > Mar 4 12:00:52 fusion kernel: da0: 38154MB (78140160 512 byte > sectors: 255H 63S/T 4864C) > Mar 4 12:00:52 fusion kernel: umass0: Residue incorrect, was 0, > should've been 512 > Mar 4 12:00:53 fusion last message repeated 14 times > Mar 4 12:01:25 fusion kernel: umass0: Residue incorrect, was 0, > should've been 8192 > Mar 4 12:01:25 fusion last message repeated 4 times > Mar 4 12:01:26 fusion kernel: umass0: Residue incorrect, was 0, > should've been 512 > Mar 4 12:01:26 fusion last message repeated 14 times > Mar 4 12:02:33 fusion kernel: umass0: at uhub0 port 2 (addr 2) > disconnected > Mar 4 12:02:33 fusion kernel: (da0:umass-sim0:0:0:0): lost device > Mar 4 12:02:33 fusion kernel: (da0:umass-sim0:0:0:0): removing > device entry > Mar 4 12:02:33 fusion kernel: umass0: detached are these messages from before or during trying to write the disklabel? if during, what does the dmesg look like when you just have the devices plugged in and you haven't issued any commands? > Anyone ever make these things work? Under Windoze 2000 and XP it just > works, no hassle at all. The USB standard is a large, difficult and fairly buggy standard and its implementation in hardware is usually pretty buggy too. Read through the -current mailing list where they've discussed much of the hardware issues with USB. If the hardware maker does not release enough documentation it can be impossible for somebody to write a FreeBSD driver for it. It takes much more work to write a driver when the device maker gives partial info for it than for MS who gets all of the detailed specs. So when you're getting free hardware support, be careful you're not complaining. You may want to try -current if you're willing to accept all that goes with that (reading the Handbook, following the mailing list, etc). That is where the newest USB code goes in. Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message