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