Bug 201175
| Summary: | Touchpad not working for HP ZBook Studio G5 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Bo (qiao.bo) |
| Component: | Input Devices | Assignee: | drivers_input-devices |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | andy.shevchenko, kai.heng.feng, pietrovigilanza7, qiao.bo, tkonicz, valborgscnd |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 4.18.8 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
dmesg upon boot under kernel 4.18.8
dmesg | grep -i irq dmesg upon boot under kernel 4.18.rc6 |
||
Created attachment 278645 [details]
dmesg | grep -i irq
I think it is related to interrupt. Because of the last line:
i2c_hid i2c-SYNA307B:00: Could not register for SYNA307B:00 interrupt, irq = 136, ret = -1
Another strange behavior: every time I start the system, touchpad not working. However, if i suspend the system and wake it up again, the touchpad starts working !! (left click, scrolling work, right click not working) I am following bug 199911, https://bugzilla.kernel.org/show_bug.cgi?id=199911 which looks like a similar problem. I followed the solution suggested in that post, (comment 68). I compiled 4.18.rc6 with the two suggested patch. The touchpad is still not working. Again, only upon reboot. If I manually suspend and wake Ubuntu, the touchpad can be partly used. Created attachment 278647 [details]
dmesg upon boot under kernel 4.18.rc6
Please let me know if more information is requested. Sorry for the broken massages, this is my first bug report :) I have the same problem, but suspending the system and wake it up again does not allow the touchpad to partially work again. If you need more information, let me know, I am completely new to this. The issue is solved under the current 4.19 stable release. Sorry, the issue seems not to be resolved entirely. I am using a Zbook Studio G5 with Ubuntu 19.04 (Kernel 5.0.0-20-generic) right now. The Touchpad seems to work nicely, but after waking up from suspend (open a closed lid), the touchpad starts to act jaggy/wiredly, it is nearly impossible to use it anymore, it feels like the mouse pointer would "stutter"- A rebood fixes this issue - until I close and open the lid again and the Zbooks wakes up from sleep-mode. The issue is not present when using a mouse after waking up from suspend, just the touchpad. (In reply to Tomasz from comment #8) > Sorry, the issue seems not to be resolved entirely. I am using a Zbook > Studio G5 with Ubuntu 19.04 (Kernel 5.0.0-20-generic) right now. The > Touchpad seems to work nicely, but after waking up from suspend (open a > closed lid), the touchpad starts to act jaggy/wiredly, it is nearly > impossible to use it anymore, it feels like the mouse pointer would > "stutter"- A rebood fixes this issue - until I close and open the lid again > and the Zbooks wakes up from sleep-mode. The issue is not present when using > a mouse after waking up from suspend, just the touchpad. I am also having this same issue at the moment. The issue is definitely not resolved ok, the issue is not resolved. Touchpad does not act normal after waking up from suspend. what can we do? at lease i reopened the issue. (In reply to PV from comment #9) > (In reply to Tomasz from comment #8) > > Sorry, the issue seems not to be resolved entirely. I am using a Zbook > > Studio G5 with Ubuntu 19.04 (Kernel 5.0.0-20-generic) right now. The > > Touchpad seems to work nicely, but after waking up from suspend (open a > > closed lid), the touchpad starts to act jaggy/wiredly, it is nearly > > impossible to use it anymore, it feels like the mouse pointer would > > "stutter"- A rebood fixes this issue - until I close and open the lid again > > and the Zbooks wakes up from sleep-mode. The issue is not present when > using > > a mouse after waking up from suspend, just the touchpad. > > I am also having this same issue at the moment. The issue is definitely not > resolved Maybe, we should also report this in bug 199911, which was closely related to this issue. Hello, just some additional Info: I tried different Distros (Debian 10, Fedora, Manjaro with Kernel 5.2rc) - the bug, as described above, persists in all the Distributions. Seems like it's the same as #203995? Based on comments 8 and 9 I close it as duplicate. *** This bug has been marked as a duplicate of bug 203995 *** |
Created attachment 278643 [details] dmesg upon boot under kernel 4.18.8 Hello, The touchpad of my HP Studio G5 is not working in Ubuntu 18.04.1. I have tried with these kernels: 4.15(comes with the image), 4.18.8 Output of xinput -list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=10 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics 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)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Video Bus id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ HP HD Camera: HP HD Camera id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)]