Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
| 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
07-04-2020, 02:36 PM
|
#1
|
|
LQ Newbie
Registered: Apr 2019
Distribution: Ubuntu
Posts: 12
Rep: 
|
Intermittent Trackpad Issues
Oh! The bane of troubleshooting... the intermittent issue!
Ok, so I have a Asus VivoBook 15 AMD Ryzen 5 laptop that I'm running Fedora on. Sometimes, maybe somewhere between 1/4 to 1/3 of the time when it boots, I have no mouse control through the trackpad. If I plug in a USB mouse that works. I'm hesitant to even mention it becuase its probably just in my head, but it seems to work better if I provide some input to the trackpad while it is booting. I captured the output of some command while it did and didn't work, and I can see the difference, but I don't know what to do with the information. Here's the output:
When it's working:
Code:
$ lsmod | grep hid
hid_multitouch 32768 0
i2c_hid 32768 0
$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ xwayland-pointer:16 id=6 [slave pointer (2)]
⎜ ↳ xwayland-relative-pointer:16 id=7 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ xwayland-keyboard:16 id=8 [slave keyboard (3)]
$ xinput list-props 6
Device 'xwayland-pointer:16':
Device Enabled (119): 1
Coordinate Transformation Matrix (121): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (244): 0
Device Accel Constant Deceleration (245): 1.000000
Device Accel Adaptive Deceleration (246): 1.000000
Device Accel Velocity Scaling (247): 10.000000
When its not working:
Code:
$ lsmod | grep hid
i2c_hid 32768 0
$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ xwayland-keyboard:16 id=6 [slave keyboard (3)]
$ xinput list-props 4
Device 'Virtual core XTEST pointer':
Device Enabled (119): 1
Coordinate Transformation Matrix (121): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
XTEST Device (238): 1
I can see that a module is missing, but how do I fix/prevent it?
Thanks!
Rhys |
|
|
|
|
07-04-2020, 05:12 PM
|
#2
|
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
1) Which version of Fedora are you using?
2) Since you're using a Wayland compositor (I assume Gnome), it may well be an issue with libinput itself. In a Wayland session the X-server (XWayland in this case) doesn't have direct access to the devices. Instead the compositor communicates to XWayland (via the Wayland Protocol) and so they are presented as virtual input devices only. While that doesn't change your problem, it might influence where to look.
Perhaps show the output of this command instead...
Code:
sudo libinput list-devices
3) Diagnostic events can be captured via
Code:
sudo libinput debug-events
You could test if any events are reported when the touchpad is supposedly not responsive to the desktop session. CTRL+C to stop it.
4) You could try running Gnome via an X-session instead. Any difference in touchpad behaviour? |
|
|
1 members found this post helpful.
|
|
07-04-2020, 06:25 PM
|
#3
|
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
Another thing to try: Add 'i8042.reset' to the grub boot parameters. That might help get the touchpad device reliably initialised at boot.
This might show what occurs when working and not...
Code:
dmesg |egrep -i "i8042|input"
|
|
|
1 members found this post helpful.
|
|
07-05-2020, 02:19 PM
|
#4
|
|
LQ Newbie
Registered: Apr 2019
Distribution: Ubuntu
Posts: 12
Original Poster
Rep:
|
Thanks for the replies!
Quote:
|
1) Which version of Fedora are you using?
|
Fedora release 32 (Thirty Two)
NAME=Fedora
VERSION="32 (Workstation Edition)"
ID=fedora
VERSION_ID=32
VERSION_CODENAME=""
PLATFORM_ID="platform:f32"
PRETTY_NAME="Fedora 32 (Workstation Edition)"
Quote:
Perhaps show the output of this command instead...
Code:
sudo libinput list-devices
3) Diagnostic events can be captured via
Code:
sudo libinput debug-events
|
I'll give it a few reboots to see if I can't get it to do the thing again and I'll let you know.
Quote:
|
4) You could try running Gnome via an X-session instead. Any difference in touchpad behaviour?
|
I don't know how to do this. Please advise.
Quote:
This might show what occurs when working and not...
Code:
dmesg |egrep -i "i8042|input"
|
Will also look for when its not working, but heres the output when it is:
Code:
$ dmesg |egrep -i "i8042|input"
[ 1.019496] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:39/PNP0C09:00/PNP0C0D:00/input/input0
[ 1.019557] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[ 1.019615] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
[ 1.019671] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[ 2.067353] i8042: PNP: PS/2 Controller [PNP030b:PS2K] at 0x60,0x64 irq 1
[ 2.067353] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 2.073659] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 2.085411] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
[ 3.392647] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:01/input/input5
[ 3.397833] input: ELAN1300:00 04F3:3087 Mouse as /devices/platform/AMDI0010:01/i2c-0/i2c-ELAN1300:00/0018:04F3:3087.0001/input/input6
[ 3.398009] input: ELAN1300:00 04F3:3087 Touchpad as /devices/platform/AMDI0010:01/i2c-0/i2c-ELAN1300:00/0018:04F3:3087.0001/input/input7
[ 3.398114] hid-generic 0018:04F3:3087.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN1300:00 04F3:3087] on i2c-ELAN1300:00
[ 3.619073] input: ELAN1300:00 04F3:3087 Mouse as /devices/platform/AMDI0010:01/i2c-0/i2c-ELAN1300:00/0018:04F3:3087.0001/input/input8
[ 3.619520] input: ELAN1300:00 04F3:3087 Touchpad as /devices/platform/AMDI0010:01/i2c-0/i2c-ELAN1300:00/0018:04F3:3087.0001/input/input9
[ 3.620235] hid-multitouch 0018:04F3:3087.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN1300:00 04F3:3087] on i2c-ELAN1300:00
[ 8.297784] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:03:00.1/sound/card0/input10
[ 8.361091] snd_hda_codec_realtek hdaudioC1D0: inputs:
[ 8.413855] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:03:00.6/sound/card1/input11
[ 8.520467] input: PC Speaker as /devices/platform/pcspkr/input/input12
[ 8.764378] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input13
[ 8.859591] input: USB2.0 HD UVC WebCam: USB2.0 HD as /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-2/3-2.2/3-2.2:1.0/input/input14
[ 21.778542] rfkill: input handler disabled
[ 30.400536] rfkill: input handler enabled
[ 33.079010] rfkill: input handler disabled
Thanks! I'll get results as soon as I can.
Rhys |
|
|
1 members found this post helpful.
|
|
07-05-2020, 04:01 PM
|
#5
|
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
Quote:
4) You could try running Gnome via an X-session instead. Any difference in touchpad behaviour?
I don't know how to do this. Please advise.
|
You should be able to choose the desktop session at the login screen. (Once you click on the user, there should be a small symbol that you can click on and select the desired session.) However, this looks more to be a kernel-related issue, hence my suggestion to try the boot parameter as explained already.
Last edited by ferrari; 07-06-2020 at 02:08 AM.
|
|
|
1 members found this post helpful.
|
|
07-06-2020, 01:55 AM
|
#6
|
|
LQ Newbie
Registered: Apr 2019
Distribution: Ubuntu
Posts: 12
Original Poster
Rep:
|
Never have I been so frustrated at something for working flawlessly...  It finally decided to ignore the mouse this evening.
Here's the results of the commands:
First, debug-events returned no output when using the mouse.
sudo libinput list-devices
When it's working it shows these, when it's not, they are absent:
(here's a pastebin of the full output working https://pastebin.com/x16KtWjL and not working https://pastebin.com/QVxb8tVT , below is just what I assume you are looking for)
Code:
Device: ELAN1300:00 04F3:3087 Mouse
Kernel: /dev/input/event6
Group: 8
Seat: seat0, default
Capabilities: pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: n/a
Calibration: n/a
Scroll methods: *button
Click methods: none
Disable-w-typing: n/a
Accel profiles: flat *adaptive
Rotation: n/a
Device: ELAN1300:00 04F3:3087 Touchpad
Kernel: /dev/input/event7
Group: 8
Seat: seat0, default
Size: 103x69mm
Capabilities: pointer gesture
Tap-to-click: disabled
Tap-and-drag: enabled
Tap drag lock: disabled
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: *two-finger edge
Click methods: *button-areas clickfinger
Disable-w-typing: enabled
Accel profiles: none
Rotation: n/a
Here is the "When its working properly" output of dmesg |egrep -i "i8042|input"
Code:
$ dmesg |egrep -i "i8042|input"
[ 1.019496] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:39/PNP0C09:00/PNP0C0D:00/input/input0
[ 1.019557] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[ 1.019615] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
[ 1.019671] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[ 2.067353] i8042: PNP: PS/2 Controller [PNP030b:PS2K] at 0x60,0x64 irq 1
[ 2.067353] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 2.073659] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 2.085411] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
[ 3.392647] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:01/input/input5
[ 3.397833] input: ELAN1300:00 04F3:3087 Mouse as /devices/platform/AMDI0010:01/i2c-0/i2c-ELAN1300:00/0018:04F3:3087.0001/input/input6
[ 3.398009] input: ELAN1300:00 04F3:3087 Touchpad as /devices/platform/AMDI0010:01/i2c-0/i2c-ELAN1300:00/0018:04F3:3087.0001/input/input7
[ 3.398114] hid-generic 0018:04F3:3087.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN1300:00 04F3:3087] on i2c-ELAN1300:00
[ 3.619073] input: ELAN1300:00 04F3:3087 Mouse as /devices/platform/AMDI0010:01/i2c-0/i2c-ELAN1300:00/0018:04F3:3087.0001/input/input8
[ 3.619520] input: ELAN1300:00 04F3:3087 Touchpad as /devices/platform/AMDI0010:01/i2c-0/i2c-ELAN1300:00/0018:04F3:3087.0001/input/input9
[ 3.620235] hid-multitouch 0018:04F3:3087.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN1300:00 04F3:3087] on i2c-ELAN1300:00
[ 8.297784] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:03:00.1/sound/card0/input10
[ 8.361091] snd_hda_codec_realtek hdaudioC1D0: inputs:
[ 8.413855] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:03:00.6/sound/card1/input11
[ 8.520467] input: PC Speaker as /devices/platform/pcspkr/input/input12
[ 8.764378] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input13
[ 8.859591] input: USB2.0 HD UVC WebCam: USB2.0 HD as /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-2/3-2.2/3-2.2:1.0/input/input14
[ 21.778542] rfkill: input handler disabled
[ 30.400536] rfkill: input handler enabled
[ 33.079010] rfkill: input handler disabled
and here is the "when its not working" output:
Code:
[ 1.028810] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:39/PNP0C09:00/PNP0C0D:00/input/input0
[ 1.028844] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[ 1.028875] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
[ 1.028920] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[ 2.081915] i8042: PNP: PS/2 Controller [PNP030b:PS2K] at 0x60,0x64 irq 1
[ 2.081916] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 2.083439] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 2.093869] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
[ 3.296915] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/LNXVIDEO:01/input/input5
[ 8.260876] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:03:00.1/sound/card0/input6
[ 8.324030] snd_hda_codec_realtek hdaudioC1D0: inputs:
[ 8.392181] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:03:00.6/sound/card1/input7
[ 8.492748] input: PC Speaker as /devices/platform/pcspkr/input/input8
[ 8.726533] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input9
[ 8.867974] input: USB2.0 HD UVC WebCam: USB2.0 HD as /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-2/3-2.2/3-2.2:1.0/input/input10
[ 21.025839] rfkill: input handler disabled
[ 84.701941] rfkill: input handler enabled
[ 88.328415] rfkill: input handler disabled
Quote:
|
Another thing to try: Add 'i8042.reset' to the grub boot parameters. That might help get the touchpad device reliably initialised at boot.
|
Finally, lets make sure I did this correctly. I'm kind of learning as I go here and I haven't learned this yet. I edited /etc/default/grub and added "i8042.reset" to the end of the line that begins "GRUB_CMDLINE_LINUX_DEFAULT=" and ran sudo update-grub. That what I was supposed to do?
Thanks again!
Rhys |
|
|
1 members found this post helpful.
|
|
07-06-2020, 02:32 AM
|
#7
|
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
Thanks for posting the definitive information. It confirms touchpad device missing from dmesg output when not initialised properly.
Quote:
Finally, lets make sure I did this correctly. I'm kind of learning as I go here and I haven't learned this yet. I edited /etc/default/grub and added "i8042.reset" to the end of the line that begins "GRUB_CMDLINE_LINUX_DEFAULT=" and ran sudo update-grub. That what I was supposed to do?
Thanks again!
Rhys
|
That's correct...and did you do this after posting the above? Just clarifying if this has made any difference, or whether you're yet to determine this?
BTW, you can confirm the running boot parameters with
Last edited by ferrari; 07-06-2020 at 02:35 AM.
|
|
|
1 members found this post helpful.
|
|
07-06-2020, 03:05 AM
|
#8
|
|
LQ Newbie
Registered: Apr 2019
Distribution: Ubuntu
Posts: 12
Original Poster
Rep:
|
Quote:
|
That's correct...and did you do this after posting the above? Just clarifying if this has made any difference, or whether you're yet to determine this?
|
I didn't figure out how to do it until as I was making the previous post. We shall see if it helps.
Can you help me understand what we did? What the information actually means and what the change to grub did?
Thanks,
Rhys |
|
|
1 members found this post helpful.
|
|
07-06-2020, 03:30 AM
|
#9
|
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
The 'i8042.reset=1' parameter causes the i8042 keyboard/mouse/touchpad controller to rest during boot. This (and related options) can help with hardware that doesn't behave in the expected fashion. Unfortunately, this can be a trial and error process.
Similar question with an informative answer
https://unix.stackexchange.com/quest...ting-of-ubuntu
Kernel parameter reference:
https://www.kernel.org/doc/Documenta...parameters.txt
Last edited by ferrari; 07-06-2020 at 03:31 AM.
|
|
|
1 members found this post helpful.
|
|
07-06-2020, 03:34 AM
|
#10
|
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
Here's a nice article about grub and modifying boot parameters when needed...
https://www.howtogeek.com/196655/how...ders-settings/
Hope that helps with your understanding.  |
|
|
1 members found this post helpful.
|
|
07-14-2020, 09:52 PM
|
#11
|
|
LQ Newbie
Registered: Apr 2019
Distribution: Ubuntu
Posts: 12
Original Poster
Rep:
|
Thanks for the info, it really helped me grasp what was going on.
I wanted to give it a good amount of time before updating this for posterity, and it seems that my issue is fixed! Thanks so much for your help troubleshooting and finding a solution!
Rhys
|
|
|
1 members found this post helpful.
|
|
07-14-2020, 09:55 PM
|
#12
|
|
Member
Registered: Oct 2018
Location: texas
Distribution: bodhi 5.1.0
Posts: 797
Rep: 
|
can you post what the fix was in case someone else comes along with the same or a similar issue?
|
|
|
|
|
07-14-2020, 10:09 PM
|
#13
|
|
LQ Newbie
Registered: Apr 2019
Distribution: Ubuntu
Posts: 12
Original Poster
Rep:
|
Quote:
Originally Posted by cordx
can you post what the fix was in case someone else comes along with the same or a similar issue?
|
Sure thing! The change that seems to have done it is changing the grub config to reset i0842.
Quote:
|
I edited /etc/default/grub and added "i8042.reset" to the end of the line that begins "GRUB_CMDLINE_LINUX_DEFAULT=" and ran sudo update-grub.
|
|
|
|
1 members found this post helpful.
|
|
07-14-2020, 10:11 PM
|
#14
|
|
LQ Guru
Registered: Sep 2003
Location: Auckland, NZ
Distribution: openSUSE Leap
Posts: 6,006
|
Gad to read that did the trick! |
|
|
1 members found this post helpful.
|
All times are GMT -5. The time now is 06:40 AM.
|
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
|
 Latest Threads
LQ News
|
|
