December 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1206703] New: Sound stops working for MSI GS66 after kernel 5.14.21-150400.24.38 update
by bugzilla_noreply＠suse.com 26 Dec '22

26 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206703 Bug ID: 1206703 Summary: Sound stops working for MSI GS66 after kernel 5.14.21-150400.24.38 update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: onur(a)delipenguen.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863696 --> https://bugzilla.suse.com/attachment.cgi?id=863696&action=edit lspci On MSI GS66 12UHS kernel 5.14.21-150400.24.38 update caused sound start to behave quite strange. Did not have any issues with older kernels. After a fresh boot the sound works fine, but when you stop playing and then start playing sound again no audio comes out of speakers, though everything seems like working fine. Changing volume levels, using different apps (Firefox, Mplayer etc.), using Alsa instead of Pulseaudio (before audio goes away, or after) etc. does not make a difference, sound acts as if it is muted. When it is stopped. Tried snd-hda-intel options like power_save=0 power_save_controller=N (as kernel parameters on boot and manually setting up in sysfs after boot) does not make a difference. I do not see power save activating for the sound card (see output of proc) and the behavior is the same on a very cold environment too so I suspect it is not sound chipset overheating / powerwave etc. removing intel_iommu kernel param does not make a difference. On /proc/asound/card0/codec#0 "Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out" section I see there is a difference for good kernel "Amp-Out vals: [0x3b 0x3b]" and when the sound is gone on bad kernel "Amp-Out vals: [0x3f 0x3f]". Could this be some sort of bad volume setup done by the driver ? Attached is some info, I can tried out other things / provide more info. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 26 Dec '22

26 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c66 --- Comment #66 from Paul Soto <pst73de(a)yahoo.com> --- I cant believe it but my original touchpad is broken... can't say whether it was broken from the beginning and I developed a feeling of being broken over time (because it was not feeling right), or it is just gone bad last week. The original touchpad has different part number from the donor touchpad (and none of them match Lenovo FRU numbers), the original one says "ROA A, the donor one "ROA C", which I suppose stands for revision A or C. Ive tested the "A" touchpad now also with Windows10 and it exhibits the same laggy behaviour (movement delayed). Hard to tell what is at fault - is it broken or badly supported by the driver for revision "A"? Ps. the pointer motion is still not as crisp as on P16 with real Synaptics touchpad (seems to me Synaptics has better movement resolution, seems to generate more events). I believe I will replace it anyway with the P16 touchpad if I find the part. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 26 Dec '22

26 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c65 --- Comment #65 from Paul Soto <pst73de(a)yahoo.com> --- Created attachment 863695 --> http://bugzilla.opensuse.org/attachment.cgi?id=863695&action=edit swapping touchpad swapping T16 touchpads. on the right original one, on the left "donor" one -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 26 Dec '22

26 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c64 --- Comment #64 from Paul Soto <pst73de(a)yahoo.com> --- eventually this is some issue with the i2c driver https://edc.intel.com/content/www/us/en/design/ipla/software-development-pl… The I2C interfaces support the following features: Speed: standard mode (up to 100 Kb/s), fast mode (up to 400 Kb/s), fast mode plus (up to 1 MB/s) and High speed mode (up to 3.2 Mb/s). 1.8 V or 3.3 V support (depending on the voltage supplied to the I2C signal group) Master I2C operation only 7-bit or 10-bit addressing 7-bit or 10-bit combined format transfers Bulk transmit mode Ignoring CBUS addresses (an older ancestor of I2C used to share the I2C bus) Interrupt or polled-mode operation Bit and byte waiting at all bus speed Component parameters for configurable software driver support Programmable SDA hold time (tHD; DAT) DMA support with 64-byte DMA FIFO per channel (up to 32-byte burst) 64-byte Tx FIFO and 64-byte Rx FIFO SW controlled serial data line (SDA) and serial clock (SCL) could be accumulating i2c packets in the TX FIFO -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 26 Dec '22

26 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c63 --- Comment #63 from Paul Soto <pst73de(a)yahoo.com> --- The last problem will randomly "fix" itself and then come back. for a while touchpad motion is as crisp as on P16 then again becomes sluggish again. To me it looks like the XY events are being randomly buffered somewhere and do not appear immediately on the input device, then a bunch of buffered events is sent all at once. I pulled latest updated, also rebooted the system, no success. Sluggish pointer directly after boot & KDE login. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 25 Dec '22

25 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c62 --- Comment #62 from Paul Soto <pst73de(a)yahoo.com> --- another way to reproduce: run evtest | grep ABS_X then: move your finger *quickly* left and right (left-stop-right-stop). on P16: events are generated only as long as the motion takes place on T16: events keep being generated for about 200-300ms after you have stopped to move the finger -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 25 Dec '22

25 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c61 --- Comment #61 from Paul Soto <pst73de(a)yahoo.com> --- more debug with evtest: what happens on T16 with synaptics driver is actually this: - I put my finger somewhere onto the surface, it generates ABS_X/Y event - then I *very* slowly move the finger to the right (and I mean really slowly, but I feel it is moving over the surface!), NO events are generated until some minimum movement has been done, then suddenly I see a bunch of events generated at once for all the movement. Lets say I put the finger at 500, generates ABS_X 500 (plus the ABS_Y etc), then nothing happens when I slowly move then generates ABS_X 501 ABS_X 502 ... ABS_X 510 all at once! this is very different from Thinkpad P16 behaviour as far as I can see, though it uses the Synaptics model SYNA801A touchpad versus ELAN0683 on T16. P16 feels crystal clean. Now tell me what is here at fault? The touchpad hardware? Linux input driver, xf86 driver? maybe i2c firmware ? what should I Look at? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 25 Dec '22

25 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c60 --- Comment #60 from Paul Soto <pst73de(a)yahoo.com> --- evtest actually shows there are NO events generated when I Move the finger slowly! (which corresponds to the feeling I have when moving the finger). I could swear there were any few days ago... can touchpad go bad on its own?! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 25 Dec '22

25 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c59 --- Comment #59 from Paul Soto <pst73de(a)yahoo.com> --- the crappy feeling now on synaptics driver actually is being caused by the driver not recognizing small finger movements again. So when I put the finger onto the touchpad and slooowly start to move it, it takes a half a second until the pointer actually starts to move (either time or displacement related). It was similar with libinput at the begining, thats why I actually switched to synaptics! Now same shitty feeling using either of them! Cant help myself - what is wrong here?! On the P16 (same Suse 15.4) the pointer feels crisp clear! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 25 Dec '22

25 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c58 --- Comment #58 from Paul Soto <pst73de(a)yahoo.com> --- Now again another problem: after the system pulled some updates, touchpad got really bad! it feels like the pointer is lagging (even after complete power off and reboot, not fixing it). I had this lagging feeling when I was using libinput at the begining but switching to synaptics driver improved it significantly. Now Ive same issue even if using xf86 synaptics driver.... deinstalled xf86-libinput to make sure they do not interfere somehow but no change, pointer still lagging! I have now also a P16 for testing (it uses actually a genuine synaptics touchpad instead of ELAN HW on T16), installed exactly the same Opensuse there (same version for xf86-synaptics driver according to yast on both machines) and the pointer on P16 feels absolutely different (it feels like it should feel, not laggy). -- You are receiving this mail because: You are the assignee for the bug.

1 0