From owner-freebsd-current@FreeBSD.ORG Fri Jan 13 21:21:42 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B85DD16A41F for ; Fri, 13 Jan 2006 21:21:42 +0000 (GMT) (envelope-from dreadpirate@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F18343D46 for ; Fri, 13 Jan 2006 21:21:41 +0000 (GMT) (envelope-from dreadpirate@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so731416wra for ; Fri, 13 Jan 2006 13:21:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=GPk03YStuqv5U2XJr8luHCHjtOSdyNLXIwt+cC23h/kbjy6G4zDbK2+ZT80eenvBB1eoo7dhPiEWP+RDhAVgS8Rj2ZADsTWoc/fkaqfcRBZH67VHHe+rYuRf4TyTF+Mvt4Iug1BtunA6i8anexeE1lfr5K61BNy1yHJ72q3TxLo= Received: by 10.65.124.13 with SMTP id b13mr2202420qbn; Fri, 13 Jan 2006 13:21:39 -0800 (PST) Received: by 10.65.138.16 with HTTP; Fri, 13 Jan 2006 13:21:39 -0800 (PST) Message-ID: Date: Fri, 13 Jan 2006 13:21:39 -0800 From: Dread Pirate Mal To: freebsd-current@freebsd.org In-Reply-To: <20060113204627.GA31171@tara.freenix.org> MIME-Version: 1.0 References: <20060113204627.GA31171@tara.freenix.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Abysmal performance on external usb drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2006 21:21:42 -0000 On 1/13/06, Ollivier Robert wrote: > > Please re-check then as if your controller support EHCI, it should appear > in the dmesg output. > > uhci0: port > 0xef40-0xef5f Hmm, it's not showing ehci at all. According to the docs the controller i= n the motherboard *is* usb 2.0, and the drive itself shows up as 2.0 if attached to another (windows) system. Andrew: pciconf shows the controller as uhci@, not as none@ So.. if it's misdetected, would it be remotely sane to try compiling sans e/ohci and just have the ehci driver there, or are they codependant ? Thanks for the replies, folks. If this controller is not supported I'll have to stamp my feet and look annoyed.