You are not logged in.

Pages: 1

#1 2022-12-13 02:12:49

prosup
Member
Registered: 2021-08-18
Posts: 16

[Hardware problem]mouse wheel scrolling direction jump problem

It's a 2.4g wireless mouse bought 1year ago,the problem occur lately:quickly scroll mid wheel ,the screen may jump up and down.
I thought it's dirty so I open it do some cleaning work,but the problem is still there,so i tried it on my windows machine,no problem at all.

here is xev result(part of it),while scrolling the wheel.
I notice there some button4 event occur,while the wheel scrolling down,quickly
But ,why?Same mouse,no problem on my windows machine.

...
ButtonPress event, serial 25, synthetic NO, window 0x4000001,
    root 0x1c4, subw 0x0, time 5966867, (84,88), root:(955,564),
    state 0x10, button 5, same_screen YES

ButtonRelease event, serial 25, synthetic NO, window 0x4000001,
    root 0x1c4, subw 0x0, time 5966867, (84,88), root:(955,564),
    state 0x1010, button 5, same_screen YES

ButtonPress event, serial 25, synthetic NO, window 0x4000001,
    root 0x1c4, subw 0x0, time 5966875, (84,88), root:(955,564),
    state 0x10, button 4, same_screen YES

ButtonRelease event, serial 25, synthetic NO, window 0x4000001,
    root 0x1c4, subw 0x0, time 5966875, (84,88), root:(955,564),
    state 0x810, button 4, same_screen YES

ButtonPress event, serial 25, synthetic NO, window 0x4000001,
    root 0x1c4, subw 0x0, time 5966883, (84,88), root:(955,564),
    state 0x10, button 5, same_screen YES

ButtonRelease event, serial 25, synthetic NO, window 0x4000001,
    root 0x1c4, subw 0x0, time 5966883, (84,88), root:(955,564),
    state 0x1010, button 5, same_screen YES

ButtonPress event, serial 25, synthetic NO, window 0x4000001,
    root 0x1c4, subw 0x0, time 5966891, (84,88), root:(955,564),
    state 0x10, button 5, same_screen YES

ButtonRelease event, serial 25, synthetic NO, window 0x4000001,
    root 0x1c4, subw 0x0, time 5966891, (84,88), root:(955,564),
    state 0x1010, button 5, same_screen YES

ButtonPress event, serial 25, synthetic NO, window 0x4000001,
    root 0x1c4, subw 0x0, time 5966899, (84,88), root:(955,564),
    state 0x10, button 5, same_screen YES
...

Last edited by prosup (2022-12-14 01:07:18)

Offline

#2 2022-12-13 02:59:32

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,171

Re: [Hardware problem]mouse wheel scrolling direction jump problem

Which mouse is it? Please post your Xorg log.

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#3 2022-12-13 05:14:46

prosup
Member
Registered: 2021-08-18
Posts: 16

Re: [Hardware problem]mouse wheel scrolling direction jump problem

MOSART Semi. 2.4G Keyboard Mouse
[     5.056] (--) Log file renamed from "/var/log/Xorg.pid-578.log" to "/var/log/Xorg.0.log"
[     4.057] 
X.Org X Server 1.21.1.4
X Protocol Version 11, Revision 0
[     4.057] Current Operating System: Linux qmo 6.0.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 10 Nov 2022 21:14:24 +0000 x86_64
[     4.058] Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=54717bf6-7002-4687-ad13-61516526c67b rw rootflags=subvol=@ loglevel=3 quiet
[     4.058]  
[     4.058] Current version of pixman: 0.42.2
[     4.058] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[     4.058] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     4.058] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 13 08:15:31 2022
[     4.060] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     4.060] (==) No Layout section.  Using the first Screen section.
[     4.060] (==) No screen section available. Using defaults.
[     4.060] (**) |-->Screen "Default Screen Section" (0)
[     4.060] (**) |   |-->Monitor "<default monitor>"
[     4.060] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[     4.060] (==) Automatically adding devices
[     4.060] (==) Automatically enabling devices
[     4.060] (==) Automatically adding GPU devices
[     4.060] (==) Automatically binding GPU devices
[     4.060] (==) Max clients allowed: 256, resource mask: 0x1fffff
[     4.061] (WW) The directory "/usr/share/fonts/misc" does not exist.
[     4.061] 	Entry deleted from font path.
[     4.061] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[     4.061] 	Entry deleted from font path.
[     4.061] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[     4.061] 	Entry deleted from font path.
[     4.061] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[     4.061] 	Entry deleted from font path.
[     4.061] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[     4.061] 	Entry deleted from font path.
[     4.061] (==) FontPath set to:
	/usr/share/fonts/TTF
[     4.061] (==) ModulePath set to "/usr/lib/xorg/modules"
[     4.061] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[     4.061] (II) Module ABI versions:
[     4.061] 	X.Org ANSI C Emulation: 0.4
[     4.061] 	X.Org Video Driver: 25.2
[     4.061] 	X.Org XInput driver : 24.4
[     4.061] 	X.Org Server Extension : 10.0
[     4.062] (++) using VT number 1

[     4.062] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[     4.062] (II) xfree86: Adding drm device (/dev/dri/card0)
[     4.063] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
[     4.064] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[     4.066] (--) PCI:*(1@0:0:0) 10de:1d01:10de:11c7 rev 161, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[     4.066] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[     4.066] (II) LoadModule: "glx"
[     4.067] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     4.077] (II) Module glx: vendor="X.Org Foundation"
[     4.077] 	compiled for 1.21.1.4, module version = 1.0.0
[     4.077] 	ABI class: X.Org Server Extension, version 10.0
[     4.077] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[     4.077] 	loading driver: nvidia
[     4.077] (==) Matched nvidia as autoconfigured driver 0
[     4.077] (==) Matched nouveau as autoconfigured driver 1
[     4.077] (==) Matched nv as autoconfigured driver 2
[     4.077] (==) Matched modesetting as autoconfigured driver 3
[     4.077] (==) Matched fbdev as autoconfigured driver 4
[     4.077] (==) Matched vesa as autoconfigured driver 5
[     4.077] (==) Assigned the driver to the xf86ConfigLayout
[     4.077] (II) LoadModule: "nvidia"
[     4.077] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[     4.089] (II) Module nvidia: vendor="NVIDIA Corporation"
[     4.089] 	compiled for 1.6.99.901, module version = 1.0.0
[     4.089] 	Module class: X.Org Video Driver
[     4.089] (II) LoadModule: "nouveau"
[     4.089] (WW) Warning, couldn't open module nouveau
[     4.089] (EE) Failed to load module "nouveau" (module does not exist, 0)
[     4.089] (II) LoadModule: "nv"
[     4.089] (WW) Warning, couldn't open module nv
[     4.089] (EE) Failed to load module "nv" (module does not exist, 0)
[     4.089] (II) LoadModule: "modesetting"
[     4.090] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     4.095] (II) Module modesetting: vendor="X.Org Foundation"
[     4.095] 	compiled for 1.21.1.4, module version = 1.21.1
[     4.095] 	Module class: X.Org Video Driver
[     4.095] 	ABI class: X.Org Video Driver, version 25.2
[     4.095] (II) LoadModule: "fbdev"
[     4.096] (WW) Warning, couldn't open module fbdev
[     4.096] (EE) Failed to load module "fbdev" (module does not exist, 0)
[     4.096] (II) LoadModule: "vesa"
[     4.096] (WW) Warning, couldn't open module vesa
[     4.096] (EE) Failed to load module "vesa" (module does not exist, 0)
[     4.096] (II) NVIDIA dlloader X Driver  520.56.06  Thu Oct  6 21:29:26 UTC 2022
[     4.096] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[     4.096] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     4.096] (II) Loading sub module "fb"
[     4.096] (II) LoadModule: "fb"
[     4.096] (II) Module "fb" already built-in
[     4.096] (II) Loading sub module "wfb"
[     4.096] (II) LoadModule: "wfb"
[     4.096] (II) Loading /usr/lib/xorg/modules/libwfb.so
[     4.098] (II) Module wfb: vendor="X.Org Foundation"
[     4.098] 	compiled for 1.21.1.4, module version = 1.0.0
[     4.098] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     4.098] (II) Loading sub module "ramdac"
[     4.098] (II) LoadModule: "ramdac"
[     4.098] (II) Module "ramdac" already built-in
[     4.135] (WW) Falling back to old probe method for modesetting
[     4.135] (II) NVIDIA(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[     4.135] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[     4.135] (==) NVIDIA(0): RGB weight 888
[     4.135] (==) NVIDIA(0): Default visual is TrueColor
[     4.135] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[     4.135] (II) Applying OutputClass "nvidia" options to /dev/dri/card0
[     4.135] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[     4.135] (**) NVIDIA(0): Enabling 2D acceleration
[     4.135] (II) Loading sub module "glxserver_nvidia"
[     4.135] (II) LoadModule: "glxserver_nvidia"
[     4.135] (II) Loading /usr/lib/nvidia/xorg/libglxserver_nvidia.so
[     4.192] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[     4.192] 	compiled for 1.6.99.901, module version = 1.0.0
[     4.192] 	Module class: X.Org Server Extension
[     4.192] (II) NVIDIA GLX Module  520.56.06  Thu Oct  6 21:26:26 UTC 2022
[     4.192] (II) NVIDIA: The X server supports PRIME Render Offload.
[     4.899] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[     4.899] (--) NVIDIA(0):     DFP-0 (boot)
[     4.899] (--) NVIDIA(0):     DFP-1
[     4.900] (II) NVIDIA(0): NVIDIA GPU NVIDIA GeForce GT 1030 (GP108-A) at PCI:1:0:0
[     4.900] (II) NVIDIA(0):     (GPU-0)
[     4.900] (--) NVIDIA(0): Memory: 2097152 kBytes
[     4.900] (--) NVIDIA(0): VideoBIOS: 86.08.24.00.01
[     4.900] (II) NVIDIA(0): Detected PCI Express Link width: 4X
[     4.943] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): connected
[     4.943] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): Internal TMDS
[     4.943] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): 165.0 MHz maximum pixel clock
[     4.943] (--) NVIDIA(GPU-0): 
[     4.943] (--) NVIDIA(GPU-0): DFP-1: disconnected
[     4.943] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[     4.943] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[     4.943] (--) NVIDIA(GPU-0): 
[     4.945] (==) NVIDIA(0): 
[     4.945] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[     4.945] (==) NVIDIA(0):     will be used as the requested mode.
[     4.945] (==) NVIDIA(0): 
[     4.945] (II) NVIDIA(0): Validated MetaModes:
[     4.945] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select"
[     4.945] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[     4.946] (--) NVIDIA(0): DPI set to (93, 94); computed from "UseEdidDpi" X config
[     4.946] (--) NVIDIA(0):     option
[     4.946] (II) UnloadModule: "modesetting"
[     4.946] (II) Unloading modesetting
[     4.947] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
[     4.947] (II) NVIDIA:     access.
[     4.949] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[     4.949] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[     4.949] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[     4.949] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[     4.949] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[     4.949] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[     4.949] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[     4.949] (II) NVIDIA(0):     Config Options in the README.
[     4.963] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[     5.035] (==) NVIDIA(0): Disabling shared memory pixmaps
[     5.035] (==) NVIDIA(0): Backing store enabled
[     5.035] (==) NVIDIA(0): Silken mouse enabled
[     5.035] (==) NVIDIA(0): DPMS enabled
[     5.036] (II) Loading sub module "dri2"
[     5.036] (II) LoadModule: "dri2"
[     5.036] (II) Module "dri2" already built-in
[     5.036] (II) NVIDIA(0): [DRI2] Setup complete
[     5.036] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[     5.036] (II) Initializing extension Generic Event Extension
[     5.036] (II) Initializing extension SHAPE
[     5.036] (II) Initializing extension MIT-SHM
[     5.036] (II) Initializing extension XInputExtension
[     5.036] (II) Initializing extension XTEST
[     5.036] (II) Initializing extension BIG-REQUESTS
[     5.036] (II) Initializing extension SYNC
[     5.037] (II) Initializing extension XKEYBOARD
[     5.037] (II) Initializing extension XC-MISC
[     5.037] (II) Initializing extension SECURITY
[     5.037] (II) Initializing extension XFIXES
[     5.037] (II) Initializing extension RENDER
[     5.037] (II) Initializing extension RANDR
[     5.037] (II) Initializing extension COMPOSITE
[     5.037] (II) Initializing extension DAMAGE
[     5.037] (II) Initializing extension MIT-SCREEN-SAVER
[     5.037] (II) Initializing extension DOUBLE-BUFFER
[     5.037] (II) Initializing extension RECORD
[     5.037] (II) Initializing extension DPMS
[     5.037] (II) Initializing extension Present
[     5.037] (II) Initializing extension DRI3
[     5.037] (II) Initializing extension X-Resource
[     5.038] (II) Initializing extension XVideo
[     5.038] (II) Initializing extension XVideo-MotionCompensation
[     5.038] (II) Initializing extension GLX
[     5.038] (II) Initializing extension GLX
[     5.038] (II) Indirect GLX disabled.
[     5.038] (II) GLX: Another vendor is already registered for screen 0
[     5.038] (II) Initializing extension XFree86-VidModeExtension
[     5.038] (II) Initializing extension XFree86-DGA
[     5.038] (II) Initializing extension XFree86-DRI
[     5.038] (II) Initializing extension DRI2
[     5.038] (II) Initializing extension NV-GLX
[     5.038] (II) Initializing extension NV-CONTROL
[     5.038] (II) Initializing extension XINERAMA
[     5.082] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[     5.082] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[     5.082] (II) LoadModule: "libinput"
[     5.082] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[     5.087] (II) Module libinput: vendor="X.Org Foundation"
[     5.087] 	compiled for 1.21.1.3, module version = 1.2.1
[     5.087] 	Module class: X.Org XInput Driver
[     5.087] 	ABI class: X.Org XInput driver, version 24.4
[     5.087] (II) Using input driver 'libinput' for 'Power Button'
[     5.087] (**) Power Button: always reports core events
[     5.087] (**) Option "Device" "/dev/input/event2"
[     5.089] (II) event2  - Power Button: is tagged by udev as: Keyboard
[     5.089] (II) event2  - Power Button: device is a keyboard
[     5.089] (II) event2  - Power Button: device removed
[     5.118] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[     5.118] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[     5.119] (II) event2  - Power Button: is tagged by udev as: Keyboard
[     5.119] (II) event2  - Power Button: device is a keyboard
[     5.120] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[     5.120] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[     5.120] (II) Using input driver 'libinput' for 'Power Button'
[     5.120] (**) Power Button: always reports core events
[     5.120] (**) Option "Device" "/dev/input/event1"
[     5.120] (II) event1  - Power Button: is tagged by udev as: Keyboard
[     5.120] (II) event1  - Power Button: device is a keyboard
[     5.120] (II) event1  - Power Button: device removed
[     5.145] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[     5.145] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[     5.147] (II) event1  - Power Button: is tagged by udev as: Keyboard
[     5.147] (II) event1  - Power Button: device is a keyboard
[     5.149] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[     5.149] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[     5.149] (II) Using input driver 'libinput' for 'Sleep Button'
[     5.149] (**) Sleep Button: always reports core events
[     5.149] (**) Option "Device" "/dev/input/event0"
[     5.150] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[     5.150] (II) event0  - Sleep Button: device is a keyboard
[     5.151] (II) event0  - Sleep Button: device removed
[     5.168] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0/event0"
[     5.168] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[     5.169] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[     5.169] (II) event0  - Sleep Button: device is a keyboard
[     5.170] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event10)
[     5.170] (II) No input driver specified, ignoring this device.
[     5.170] (II) This device may have been added with another device file.
[     5.170] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event11)
[     5.170] (II) No input driver specified, ignoring this device.
[     5.170] (II) This device may have been added with another device file.
[     5.170] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event12)
[     5.170] (II) No input driver specified, ignoring this device.
[     5.170] (II) This device may have been added with another device file.
[     5.171] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=10 (/dev/input/event13)
[     5.171] (II) No input driver specified, ignoring this device.
[     5.171] (II) This device may have been added with another device file.
[     5.171] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event9)
[     5.171] (II) No input driver specified, ignoring this device.
[     5.171] (II) This device may have been added with another device file.
[     5.172] (II) config/udev: Adding input device MOSART Semi. 2.4G Keyboard Mouse (/dev/input/event3)
[     5.172] (**) MOSART Semi. 2.4G Keyboard Mouse: Applying InputClass "libinput keyboard catchall"
[     5.172] (II) Using input driver 'libinput' for 'MOSART Semi. 2.4G Keyboard Mouse'
[     5.172] (**) MOSART Semi. 2.4G Keyboard Mouse: always reports core events
[     5.172] (**) Option "Device" "/dev/input/event3"
[     5.173] (II) event3  - MOSART Semi. 2.4G Keyboard Mouse: is tagged by udev as: Keyboard
[     5.173] (II) event3  - MOSART Semi. 2.4G Keyboard Mouse: device is a keyboard
[     5.173] (II) event3  - MOSART Semi. 2.4G Keyboard Mouse: device removed
[     5.205] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/0003:062A:4101.0001/input/input3/event3"
[     5.205] (II) XINPUT: Adding extended input device "MOSART Semi. 2.4G Keyboard Mouse" (type: KEYBOARD, id 9)
[     5.209] (II) event3  - MOSART Semi. 2.4G Keyboard Mouse: is tagged by udev as: Keyboard
[     5.210] (II) event3  - MOSART Semi. 2.4G Keyboard Mouse: device is a keyboard
[     5.213] (II) config/udev: Adding input device MOSART Semi. 2.4G Keyboard Mouse (/dev/input/event4)
[     5.213] (**) MOSART Semi. 2.4G Keyboard Mouse: Applying InputClass "libinput pointer catchall"
[     5.213] (II) Using input driver 'libinput' for 'MOSART Semi. 2.4G Keyboard Mouse'
[     5.213] (**) MOSART Semi. 2.4G Keyboard Mouse: always reports core events
[     5.213] (**) Option "Device" "/dev/input/event4"
[     5.217] (II) event4  - MOSART Semi. 2.4G Keyboard Mouse: is tagged by udev as: Mouse
[     5.217] (II) event4  - MOSART Semi. 2.4G Keyboard Mouse: device is a pointer
[     5.218] (II) event4  - MOSART Semi. 2.4G Keyboard Mouse: device removed
[     5.258] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.1/0003:062A:4101.0002/input/input4/event4"
[     5.258] (II) XINPUT: Adding extended input device "MOSART Semi. 2.4G Keyboard Mouse" (type: MOUSE, id 10)
[     5.259] (**) Option "AccelerationScheme" "none"
[     5.259] (**) MOSART Semi. 2.4G Keyboard Mouse: (accel) selected scheme none/0
[     5.259] (**) MOSART Semi. 2.4G Keyboard Mouse: (accel) acceleration factor: 2.000
[     5.259] (**) MOSART Semi. 2.4G Keyboard Mouse: (accel) acceleration threshold: 4
[     5.263] (II) event4  - MOSART Semi. 2.4G Keyboard Mouse: is tagged by udev as: Mouse
[     5.263] (II) event4  - MOSART Semi. 2.4G Keyboard Mouse: device is a pointer
[     5.266] (II) config/udev: Adding input device MOSART Semi. 2.4G Keyboard Mouse (/dev/input/mouse0)
[     5.266] (II) No input driver specified, ignoring this device.
[     5.266] (II) This device may have been added with another device file.
[     5.268] (II) config/udev: Adding input device MOSART Semi. 2.4G Keyboard Mouse Consumer Control (/dev/input/event5)
[     5.268] (**) MOSART Semi. 2.4G Keyboard Mouse Consumer Control: Applying InputClass "libinput keyboard catchall"
[     5.268] (II) Using input driver 'libinput' for 'MOSART Semi. 2.4G Keyboard Mouse Consumer Control'
[     5.268] (**) MOSART Semi. 2.4G Keyboard Mouse Consumer Control: always reports core events
[     5.268] (**) Option "Device" "/dev/input/event5"
[     5.272] (II) event5  - MOSART Semi. 2.4G Keyboard Mouse Consumer Control: is tagged by udev as: Keyboard
[     5.272] (II) event5  - MOSART Semi. 2.4G Keyboard Mouse Consumer Control: device is a keyboard
[     5.273] (II) event5  - MOSART Semi. 2.4G Keyboard Mouse Consumer Control: device removed
[     5.298] (II) libinput: MOSART Semi. 2.4G Keyboard Mouse Consumer Control: needs a virtual subdevice
[     5.298] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.1/0003:062A:4101.0002/input/input5/event5"
[     5.298] (II) XINPUT: Adding extended input device "MOSART Semi. 2.4G Keyboard Mouse Consumer Control" (type: MOUSE, id 11)
[     5.298] (**) Option "AccelerationScheme" "none"
[     5.298] (**) MOSART Semi. 2.4G Keyboard Mouse Consumer Control: (accel) selected scheme none/0
[     5.298] (**) MOSART Semi. 2.4G Keyboard Mouse Consumer Control: (accel) acceleration factor: 2.000
[     5.298] (**) MOSART Semi. 2.4G Keyboard Mouse Consumer Control: (accel) acceleration threshold: 4
[     5.299] (II) event5  - MOSART Semi. 2.4G Keyboard Mouse Consumer Control: is tagged by udev as: Keyboard
[     5.299] (II) event5  - MOSART Semi. 2.4G Keyboard Mouse Consumer Control: device is a keyboard
[     5.300] (II) config/udev: Adding input device MOSART Semi. 2.4G Keyboard Mouse System Control (/dev/input/event6)
[     5.300] (**) MOSART Semi. 2.4G Keyboard Mouse System Control: Applying InputClass "libinput keyboard catchall"
[     5.300] (II) Using input driver 'libinput' for 'MOSART Semi. 2.4G Keyboard Mouse System Control'
[     5.300] (**) MOSART Semi. 2.4G Keyboard Mouse System Control: always reports core events
[     5.300] (**) Option "Device" "/dev/input/event6"
[     5.301] (II) event6  - MOSART Semi. 2.4G Keyboard Mouse System Control: is tagged by udev as: Keyboard
[     5.301] (II) event6  - MOSART Semi. 2.4G Keyboard Mouse System Control: device is a keyboard
[     5.301] (II) event6  - MOSART Semi. 2.4G Keyboard Mouse System Control: device removed
[     5.315] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.1/0003:062A:4101.0002/input/input6/event6"
[     5.315] (II) XINPUT: Adding extended input device "MOSART Semi. 2.4G Keyboard Mouse System Control" (type: KEYBOARD, id 12)
[     5.316] (II) event6  - MOSART Semi. 2.4G Keyboard Mouse System Control: is tagged by udev as: Keyboard
[     5.316] (II) event6  - MOSART Semi. 2.4G Keyboard Mouse System Control: device is a keyboard
[     5.316] (II) config/udev: Adding input device MOSART Semi. 2.4G Keyboard Mouse (/dev/input/event7)
[     5.316] (II) No input driver specified, ignoring this device.
[     5.316] (II) This device may have been added with another device file.
[     5.317] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event14)
[     5.317] (II) No input driver specified, ignoring this device.
[     5.317] (II) This device may have been added with another device file.
[     5.317] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event15)
[     5.317] (II) No input driver specified, ignoring this device.
[     5.317] (II) This device may have been added with another device file.
[     5.317] (II) config/udev: Adding input device PC Speaker (/dev/input/event8)
[     5.317] (II) No input driver specified, ignoring this device.
[     5.317] (II) This device may have been added with another device file.
[     5.322] (**) MOSART Semi. 2.4G Keyboard Mouse Consumer Control: Applying InputClass "libinput keyboard catchall"
[     5.322] (II) Using input driver 'libinput' for 'MOSART Semi. 2.4G Keyboard Mouse Consumer Control'
[     5.322] (**) MOSART Semi. 2.4G Keyboard Mouse Consumer Control: always reports core events
[     5.322] (**) Option "Device" "/dev/input/event5"
[     5.322] (II) libinput: MOSART Semi. 2.4G Keyboard Mouse Consumer Control: is a virtual subdevice
[     5.322] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.1/0003:062A:4101.0002/input/input5/event5"
[     5.322] (II) XINPUT: Adding extended input device "MOSART Semi. 2.4G Keyboard Mouse Consumer Control" (type: KEYBOARD, id 13)
[     5.365] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): connected
[     5.365] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): Internal TMDS
[     5.365] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): 165.0 MHz maximum pixel clock
[     5.365] (--) NVIDIA(GPU-0): 
[     5.409] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): connected
[     5.409] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): Internal TMDS
[     5.409] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): 165.0 MHz maximum pixel clock
[     5.409] (--) NVIDIA(GPU-0): 
[    69.981] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): connected
[    69.981] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): Internal TMDS
[    69.981] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): 165.0 MHz maximum pixel clock
[    69.981] (--) NVIDIA(GPU-0): 
[    69.981] (--) NVIDIA(GPU-0): DFP-1: disconnected
[    69.981] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[    69.981] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[    69.981] (--) NVIDIA(GPU-0): 
[    70.698] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): connected
[    70.698] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): Internal TMDS
[    70.698] (--) NVIDIA(GPU-0): MIG -MIGRATE (DFP-0): 165.0 MHz maximum pixel clock
[    70.698] (--) NVIDIA(GPU-0): 
[    70.698] (--) NVIDIA(GPU-0): DFP-1: disconnected
[    70.698] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[    70.698] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[    70.698] (--) NVIDIA(GPU-0):

Offline

#4 2022-12-13 08:49:13

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,744

Re: [Hardware problem]mouse wheel scrolling direction jump problem

That's a thing w/ that device https://bbs.archlinux.org/viewtopic.php?id=267057 (and I'd intensely test whether the windows driver actually mitigates this or you're just not noticing the behavior b/c of "smooth scrolling")
The events are all 8ms apart, so this is probably not some spurious event.
The only mitigation would be to trace the wheel and infer that a reversal this fast seems unlikely™, but I'm not aware of a libinput quirk that would do so.

Semi-related: do you manipulate the https://wiki.archlinux.org/title/Mouse_polling_rate ?
What's the output of

lsusb -vd 062a:4101 | grep bInterval

?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2022-12-13 09:09:06

prosup
Member
Registered: 2021-08-18
Posts: 16

Re: [Hardware problem]mouse wheel scrolling direction jump problem

I'm aware the problem might be with the mouse because of the event log,sadly.
Just curious ,given windows could use the mouse normally ,could we find a solution?

----
I'v never manipulated the polling rate.

lsusb -vd 062a:4101 | grep bInterval
        bInterval              10
        bInterval               4

full log below

Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x062a MosArt Semiconductor Corp.
  idProduct          0x4101 Wireless Keyboard/Mouse
  bcdDevice            3.22
  iManufacturer           1 MOSART Semi.
  iProduct                2 2.4G Keyboard Mouse
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x003b
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      1 Keyboard
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      65
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      2 Mouse
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     168
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0007  1x 7 bytes
        bInterval               4
Device Status:     0x0000
  (Bus Powered)

Offline

#6 2022-12-13 14:01:31

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,744

Re: [Hardware problem]mouse wheel scrolling direction jump problem

I'v never manipulated the polling rate.

You could try what happens if you fix it to 100Hz (10ms delay, 16ms event frequency)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2022-12-14 01:06:45

prosup
Member
Registered: 2021-08-18
Posts: 16

Re: [Hardware problem]mouse wheel scrolling direction jump problem

Nothing changed,Seems I'v to bought another mouse ~~>_<~~
thx btw.

Offline

#8 2022-12-14 08:24:55

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,744

Re: [Hardware problem]mouse wheel scrolling direction jump problem

To make sure the change worked, does the event frequency in xev go down from ~8ms to ~16ms?
Not sure whether the device supports that to begin with, but you could also try to disable "HighResolutionWheelScrolling", https://man.archlinux.org/man/extra/xf8 … n#Option~9

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB