Re: Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
I found the cause of this problem. Due to the bug in Xorg it unloads the keyboard driver when it gets signal from hald that keyboard is disconnected, even though there is still another keyboard that is hooked up to kbdmux. Looks like Xorg code assumes that there can only be one keyboard and isn't aware of kbdmux. This was when hald is enabled (by default), and ServerFlags section in xorg.conf looked like this: Section ServerFlags Option AllowEmptyInput yes EndSection When I changed this section to this: Section ServerFlags Option AutoAddDevices False EndSection keyboard doesn't get affected, but mouse disappears for good when unplugged and plugged back, since (I guess) Xorg ignores ums0 device errors. I filed the following PRs with Xorg: https://bugs.freedesktop.org/show_bug.cgi?id=60069 https://bugs.freedesktop.org/show_bug.cgi?id=60070 Yuri ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
Al 30/01/2013 12:14, En/na Yuri ha escrit: I found the cause of this problem. Due to the bug in Xorg it unloads the keyboard driver when it gets signal from hald that keyboard is disconnected, even though there is still another keyboard that is hooked up to kbdmux. Looks like Xorg code assumes that there can only be one keyboard and isn't aware of kbdmux. This was when hald is enabled (by default), and ServerFlags section in xorg.conf looked like this: Section ServerFlags Option AllowEmptyInput yes EndSection When I changed this section to this: Section ServerFlags Option AutoAddDevices False EndSection keyboard doesn't get affected, but mouse disappears for good when unplugged and plugged back, since (I guess) Xorg ignores ums0 device errors. I filed the following PRs with Xorg: https://bugs.freedesktop.org/show_bug.cgi?id=60069 https://bugs.freedesktop.org/show_bug.cgi?id=60070 Yuri ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org Take a look at uhidd. I had the same problem a few time ago and because of it I switched to it. Perhaps will do fine for your setup. Regards, Gustau -- Salut i força, Gustau --- Prou top-posting : http://ca.wikipedia.org/wiki/Top-posting Stop top-posting : http://en.wikipedia.org/wiki/Posting_style O O O Gustau Pérez i Querol O O O Unitat de Gestió dels departaments O O O Matemàtica Aplicada IV i Enginyeria Telemàtica Universitat Politècnica de Catalunya Edifici C3 - Despatx S101-B UPC Campus Nord UPC C/ Jordi Girona, 1-3 08034 - Barcelona ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
On 01/14/2013 23:12, Hans Petter Selasky wrote:
The problem is that the Nano transceiver also provides a keyboard, which is
set as default.
See /etc/devd.conf and:
# When a USB keyboard arrives, attach it as the console keyboard.
attach 100 {
device-name ukbd0;
action /etc/rc.d/syscons setkeyboard /dev/ukbd0;
};
detach 100 {
device-name ukbd0;
action /etc/rc.d/syscons setkeyboard /dev/kbd0;
};
Which probably should be updated.
These directives look quite crude.
device-name ukbd0; should probably be device-name ukbd[0-9]+;
Also why kbd0 is taken as new default after ukbd disconnect?
Replacing kbd0 with kbd1 there didn't fix the problem though as I expected.
Following /etc/rc.d/sysconsit looks like in my case /etc/rc.d/syscons
setkeyboard /dev/ukbd0 doesn't do anything, since kbdcontrol -k ${kbd}
${kbddev} is only called when there is no kbdmux.
Here is another problem:
In the presence of mouse, this command doesn't show ukbd0 attached to
kbdmux:
# kbdcontrol -i /dev/ttyv0
kbd1:
kbdmux0, type:AT 101/102 (2)
Also it looks like the keyboard provided by mouse isn't working. Mouse
keyboard only has 2 buttons, by default Page-Up and Page-Down and these
events are never triggered.
Trying to attach it manually, following kbdcontrol(1), I get this error:
# kbdcontrol -a ukbd0 /dev/kbdmux0
su: /dev/kbdmux0: Device busy
Who is normally supposed to connect ukbd to kbdmux?
Yuri
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
Actually there probably still can be bug there. I have laptop, which lost internal keyboard after I plug and unplug my wireless KB+ Mouse. When wireless plugged both KBs are working. I'll try to reproduce it near days, will write back. -- Regards, Alexander Yerenkow ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
On 01/14/2013 23:12, Hans Petter Selasky wrote:
The problem is that the Nano transceiver also provides a keyboard, which is
set as default.
See /etc/devd.conf and:
# When a USB keyboard arrives, attach it as the console keyboard.
attach 100 {
device-name ukbd0;
action /etc/rc.d/syscons setkeyboard /dev/ukbd0;
};
detach 100 {
device-name ukbd0;
action /etc/rc.d/syscons setkeyboard /dev/kbd0;
};
Which probably should be updated.
Actually, disabling the above entries altogether also doesn't solve the
problem.
However, stopping devd daemon causes the problem to disappear. Even
though devd.conf even didn't have those ukbd directives.
I ran devd with -D flag, but log only shows the execution of 'syscons'
and 'moused' when the mouse is plugged/unplugged.
Removing moused entries also doesn't solve the problem.
So devd does something that triggers this problem, even though it
doesn't execute any commands. Looks like a mystery.
Yuri
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
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: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ---messages (plug out)--- Jan 14 14:30:59 eagle kernel: ugen1.2: Microsoft 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: Microsoft at usbus1 Jan 14 14:31:09 eagle kernel: ukbd0: Microsoft Microsoft Nano Transceiver v1.0, class 0/0, rev 2.00/6.74, addr 2 on usbus1 Jan 14 14:31:09 eagle kernel: kbd2 at ukbd0 Jan 14 14:31:09 eagle kernel: ums0: Microsoft Microsoft Nano Transceiver v1.0, class 0/0, rev 2.00/6.74, addr 2 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: Microsoft Microsoft Nano Transceiver v1.0, class 0/0, rev 2.00/6.74, addr 2 on usbus1 $ ls -l /dev/*kbd* crw--- 1 root wheel0, 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 wheel0, 13 Jan 4 11:50 /dev/kbdmux0 crw--- 1 root wheel0, 182 Jan 14 14:38 /dev/ukbd0 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
On Monday 14 January 2013 23:57:13 Yuri wrote:
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: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0
atkbd0: AT Keyboard irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
---messages (plug out)---
Jan 14 14:30:59 eagle kernel: ugen1.2: Microsoft 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: Microsoft at usbus1
Jan 14 14:31:09 eagle kernel: ukbd0: Microsoft Microsoft Nano
Transceiver v1.0, class 0/0, rev 2.00/6.74, addr 2 on usbus1
Jan 14 14:31:09 eagle kernel: kbd2 at ukbd0
Jan 14 14:31:09 eagle kernel: ums0: Microsoft Microsoft Nano
Transceiver v1.0, class 0/0, rev 2.00/6.74, addr 2 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: Microsoft Microsoft Nano
Transceiver v1.0, class 0/0, rev 2.00/6.74, addr 2 on usbus1
$ ls -l /dev/*kbd*
crw--- 1 root wheel0, 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 wheel0, 13 Jan 4 11:50 /dev/kbdmux0
crw--- 1 root wheel0, 182 Jan 14 14:38 /dev/ukbd0
The problem is that the Nano transceiver also provides a keyboard, which is
set as default.
See /etc/devd.conf and:
# When a USB keyboard arrives, attach it as the console keyboard.
attach 100 {
device-name ukbd0;
action /etc/rc.d/syscons setkeyboard /dev/ukbd0;
};
detach 100 {
device-name ukbd0;
action /etc/rc.d/syscons setkeyboard /dev/kbd0;
};
Which probably should be updated.
--HPS
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
