From owner-freebsd-questions@FreeBSD.ORG Mon Jan 3 09:53:24 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D3C916A4CE for ; Mon, 3 Jan 2005 09:53:24 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 15FEB43D39 for ; Mon, 3 Jan 2005 09:53:23 +0000 (GMT) (envelope-from ph.schulz@gmx.de) Received: (qmail invoked by alias); 03 Jan 2005 09:53:21 -0000 Received: from dsl-082-082-078-080.arcor-ip.net (EHLO [192.168.1.5]) (82.82.78.80) by mail.gmx.net (mp025) with SMTP; 03 Jan 2005 10:53:21 +0100 X-Authenticated: #1954550 Message-ID: <41D915FF.1090707@gmx.de> Date: Mon, 03 Jan 2005 10:53:03 +0100 From: Phil Schulz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041121 X-Accept-Language: de, en-us, en MIME-Version: 1.0 To: Trey Sizemore References: <1104696792.806.6.camel@localhost> <1104715334.806.11.camel@localhost> In-Reply-To: <1104715334.806.11.camel@localhost> X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 cc: freebsd-questions@freebsd.org Subject: Re: Why might my USB devices *not* be detected? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2005 09:53:24 -0000 On 01/03/05 02:22, Trey Sizemore wrote: > On Sun, 2005-01-02 at 15:13 -0500, Trey Sizemore wrote: > > > Sorry for replying to myself, but wanted to fix the subject (less > confusing). Might this have something to do with the usbd.conf file > (I've not changed mine, but perhaps something to be added?). > What happens if you plug in the device(s) before you boot the system? On my laptop, USB devices were only detected when the system booted, not when it was already up. That issue was solved by compiling ehci into the kernel. If that doesn't help, you might want to show your dmesg. Regards, Phil.