Date: Sat, 14 Jan 2006 09:58:57 +1100 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Dread Pirate Mal <dreadpirate@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Abysmal performance on external usb drive Message-ID: <20060113225857.GL13244@cirb503493.alcatel.com.au> In-Reply-To: <a6d45d040601131321t121ef7f2g5a7d01c2dbcfc83f@mail.gmail.com> References: <a6d45d040601131234n4c053225wa75cba6063c71def@mail.gmail.com> <20060113204627.GA31171@tara.freenix.org> <a6d45d040601131321t121ef7f2g5a7d01c2dbcfc83f@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2006-Jan-13 13:21:39 -0800, Dread Pirate Mal wrote: >On 1/13/06, Ollivier Robert <roberto@keltia.freenix.fr> wrote: >> >> Please re-check then as if your controller support EHCI, it should appear >> in the dmesg output. >> > uhci0: <Intel 82801BA/BAM (ICH2) USB controller USB-A> port >> 0xef40-0xef5f > > Hmm, it's not showing ehci at all. According to the docs the >controller in 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 ? AFAIK, you need both. The USB1 and USB2 controllers are normally distinct PCI devices (I think this is required). Possibly your USB2 controller has an ID that is not recognized by ehci. You might like to post the output of "pciconf -lv". -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060113225857.GL13244>