Arch Linux

megacar

Member

Registered: 2024-02-06

Posts: 4

no touchscreen after wake up from S3 sleep

Hi,
Arch newbie here.

The reason I registered here is to ask about this article:
https://wiki.archlinux.org/title/Lenovo … ter_resume

I have the same problem, but different hardware.
Was hoping someone (who knows acpi_call, or if the person who wrote the wiki article is still active here) could help me get a string relevant for my hardware. '\\_SB.PCI0.LPCB.EC._Q2A' is the one for the above mentioned Lenovo.

It's a converted chromebook, Acer Spin 512 R851TN (SPARKY360 Gemini Lake)
Laptop is running coreboot custom uefi bios 4.22.2 mrchromebox (https://mrchromebox.tech/)

Same issue with same logs happens in Fedora 39, Ubuntu 23.10 and Arch release 2024.02.01.
I suspect it might be a bios issue, same as with Lenovo from your wiki
Opened firmware bug https://github.com/MrChromebox/firmware/issues/578 but they do not think its firmware, saying it might be OS. in that case linux kernel I guess.
Anyway, I think my only chance of working around this (other then disabling touchscreen altogether) is getting help from you guys

here is the log in one of the many reproduced moments:

Feb 04 21:23:13 fedora kernel: ACPI: PM: Preparing to enter system sleep state S3
Feb 04 21:23:13 fedora kernel: ACPI: EC: event blocked
Feb 04 21:23:13 fedora kernel: ACPI: EC: EC stopped
Feb 04 21:23:13 fedora kernel: ACPI: PM: Saving platform NVS memory
Feb 04 21:23:13 fedora kernel: Disabling non-boot CPUs ...
Feb 04 21:23:13 fedora kernel: smpboot: CPU 1 is now offline
Feb 04 21:23:13 fedora kernel: smpboot: CPU 2 is now offline
Feb 04 21:23:13 fedora kernel: smpboot: CPU 3 is now offline
Feb 04 21:23:13 fedora kernel: ACPI: PM: Low-level resume complete
Feb 04 21:23:13 fedora kernel: ACPI: EC: EC started
Feb 04 21:23:13 fedora kernel: ACPI: PM: Restoring platform NVS memory
Feb 04 21:23:13 fedora kernel: Enabling non-boot CPUs ...
Feb 04 21:23:13 fedora kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Feb 04 21:23:13 fedora kernel: CPU1 is up
Feb 04 21:23:13 fedora kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Feb 04 21:23:13 fedora kernel: CPU2 is up
Feb 04 21:23:13 fedora kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Feb 04 21:23:13 fedora kernel: CPU3 is up
Feb 04 21:23:13 fedora kernel: ACPI: PM: Waking up from system sleep state S3
Feb 04 21:23:13 fedora kernel: ACPI: EC: interrupt unblocked
Feb 04 21:23:13 fedora kernel: ACPI: EC: event unblocked
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: report size changes, was: 82, new: 54
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x51f vs 0x00
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x51f vs 0x00
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x51f vs 0x00
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x51f vs 0x00
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x51f vs 0x00
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x2a4c vs 0x10
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x9b4 vs 0x4126
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x611 vs 0x8800
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x956 vs 0x300
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x987 vs 0x104
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x67c vs 0xb00
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x962 vs 0x420
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0xad6 vs 0x211
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x527 vs 0x80
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0x9ce vs 0x411
Feb 04 21:23:13 fedora kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0xaf5 vs 0x100

hope it's the correct subforum, and that I didn't break any posting rules.
thanks in advance

Last edited by megacar (2024-02-06 08:13:49)

megacar

Member

Registered: 2024-02-06

Posts: 4

Re: no touchscreen after wake up from S3 sleep

when i try to rmmod then modprobe raydium_i2c_ts

Feb 06 23:23:32 acer kernel: i2c_designware i2c_designware.5: i2c_dw_handle_tx_abort: lost arbitration
Feb 06 23:23:33 acer kernel: i2c_designware i2c_designware.5: controller timed out

and after that, log gets flooded with acer kernel: raydium_ts i2c-RAYD0001:00: raydium_i2c_irq: invalid packet crc 0xbla vs 0xbla

device

Feb 06 23:27:55 acer kernel: input: Raydium Touchscreen as /devices/pci0000:00/0000:00:17.3/i2c_designware.5/i2c-5/i2c-RAYD0001:00/input/input6

libinput

Device:           Raydium Touchscreen
Kernel:           /dev/input/event7
Group:            9
Seat:             seat0, default
Size:             68x46mm
Capabilities:     touch 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      identity matrix
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0.0

can i open a kernel bug for this?
should it be upstream mainline, or to some distro like arch or ubuntu?

Last edited by megacar (2024-02-08 15:32:02)