From owner-freebsd-current Wed Dec 4 20: 9:31 2002 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 B3A5637B404 for ; Wed, 4 Dec 2002 20:09:28 -0800 (PST) Received: from ns3.safety.net (ns3.safety.net [216.40.201.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D77043E4A for ; Wed, 4 Dec 2002 20:09:28 -0800 (PST) (envelope-from cbiffle@safety.net) Received: from localhost (rs.rackshack.net.safety.net [216.40.201.32]) by ns3.safety.net (8.10.2/8.10.2) with ESMTP id gB549QO16881; Wed, 4 Dec 2002 21:09:26 -0700 From: "Cliff L. Biffle" To: Darryl Okahata Subject: Re: USB issues with Apollo KT133A mobo Date: Wed, 4 Dec 2002 21:09:26 -0700 User-Agent: KMail/1.5 Cc: freebsd-current@FreeBSD.ORG References: <200212050011.QAA29605@mina.soco.agilent.com> In-Reply-To: <200212050011.QAA29605@mina.soco.agilent.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200212042109.26410.cbiffle@safety.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday 04 December 2002 05:11 pm, Darryl Okahata wrote: > 1. IIRC, USB ports on KT133A motherboards were buggy (???). Could be. The ATA controller was also flaking out under 4.7, but is solid as a rock under 5.0-DP2, which is why I'm sticking with it despite other potential bugs. I can burn CDs now! > 2. Drawing too much power from the USB ports can cause the ports to shut > down. The absolute maximum limit is 500mA, which isn't much (some > 2.5" USB hard disks can draw MUCH more, which violates the spec, and > sometimes works, and sometimes doesn't). The behavior persists with just an optical USB mouse, which can't possibly be sucking more than a few dozen mills. (I hope.) In the discussion link you sent me, they discuss the controller disabling the port due to excessive current draw...would it re-enable the port when I simply un/replug the mouse? Normally I'd expect that to require a reboot. (The mouse does come back when I remove it and reinsert it, and generally X doesn't even notice.) The KT133 discussion suggests it's a hardware problem, which wouldn't surprise me...this particular mobo is a very early Athlon board, and the chipset may be buggy. -Cliff L. Biffle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message