Lenovo ideapad flex 5i [LILLPUP] touchscreen not working [RWLEGACY]

Support Linux Support
1

My chromebooks touchscreen is the only thing(besides fan control and backlight) doesn’t work on arch, and probably other distros, The touchscreen isn’t even detected on x11 here is xinput:

❯ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳   HID Gaming Mouse                      	id=7	[slave  pointer  (2)]
⎜   ↳   HID Gaming Mouse Keyboard             	id=8	[slave  pointer  (2)]
⎜   ↳ Elan Touchpad                           	id=9	[slave  pointer  (2)]
⎜   ↳ keyd virtual pointer                    	id=11	[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)]
    ↳ AT Translated Set 2 keyboard            	id=10	[slave  keyboard (3)]
    ↳ keyd virtual keyboard                   	id=12	[slave  keyboard (3)]
    ↳   HID Gaming Mouse Keyboard             	id=13	[slave  keyboard (3)]
    ↳ sof-rt5682 Headset Jack                 	id=14	[slave  keyboard (3)]

Hyprland doesn’t detect it aswell;

❯ hyprctl devices
mice:
	Mouse at 5913df0ada70:
		--hid-gaming-mouse
			default speed: 0.00000
	Mouse at 5913e0018e70:
		--hid-gaming-mouse-keyboard-1
			default speed: 0.00000
	Mouse at 5913e0117630:
		elan-touchpad
			default speed: 0.00000
	Mouse at 5913e01d8c90:
		keyd-virtual-pointer
			default speed: 0.00000


Keyboards:
	Keyboard at 5913df088f70:
		power-button
			rules: r "", m "", l "gb", v "", o ""
			active keymap: English (UK)
			main: no
	Keyboard at 5913e0035910:
		--hid-gaming-mouse-keyboard
			rules: r "", m "", l "gb", v "", o ""
			active keymap: English (UK)
			main: no
	Keyboard at 5913e0117ad0:
		sof-rt5682-headset-jack
			rules: r "", m "", l "gb", v "", o ""
			active keymap: English (UK)
			main: no
	Keyboard at 5913e049a0f0:
		at-translated-set-2-keyboard
			rules: r "", m "", l "gb", v "", o ""
			active keymap: English (UK)
			main: no
	Keyboard at 5913e02a4360:
		keyd-virtual-keyboard
			rules: r "", m "", l "gb", v "", o ""
			active keymap: English (UK)
			main: yes


Tablets:


Touch:


Switches:
	Switch Device at 5913e04fbf60:
		Tablet Mode Switch
	Switch Device at 5913e02f8e90:
		Lid Switch


~
❯
2

that’s likely because the stock firmware uses nonstandard ACPI extensions to help ChromeOS identify the touchscreen model, and they aren’t supported by upstream linux.

post a cbmem log and I can tell you for sure.

3

The command on website didn’t work for me so I did sudo cbmem:

5

Link to file, not supported her so I upload to mega 85.9 KB file on MEGA

6

it’s a small text file, next time use pastebin or the like. Mega is overkill and more of a pain to use

looks like the stock firmware is enabling 2 touchpads and expecting the kernel to figure it out - that has a low probability for success with upstream linux

\_SB.PCI0.I2C1.H05D: Goodix Touchscreen at I2C: 00:5d
\_SB.PCI0.I2C1.D010: ELAN Touchscreen at I2C: 00:10

it’s possible that reloading the correct touchscreen driver manually might work,
you’ll just have to try and see. what does the Linux dmesg log say?

7

Patsebin:dmesg.log - Pastebin.com

8

linux tried to load the drivers for both touchscreens, but both failed. I’m not sure there’s anything that can be done to fix that with RWL.

[    5.257208] elants_i2c i2c-ELAN0001:00: supply vcc33 not found, using dummy regulator
[    5.257225] elants_i2c i2c-ELAN0001:00: supply vccio not found, using dummy regulator
[    5.283861] elants_i2c i2c-ELAN0001:00: nothing at this address

[    5.314023] i2c_hid_acpi i2c-GDIX0000:00: failed to reset device: -121
[    5.315033] i2c_hid_acpi i2c-GDIX0000:00: failed to change power setting.
[    6.340104] i2c_hid_acpi i2c-GDIX0000:00: failed to change power setting.
[    7.364081] i2c_hid_acpi i2c-GDIX0000:00: failed to change power setting.
[    8.388020] i2c_hid_acpi i2c-GDIX0000:00: failed to change power setting.
[    9.411799] i2c_hid_acpi i2c-GDIX0000:00: can't add hid device: -121
[    9.421197] i2c_hid_acpi i2c-GDIX0000:00: probe with driver i2c_hid_acpi failed with error -121
9

could UEFI full be any better?

10

yes, the UEFI Full ROM firmware does not have this issue, because it initializes and detects the correct touchscreen at boot time so it’s ready to go for the OS