From owner-freebsd-questions Fri Oct 27 12:15: 4 2000 Delivered-To: freebsd-questions@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [171.66.112.163]) by hub.freebsd.org (Postfix) with ESMTP id 691DA37B4C5 for ; Fri, 27 Oct 2000 12:15:02 -0700 (PDT) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id MAA45877; Fri, 27 Oct 2000 12:03:16 -0700 (PDT) Date: Fri, 27 Oct 2000 12:03:16 -0700 (PDT) From: Annelise Anderson To: Mike Meyer Cc: questions@freebsd.org Subject: Re: USB Hard Drive In-Reply-To: <14841.12260.624316.766250@guru.mired.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Oct 2000, Mike Meyer wrote: > Annelise Anderson writes: > > I have a Buslink USB Portable Hard Drive (L Series) (10 gb.) that I > > can't get working in FreeBSD. > > I have all the scsi stuff and the usb stuff in the kernel (on 4.1- > > STABLE as of October 25, 2000) and I get the line in dmesg: > > ugen0: buslink-inc. USB-ATAPI4 Bridge Controller rev 1.00/1.00 addr3 > > ugen isn't a disk device; umass is. If you've got the umass device in > the kernel and aren't getting the umass device line (umass0: ...), > then it isn't going to work. No umass0 shows up on boot; and there's no device node like that in /dev, where it seems I'd need to have it if I'm going to treat it like da0 etc. Attempts to mount the file system (msdos) on /dev/da[0-5]c produce "device not configured," and no da devices show up on boot. Other usb devices work--hub, mouse, ethernet, keyboard. Guess this one just doesn't. Thanks--at least it's good to know when to give up. Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message