Bug 1213771 - Touchpad randomly stops working on Lenovo IdeaPad 5 14ALC05
Summary: Touchpad randomly stops working on Lenovo IdeaPad 5 14ALC05
Status: NEW
: 1213773 (view as bug list)
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: openSUSE Kernel Bugs
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-28 22:00 UTC by Roberto Pio Iannello
Modified: 2023-08-07 10:51 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
tiwai: needinfo? (robertoiannello02)


Attachments
dmesg (989 bytes, text/plain)
2023-07-28 22:00 UTC, Roberto Pio Iannello
Details
complete dmesg output when touchpad is working properly (87.73 KB, text/plain)
2023-07-30 09:15 UTC, Roberto Pio Iannello
Details
hwinfo output when the touchpad is working properly (1.44 MB, text/plain)
2023-07-30 09:15 UTC, Roberto Pio Iannello
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roberto Pio Iannello 2023-07-28 22:00:51 UTC
Created attachment 868493 [details]
dmesg

When using my laptop, sometimes the touchpad randomly stops working with apparently no reason, restarting drivers doesn't work, it seems that's something related to amd power management, switchet also to vanilla kernel but anything changed.
Comment 1 Andreas Stieger 2023-07-29 12:37:14 UTC
*** Bug 1213773 has been marked as a duplicate of this bug. ***
Comment 2 Andreas Stieger 2023-07-29 15:41:11 UTC
Do not touch the priority field unless you are a developer.
Comment 3 Takashi Iwai 2023-07-30 08:22:20 UTC
Is this a regression from the earlier kernels?

In anyway, please give the hwinfo and the full output of dmesg.
Also, if you see the broken state, please give the same outputs for comparison, too.
Comment 4 Roberto Pio Iannello 2023-07-30 09:14:24 UTC
(In reply to Takashi Iwai from comment #3)
> Is this a regression from the earlier kernels?
> 
> In anyway, please give the hwinfo and the full output of dmesg.
> Also, if you see the broken state, please give the same outputs for
> comparison, too.


I have this problem since my first Linux install with another distro in this laptop (Kernel 5.4) and it still persists. It seems that in Manjaro Linux they have solved the problem somehow.

Here in the attachments the dmesg and hwinfo outputs when the touchpad is working normally
Comment 5 Roberto Pio Iannello 2023-07-30 09:15:29 UTC
Created attachment 868508 [details]
complete dmesg output when touchpad is working properly
Comment 6 Roberto Pio Iannello 2023-07-30 09:15:59 UTC
Created attachment 868509 [details]
hwinfo output when the touchpad is working properly
Comment 7 Takashi Iwai 2023-07-30 09:16:35 UTC
(In reply to Roberto Pio Iannello from comment #4)
> It seems that in Manjaro Linux
> they have solved the problem somehow.

It would be great if you have a bit more details about this (or URL).
Comment 8 Roberto Pio Iannello 2023-07-30 09:31:39 UTC
(In reply to Takashi Iwai from comment #7)
> (In reply to Roberto Pio Iannello from comment #4)
> > It seems that in Manjaro Linux
> > they have solved the problem somehow.
> 
> It would be great if you have a bit more details about this (or URL).

Unfortunately I don't have any detail.

It simply worked out of the box, maybe they have a modified kernel.
When I first installed Manjaro I thought that the touchpad was working because they have a more recent kernel and the bug was fixed with Linux 6, but when I tried fedora 36 and now opensuse tumbleweed I noticed that the issue it's still here.
Comment 9 Takashi Iwai 2023-07-30 10:53:06 UTC
OK, then at least could you tell me which Manjaro kernel version / package, so that we can take a bit look?
Comment 10 Roberto Pio Iannello 2023-07-30 16:51:52 UTC
(In reply to Takashi Iwai from comment #9)
> OK, then at least could you tell me which Manjaro kernel version / package,
> so that we can take a bit look?

It should be kernel 6.2 and above but I'm not really sure, I'm really sorry, wold like to help but I don't know how to know from which kernel version it started to work
Comment 11 Roberto Pio Iannello 2023-07-30 16:53:08 UTC
(In reply to Takashi Iwai from comment #9)
> OK, then at least could you tell me which Manjaro kernel version / package,
> so that we can take a bit look?

It should be kernel 6.2 and above but I'm not really sure, I'm really sorry, wold like to help but I don't know how to know from which kernel version it started to work 

Maybe it's only a lower chance, because I remember that even on Manjaro it happened one time.
Comment 12 Takashi Iwai 2023-08-07 10:51:40 UTC
OK, then at best, please report this to the upstream.  But it's a bit difficult to tackle, as we don't know exactly which component triggers the problem.
But, as it's an input problem, I'd begin with the input subsystem.