From owner-freebsd-questions Sun Oct 15 13:17:55 2000 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-27-149-77.mmcable.com [24.27.149.77]) by hub.freebsd.org (Postfix) with SMTP id 1462B37B66C for ; Sun, 15 Oct 2000 13:17:51 -0700 (PDT) Received: (qmail 1968 invoked by uid 100); 15 Oct 2000 20:17:50 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14826.4334.336466.158680@guru.mired.org> Date: Sun, 15 Oct 2000 15:17:50 -0500 (CDT) To: Brian B Cc: questions@freebsd.org Subject: Re: USB Hard Drive Question In-Reply-To: <103823930@toto.iv> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian B writes: > I have a USB Hard Drive and I am running FreeBSD 4.1.1-STABLE > currently. When I plug the Hard Drive into my Unix machine it > recognizes the following: > > usb0: on uhci0 > usb0: USB Revision 1.0 > ugen0: buslink-inc USB-ATAPI4 Bridge Controller, rev. 1.00/1.00 addr 2 > > So it seems like it see's the USB Hard Drive Controller but I can't > figure out what the Hard Drive device name would be? Does anyone > know if this drive will work at all, am I missing something? What you're missing is knowing that the USB driver recognizes lots of devices without having anything more than a generic driver for them. This is useful, because userland code can do things with the ugen devices without a driver. If a more specific driver is available, that shows up as well. Here's my USB printer: ulpt0: Belkin Components (2nd) F5U002 Parallel printer adapter, rev 1.00/1.04, a ddr 2, iclass 7/1 The device name is the first part of the dmesg line (ulpt0). The umass driver should work for this device, as it claims to handle ATAPI drives. If it does, you'll get a "umass0" device. If it isn't, it may be a quirk in the drive, and that will have to be fixed in code. Either that, or the USB-ATAPI bridge isn't a umass ATAPI device, in which case you're out of luck.