Description of the issue (screenshots if relevant): !
Relevant informations (hardware involved, software version, logs or output…): I’m using a laptop Acer Predator Helios 500 with Ryzen 2700 and AMD Vega56 the rest are general.
this touchpad I have read somewhere that something know trouble but at least I have try with ubuntu 19.04 and Opensuse Tumbleweed it works.
anyidea how to make this touchpad work under OMv LX 4.0 ? since this is the only distro that works well with helios 500 AMD cpu and error display (after screen off/sleep)
<itchka_> There is one simple thing he could check. The Predator has a keyboard function to turn off the touchpad. On my install this works…maybe he has turned it off by accident.
Hi I’m itchka and have a similar machine to you Rynez Radeon based Predator laptop. I am running Om Lx4 and I’m not experiencing any issues with my touchpad. If you are still having trouble try plugging in a usb mouse. If you still have issues please come back here and I will try and help. If you feel able please file a bug to allow us to properly track this issue.
[Tue Jun 11 14:54:27 2019] psmouse serio1: synaptics: Your touchpad (PNP: SYN1b8d PNP0f13 PNP0f03) 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.
[Tue Jun 11 14:54:27 2019] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2a1, caps: 0xf00123/0x840300/0x2e800/0x0, board
id: 3164, fw id: 2150116
[Tue Jun 11 14:54:27 2019] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input2
I was using kernel-release-desktop-5.1.0 so as fireedo has loaded kernel-release-desktop-5.1.9 I tried that. It still works. I checked my machine spec against yours and the only difference is that you are running an updated BIOS. 1.07 as opposed to my 1.06. The update is described on Acer’s site is Add 30ms delay time for LED POST CMD to fix abnormal PWM IC. PWM stands for Pulse Width Modulation and probably relates to a power supply. It is within the bounds of possibility that this delay could affect a kernel detection mechanism. We have another user that has a predator I will check what BIOS he is running.
Edit
Here’s some evidence in your dmesg output. The device is not switched on and therefore is not detected.
[Mon Jun 17 06:18:24 2019] i2c_hid i2c-SYNA7B99:00: i2c-SYNA7B99:00 supply vdd not found, using dummy regulator
[Mon Jun 17 06:18:24 2019] i2c_hid i2c-SYNA7B99:00: i2c-SYNA7B99:00 supply vddl not found, using dummy regulator
[Mon Jun 17 06:18:24 2019] ACPI: Video Device [DGPU] (multi-head: yes rom: no post: no)
[Mon Jun 17 06:18:24 2019] i2c_designware AMDI0010:03: i2c_dw_handle_tx_abort: lost arbitration
[Mon Jun 17 06:18:24 2019] i2c_designware AMDI0010:03: i2c_dw_handle_tx_abort: lost arbitration
[Mon Jun 17 06:18:24 2019] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:27/device:28/device:29/LNXVIDEO:00/input/input5
[Mon Jun 17 06:18:24 2019] i2c_designware AMDI0010:03: i2c_dw_handle_tx_abort: lost arbitration
[Mon Jun 17 06:18:24 2019] i2c_designware AMDI0010:03: i2c_dw_handle_tx_abort: lost arbitration
In the ub dmesg I see this:
1.342135] i2c_hid i2c-SYNA7B99:00: i2c-SYNA7B99:00 supply vdd not found, using dummy regulator
[ 1.342149] i2c_hid i2c-SYNA7B99:00: Linked as a consumer to regulator.0
[ 1.342151] i2c_hid i2c-SYNA7B99:00: i2c-SYNA7B99:00 supply vddl not found, using dummy regulator
Which is a different kernel module.
thankyou @Colin , well maybe that the culprit here, but too bad I cant revert back to the old BIOS, acer doesnt have that mechanism.
So maybe I will wait for luck maybe someday (I hope no too long) that my touchpad will be fixed or working
I have BIOS 1.07 as well (and not having issues), so that’s not the problem – but you may want to check your BIOS settings. On the “Main” page, there’s a “Touchpad” setting. I’ve had to set it to “Basic” to make my touchpad work.