From owner-freebsd-stable Sun Dec 30 21:58:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 5556F37B428 for ; Sun, 30 Dec 2001 21:58:56 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id fBV5xI412403; Sun, 30 Dec 2001 21:59:19 -0800 (PST) Date: Sun, 30 Dec 2001 21:59:18 -0800 (PST) From: Doug White To: Randall Hopper Cc: Subject: Re: USB help needed In-Reply-To: <20011229173628.A862@nc.rr.com> Message-ID: X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 29 Dec 2001, Randall Hopper wrote: > I got this little MyMP3 player here which has a USB port and functions > as a removable 32MB hard disk in Windows. Just for kicks I thought I'd try > to access it from FreeBSD. > > When I do a 'camcontrol rescan 0' or rescan 1, devlist doesn't show > any new devices. > > Any suggestions? And (backing up a step) are USB mass storage devices > typically generic enough (like IDE hard disks) that I could even hope for > this to work without device-specific support in the FreeBSD kernel? You need to figure out why the device isn't responding to data transmissions. They're just timing out. > umass0: Handling CBI state 11 (CBI Data), xfer=0xc1783200, TIMEOUT > umass0: Data-in 36b failed, TIMEOUT > umass0: CBI Reset Did you hack it to attach to umass? It might need to be quirked. Check out src/sys/dev/usb/umass.c and src/sys/dev/usb/usb_quirks.c for hints. It's entirely possible the device requires a special driver. If it needs one under Windows I'll bet it'll require additional hackery. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message