<div>I think it is not a roblem of KDE. A mouse problem started with update of Xorg. Search the old post and you will something useful I have the same problem on FreeBSD 9.0-release.<br></div><div><br></div><br><div class="gmail_quote">
On Sun, Jun 3, 2012 at 10:06 AM, Jerry <span dir="ltr"><<a href="mailto:jerry@seibercom.net" target="_blank">jerry@seibercom.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
After recently updating to the "8.3" version and updating KDE to the<br>
latest version in the ports system, I have had nothing but problems<br>
getting the mouse and occasionally the keyboard to load. Both work fine<br>
when FreeBSD starts up; however, when starting KDE the mouse has a 50%<br>
chance of not working. The keyboard error is around 10%. This is a<br>
Microsoft® Wireless Comfort Keyboard 5000 and Microsoft® Wireless Mouse<br>
5000<br>
<br>
SYSTEM: FreeBSD 8.3-STABLE amd64<br>
<br>
Excerpts form what I believe to be the pertinent data from the Xorg log<br>
files. The complete logs are available if required.<br>
<br>
<When it works><br>
<br>
(II) config/hal: Adding input device Microsoft 2.4GHz Transceiver v7.0<br>
(II) LoadModule: "mouse"<br>
(II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so<br>
(II) Module mouse: vendor="X.Org Foundation"<br>
compiled for 1.7.7, module version = 1.7.1<br>
Module class: X.Org XInput Driver<br>
ABI class: X.Org XInput driver, version 7.0<br>
(WW) Microsoft 2.4GHz Transceiver v7.0: No Device specified, looking for one...<br>
(II) Microsoft 2.4GHz Transceiver v7.0: Setting Device option to "/dev/sysmouse"<br>
(--) Microsoft 2.4GHz Transceiver v7.0: Device: "/dev/sysmouse"<br>
(==) Microsoft 2.4GHz Transceiver v7.0: Protocol: "Auto"<br>
(**) Microsoft 2.4GHz Transceiver v7.0: always reports core events<br>
(**) Option "Device" "/dev/sysmouse"<br>
(==) Microsoft 2.4GHz Transceiver v7.0: Emulate3Buttons, Emulate3Timeout: 50<br>
(**) Microsoft 2.4GHz Transceiver v7.0: ZAxisMapping: buttons 4 and 5<br>
(**) Microsoft 2.4GHz Transceiver v7.0: Buttons: 9<br>
(II) XINPUT: Adding extended input device "Microsoft 2.4GHz Transceiver v7.0" (type: MOUSE)<br>
(**) Microsoft 2.4GHz Transceiver v7.0: (accel) keeping acceleration scheme 1<br>
(**) Microsoft 2.4GHz Transceiver v7.0: (accel) acceleration profile 0<br>
(II) Microsoft 2.4GHz Transceiver v7.0: SetupAuto: hw.iftype is 4, hw.model is 0<br>
(II) Microsoft 2.4GHz Transceiver v7.0: SetupAuto: protocol is SysMouse<br>
(II) config/hal: Adding input device Microsoft 2.4GHz Transceiver v7.0<br>
<br>
<When it doesn't><br>
<br>
(II) config/hal: Adding input device Microsoft 2.4GHz Transceiver v7.0<br>
(II) LoadModule: "mouse"<br>
(II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so<br>
(II) Module mouse: vendor="X.Org Foundation"<br>
compiled for 1.7.7, module version = 1.7.1<br>
Module class: X.Org XInput Driver<br>
ABI class: X.Org XInput driver, version 7.0<br>
(WW) Microsoft 2.4GHz Transceiver v7.0: No Device specified, looking for one...<br>
(II) Microsoft 2.4GHz Transceiver v7.0: Setting Device option to "/dev/ums0"<br>
(--) Microsoft 2.4GHz Transceiver v7.0: Device: "/dev/ums0"<br>
(==) Microsoft 2.4GHz Transceiver v7.0: Protocol: "Auto"<br>
(**) Microsoft 2.4GHz Transceiver v7.0: always reports core events<br>
(**) Option "Device" "/dev/ums0"<br>
(EE) xf86OpenSerial: Cannot open device /dev/ums0<br>
Device busy.<br>
(EE) Microsoft 2.4GHz Transceiver v7.0: cannot open input device<br>
(II) UnloadModule: "mouse"<br>
(EE) PreInit returned NULL for "Microsoft 2.4GHz Transceiver v7.0"<br>
(EE) config/hal: NewInputDeviceRequest failed (8)<br>
<br>
It appears to get confused between "/dev/sysmouse" and "/dev/ums0". I<br>
have used a Logitech board and mouse also but the problem still exists.<br>
I installed new batteries into both the keyboard and mouse and made sure<br>
the USB receiver was properly plugged in. This setup has worked since<br>
FreeBSD 8.0 with out a problem until now.<br>
<br>
When the keyboard craps out I have to either access the machine from<br>
another terminal or pull the plug.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Jerry ♔<br>
<br>
Disclaimer: off-list followups get on-list replies or get ignored.<br>
Please do not ignore the Reply-To header.<br>
__________________________________________________________________<br>
<br>
_______________________________________________<br>
kde-freebsd mailing list<br>
<a href="mailto:kde-freebsd@kde.org">kde-freebsd@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-freebsd" target="_blank">https://mail.kde.org/mailman/listinfo/kde-freebsd</a><br>
See also <a href="http://freebsd.kde.org/" target="_blank">http://freebsd.kde.org/</a> for latest information<br>
</font></span></blockquote></div><br>