From owner-freebsd-usb@FreeBSD.ORG Mon Jan 14 22:57:14 2013 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E2B60F70 for ; Mon, 14 Jan 2013 22:57:14 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id B93FB178 for ; Mon, 14 Jan 2013 22:57:14 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id r0EMvDcP071832 for ; Mon, 14 Jan 2013 14:57:14 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <50F48D49.1060406@rawbw.com> Date: Mon, 14 Jan 2013 14:57:13 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: freebsd-usb@freebsd.org Subject: Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2013 22:57:15 -0000 I have Microsoft USB Explorer Touch mouse. It works fine, but when I plug out its (wireless) USB dongle, keyboard also stops working. Plugging the dongle back in enables the keyboard again. Plugging in some other USB mouse instead doesn't make keyboard work again. There were two keyboard devices defined before this mouse was first plugged in: kbd0 at atkbd0 and kbd1 at kbdmux0, see messages below. This mouse defines the new keyboard device kbd2 at ukbd0. When the dongle is plugged out, these two items (kbd2 at ukbd0) disappear from /dev, leaving all the same devices that existed before. Except keyboard becomes disfunctional. What could be a problem with this USB mouse? Looks like it interacts with the previous setup and leaves something modified when plugged out. Yuri PS: This of course isn't the major usability issue since, when plugged in, everything works. Nevertheless, I can't plug it out without losing the keyboard. ---messages (kbd related during boot)-- kbd1 at kbdmux0 <...skipped...> atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ---messages (plug out)--- Jan 14 14:30:59 eagle kernel: ugen1.2: at usbus1 (disconnected) Jan 14 14:30:59 eagle kernel: ukbd0: at uhub1, port 1, addr 2 (disconnected) Jan 14 14:30:59 eagle kernel: ums0: at uhub1, port 1, addr 2 (disconnected) Jan 14 14:30:59 eagle kernel: uhid0: at uhub1, port 1, addr 2 (disconnected) ---messages (plug in)--- Jan 14 14:31:09 eagle kernel: ugen1.2: at usbus1 Jan 14 14:31:09 eagle kernel: ukbd0: on usbus1 Jan 14 14:31:09 eagle kernel: kbd2 at ukbd0 Jan 14 14:31:09 eagle kernel: ums0: on usbus1 Jan 14 14:31:09 eagle kernel: ums0: 5 buttons and [XYZT] coordinates ID=26 Jan 14 14:31:09 eagle kernel: ums0: 0 buttons and [T] coordinates ID=0 Jan 14 14:31:09 eagle kernel: uhid0: on usbus1 $ ls -l /dev/*kbd* crw------- 1 root wheel 0, 57 Jan 4 11:50 /dev/atkbd0 lrwxr-xr-x 1 root wheel 6 Jan 4 11:50 /dev/kbd0 -> atkbd0 lrwxr-xr-x 1 root wheel 7 Jan 4 11:50 /dev/kbd1 -> kbdmux0 lrwxr-xr-x 1 root wheel 5 Jan 14 14:38 /dev/kbd2 -> ukbd0 crw------- 1 root wheel 0, 13 Jan 4 11:50 /dev/kbdmux0 crw------- 1 root wheel 0, 182 Jan 14 14:38 /dev/ukbd0