From owner-freebsd-current@FreeBSD.ORG Sat Oct 13 17:11:34 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 9FA8B16A41B for ; Sat, 13 Oct 2007 17:11:34 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (conducive.net [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 5F63613C46E for ; Sat, 13 Oct 2007 17:11:33 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:64641 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IgkWS-0008uE-GF for freebsd-current@freebsd.org; Sat, 13 Oct 2007 17:11:32 +0000 Message-ID: <4710FC44.60103@conducive.net> Date: Sat, 13 Oct 2007 13:11:32 -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: <1192219511.13906.56.camel@xenon.stonehenge.sk> <471061A6.9070909@conducive.org> <200710131712.43265.hselasky@c2i.net> In-Reply-To: <200710131712.43265.hselasky@c2i.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 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: Sat, 13 Oct 2007 17:11:34 -0000 Hans Petter Selasky wrote: > On Saturday 13 October 2007, W B Hacker wrote: >> Michal Varga wrote: >>> Yesterday I bought an AMD690-based motherboard for a 7-current desktop - >>> >>> http://www.gigabyte.us/Products/Motherboard/Products_Spec.aspx?ClassValue >>> =Motherboard&ProductID=2437&ProductName=GA-MA69VM-S2 >> *Snip* >> >>> USB: >>> Second issue is with USB, the initialization fails every time when there >>> is mouse plugged in prior to FreeBSD boot (but not if the mouse is >>> plugged later). >> Similar. ASUS P5K, GigaByte G33-DS3R. >> >> Option the USB mouse support OFF in the BIOS. >> >> Otherwise, though detected, it is *ALSO* presumed to be 'in use', since the >> BIOS deosn't just 'enable' it - it actually starts it, and before the OS >> boots. >> >> If NOT claimed by the BIOS, FreeBSD will find and use it from the defaults >> in /etc/rc. No need to even bother with an /etc/rc.conf entry. >> >> Xorg (if you use it) will generally be au fait with that, even with the >> mouse active in a CLI session before you startx or a wm. >> >> The OS it doing as it should do here - honoring the pre-existing resource >> claim. > > Are you sure about that? Certainly sounds 'contrarian' ...but that's what worked. Spent a day or two tracking it, watching /dev/ums0 & the usb devs get loaded, then unloaded, forcing it back in with various /boot/loader.conf and/or manual steps, having the mouse ignored OR go mad.. Commenting in/out default mouse in /etc/rc and trying various manual flags in /etc/rc.conf was no help. Not invoking/not invoking ums in /boot/loader.conf Yet autoload just fine IF unplugged and re-plugged. Tailed /var/log/messages and saw just the right stuff go by. > > I thought that the FreeBSD USB HC drivers always took away control from the > BIOS when the USB drivers where loaded. > It appears to try to do that. 'Always' is subject to a factory recall. dmesg.boot is exactly what one would expect, even to the make & model of each of USB meese tried (Logitech, Kensington, Atech). System would load ums, then unload it. ums0 would appear in /dev, then *disappear*. > Michal Varga: Do you have USB in the kernel or are you loading the USB > modules ? > > --HPS > See above. The BIOS issue has bitten both ways - and more. Lie to it and see if that fixes the problem. HTH, Bill _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >