From owner-freebsd-current@FreeBSD.ORG Sun Oct 14 15:04:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3CB416A46E for ; Sun, 14 Oct 2007 15:04:12 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (lindfield.ch [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 6B97813C457 for ; Sun, 14 Oct 2007 15:04:12 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:63841 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Ih50k-000ERr-DZ for freebsd-current@freebsd.org; Sun, 14 Oct 2007 15:04:10 +0000 Message-ID: <47122FEA.6030400@conducive.net> Date: Sun, 14 Oct 2007 11:04:10 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <1192302906.1028.31.camel@xenon.stonehenge.sk> <471122EB.8090906@conducive.net> <200710141314.51326.hselasky@c2i.net> In-Reply-To: <200710141314.51326.hselasky@c2i.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: GigaByte GA-MA69VM USB+mouse problem [WAS: AMD690G/V issues with 7-current (sata, usb)] 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: Sun, 14 Oct 2007 15:04:12 -0000 Hans Petter Selasky wrote: > Hi Bill ! *trimming the 'history' - its in archives... >> tail -f /var/log/messages >> >> - you will be looking for the message announceing ums & usb load >> >> >> ls /dev/u* before unplugging, Again after re-plugging >> >> - you are looking for /dev/um0 and at least one /dev/usb(n) changing. > > Why should one of the /dev/usbX change ? As an 'opinion' - it should NOT. As an *observation* it/they DID. Specifically, loaded, then unloaded - reloaded on unplug-replug, accompanied by 'message' traffic so reporting. That could be: - mechanical environment: i.e. unreliable USB contacts, 'cold' MB or mouse PCB solder joint, cracked trace on MB or mouse PCB, et al... - electrical environment: flakey power supply, defective mouse PCB, bad cables, more current-drain than the USB port can handle. - firmware environment: firmware on mouse that shuts it OFF or awaits a wake-up initialization, USB port power-saving.. The fact that it works OK after unplug/replug says IF any of the above are involved, it is a transitory, perhaps related to boot-up power drain. - software environment: there are a great many bytes involved, BIOS and OS. That my dmesg.boot showed what was correct, and the one just posted did not, say the BIOS may be involved. The rarity of other similar reports HERE on the list suggest that whatever it is, it is probably not FreeBSD code. Hence my suggestion to see if the symptoms persisted with other mice and/or responded to BIOS setting changes. Coders cannot fix the 'external' world, and should not be asked to do so. >> AFAIK, um0 and usb(n) will load by default. > > What is "um0" ? You mean "ums0" ? > Yes, sorry. >> ..which you might just try, as that 'mad mouse' I experienced was a > > Can you explain what you mean by "mad mouse" ? > Cursor visible, but blinking, position jumping around at a high rate of refresh, responding marginally or not at all to movement of the mouse itself. Was once upon a time a common problem. Long ago fixed in the general case. > By the way there is a "man ums" command that might be interesting. > It was helpful along the way, yes. What was needed OTOH was a 'man CLUEBAT' applied to whomever coded the BIOS! Or a man 'FAULT ISOLATE' before jumping on coders at all.... ;-) Bill