From owner-freebsd-current@FreeBSD.ORG Sun Oct 14 18:45:29 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 5A24016A417 for ; Sun, 14 Oct 2007 18:45:29 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.188]) by mx1.freebsd.org (Postfix) with ESMTP id C4D8A13C448 for ; Sun, 14 Oct 2007 18:45:28 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so1263945mue for ; Sun, 14 Oct 2007 11:45:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:organization:date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=EzvjUdqf5vKrvzLPA5D+J0aIfDXxlFvJ3r+UqCNGQRI=; b=aR2aEMM3yDpgL+xkm6+8khAtzvAMfCeRislSV8w4rVrljkp/FS/8N684HhevMy8hC4et8gQDZF5kkc99JByGvV67mVpvHwvzDG1PSxZBCyOULvBPbTwODLZG6beUJoqrXJDhHGspgbhua73hSK3U3jdLomsj7vYqnPnXe8WJktA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:subject:from:to:cc:in-reply-to:references:content-type:organization:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=lv+y5djlvWlJsxWDPCnVuKddRCuAlW94beMAcwtLoldEaUxCUp7UAUYdNYAj6nFQkEedtJJPk7oXoiqCcGMVch8Q+e/tUhjdq1c/ikSE4ANaGrDLCSSPPILUhzVkYAOK35G611oVuxzx8nIn3nK7aYHWYe5i+xuuNKtyaNd0XUA= Received: by 10.86.86.12 with SMTP id j12mr555466fgb.1192387526921; Sun, 14 Oct 2007 11:45:26 -0700 (PDT) Received: from ?10.0.100.2? ( [89.176.79.57]) by mx.google.com with ESMTPS id p9sm6285786fkb.2007.10.14.11.45.25 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 14 Oct 2007 11:45:25 -0700 (PDT) From: Michal Varga To: =?UTF-8?Q?=E9=9F=93=E5=AE=B6=E6=A8=99?= Bill Hacker In-Reply-To: <47125798.8040809@conducive.net> References: <1192302906.1028.31.camel@xenon.stonehenge.sk> <471122EB.8090906@conducive.net> <200710141314.51326.hselasky@c2i.net> <47122FEA.6030400@conducive.net> <1192376452.1183.26.camel@xenon.stonehenge.sk> <47125798.8040809@conducive.net> Content-Type: text/plain; charset=UTF-8 Organization: Stonehenge Date: Sun, 14 Oct 2007 20:45:22 +0200 Message-Id: <1192387522.1100.33.camel@xenon.stonehenge.sk> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: GigaByte GA-MA69VM USB+mouse problem 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 18:45:29 -0000 On Sun, 2007-10-14 at 13:53 -0400, 韓家標 Bill Hacker wrote: > Keep on 'thinking opposite', then. > > I'll kick back and have a Bushmills, neat. > > Testing of 4 different MB, 3 USB and one PS2 mice with 6 flavors of FreeBSD, and > one of DragonFlyBSD turned up: > > Option USB mouse support ON in BIOS, waste two days. > > Option USB mouse support OFF in BIOS, mouse responds as it should. > I already said that I have "USB mouse support = OFF" in BIOS. It is obviously one of the first things one tries to toggle if something like mouse doesn't work. > > Two facts: > > 1. This is a really generic low budget A4Tech mouse, I buy this single > > model for about 5 years, because I love their design (they don't have > > any) and their functions (they don't have any). I've had them attached > > everywhere, from Pentium II, PIII, P4, Athlon, AM2 boards and this is > > the first time the mouse doesn't work. If there was something really > > special about this particular model, I'd be aware of that for some years > > already.. > > > > ...but as you've just enumerated - the MB, its 'bridge' and USB chipset has > changed, and the *BIOS* has changed.... > But not the mouse (please read again what the point was about). And I'd really like to test this motherboard with a different mouse model, but I don't have any other nearby, just these (and a bunch of PS/2 that are of no use here) and they always worked perfectly. So at least until tomorrow, let's assume that the mouse is not a problem here, as it is just a plain simple generic USB mouse, nothing more. > > 2. Windows 2000 can initialize the mouse without any problems (and with > > no specific drivers). FreeBSD can do that too, *after* the mouse is > > plugged in when the OS is already running. I wouldn't argue if this is > > GigaByte BIOS's fault or not, or if FreeBSD should do something more (or > > less) during the initialization, this is not my field of expertise. But > > Clearly so. > > Windows is an entirely different environment, and not 'of interest'. > > DragonFly was close enough to be of interest. > How it is that a different operating system running on this motherboard that doesn't show any symptoms with the mouse is "not of interest"? If I said "Linux" or "Atari TOS", would that be ok, but because it works with "Winbl0w$$$", such information is automatically of no interest? Well, what a twist. > The ums and usb are kldload/unload 'able modules. > I've been banging on that very approach.. > > Didn't help. > > BIOS setting USB kbd DISABLE, USB mouse DISABLE, all other USB ENABLE did. > > To be fair, your 'thinking opposite' has generated a lot less of a > global-warming carbon footprint than all these machines I have running and the > A/C to cool them. > > So keep at it... > > OTOH, my mouse JF works.... > Ok, what should I do to convince you that I DO have USB/kbd/mouse/support disabled in BIOS? Should I take a picture with a camera? Dump you raw CMOS data? Buy you a ticket to come look at it? Really, I disabled it the next reboot that I noticed my mouse isn't working. I tried all combinations, tried to disable USB 2.0, legacy support, flashed BIOS to the latest version, it has no effect on the mouse problem. What I need are some ideas or pointers to what should I try *next*, and you are not very helpful trying to convince me that I don't know how to operate BIOS setup. If disabling USB mouse support in BIOS helped in your case, I'm happy for you, but I have a different motherboard and this approach clearly doesn't work. So if you, by a chance, have any other ideas, I'll be more than happy to hear them. m.