Howto fix a too sensitive touchpad on Linux

If your touchpad is too sensitive (meaning the cursor jumps around when you either put your finger on the touchpad or you remove your finger from the touchpad) then here’s how to fix it:

Open a terminal window and find out the ID of the touchpad:

The output should look something like this:

So the touchpad (an Alps in my case) has ID 13.

Now let’s list the properties (settings) of the touchpad:

The output should look something like this:

The setting to look for is “Synaptics Finger”:

The “298” is the ID of the setting and the “12, 15, 0” values represent FingerLow, FingerHigh and FingerPress. You can read about their meaning here

Start increasing the first 2 values each in increments of 2 with the following command. The changes become active immediately. If the touchpad is still too sensitive then keep on increasing those values until the problem is solved.

The syntax of the command is:

In my case the values that solved the problem were:

Once the proper values are found they can be made permanent by adding them to the InputClass of the synaptics config file:

If the problem can not be solved by changing the FingerLow and FingerHigh values then there are a ton of links in Google that discuss this problem. An excellent resource is https://wiki.archlinux.org/index.php/Touchpad_Synaptics

SystemD: Understanding Predictable Network Interface Names

Here is an explanation of how SystemD predictable network interface names are determined.

Predictable network interface device names are based on:
– firmware/bios-provided index numbers for on-board devices
– firmware-provided pci-express hotplug slot index number
– physical/geographical location of the hardware
– the interface’s MAC address

Two character prefixes based on the type of interface:

Type of names:

All multi-function PCI devices will carry the [f] number in the device name including the function 0 device.

When using PCI geography the PCI domain is only prepended when it is not 0.

For USB devices the full chain of port numbers of hubs is composed. If the name gets longer than the maximum number of 15 characters the name is not exported.
The usual USB configuration == 1 and interface == 0 values are suppressed.

PCI ethernet card with firmware index “1”:

PCI ethernet card in hotplug slot with firmware index number:

PCI ethernet multi-function card with 2 ports:

PCI wlan card:

USB built-in 3G modem:

USB Android phone:

How to turn it off

There are 4 ways to turn it off and get back your old trusted network interface names (like ethX etc.):

Boot the kernel with net.ifnames=0 (might also need biosdevname=0)

Disable the assignment of fixed names so that the unpredictable kernel names are used again by masking udev’s rule file for the default policy:
ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
(since v209: this file was called 80-net-name-slot.rules in release v197 through v208)

Use your own manual naming scheme (e.g. “internet0”, “dmz0” or “lan0”) by creating your own udev rules file and set the NAME property for the devices. Make sure to order it before the default policy file, for example by naming it
/etc/udev/rules.d/70-my-net-names.rules

Alter the default policy file for picking a different naming scheme for example for naming all interface names after their MAC address by default:
cp /usr/lib/udev/rules.d/80-net-setup-link.rules /etc/udev/rules.d/80-net-setup-link.rules
Then edit the file there and change the lines as necessary.

More information here.