~Toughbooktalk~

When touchscreen calibration (xinput_calibrator) is not readily available with the Linux distribution following Jeff's tweaks here and elsewhere, I go to this link:
https://launchpad.net/~tias/+archive/ub ... brator-ppa
The inventer, Tias Guns gives directions on adding the PPA that allows software center to add the program to your system. Once it has been added, you can then follow Jeff's tweaks and get your touchscreen calibrated. As a kudos, here is a bio link for Tias Guns: http://people.cs.kuleuven.be/~tias.guns/
Best regards,
Time to hit the Salt Mines

I "re-found" this link, looking for this code Sadlmkr provided:
xset m 8 1
ran it in Terminal because my mouse was quite laggy on the CF-28
running Debian MicroWattR8. Now me mouse is very "perky".
Thanks Lefty

Bump

kode-niner wrote:I don't know why I didn't think of looking at this, but xinput_calibrator has all the options to write directly to a file without the extra crap.

Code: Select all

xinput_calibrator --output-type xorg.conf.d --output-filename /etc/X11/xorg.conf.d/99-calibration.conf

I forgot one thing from your earlier post which caused several crashes and

On an early post you said"go into the 99.conf file and delete the xtra krap." KRASH if you don't DO that or better yet use the quoted line above.

WHAT IT DOES:
1. Name the file/program in terminal. (xinput_calibrator)
2. Tell it to make it look like an xorg.conf.d file.
3. Name the output file name. 99-etc.

One thing missing is the /etc/X11/xorg.conf.d/ DIRECTORY.

So either #or: #at least on Makulu this directory is there already.

Testing.

Too much information?

Sometimes I write to clear my head.

Clarification and confusion start and end with the same letter.

Nice picture.

Still I find it interesting that Makulu had a version of xinput_calibrator compiled without xorg.conf.d support, making the extra-crap-removal mandatory.

First one I have seen where xinput was not already loaded in the package manager.

Maybe we should send the writer a Toughbook.

I was a bit surprised to have it send the whole package into 99-calib.

NOW WHAT????.....CF-31 F1/F2 dysfunctional.....

kode, what do you do with recommendations to install acpi ..........wait a minute I'll look up the text....

ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

I've been switching this drive through three different Marks of 30 ...and presently on CF-31. There have always been subtle differences between Marks generally ACPI related since MINT 10 and before.

And to confuse myself a bit more I have a DVD Cinannamon Debian 2.0 (2.16 now?) and a downloaded 2.88.

2.88 is a little smoother. (and 64bit FWIW)

Sadlmkr wrote: kode, what do you do with recommendations to install acpi ..........wait a minute I'll look up the text....

ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

That's a message you get when your OS boots up, right? I would probably ignore it if my stuff works. I'd only track down the ACPI module for whatever piece of hardware that needs it if the native driver is causing conflicts with something else.

A line from dmesg.