From owner-freebsd-current@FreeBSD.ORG Wed Mar 18 05:35:08 2009 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 EE3B6106566B for ; Wed, 18 Mar 2009 05:35:07 +0000 (UTC) (envelope-from mrossi@swin.edu.au) Received: from gpo7.cc.swin.edu.au (gpo7.cc.swin.edu.au [136.186.1.36]) by mx1.freebsd.org (Postfix) with ESMTP id 6D7118FC19 for ; Wed, 18 Mar 2009 05:35:07 +0000 (UTC) (envelope-from mrossi@swin.edu.au) Received: from mrossi.caia.swin.edu.au (mrossi.caia.swin.edu.au [136.186.229.109]) by gpo7.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id n2I5GKmM004970 for ; Wed, 18 Mar 2009 16:16:22 +1100 Message-ID: <49C083A4.5020608@swin.edu.au> Date: Wed, 18 Mar 2009 16:16:20 +1100 From: Mattia Rossi User-Agent: Thunderbird 2.0.0.19 (X11/20090309) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: USB2, mouse and X 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: Wed, 18 Mar 2009 05:35:08 -0000 Hi, I've seen that there are a lot of issues with mice and the new USB2 stack, but as my problem is still not resolved with the current kernel, i think it's time to report my problem: My mouse (or maybe keyboard?) issues regard only the X window system (I tried fluxbox and KDE4). Mouse and keyboard are USB, attached via a USB hub (integrated in my monitor). They both work without flaws in the console, but it's a pain to write text in different windows in X. The typed text just doesn't get displayed some times, unless the mouse cursor is moved. Sometimes after typing some text, and moving the mouse afterwards, the text gets written, but letters will be grouped together and look like this: this iss whahatppen (this is what happens) I guess it's related to the moused problems (it's a HP branded Logitech mouse), so here are the dumps for the mouse and keyboard, dmesg output and uname output: FreeBSD 8.0-CURRENT #11 r189933M: Wed Mar 18 10:34:42 EST 2009 i386 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 12Mbps Full Speed USB v1.0 usbus6: 480Mbps High Speed USB v2.0 ad0: 152627MB at ata0-master SATA300 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 ugen6.1: at usbus6 uhub6: on usbus6 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub4: 2 ports with 2 removable, self powered uhub5: 2 ports with 2 removable, self powered uhub2: 4 ports with 4 removable, self powered uhub6: 6 ports with 6 removable, self powered ugen6.2: at usbus6 uhub7: on usbus6 uhub7: 2 ports with 1 removable, self powered ugen6.3: at usbus6 ukbd0: on usbus6 kbd2 at ukbd0 ugen6.4: at usbus6 ums0: on usbus6 ums0: 3 buttons and [XYZ] coordinates Keyboard: usbconfig -u 6 -a 3 do_request 0x81 0x06 0x2200 1 0x100 REQUEST = <0x06 0x0c 0x00 0x09 0x01 0xa1 0x01 0x85 0x01 0x25 0x01 0x15 0x00 0x75 0x01 0x0a 0x8a 0x01 0x0a 0x11 0x00 0x0a 0x12 0x00 0x0a 0x23 0x02 0x0a 0x21 0x02 0x0a 0x13 0x00 0x0a 0x14 0x00 0x0a 0x15 0x00 0x95 0x08 0x81 0x06 0x81 0x01 0x81 0x01 0x81 0x01 0x81 0x01 0xc0 0x06 0x00 0xff 0x09 0x01 0xa1 0x01 0x85 0x02 0x25 0x01 0x15 0x00 0x75 0x01 0x0a 0x8a 0x01 0x0a 0x25 0x02 0x0a 0x24 0x02 0x0a 0x23 0x02 0x0a 0x21 0x02 0x0a 0x2a 0x02 0x0a0x27 0x02 0x0a 0x26 0x02 0x95 0x08 0x81 0x06 0x81 0x01 0x81 0x01 0x81 0x01 0x81 0x01 0x15 0x00 0x27 0xff 0xff 0xff 0x7f 0x09 0x30 0x75 0x20 0x95 0x01 0xb1 0x02 0xc0><%u#!%u%$#!*'&'0u > usbconfig -u 6 -a 3 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = Mouse: usbconfig -u 6 -a 4 do_request 0x81 0x06 0x2200 1 0x100 REQUEST = <0x05 0x01 0x09 0x02 0xa1 0x01 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x03 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x03 0x81 0x02 0x75 0x05 0x95 0x01 0x81 0x01 0x05 0x01 0x09 0x30 0x09 0x31 0x09 0x38 0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x03 0x81 0x06 0xc0 0xc0><)%uu018%u> usbconfig -u 6 -a 4 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = And that's the dmesg output for the mouse if it's attached to one of the front ports of the PC: ums0: at uhub7, port 2, addr 4 (disconnected) ugen6.4: at usbus6 (disconnected) ugen1.2: at usbus1 ums0: on usbus1 ums0: 3 buttons and [XYZ] coordinates And the dumps (which don't change - just to eliminate the USB hub as problem source): usbconfig -u 1 -a 2 do_request 0x81 0x06 0x2200 1 0x100 REQUEST = <0x05 0x01 0x09 0x02 0xa1 0x01 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x03 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x03 0x81 0x02 0x75 0x05 0x95 0x01 0x81 0x01 0x05 0x01 0x09 0x30 0x09 0x31 0x09 0x38 0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x03 0x81 0x06 0xc0 0xc0><)%uu018%u> usbconfig -u 1 -a 2 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = <0x05 0x01 0x09 0x02 0xa1 0x01 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x03 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x03 0x81 0x02 0x75 0x05 0x95 0x01 0x81 0x01 0x05 0x01 0x09 0x30 0x09 0x31 0x09 0x38 0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x03 0x81 0x06 0xc0 0xc0><)%uu018%u> Additional observation: After unplugging the mouse from the hub and plugging it into the front USB connector, I need to switch to a console from X to have the moused (I suppose) kick in, in order to be able to use the mouse again. When I switch back to X it works, otherwise it won't. (Probably because it wants me to move the mouse before it continues operating.. or some crap like that..) X is xorg-7.4 with server xorg-server-1.5.3_7 KDE4 is the latest 4.2.1 from today. Completely rebuilt. moused is actually disabled/missing from rc.conf and the X server is started with "AllowEmptyInput" "off" as described by the last UPDATING information in /usr/ports and/or /usr/src. Would be nice if this issue (which persists since the introduction of USB2) could be solved. Thanks Mat