From owner-freebsd-current@FreeBSD.ORG Mon Feb 22 13:41:25 2010 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 69F0E10656C3 for ; Mon, 22 Feb 2010 13:41:25 +0000 (UTC) (envelope-from freebsd-current@chrishedley.com) Received: from smtp3.enta.net (smtp3.enta.net [87.127.246.178]) by mx1.freebsd.org (Postfix) with ESMTP id 1BB348FC0C for ; Mon, 22 Feb 2010 13:41:24 +0000 (UTC) Received: from mail.chrishedley.com (unknown [78.32.138.135]) by smtp3.enta.net (Postfix) with ESMTP id 9651DB57C5B for ; Mon, 22 Feb 2010 13:41:23 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id 0050770669 for ; Mon, 22 Feb 2010 13:41:22 +0000 (GMT) X-Virus-Scanned: amavisd-new at chrishedley.com Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id CgZM4MNF3Rho for ; Mon, 22 Feb 2010 13:41:18 +0000 (GMT) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.chrishedley.com (Postfix) with ESMTP id 58CC770646 for ; Mon, 22 Feb 2010 13:41:18 +0000 (GMT) Date: Mon, 22 Feb 2010 13:41:18 +0000 (GMT) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: freebsd-current@FreeBSD.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Subject: ums fails to initialise correctly 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: Mon, 22 Feb 2010 13:41:25 -0000 I wasn't sure whether this question was better asked on this list or the freebsd-usb one; but since I'm already subscribed here, I figured it was a good place to start. I'm having a lot of problems getting the ums (USB mouse) driver to initialise the mouse correctly. The only time it'll do so is if I physically unplug the mouse and reattach it; otherwise, it seems there's no way of getting it to initialise correctly. The mouse in question is a Logitech MX Revolution wireless model, though I'm not sure how relevant that is. Confusingly, the kernel messages are identical when it comes to seeing the mouse initially and reattaching it; perhaps significantly, if I plug it into my KVM switch (as opposed to one of the computer's own ports), it still fails to initialise if I switch it away from the FreeBSD system and back again: I have to do the physical detach/reattach process to get it to reinitialise. One possible lead is that once the mouse is working, it's fine when it's switched between the two FreeBSD systems, but switching to Windows and back renders it unusable again until I physically reattach it. I had wondered if it might be some hardware weirdness, but Windows (XP and 7) and Linux (on the same computer as FreeBSD) have no problems with it. The symptoms are just a lack of any data; otherwise everything seems identical between it working and not: the messages are the same, the /dev entry is being created correctly, devd starts up the moused process for me, but there's nothing. It's not a moused problem either, cat -v /dev/ums1 also reveals no data. I've tried pretty much every BIOS configuration I can think of, I've tried FreeBSD with both the ehci and ohci drivers, both compiled into the kernel and as modules; I've used usbconfig to see if there's any difference in configuration between the mouse working and not working, but nothing at all; variously loading and unloading ums, attempting to reset it or do a software power off and back on with usbconfig also won't bring it back to life. Meanwhile, the USB keyboard "just works", whatever I do. I spent much of the past couple of days Googling for suggestions and discovered it wasn't an uncommon problem, but could find no definite solution (other than suggestions to disable legacy support if it was enabled and vice versa - which didn't work). I did find similar queries going back to 2003, which makes me wonder if it's a problem without any obvious solution, but I thought I'd ask anyway. I'm using -current in its amd64 form on an old-ish dual-core AMD with an Asus motherboard, if that gives anybody any clues. But I figure I should get back to whether or not this is the right place to ask before I start posting reams of configuration and debugging information!