Microsoft Microsoft® 2.4GHz Transceiver v6.0

Hi!
I’ve got a microsoft wireless keyboard + mouse… it’s not good, i know, but I have it now.
Problem: The mouse wheel is hyper sensitive in KDE. Please help to correct it in OpenSUSE 11.4.
Thanks.
Nick

On 03/12/2011 11:36 AM, nickwest wrote:
>
> Hi!
> I’ve got a microsoft wireless keyboard + mouse… it’s not good, i
> know, but I have it now.
> Problem: The mouse wheel is hyper sensitive in KDE. Please help to
> correct it in OpenSUSE 11.4.
> Thanks.
> Nick
>
>
have you tried adjusting it?

go Personal Settings - Configure Desktop > Hardware > Input Devices >
Mouse > Advanced and next to “Mouse wheel scrolls by” spin down from
whatever it is now, to something less…maybe a LOT less…

does that help?


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.1.8, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11

Yes, I’ve set it to “1 string”. Without a result. This is my Xorg log. Strange, X not found a mouse, but found a two keyboards. Or i’ve made mistake?

1720.114]
X.Org X Server 1.9.3
Release Date: 2010-12-13
1720.114] X Protocol Version 11, Revision 0
1720.114] Build Operating System: openSUSE SUSE LINUX
1720.114] Current Operating System: Linux STRELKA 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10 +0100 x86_64
1720.114] Kernel command line: root=/dev/disk/by-id/ata-ST31000528AS_9VP8JDKC-part6 resume=/dev/disk/by-id/ata-ST31000528AS_9VP8JDKC-part5 splash=silent quiet showopts vga=0x31a
1720.114] Build Date: 22 February 2011 10:08:09PM

1720.633] (II) AIGLX: Loaded and initialized OpenGL driver(II) GLX: Initialized DRI GL provider for screen 0
1720.662] (II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-8AA988DD479FAABEC4FC3CCCF4CC29B4948840B4.xkm
1720.667] (II) config/udev: Adding input device Power Button (/dev/input/event5)
1720.667] () Power Button: Applying InputClass “evdev keyboard catchall”
1720.667] (
) Power Button: Applying InputClass “LocalKeyboard”
1720.667] (II) LoadModule: “evdev”
1720.667] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
1720.667] (II) Module evdev: vendor=“X.Org Foundation”
1720.667] compiled for 1.9.3, module version = 2.6.0
1720.667] Module class: X.Org XInput Driver
1720.667] ABI class: X.Org XInput driver, version 11.0
1720.667] () Power Button: always reports core events
1720.667] (
) Power Button: Device: “/dev/input/event5”
1720.673] (–) Power Button: Found keys
1720.673] (II) Power Button: Configuring as keyboard
1720.673] (II) XINPUT: Adding extended input device “Power Button” (type: KEYBOARD)
1720.673] () Option “xkb_rules” “evdev”
1720.673] (
) Option “xkb_model” “evdev”
1720.673] () Option “xkb_layout” “us,ru”
1720.673] (
) Option “xkb_variant” “,winkeys”
1720.673] () Option “xkb_options” “grp:ctrl_shift_toggle,grp_led:scroll”
1720.674] (II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-ADB0C3A7981A9F42535006721CEF11DFC2062FEC.xkm
1720.676] (II) config/udev: Adding input device Power Button (/dev/input/event4)
1720.676] (
) Power Button: Applying InputClass “evdev keyboard catchall”
1720.676] () Power Button: Applying InputClass “LocalKeyboard”
1720.676] (
) Power Button: always reports core events
1720.676] () Power Button: Device: “/dev/input/event4”
1720.681] (–) Power Button: Found keys
1720.681] (II) Power Button: Configuring as keyboard
1720.681] (II) XINPUT: Adding extended input device “Power Button” (type: KEYBOARD)
1720.681] (
) Option “xkb_rules” “evdev”
1720.681] () Option “xkb_model” “evdev”
1720.681] (
) Option “xkb_layout” “us,ru”
1720.681] () Option “xkb_variant” “,winkeys”
1720.681] (
) Option “xkb_options” “grp:ctrl_shift_toggle,grp_led:scroll”
1720.685] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v6.0 (/dev/input/event0)
1720.685] () Microsoft Microsoft® 2.4GHz Transceiver v6.0: Applying InputClass “evdev keyboard catchall”
1720.685] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Applying InputClass “LocalKeyboard”
1720.685] () Microsoft Microsoft® 2.4GHz Transceiver v6.0: always reports core events
1720.685] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Device: “/dev/input/event0”
1720.693] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found keys
1720.693] (II) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Configuring as keyboard
1720.693] (II) XINPUT: Adding extended input device “Microsoft Microsoft® 2.4GHz Transceiver v6.0” (type: KEYBOARD)
1720.693] () Option “xkb_rules” “evdev”
1720.693] (
) Option “xkb_model” “evdev”
1720.693] () Option “xkb_layout” “us,ru”
1720.693] (
) Option “xkb_variant” “,winkeys”
1720.693] () Option “xkb_options” “grp:ctrl_shift_toggle,grp_led:scroll”
1720.693] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v6.0 (/dev/input/event1)
1720.693] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Applying InputClass “evdev pointer catchall”
1720.693] () Microsoft Microsoft® 2.4GHz Transceiver v6.0: Applying InputClass “evdev keyboard catchall”
1720.693] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Applying InputClass “LocalKeyboard”
1720.693] () Microsoft Microsoft® 2.4GHz Transceiver v6.0: always reports core events
1720.693] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Device: “/dev/input/event1”
1720.701] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found 9 mouse buttons
1720.701] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found scroll wheel(s)
1720.701] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found relative axes
1720.701] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found x and y relative axes
1720.701] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found absolute axes
1720.701] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found keys
1720.701] (II) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Configuring as mouse
1720.701] (II) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Configuring as keyboard
1720.701] (II) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Adding scrollwheel support
1720.701] () Microsoft Microsoft® 2.4GHz Transceiver v6.0: YAxisMapping: buttons 4 and 5
1720.701] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
1720.701] (II) XINPUT: Adding extended input device “Microsoft Microsoft® 2.4GHz Transceiver v6.0” (type: KEYBOARD)
1720.701] () Option “xkb_rules” “evdev”
1720.701] (
) Option “xkb_model” “evdev”
1720.701] () Option “xkb_layout” “us,ru”
1720.701] (
) Option “xkb_variant” “,winkeys”
1720.701] () Option “xkb_options” “grp:ctrl_shift_toggle,grp_led:scroll”
1720.701] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: (accel) keeping acceleration scheme 1
1720.701] () Microsoft Microsoft® 2.4GHz Transceiver v6.0: (accel) acceleration profile 0
1720.701] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: (accel) acceleration factor: 2.000
1720.701] () Microsoft Microsoft® 2.4GHz Transceiver v6.0: (accel) acceleration threshold: 4
1720.701] (II) Microsoft Microsoft® 2.4GHz Transceiver v6.0: initialized for relative axes.
1720.701] (WW) Microsoft Microsoft® 2.4GHz Transceiver v6.0: ignoring absolute axes.
1720.701] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v6.0 (/dev/input/mouse0)
1720.701] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Applying InputClass “LocalKeyboard”
1720.701] (II) No input driver/identifier specified (ignoring)
1720.702] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v6.0 (/dev/input/event2)
1720.702] () Microsoft Microsoft® 2.4GHz Transceiver v6.0: Applying InputClass “evdev keyboard catchall”
1720.702] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Applying InputClass “LocalKeyboard”
1720.702] () Microsoft Microsoft® 2.4GHz Transceiver v6.0: always reports core events
1720.702] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Device: “/dev/input/event2”
1720.709] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found 1 mouse buttons
1720.709] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found scroll wheel(s)
1720.709] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found relative axes
1720.709] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found absolute axes
1720.709] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found x and y absolute axes
1720.709] (–) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Found keys
1720.709] (II) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Configuring as mouse
1720.709] (II) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Configuring as keyboard
1720.709] (II) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Adding scrollwheel support
1720.709] () Microsoft Microsoft® 2.4GHz Transceiver v6.0: YAxisMapping: buttons 4 and 5
1720.709] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
1720.709] (II) XINPUT: Adding extended input device “Microsoft Microsoft® 2.4GHz Transceiver v6.0” (type: KEYBOARD)
1720.709] () Option “xkb_rules” “evdev”
1720.709] (
) Option “xkb_model” “evdev”
1720.709] () Option “xkb_layout” “us,ru”
1720.709] (
) Option “xkb_variant” “,winkeys”
1720.709] () Option “xkb_options” “grp:ctrl_shift_toggle,grp_led:scroll”
1720.709] (EE) Microsoft Microsoft® 2.4GHz Transceiver v6.0: failed to initialize for relative axes.
1720.709] (WW) Microsoft Microsoft® 2.4GHz Transceiver v6.0: found 37 axes, limiting to 36.
1720.709] (II) Microsoft Microsoft® 2.4GHz Transceiver v6.0: initialized for absolute axes.
1720.710] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v6.0 (/dev/input/js0)
1720.710] (
) Microsoft Microsoft® 2.4GHz Transceiver v6.0: Applying InputClass “LocalKeyboard”
1720.710] (II) No input driver/identifier specified (ignoring)
1720.712] (II) config/udev: Adding input device HDA ATI SB Headphone (/dev/input/event6)
1720.712] (II) No input driver/identifier specified (ignoring)
1720.714] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
1720.714] (II) No input driver/identifier specified (ignoring)
1725.645] (II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-ADB0C3A7981A9F42535006721CEF11DFC2062FEC.xkm
1730.490] (II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-DEE8D2060D91ED62BFA836153DA050FE743DB84D.xkm

Yet I’ve inserted (The Xlog shows after the following inclusion.)

Section “InputClass”
# 045e:0745
Identifier “Microsoft Microsoft® 2.4GHz Transceiver v6.0”
MatchVendor “Microsoft Corp.”
MatchProduct “USB HID v1.11 Mouse”
MatchIsPointer “on”
Driver “evdev”
Option “HWHEELRelativeAxisButtons” “7 6”
Option “Sensitivity” “0.2”
EndSection

in /etc/X11/xorg.conf.d/11-mouse.conf
Without result too.

The problem is solved. After working in OS Windows the Transceiver remember some setting and stay in hyper sensitive mode. Linux do not clear this setting. After unplug|plug usb transceiver i’ve got a normal sensitivity of wheel. If I find a pattern, then I’ll write more.
Thanks
Nick

On 03/12/2011 01:36 PM, nickwest wrote:
>
> Thanks
>

no, thank YOU…(for finding a solution and posting it here so others
who google in can find it…)


DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.1.8, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11