OpenMandriva LX 4.0 Acer Helios 500 AMD ryzen Touchpad not working

Hello,

  • OpenMandriva Lx version: 4.0

  • Desktop environment (KDE, LXQT…): KDE

  • 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)

Thankyou

2 Likes

Hey. I do not have this equipment and it’s hard for me to answer for your problem but maybe we’ll come up with something together.

Show me:

inxi -F -c 0

and also upload somewhere output from this:

dmesg > dmesg.log

journalctl -b > journal.log

1 Like

Also /var/log/Xorg.0.log could contain useful info.

1 Like

@bero and @Colin have the same model and afaik is working fine.

The only thing is not working in general in Linux is the battery custom interface.

1 Like

Got this from @Colin on IRC:

<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.

I have that too on one lenovo box. If you press the wrong Fn key touchpad is off =)

1 Like

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.

2 Likes

here are my output :

inxi.txt (2.1 KB)

dmesg.txt (93.1 KB)

and about the function touchpad key I have try and no luck

Thankyou
(and sorry I’m a new user here so I can only upload 2 links)

1 Like

Thanks for the reply.

I just bumped you to user status. Should give you more freedom to post about this or any other issue as you wish to.

1 Like

Hmm I cannot see any touchpad in your dmesg.

All predators should use ‘SYNA7B99:00 06CB:7B99 as Touchpad’

@colin what does dmesg | grep -i touchpad , returns on your one ?

Can you post the output of the following command:

xinput -list

@fireedo Also this log please too.

thankyou a lot @ben79

@abucodonosor
dmesg | grep -i touchpad has no result / nothing found

here my Xorg log and xinput result :
xinput.txt (1.3 KB)
Xorg.txt (49.2 KB)

[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

This is on kernel 5.1.0-desktop-1omv4000

@colin what kind -input packages do you have installed ?

x11-driver-input.znver1                                              1.0.0-35                                    cooker-znver1            
x11-driver-input-evdev.znver1                                        2.10.6-4                                    cooker-znver1            
x11-driver-input-evdev-devel.znver1                                  2.10.6-4                                    cooker-znver1            
x11-driver-input-evtouch.znver1                                      0.8.8-23                                    cooker-znver1            
x11-driver-input-fpit.znver1                                         1.4.0-20                                    cooker-znver1            
x11-driver-input-hyperpen.znver1                                     1.4.1-20                                    cooker-znver1            
x11-driver-input-joystick.znver1                                     1.6.3-2                                     cooker-znver1            
x11-driver-input-libinput.znver1                                     0.28.2-1                                    cooker-znver1            
x11-driver-input-libinput-devel.znver1                               0.28.2-1                                    cooker-znver1            
x11-driver-input-mouse.znver1                                        1.9.3-2                                     cooker-znver1            
x11-driver-input-mouse-devel.znver1                                  1.9.3-2                                     cooker-znver1            
x11-driver-input-mutouch.znver1                                      1.3.0-20                                    cooker-znver1            
x11-driver-input-penmount.znver1                                     1.5.0-26                                    cooker-znver1            
x11-driver-input-synaptics.znver1                                    1.9.1-2                                     cooker-znver1            
x11-driver-input-synaptics-devel.znver1                              1.9.1-2                                     cooker-znver1            
x11-driver-input-vmmouse.znver1                                      13.1.0-3                                    cooker-znver1            
x11-driver-input-void.znver1                                         1.4.1-16                                    cooker-znver1            
x11-driver-input-wacom.znver1                                        0.36.1-2                                    cooker-znver1            
x11-driver-input-wacom-devel.znver1                                  0.36.1-2                                    cooker-znver1

Sounds like kernel-release config got overwrited so touchpads that works as PS2 over SMbus may not work.

Bug was fixed there

I try to boot using ubuntu just to check my touchpad and it works.
here my outputs :
xinput_ubuntu.txt (1.3 KB)

dmesg_ubuntu.txt (283 Bytes)

dmesg_all_ubuntu.txt (90.2 KB)

journalctl.txt (366.8 KB)

maybe I missed something? or do I have to edit something?

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

thankyou a lot :+1:

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.

1 Like