Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

2 votes
2 answers
2853 views
Working acpi kernel options for Asus FX503VD?
On kernel version *4.15.0-sabayon*, the only way to load X is with the kernel options: acpi_osi=! acpi_osi='Windows 2009' (and `acpi=off` but that's radical and leaves me with no sensors). Otherwise I get unresponsive black screen and no obvious error in the `X.org log`. The problem with this option...
On kernel version *4.15.0-sabayon*, the only way to load X is with the kernel options: acpi_osi=! acpi_osi='Windows 2009' (and acpi=off but that's radical and leaves me with no sensors). Otherwise I get unresponsive black screen and no obvious error in the X.org log. The problem with this option is that it turns off the *Elan 1200 touchpad* (not only for me, other people complain about it as well). So I'm looking for other (if possible tested) kernel options which might work on my laptop (or similar). I've tested already many permutations of different windows versions and modeset and acpi_rev_override=5 and pcie_port_pm=off, but obviously I can't cover them all so if anyone had success with this, please share.
jane_xxx (51 rep)
May 5, 2018, 08:09 PM • Last activity: Aug 4, 2025, 02:04 AM
0 votes
1 answers
2416 views
Debugging an unresponsive touchpad on Lenovo Ideapad 320-15ABR
I have a Lenovo Ideapad 320-15ABR, (I found the exact model name with `dmidecode`). I'm having trouble getting the touchpad to work. It's not showing up in `xinput --list` or `cat /proc/bus/input/devices`. I'm using Linux 4.13.2, compiled with some extra debugging messages. Here's some relevant dmes...
I have a Lenovo Ideapad 320-15ABR, (I found the exact model name with dmidecode). I'm having trouble getting the touchpad to work. It's not showing up in xinput --list or cat /proc/bus/input/devices. I'm using Linux 4.13.2, compiled with some extra debugging messages. Here's some relevant dmesg output when booted with i8042.nopnp. Without this option, I get the message: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp $ dmesg|grep psm [ 2.595815] bus: 'serio': add driver psmouse [ 2.627475] bus: 'serio': driver_probe_device: matched device serio1 with driver psmouse [ 2.627477] bus: 'serio': really_probe: probing driver psmouse with device serio1 [ 2.627482] psmouse serio1: no default pinctrl state [ 2.651584] psmouse: probe of serio1 rejects match -19 $ dmesg|grep i8042 [ 2.577522] i8042: PNP detection disabled [ 2.578648] Registering platform device 'i8042'. Parent at platform [ 2.578650] device: 'i8042': device_add [ 2.578655] bus: 'platform': add device i8042 [ 2.578668] PM: Adding info for platform:i8042 [ 2.578682] bus: 'platform': add driver i8042 [ 2.578692] bus: 'platform': driver_probe_device: matched device i8042 with driver i8042 [ 2.578694] bus: 'platform': really_probe: probing driver i8042 with device i8042 [ 2.578699] i8042 i8042: no default pinctrl state [ 2.578702] devices_kset: Moving i8042 to end of list [ 2.595059] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 2.595070] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 2.595125] driver: 'i8042': driver_bound: bound to device 'i8042' [ 2.595150] bus: 'platform': really_probe: bound device i8042 to driver i8042 [ 2.604184] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 **edit:** I've opened a ticket here in case anyone is interested in following this problem: https://bugzilla.kernel.org/show_bug.cgi?id=196985
nnyby (125 rep)
Sep 18, 2017, 05:10 PM • Last activity: Jul 30, 2025, 10:07 PM
1 votes
4 answers
3842 views
How to enable Tap to click on MATE desktop (Debian 8.7 powerpc)
Using advice from this forum, I got tap to click working in LXDE on my Powerbook G4 running Debian 8.7. I have since been experimenting with the MATE desktop, how do I get tap to click working in MATE? Thank you.
Using advice from this forum, I got tap to click working in LXDE on my Powerbook G4 running Debian 8.7. I have since been experimenting with the MATE desktop, how do I get tap to click working in MATE? Thank you.
Simon Baldwin (567 rep)
Jan 26, 2017, 08:12 AM • Last activity: Jul 27, 2025, 01:06 PM
2 votes
2 answers
2601 views
Asus TUF Ubuntu 18.04.1 elantech mouse freezes frequently
I purchased a ASUS TUF FX504GE laptop and dual booted it with Ubuntu 18.04.1 .After which my elantech touchpad stopped working.I updated my kernel to 4.20.6, after which it does work,but freezes unexpectedly for 3-4 minutes. After searching about this problem, for some people updating to 4.20 was th...
I purchased a ASUS TUF FX504GE laptop and dual booted it with Ubuntu 18.04.1 .After which my elantech touchpad stopped working.I updated my kernel to 4.20.6, after which it does work,but freezes unexpectedly for 3-4 minutes. After searching about this problem, for some people updating to 4.20 was the solution but still there are peoplefor whom this didn't work. Some solutions recommended running xinput. My results are below:
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ ELAN1200:00 04F3:3090 Touchpad         	id=13	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Asus Wireless Radio Control             	id=7	[slave  keyboard (3)]
    ↳ Video Bus                               	id=8	[slave  keyboard (3)]
    ↳ Video Bus                               	id=9	[slave  keyboard (3)]
    ↳ Power Button                            	id=10	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=11	[slave  keyboard (3)]
    ↳ USB2.0 HD UVC WebCam: USB2.0 HD         	id=12	[slave  keyboard (3)]
    ↳ Asus WMI hotkeys                        	id=14	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=15	[slave  keyboard (3)]
The output shows id=13 as ELAN1200 touchpad. For the solutions suggested, this was wrongly set to PS/2 etc etc. But for me this value is correct. I need to solve this issue.
Srajan Soni (21 rep)
Feb 2, 2019, 02:56 PM • Last activity: Jul 26, 2025, 05:05 PM
0 votes
0 answers
52 views
Problem with touchpad lag running Linux on X1 carbon gen 7
I bought this second hand laptop one month ago (Lenovo X1 carbon gen7) and I started installing Arch Linux on it and I noticed there was a problem with the touch pad. The touchpad works at the end but lags something and the feeling is not smooth as it has to be normally, I cannot explain my issue be...
I bought this second hand laptop one month ago (Lenovo X1 carbon gen7) and I started installing Arch Linux on it and I noticed there was a problem with the touch pad. The touchpad works at the end but lags something and the feeling is not smooth as it has to be normally, I cannot explain my issue better than this. So now I tried another OS, I'm trying NixOS and I still have the same issue.I also tried to change battery cause maybe the old battery could cause some issues but nothing. So I decided to ask you that maybe you know what can be the problem. From the dmesg --level=err,warn I got the following:
[    0.281813] Transient Scheduler Attacks: MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html  for more details.
[    0.700594] pnp 00:09: disabling [mem 0x000c0000-0x000c3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.700601] pnp 00:09: disabling [mem 0x000c8000-0x000cbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.700605] pnp 00:09: disabling [mem 0x000d0000-0x000d3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.700608] pnp 00:09: disabling [mem 0x000d8000-0x000dbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[    0.847790] hpet_acpi_add: no address or irqs in _CRS
[    0.881477] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    3.262763] booting system configuration /nix/store/rh1r691mrs6v1hzrz7vdiwr7jscr6965-nixos-system-nixos-25.05.806427.32a4e8794210
[    4.637919] resource: resource sanity check: requesting [mem 0x00000000fed10000-0x00000000fed15fff], which spans more than pnp 00:06 [mem 0xfed10000-0xfed13fff]
[    4.637923] caller snb_uncore_imc_init_box+0x86/0xe0 [intel_uncore] mapping multiple BARs
[    4.944104] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
[    5.125487] iwlwifi 0000:00:14.3: WRT: Overriding region id 0
[    5.125492] iwlwifi 0000:00:14.3: WRT: Overriding region id 1
[    5.125494] iwlwifi 0000:00:14.3: WRT: Overriding region id 2
[    5.125496] iwlwifi 0000:00:14.3: WRT: Overriding region id 3
[    5.125498] iwlwifi 0000:00:14.3: WRT: Overriding region id 4
[    5.125500] iwlwifi 0000:00:14.3: WRT: Overriding region id 6
[    5.125502] iwlwifi 0000:00:14.3: WRT: Overriding region id 8
[    5.125504] iwlwifi 0000:00:14.3: WRT: Overriding region id 9
[    5.125506] iwlwifi 0000:00:14.3: WRT: Overriding region id 10
[    5.125508] iwlwifi 0000:00:14.3: WRT: Overriding region id 11
[    5.125510] iwlwifi 0000:00:14.3: WRT: Overriding region id 15
[    5.125512] iwlwifi 0000:00:14.3: WRT: Overriding region id 16
[    5.125514] iwlwifi 0000:00:14.3: WRT: Overriding region id 18
[    5.125516] iwlwifi 0000:00:14.3: WRT: Overriding region id 19
[    5.125518] iwlwifi 0000:00:14.3: WRT: Overriding region id 20
[    5.125519] iwlwifi 0000:00:14.3: WRT: Overriding region id 21
[    5.125522] iwlwifi 0000:00:14.3: WRT: Overriding region id 28
[    5.223140] spi-nor spi0.0: supply vcc not found, using dummy regulator
[    5.781228] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not yet available, widget card binding deferred
[    6.890891] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
[    7.941680] nvme nvme0: using unchecked data buffer
[   51.874573] intel_pch_thermal 0000:00:12.0: CPU-PCH current temp [58C] higher than the threshold temp [50C], S0ix might fail. Start cooling...
[   60.615650] intel_pch_thermal 0000:00:12.0: Wakeup event detected, abort cooling
[  153.163522] intel_pch_thermal 0000:00:12.0: CPU-PCH current temp [50C] higher than the threshold temp [50C], S0ix might fail. Start cooling...
[ 2611.805595] warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Where the error is just:
[    4.944104] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
If you can help me also to understand how to diagnose and solve these problems it would be really nice, thanks in advance. --- I also tried to blacklisted the i2c_i801 module and the error doesn't appear anymore but the lag of the touchpad still persist. --- After three days of work I realize that maybe the problem of SMBus has nothing to do with the touchpad. And the problem with the touchpad is another one but I really cannot solve it. I can show you the journalctl -p 3 results:
lug 22 19:11:28 nixos kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
lug 22 19:13:17 nixos kwin_wayland: kwin_libinput: Libinput: event12 - SYNA8005:00 06CB:CD8C Touchpad: kernel bug: Touch jump detected and discarded.
                                          See https://wayland.freedesktop.org/libinput/doc/1.27.1/touchpad-jumping-cursors.html  for details
lug 22 19:13:25 nixos kwin_wayland: kwin_libinput: Libinput: event12 - SYNA8005:00 06CB:CD8C Touchpad: kernel bug: Touch jump detected and discarded.
                                          See https://wayland.freedesktop.org/libinput/doc/1.27.1/touchpad-jumping-cursors.html  for details
lug 22 19:13:26 nixos kwin_wayland: kwin_libinput: Libinput: event12 - SYNA8005:00 06CB:CD8C Touchpad: kernel bug: Touch jump detected and discarded.
                                          See https://wayland.freedesktop.org/libinput/doc/1.27.1/touchpad-jumping-cursors.html  for details
lug 22 19:15:44 nixos kwin_wayland: kwin_libinput: Libinput: event12 - SYNA8005:00 06CB:CD8C Touchpad: kernel bug: Touch jump detected and discarded.
                                          See https://wayland.freedesktop.org/libinput/doc/1.27.1/touchpad-jumping-cursors.html  for details
lug 22 19:17:01 nixos kwin_wayland: kwin_libinput: Libinput: event12 - SYNA8005:00 06CB:CD8C Touchpad: kernel bug: Touch jump detected and discarded.
                                          See https://wayland.freedesktop.org/libinput/doc/1.27.1/touchpad-jumping-cursors.html  for details
lug 22 19:17:01 nixos kwin_wayland: kwin_libinput: Libinput: event12 - SYNA8005:00 06CB:CD8C Touchpad: WARNING: log rate limit exceeded (5 msgs per 24h). Discarding future messages.
So, there is this problem with libinput that maybe makes the touchpad lagging. Please help me :(.
michael pasqui (101 rep)
Jul 17, 2025, 05:07 PM • Last activity: Jul 22, 2025, 05:53 PM
1 votes
1 answers
91 views
ThinkPad T14 Gen1 - Trackpoint - Wayland - Stops working during usage
I have a Lenovo ThinkPad T14 gen1 for more than a year now and I run it with Ubuntu 24.04 LTS. Since that I have the problem with the trackpoint, that during usage it stops working randomly. I still can use the touchpad. The only solution is: reboot, standby or run `sudo modprobe -r psmouse && sudo...
I have a Lenovo ThinkPad T14 gen1 for more than a year now and I run it with Ubuntu 24.04 LTS. Since that I have the problem with the trackpoint, that during usage it stops working randomly. I still can use the touchpad. The only solution is: reboot, standby or run sudo modprobe -r psmouse && sudo modprobe psmouse When the trackpoint stopped working and I run sudo evtest /dev/input/event13 I also see that it has no action anymore. Besides I run sudo dmesg | grep -i -e psmouse -e trackpoint -e serio but I did it after the modprobe, because the trackpoint stopped working while I was clicking something and the click hang as well. The output is: [ 0.881089] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 0.881107] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 0.883951] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 [ 2.047781] psmouse serio1: synaptics: queried max coordinates: x [..5678], y [..4694] [ 2.084079] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1162..] [ 2.084086] psmouse serio1: synaptics: Trying to set up SMBus access [ 2.087100] psmouse serio1: synaptics: SMbus companion is not ready yet [ 2.155641] psmouse serio1: synaptics: Touchpad model: 1, fw: 10.32, id: 0x1e2a1, caps: 0xf014a3/0x940300/0x12e800/0x500000, board id: 3471, fw id: 2909640 [ 2.155652] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [ 2.196323] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5 [ 2.673734] psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x11, buttons: 3/3 [ 2.880435] input: TPPS/2 Elan TrackPoint as /devices/platform/i8042/serio1/serio2/input/input6 [ 5.177567] psmouse serio1: synaptics: queried max coordinates: x [..5678], y [..4694] [ 5.207013] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1162..] [ 5.207025] psmouse serio1: synaptics: Trying to set up SMBus access [ 5.587289] serio: RMI4 PS/2 pass-through port at rmi4-00.fn03 [ 5.706040] psmouse serio3: trackpoint: Elan TrackPoint firmware: 0x11, buttons: 3/3 [ 5.744593] input: TPPS/2 Elan TrackPoint as /devices/pci0000:00/0000:00:1f.4/i2c-0/0-002c/rmi4-00/rmi4-00.fn03/serio3/input/input18 [17021.800494] psmouse serio1: synaptics: queried max coordinates: x [..5678], y [..4694] [17021.833970] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1162..] [17021.833996] psmouse serio1: synaptics: Trying to set up SMBus access [17022.136075] serio: RMI4 PS/2 pass-through port at rmi4-01.fn03 [17022.249496] psmouse serio4: trackpoint: Elan TrackPoint firmware: 0x11, buttons: 3/3 [17022.296166] input: TPPS/2 Elan TrackPoint as /devices/pci0000:00/0000:00:1f.4/i2c-0/0-002c/rmi4-01/rmi4-01.fn03/serio4/input/input22 I mean, I have a workaround, but it is still annoying. Any idea what else I can try? some other log to check? I also read about switching to PS/2 but this will disable the scrolling functionality.
Stephan (119 rep)
Jul 19, 2025, 02:35 PM • Last activity: Jul 20, 2025, 11:53 AM
7 votes
1 answers
2697 views
syndaemon won't disable touchpad while typing
I am trying to use syndaemon to disable my touchpad while I type. I know that the GUI for this doesn't work for many people but all the posts I've seen online suggest that using syndaemon from the command line should work. It doesn't work for me, however. To test whether the touchpad is off while I...
I am trying to use syndaemon to disable my touchpad while I type. I know that the GUI for this doesn't work for many people but all the posts I've seen online suggest that using syndaemon from the command line should work. It doesn't work for me, however. To test whether the touchpad is off while I type, I type with one hand while moving the mouse and clicking with the other. I've also tried turning on palm detection, which I test just by typing for a while and seeing if I get a touchpad click (I always do, pretty promptly). Linux Mint 17.2 Rafaela (installed it yesterday) Dell Inspiron 11 3000 series * Output of xinput list: > xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ DLL064D:00 06CB:2985 id=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Video Bus id=8 [slave keyboard (3)] ↳ Power Button id=9 [slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)] ↳ Dell WMI hotkeys id=15 [slave keyboard (3)] What I've tried so far: * Control Center -> Mouse -> disable touchpad while typing: no effect * gpointing-device-settings: shows two touchpads: * DLL0446:00 06CB:2985: enable palm detection -> no effect; when I disable this touchpad, my touchpad becomes unresponsive * SynPS/2 Synaptics Touchpad: disabled (turning it on and modifying settings seems to have no effect) * syndaemon: killall syndaemon; syndaemon -i 10 -K -d: no effect (also tried with -R). ps aux | egrep syndaemon shows that no other syndaemon processes are running. I have tried this with and without the "disable touchpad while typing" checkbox set in Mouse Preferences. * synclient: synclient PalmDetect=1 PalmMinWidth=10 PalmMinZ=200: no effect I am at my wit's end. The solutions attempted above seem to work for everyone else! Why can't I get syndaemon to work for me?
Jessica Hekman (71 rep)
Jul 19, 2015, 07:00 PM • Last activity: Jul 5, 2025, 02:02 AM
7 votes
1 answers
4888 views
Very High CPU Usage By IRQ #16
I recently noticed that one of my CPUs was idling at around 85-90% and according to `top` the usage was coming from interrupts, so [just like in this question][1] I used a combination of `dmesg` and periodically `cat`ing `/proc/interrupts` and found out this: CPU0 CPU1 CPU2 CPU3 0: 17 0 0 0 IR-IO-AP...
I recently noticed that one of my CPUs was idling at around 85-90% and according to top the usage was coming from interrupts, so just like in this question I used a combination of dmesg and periodically cating /proc/interrupts and found out this: CPU0 CPU1 CPU2 CPU3 0: 17 0 0 0 IR-IO-APIC 2-edge timer 1: 11548 0 2429 0 IR-IO-APIC 1-edge i8042 8: 0 0 0 1 IR-IO-APIC 8-edge rtc0 9: 7 16 0 0 IR-IO-APIC 9-fasteoi acpi 12: 14530 108887 0 0 IR-IO-APIC 12-edge i8042 16: 78464100 0 0 11702812 IR-IO-APIC 16-fasteoi idma64.0, i2c_designware.0, i801_smbus 120: 0 0 0 0 DMAR-MSI 0-edge dmar0 121: 0 0 0 0 DMAR-MSI 1-edge dmar1 As you can see, IRQ #16 is sending interrupts like crazy (every time the CPU wakes up from S3 it seems to start spamming a different CPU), I also found out that my touchpad uses the same IRQ and if the I2C mode is enabled (or *advanced* mode, according to my BIOS), it randomly stops working with the following messages (from dmesg): [ 167.851139] irq 16: nobody cared (try booting with the "irqpoll" option) [ 167.851158] CPU: 2 PID: 3874 Comm: firefox Not tainted 4.15.3-300.fc27.x86_64 #1 [ 167.851160] Hardware name: Acer Aspire E5-575/Ironman_SK , BIOS V1.04 04/26/2016 [ 167.851162] Call Trace: [ 167.851171] [ 167.851185] dump_stack+0x5c/0x85 [ 167.851193] __report_bad_irq+0x30/0xc0 [ 167.851196] note_interrupt+0x235/0x280 [ 167.851198] handle_irq_event_percpu+0x51/0x70 [ 167.851201] handle_irq_event+0x27/0x50 [ 167.851204] handle_fasteoi_irq+0x6b/0x120 [ 167.851209] handle_irq+0xaf/0x120 [ 167.851214] do_IRQ+0x41/0xc0 [ 167.851219] common_interrupt+0xa2/0xa2 [ 167.851222] [ 167.851224] RIP: 0010:_raw_spin_lock+0x10/0x20 [ 167.851226] RSP: 0000:ffffa85a857dfdd0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdb [ 167.851230] RAX: 0000000000000000 RBX: ffff8d0a268930c8 RCX: 00003ffffffff000 [ 167.851231] RDX: 0000000000000001 RSI: 8000000000000025 RDI: ffffd21648d7ca70 [ 167.851232] RBP: ffffd2164892e100 R08: 0000000000000000 R09: 0000000000171800 [ 167.851233] R10: 0000000000271800 R11: 0000000000001000 R12: 0000000000000000 [ 167.851234] R13: 8000000224b84867 R14: ffffd21648d7ca70 R15: ffff8d0a35f29810 [ 167.851244] __handle_mm_fault+0xa4c/0x1290 [ 167.851249] handle_mm_fault+0xaa/0x1f0 [ 167.851255] __do_page_fault+0x25d/0x4e0 [ 167.851262] ? SyS_mmap_pgoff+0xfb/0x250 [ 167.851264] do_page_fault+0x32/0x110 [ 167.851267] ? page_fault+0x36/0x60 [ 167.851269] page_fault+0x4c/0x60 [ 167.851272] RIP: 0033:0x7ff86dc0b205 [ 167.851273] RSP: 002b:00007ffe6493e888 EFLAGS: 00010206 [ 167.851276] handlers: [ 167.851291] [] idma64_irq [idma64] [ 167.851296] [] i2c_dw_isr [ 167.851302] [] i801_isr [i2c_i801] [ 167.851304] Disabling IRQ #16 Is this a hardware issue? What can I do? ---------- Finally I have a chance to dig more into this, by running lspci -nnkv I found out 2 devices that are using IRQ 16: 00:15.0 Signal processing controller : Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21) Subsystem: Acer Incorporated [ALI] Device [1025:1094] Flags: fast devsel, IRQ 16 Memory at a132b000 (64-bit, non-prefetchable) [size=4K] Capabilities: Power Management version 3 Capabilities: Vendor Specific Information: Len=14 Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci and: 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) Subsystem: Acer Incorporated [ALI] Device [1025:1094] Flags: medium devsel, IRQ 16 Memory at a132e000 (64-bit, non-prefetchable) [size=256] I/O ports at 4040 [size=32] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 The problem seems to go away if I unload the intel_lpss_pci module i.e. rmmod intel_lpss_pci, but of course the touchpad would stop working. But I guess it's better than having a CPU always at 100%.
arielnmz (559 rep)
Mar 1, 2018, 05:25 AM • Last activity: Jun 26, 2025, 02:05 PM
1 votes
2 answers
4310 views
Shortcuts to enable/disable a touchpad in GNOME3 on Wayland
I'm trying to add custom shortcuts to enable/disable a touchpad on my laptop. I have GNOME 3 on Wayland. Using a suggestion from https://unix.stackexchange.com/a/571537/138312, I managed to do it using a terminal. **However**, if I put exactly the same commands into shortcuts (using a GUI, the only...
I'm trying to add custom shortcuts to enable/disable a touchpad on my laptop. I have GNOME 3 on Wayland. Using a suggestion from https://unix.stackexchange.com/a/571537/138312 , I managed to do it using a terminal. **However**, if I put exactly the same commands into shortcuts (using a GUI, the only way I know), they don't work. Does anyone know the solution for this, or any other way around to have shortcuts for a touchpad? Some details, if needed: Lenovo Thinkpad T450s, Debian 9, Gnome 3.22.2
Karen Fidanyan (11 rep)
Jun 15, 2020, 03:08 PM • Last activity: Jun 21, 2025, 11:49 PM
1 votes
1 answers
809 views
Disable physical left click on touchpad but keeping tap
I need to disable the clicking on touchpad as my touchpad is a bit broken and get stuck specifically on the left side. Unfortunately I am unable to find the one-line command.
I need to disable the clicking on touchpad as my touchpad is a bit broken and get stuck specifically on the left side. Unfortunately I am unable to find the one-line command.
Alessio_110 (411 rep)
Jan 23, 2022, 07:03 PM • Last activity: Jun 13, 2025, 04:01 PM
3 votes
1 answers
658 views
Finding the right drivers in the linux kernel
I have an ELAN touch-pad with vendor id 04F3:3128 and I'm trying to find the right Linux kernel drivers to support it. I will start by noting that the touch-pad works with live CDs, like for example Linux Mint. I can, however, not seem to find the right settings in the kernel to get it to work. (On...
I have an ELAN touch-pad with vendor id 04F3:3128 and I'm trying to find the right Linux kernel drivers to support it. I will start by noting that the touch-pad works with live CDs, like for example Linux Mint. I can, however, not seem to find the right settings in the kernel to get it to work. (On a live CD where the mouse pad works) if I go into /sys/bus/hid/devices, I can find the device here listed as 0018:04F3:3128.0001. If I then cd into the device and then into the subsystem directory and then further into the directory drivers, here I can find hid-generic and hid-multitouch. I have enabled those using make nconfig and compiled the kernel, but it still can't find the mouse pad. How can I find the proper settings (or modules) in the kernel to support my mouse pad?
spinosarus123 (175 rep)
May 5, 2022, 05:17 PM • Last activity: Jun 11, 2025, 12:55 AM
3 votes
3 answers
3732 views
Fedora 26--Trackpad Stops Working
I recently updated my laptop from Fedora 25 to 26. After the update, sometimes, usually after I close the lid, the trackpad stops working entirely. I can't move the pointer, click, or scroll. Currently, I'm just restarting my computer from the terminal when this happens, which is very annoying. I've...
I recently updated my laptop from Fedora 25 to 26. After the update, sometimes, usually after I close the lid, the trackpad stops working entirely. I can't move the pointer, click, or scroll. Currently, I'm just restarting my computer from the terminal when this happens, which is very annoying. I've tried the following: - Boot the Fedora 25 kernel from Grub - Install the old mouse driver (xorg-x11-drv-synaptics-legacy) - Remove psmouse from the kernel and add it back (it says modprobe: FATAL: Module psmouse is builtin.) None of these have worked. Anyone know how to fix this? **EDIT:** Here is the output of dmesg | grep mouse after it has frozen: [ 0.819297] mousedev: PS/2 mouse device common for all mice [ 1.585896] psmouse serio1: synaptics: queried max coordinates: x [..5664], y [..4708] [ 1.612130] psmouse serio1: synaptics: queried min coordinates: x [1276..], y [1146..] [ 1.664277] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2a1, caps: 0xf00623/0x840300/0x12e800/0x400000, board id: 3096, fw id: 2430125 [ 1455.599299] psmouse serio1: Failed to disable mouse on isa0060/serio1 [ 1457.549499] psmouse serio1: synaptics: queried max coordinates: x [..5664], y [..4708] [ 1457.575672] psmouse serio1: synaptics: queried min coordinates: x [1276..], y [1146..] [ 1933.961382] psmouse serio1: Failed to disable mouse on isa0060/serio1 [ 1935.980668] psmouse serio1: synaptics: Unable to query device. Also, even if the trackpad doesn't work, a USB mouse still does.
James Westman (131 rep)
Jul 20, 2017, 12:52 PM • Last activity: Jun 1, 2025, 11:05 PM
0 votes
1 answers
1944 views
How to emulate touch event by writing to /dev/input/eventX in Linux?
I am working on an embedded Linux (kernel 5.10.24) with a touch screen. Now I want to trigger touch event by writing to /dev/input/eventX corresponding to the touch screen. To figure out the event I want to emulate, I firstly collected the events by touching the screen. Then I hard coded the events...
I am working on an embedded Linux (kernel 5.10.24) with a touch screen. Now I want to trigger touch event by writing to /dev/input/eventX corresponding to the touch screen. To figure out the event I want to emulate, I firstly collected the events by touching the screen. Then I hard coded the events in codes and write them one by one to the /dev/input/eventX. Below are the events I got from a touching.
~ # ./touchevent
timeS=1651152027,timeUS=312095,type=3,code=57,value=50
timeS=1651152027,timeUS=312095,type=3,code=53,value=218
timeS=1651152027,timeUS=312095,type=3,code=54,value=1223
timeS=1651152027,timeUS=312095,type=3,code=48,value=54
timeS=1651152027,timeUS=312095,type=3,code=58,value=54
timeS=1651152027,timeUS=312095,type=1,code=330,value=1
timeS=1651152027,timeUS=312095,type=0,code=0,value=0
timeS=1651152027,timeUS=448388,type=3,code=57,value=-1
timeS=1651152027,timeUS=448388,type=1,code=330,value=0
timeS=1651152027,timeUS=448388,type=0,code=0,value=0
I hardcoded the first 7 events (including an EV_SYN) to write to /dev/input/eventX.
#include 
#include 
#include 
#include 
#include 
int main( void )
{
        int                     fd;
        int                     ret;
        struct input_event      event;

        fd = open( "/dev/input/event0", O_RDWR);
        if ( fd < 0 )
        {
                perror( "/dev/input/event0" );
                return(-1);
        }

        event.type = 3;
        event.code = 53;
        event.value = 218;
        ret     = write( fd, &event, sizeof(struct input_event) );
        printf("ret: %d\n", ret);

        event.type = 3;
        event.code = 54;
        event.value = 1223;
        ret     = write( fd, &event, sizeof(struct input_event) );
        printf("ret: %d\n", ret);

        event.type = 3;
        event.code = 48;
        event.value = 54;
        ret     = write( fd, &event, sizeof(struct input_event) );
        printf("ret: %d\n", ret);

        event.type = 3;
        event.code = 58;
        event.value = 54;
        ret     = write( fd, &event, sizeof(struct input_event) );
        printf("ret: %d\n", ret);

        event.type = 1;
        event.code = 330;
        event.value = 1;
        ret     = write( fd, &event, sizeof(struct input_event) );
        printf("ret: %d\n", ret);

        event.type = 0;
        event.code = 0;
        event.value = 0;
        ret     = write( fd, &event, sizeof(struct input_event) );
        printf("ret: %d\n", ret);

        close( fd );
.....
}
When I ran the code on the target, there is NO expected response from the touch screen. I am not sure if it is possible to emulate touch events by writing to /dev/input/eventX, if so, what did I miss on doing it ? I don't have sendevent/getevent tools from Andriod, and I want to do this by myself.
wangt13 (631 rep)
May 5, 2023, 01:31 AM • Last activity: May 30, 2025, 10:07 AM
5 votes
1 answers
2783 views
How to check if If i2c-hid and hid-rmi are not used for touchpad?
I'm seeing the following warning in `dmesg`: [ 2.631179] psmouse serio2: synaptics: Your touchpad (PNP: SYN1218 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kerne...
I'm seeing the following warning in dmesg: [ 2.631179] psmouse serio2: synaptics: Your touchpad (PNP: SYN1218 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kernel.org. ... [ 2.819449] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input10 The touchpad works, but I feel that it is not working as well as it used to. I'm on Gentoo with a custom configured kernel. I've recently switched to other distros and came back to Gentoo and reconfigured the kernel from the ground up. I don't believe I did something out of the ordinary with regards to the input devices, so this *might* be a bug as suggested in dmesg. $ uname -r 5.1.4-gentoo $ grep -E 'INPUT|I2C_HID|HID_RMI' .config CONFIG_RFKILL_INPUT=y CONFIG_INPUT=y CONFIG_INPUT_LEDS=m CONFIG_INPUT_FF_MEMLESS=y CONFIG_INPUT_POLLDEV=y CONFIG_INPUT_SPARSEKMAP=m # CONFIG_INPUT_MATRIXKMAP is not set # CONFIG_INPUT_MOUSEDEV is not set # CONFIG_INPUT_JOYDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set CONFIG_INPUT_KEYBOARD=y CONFIG_INPUT_MOUSE=y CONFIG_INPUT_JOYSTICK=y CONFIG_INPUT_TABLET=y CONFIG_INPUT_TOUCHSCREEN=y CONFIG_INPUT_MISC=y # CONFIG_INPUT_AD714X is not set # CONFIG_INPUT_BMA150 is not set # CONFIG_INPUT_E3X0_BUTTON is not set # CONFIG_INPUT_MSM_VIBRATOR is not set # CONFIG_INPUT_PCSPKR is not set # CONFIG_INPUT_MMA8450 is not set # CONFIG_INPUT_APANEL is not set # CONFIG_INPUT_ATLAS_BTNS is not set # CONFIG_INPUT_ATI_REMOTE2 is not set # CONFIG_INPUT_KEYSPAN_REMOTE is not set # CONFIG_INPUT_KXTJ9 is not set # CONFIG_INPUT_POWERMATE is not set # CONFIG_INPUT_YEALINK is not set # CONFIG_INPUT_CM109 is not set # CONFIG_INPUT_UINPUT is not set # CONFIG_INPUT_PCF8574 is not set # CONFIG_INPUT_ADXL34X is not set # CONFIG_INPUT_IMS_PCU is not set # CONFIG_INPUT_CMA3000 is not set # CONFIG_INPUT_IDEAPAD_SLIDEBAR is not set # CONFIG_INPUT_DRV2665_HAPTICS is not set # CONFIG_INPUT_DRV2667_HAPTICS is not set CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y CONFIG_USB_PWC_INPUT_EVDEV=y CONFIG_SND_JACK_INPUT_DEV=y # CONFIG_SND_HDA_INPUT_BEEP is not set CONFIG_HID_RMI=y CONFIG_I2C_HID=y > If i2c-hid and hid-rmi are not used **My question**: how do I check if those are not used? > you might want to try setting psmouse.synaptics_intertouch to 1 $ sudo sysctl -a | grep "psmouse.synaptics_intertouch" Returns nothing, so nothing to set there.
Tim (1104 rep)
May 25, 2019, 09:22 AM • Last activity: May 20, 2025, 05:06 PM
11 votes
3 answers
19718 views
How do I enable two finger right click in Ubuntu GNOME?
I just installed it, and I can't figure out how to do two finger right click by tapping the touchpad. Additionally, I just discovered that I can't tap to click either! Help?
I just installed it, and I can't figure out how to do two finger right click by tapping the touchpad. Additionally, I just discovered that I can't tap to click either! Help?
Corey Levinson (359 rep)
Sep 25, 2019, 06:46 PM • Last activity: May 18, 2025, 06:02 AM
1 votes
1 answers
1996 views
How do I change touchpad behavior with libinput running under wayland
The typical method of changing trackpad behavior is to edit `/etc/X11/xorg.conf.d/ -synaptics.conf`. I'm running Fedora 25 running GNOME 3.22 and which uses Wayland by default, not X, so there is no ` -synaptics.conf` file in there, just this: ```$ ls /etc/X11/xorg.conf.d/ 00-keyboard.conf ``` So ho...
The typical method of changing trackpad behavior is to edit /etc/X11/xorg.conf.d/-synaptics.conf. I'm running Fedora 25 running GNOME 3.22 and which uses Wayland by default, not X, so there is no -synaptics.conf file in there, just this:
$ ls /etc/X11/xorg.conf.d/
00-keyboard.conf
So how do you change the trackpad behavior in this situation?
iLikeDirt (123 rep)
Nov 21, 2016, 03:52 AM • Last activity: May 13, 2025, 08:08 PM
5 votes
1 answers
2546 views
Wayland Touchpad Jumping - Motion Treshold?
I just switched from Ubuntu 17.10 to Debian Buster Sid, using GNOME 3.26.2. I'm using a Thinkpad T430. See below for more information on my touchpad. $ grep -B 5 mouse /proc/bus/input/devices I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio...
I just switched from Ubuntu 17.10 to Debian Buster Sid, using GNOME 3.26.2. I'm using a Thinkpad T430. See below for more information on my touchpad. $ grep -B 5 mouse /proc/bus/input/devices I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input2 U: Uniq= H: Handlers=mouse0 event1 -- [...] The problem is that **two finger scrolling is very unprecise due to jumping**. While I'm scrolling everything works fine, but as soon as I'm lifting up my fingers to stop, the page just randomly jumps or scrolls a bit randomly up or down. I never experienced such behaviour under Ubuntu. I suspect that the motion threshold is simply to low, so that my lifting figures are detected as another scroll. All solutions for similar issues that I found requiere to edit the conf file which, as I found out, isn't used under Wayland. So I checked gsettings but didn't find a proper key: $ gsettings list-keys org.gnome.desktop.peripherals.touchpad send-events natural-scroll tap-to-click two-finger-scrolling-enabled left-handed click-method speed tap-and-drag edge-scrolling-enabled disable-while-typing How to fix this? Thank you and have a nice day!
DisplayName (51 rep)
Mar 16, 2018, 10:13 AM • Last activity: May 10, 2025, 06:08 PM
8 votes
3 answers
3004 views
IMWheel creates jittery scroll when using touch-pad
Mouse scroll performance is poor in Linux and there is no built-in method to control the same. Hence, I did some digging and came across `IMWheel`. I followed this tutorial [How to Adjust or Increase Mouse Scroll Wheel Speed in Linux][1] and set my mouse scroll speed to 5. This seemed to fix my phys...
Mouse scroll performance is poor in Linux and there is no built-in method to control the same. Hence, I did some digging and came across IMWheel. I followed this tutorial How to Adjust or Increase Mouse Scroll Wheel Speed in Linux and set my mouse scroll speed to 5. This seemed to fix my physical mouse scroll speed. However, scrolling using the touchpad of my laptop is anything but perfect. The page seems to behave erratically and jumps every time a certain amount of page is scrolled and is very unpleasant. On disabling IMWheel, the touchpad behavior seems to return back to normal. Is there any method to have a decent scroll speed for physical mouse and yet keep the existing scrolling experience for the touchpad in Linux? Like it is there in Windows? If there is, please guide me on how to fix this issue. This problem literally keeps me from using Linux at all! Given below are my current mouse and touchpad settings: Current Mouse settings: Current Mouse Settings Current Touchpad settings: Current Touchpad Settings Hardware and Software Details: - OS: Linux Mint Cinnamon 19.1 - Laptop: HP AB032TX (Dual Boot: Windows 10 & Linux Mint) - Software in question: IMWheel - Touchpad Driver: Synaptics (Default drivers that came with Mint) - Physical Mouse: Logitech normal optical mouse
Animikh_Aich (181 rep)
Apr 4, 2019, 02:42 PM • Last activity: May 4, 2025, 09:02 PM
0 votes
0 answers
54 views
disabling I8042 driver completely
"i8042 is still probing even though I disabled CONFIG_SERIO_I8042. Does it have dependent configurations? Even after passing kernel command-line arguments: i8042.nopnp i8042.noaux , I still see an entry at /sys/bus/serio/devices/serio0."
"i8042 is still probing even though I disabled CONFIG_SERIO_I8042. Does it have dependent configurations? Even after passing kernel command-line arguments: i8042.nopnp i8042.noaux , I still see an entry at /sys/bus/serio/devices/serio0."
Malin Shaik (11 rep)
Apr 28, 2025, 05:16 PM
0 votes
1 answers
2222 views
Arch linux touchpad lag
Recently i did a fresh install of arch linux as described in the wiki, and installed gnome along with it. Everything seems to work, but the track pad seems to have a slight delay to it. Not enough to be unusable, but enough to be noticeable and annoying; it's definitely not as smooth as it was on ub...
Recently i did a fresh install of arch linux as described in the wiki, and installed gnome along with it. Everything seems to work, but the track pad seems to have a slight delay to it. Not enough to be unusable, but enough to be noticeable and annoying; it's definitely not as smooth as it was on ubuntu unity. Can someone suggest a fix? I'm using wayland (i think? i'm new to linux) ,and apparently theres no way to config the track pad? Speed is set to max on gnome settings.
nub (11 rep)
Jun 1, 2017, 08:09 AM • Last activity: Apr 28, 2025, 05:02 AM
Showing page 1 of 20 total questions