Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a problem with the touchscreen of my new convertible. If I do a touch and the previous touch was just moments ago, everything works fine. However, if the previous touch was about 3 seconds or more ago and I do a touch, only the touchdown event gets triggered and the touch doesn't get released (resulting in a right click after a moment).
I am using debian with gnome at the moment, but a quick test with fedora gave exactly the same behavior. Depending on the time difference to the previous touch, the touch gets handled correctly or just the touchdown event is recognized.
It seems to be a race condition, because if I do a long touch (about 0.5s), it works independent of the delay to the previous touch. I assume something switches back to touchpad mode after 3 seconds and is then too slow to switch to touchscreen mode again. However, disabling the touchpad or unloading the psmouse driver did not help.
Does anybody have an idea how to fix this? It's pretty annoying because it makes my touchscreen useless.
Distribution: K/Ubuntu 18.04-14.04, Scientific Linux 6.3-6.4, Android-x86, Pretty much all distros at one point...
Posts: 1,802
Rep:
It seems a lot of the people installing Linux on that machine simply blacklisted the touchscreen driver to get it to even install. Someone else blacklisted the tilt sensors...
Thanks for your research. I had similar problems like the people in this thread with experiencing kernel panics (Arch Linux and Fedora). However, the newest Debian testing version worked out of the box without any troubles including screen rotation, keyboard auto-disable etc. except for this touchscreen-bug.
Blacklisting the tile sensors did not help unfortunately.
For those struggling with the same problem: I found a (hacked) workaround. I wrote a little program that analyzes the output of the driver. If within the last 150ms nothing happened, but the touchscreen still says that the touch is active, the program simulates a touch-release event.
As can be seen, the program uses the device file in /dev to analyze the output and simulate new input. The event-number should be adopted to fit your system.
It's just an ugly hack, but works more or less for me. Anyways, if somebody could find a solution that fixes the driver or whatever is the problem, this would of course be much nicer.
I had just noticed this last night on my new ThinkPad Yoga, with the stylus as well, so you are not alone. I haven't had a chance to play, but now that I know I'm not alone I'll research further, let you know what I come up with if I have the time.
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch, AntiX, ArtiX
Posts: 1,364
Rep:
... shot in the dark, here ... : The behaviour you're describing reminds me of an issue I had with another type of device where the power management software was suspending certain peripherals after a few seconds of inactivity. I was able to control this with powertop. ... Might be worth a look ...
I disabled "Runtime PM for I2C Adapter i2c-10 (Synopsys DesignWare I2C adapter)" in powertop and now my touchscreen works flawless, even without the script. I hope the touchscreen does not drain my battery too much, but if this would be the case I could also manually turn it off and on.
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch, AntiX, ArtiX
Posts: 1,364
Rep:
Quote:
Originally Posted by silvanm
Thanks a lot, that worked!
I disabled "Runtime PM for I2C Adapter i2c-10 (Synopsys DesignWare I2C adapter)" in powertop and now my touchscreen works flawless, even without the script. I hope the touchscreen does not drain my battery too much, but if this would be the case I could also manually turn it off and on.
Anyways, thanks for the hint, that was great.
Cool - glad I could help you in finding the solution, silvanm. For better general battery-saving and power management performance, I've found laptop-mode-tools and xfce4-power-manager useful, even with DE's that come with their own PM stuff (i.e. Gnome). Depending on your hardware, your mileage may vary, and of course powertop remains a useful troubleshooting and fine-tuning tool.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.