From owner-freebsd-current Thu Dec 5 8:18:55 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 246A937B401 for ; Thu, 5 Dec 2002 08:18:54 -0800 (PST) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F31143EA9 for ; Thu, 5 Dec 2002 08:18:53 -0800 (PST) (envelope-from darrylo@soco.agilent.com) Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 24A16DFD5; Thu, 5 Dec 2002 09:18:48 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by relcos1.cos.agilent.com (Postfix) with ESMTP id B033238D; Thu, 5 Dec 2002 09:18:47 -0700 (MST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_25184)/8.9.3 SMKit7.1.1_Agilent) with ESMTP id IAA16082; Thu, 5 Dec 2002 08:18:47 -0800 (PST) Message-Id: <200212051618.IAA16082@mina.soco.agilent.com> To: "Cliff L. Biffle" Cc: freebsd-current@FreeBSD.ORG Subject: Re: USB issues with Apollo KT133A mobo Reply-To: Darryl Okahata In-Reply-To: Your message of "Wed, 04 Dec 2002 21:09:26 MST." <200212042109.26410.cbiffle@safety.net> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Thu, 05 Dec 2002 08:18:46 -0800 From: Darryl Okahata 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 "Cliff L. Biffle" wrote: > 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! Many (most? all?) KT133A-based motherboards have a known issue with the PCI bus that often results in an IDE transfer problem. However, this was fixed (IIRC) in FreeBSD around the 4.5/4.6 timeframe (maybe earlier). [ Hmmm. You're probably seeing another problem with 4.7. ] > 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.) I don't know how FreeBSD handles it. Under Windows, a dialog box pops up when an overcurrent situation occurs, and the box contains a button that'll reset and re-enable the bus. > 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. Motherboards using the VIA KT133A chipset generally do not have a good reputation. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message