From owner-freebsd-usb@FreeBSD.ORG Mon Dec 6 13:52:39 2004 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81DC116A4CE for ; Mon, 6 Dec 2004 13:52:39 +0000 (GMT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3862B43D41 for ; Mon, 6 Dec 2004 13:52:39 +0000 (GMT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 7E15A3D37; Mon, 6 Dec 2004 08:52:38 -0500 (EST) From: "Dan Langille" To: freebsd-usb@freebsd.org Date: Mon, 06 Dec 2004 08:52:39 -0500 MIME-Version: 1.0 Message-ID: <41B41DD7.7383.A29056E5@localhost> Priority: normal In-reply-to: <200412061345.iB6DjRw14911@Mail.NOSPAM.DynDNS.dK> X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body cc: Dan Langille Subject: Re: lexar usb media failure to attach X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 13:52:39 -0000 On 6 Dec 2004 at 14:45, Barry Bouwsma wrote: > > > > At 04:41 PM 05/12/2004, Dan Langille wrote: > > > >I purchased a USB memory device last week. It looks like it won't > > > >work with FreeBSD 4.10-STABLE #1: Sun Jul 25 00:53:29 EDT 2004 > > > >Nov 30 22:03:05 laptop /kernel: umass0: LEXAR MEDIA JUMPDRIVE ELITE, rev > > > Can anyone recommend a USB thumb drive that they know works with > > FreeBSD 4.10 and 5.*? I'll return this one ASAP. > > I hope I don't sound like an advocate or anything, but is there a > chance that you can try this with, say, NetBSD? I've attached a > good number of devices to my FreeBSD systems that have required me > to patch under the hood, that when attached to a recent NetBSD, have > Just Worked. > > As the FreeBSD USB code is largely taken from NetBSD, but has over > time lagged somewhat behind, doing something like this can help you > determine if it should be relatively easy to fix FreeBSD. Also, I've > noticed that I experience problems that are very dependent on the > particular combination of hardware (like controllers) I use, so the > more juggling you can do, the better. > > Also, a handy thing you can do, if you don't already, is to build > your USB support as kernel modules, and then try out modules built > from more recent source if there have been recent commits, or try > building modules with code adapted from -current or even NetBSD to > see if that can solve the problem. My present kernel was built on > 08.Jun and I have no problems with more recent usb.ko and umass.ko > modules. You can build individual modules in your source tree by > `cd /path-to-src/src/sys/modules/usb && make -m /path-to-src/src/share/mk' > replacing modules/usb with modules/umass or whatever you want to build > (which writes in your source tree; I use unionfs to write these into > a source-hacks tree atop my virginal source tree) -- a timesaver on > my slow system that may help you if you feel like experimenting. > > Just a few hints, that I hope could be helpful, if not for you, then > hopefully for someone reading this sometime... I know David Maxwell (NetBSD security guy). The Ottawa BSD group is meeting this Thursday. I'll ask him to bring along his laptop.... ;) -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/