Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am using a wireless mouse on my slackware-arm current (14.2) and its moving too slow. I've read a few posts towards its resolution and implemented them, yet it continues to be slow. The speed seems to have improved, but the acceleration and deceleration are still a major worry. The mouse starts a few ms after i move it, and stops after a few ms after i've stopped. Following is an output of xinput. I have already changed the value of 'libinput Accel Speed" to 1.0, which was 0.0 earlier.
The XFCE setting of "Mouse and Touchpad" does not seem to help much
There seems to have been a few people using the 'MOSART Semi. 2.4G Wireless Mouse' device who have faced problems under Linux. I don't have the same mouse so I'm unable to test. However, one solution I found on Google was to do this:
1. Unplug wireless mouse dongle.
2. Run modprobe -r usbhid on the command line.
3. Reconnect wireless mouse dongle again.
Does /usr/lib/udev/hwdb.d/70-mouse.hwdb exist? I ask because I'm not sure if Slackware 42.2 has eudev configured to use the hardware database. If the hardware database does exist then it may be possible to create an entry and specify a suitable DPI value for your mouse (and hence influence its effective speed/behaviour with libinput).
There is a 'mouse-dpi-tool' utility which can be used to estimate DPI for your mouse by moving the mouse over a certain physical distance. It also reports the sample frequency of the mouse hardware.
I apologize in advance if this approach can't be used with Slackware, (but good if it can).
@Exaga tried doesn't work
@ferrari
looking at the preset values for other vendor mice, mine seems dismal figures, yet tried and failed to see any improvement...
Code:
root@slackpi:~# mouse-dpi-tool /dev/input/event2
Mouse MOSART Semi. 2.4G Wireless Mouse on /dev/input/event2
Move the device 250mm/10in or more along the x-axis.
Pause 3 seconds before movement to reset, Ctrl+C to exit.
Covered distance in device units: 638 at frequency 31.4Hz /^C
Estimated sampling frequency: 31Hz (mean 31Hz)
To calculate resolution, measure physical distance covered
and look up the matching resolution in the table below
40mm 1.59in 400dpi
27mm 1.06in 600dpi
20mm 0.80in 800dpi
16mm 0.64in 1000dpi
13mm 0.53in 1200dpi
11mm 0.46in 1400dpi
10mm 0.40in 1600dpi
9mm 0.35in 1800dpi
8mm 0.32in 2000dpi
7mm 0.29in 2200dpi
6mm 0.27in 2400dpi
If your resolution is not in the list, calculate it with:
resolution=638/inches, or
resolution=638 * 25.4/mm
Entry for hwdb match (replace XXX with the resolution in DPI):
mouse:usb:v062ap4102:name:MOSART Semi. 2.4G Wireless Mouse:
MOUSE_DPI=XXX@31
root@slackpi:~#
That does seem very low! Since you report that the mouse is too slow, you could try increasing it a bit eg 100. That should increase the effective speed. There is a trade-off with accuracy, so don't be tempted to increase it too much.
Dots per inch (DPI) is a measurement of how sensitive a mouse is. The higher a mouse’s DPI, the farther the cursor on your screen will move when you move the mouse. A mouse with a higher DPI setting detects and reacts to smaller movements.
A higher DPI isn’t always better. You don’t want your mouse cursor to fly all the way across the screen when you move your mouse a little bit. On the other hand, a higher DPI setting helps your mouse detect and respond to smaller movements so you can point at things more accurately. For example, let’s say you’re playing a first-person shooter game. When zooming in with a sniper rifle and trying to aim precisely at small targets, a high DPI could be valuable by allowing you to smoothly aim with small mouse movements. When playing the game normally without a zoomed-in sniper rifle, this high DPI may be too sensitive. This is why many high-end gaming mouse have buttons that you can flick to switch between DPI settings on the fly when playing a game.
I know little about eudev (other than it's a alternative to systemd-based udev), but hopefully these commands are compatible. After making changes to the the hardware database file, it can be updated (as root) using....
Code:
udevadm hwdb --update
Code:
udevadm trigger
It might be simplest to reboot, and then check mouse speed again.
Taking care to use the appropriate device path pertaining to your mouse (eg /dev/input/event2), check that the DPI settings do match what you've set...
That does seem very low! Since you report that the mouse is too slow, you could try increasing it a bit eg 100. That should increase the effective speed.
I think my DPI calculation is mistaken (hence edited my post #5)
I connected my K400 keyboard and tried the same with the touchpad (opened gimp to move mouse roughly 10 inches on its scale) and it gave me similar DPI values @125 Hz. The K400 touchpad is however working perfectly.
Can you help me the calculation for K400+ for comparison (I am not sure if the same tool can be used for touchpads too, i assume yes)?
Code:
root@slackpi:~# mouse-dpi-tool /dev/input/event0
Mouse Logitech K400 Plus on /dev/input/event0
Move the device 250mm/10in or more along the x-axis.
Pause 3 seconds before movement to reset, Ctrl+C to exit.
Covered distance in device units: 700 at frequency 128.2Hz / \^C
Estimated sampling frequency: 128Hz (mean 70Hz)
WARNING: Max frequency is more than 30% higher than mean frequency. Manual verification required!
To calculate resolution, measure physical distance covered
and look up the matching resolution in the table below
44mm 1.75in 400dpi
29mm 1.17in 600dpi
22mm 0.88in 800dpi
17mm 0.70in 1000dpi
14mm 0.58in 1200dpi
12mm 0.50in 1400dpi
11mm 0.44in 1600dpi
9mm 0.39in 1800dpi
8mm 0.35in 2000dpi
8mm 0.32in 2200dpi
7mm 0.29in 2400dpi
If your resolution is not in the list, calculate it with:
resolution=700/inches, or
resolution=700 * 25.4/mm
Entry for hwdb match (replace XXX with the resolution in DPI):
mouse:usb:v046dp404d:name:Logitech K400 Plus:
MOUSE_DPI=XXX@128
root@slackpi:~#
That does seem very low! Since you report that the mouse is too slow, you could try increasing it a bit eg 100. That should increase the effective speed. There is a trade-off with accuracy, so don't be tempted to increase it too much.
I've tried increasing to 100, then tried 400.. there is no noticable change...
I've tried increasing to 100, then tried 400.. there is no noticable change...
Just to confirm that you've run the udevadm commands I gave after making the change and confirmed the mouse DPI settings (as per post #7 and #8), or at least rebooted then tested again?
Just to confirm that you've run the udevadm commands I gave after making the change and confirmed the mouse DPI settings (as per post #7 and #8), or at least rebooted then tested again?
Yes, i've used the udevadm commands each time i changed the values
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
