Lenovo notebook screen useless after last few updates

crom5

Hello all,
after the last few upadates, my girlfriend's notebook (Lenovo Y700-17ISK) screen has suddenly become useless.
In other words, it constantly vibrates and trembles and shakes in a way that you can't look at it for more than 2 minutes because your eyes start to hurt.
Thanks in advance for any help.

Video (you must watch in full screen mode, otherwise you don't see the problem):

Solus Budgie fully updated.
Lenovo Y700-17ISK
NVIDIA Optimus disabled in BIOS.

$ lspci | grep -i --color 'vga|3d|2d'
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)

sudo lshw -c video
*-display
description: VGA compatible controller
product: HD Graphics 530
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 06
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:128 memory:a0000000-a0ffffff memory:90000000-9fffffff ioport:4000(size=64) memory:c0000-dffff

sudo glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel (0x8086)
Device: Mesa Intel(R) HD Graphics 530 (SKL GT2) (0x191b)
Version: 21.1.3
Accelerated: yes
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 530 (SKL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.1.3
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.1.3
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.1.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

JoshStrobl

This is an upstream issue and not something we can resolve. I would suggest posting on https://gitlab.freedesktop.org/drm/intel/-/issues/3714 that you have the problem, provide your various info there.

crom5

Hello,
thanks for you advice.
i just want to let you know that the problem is still here after applying all today's updates (including new kernel 5.13).

JoshStrobl

Seeing as the bug I linked isn't fixed, yes that would make sense...

crom5

Hello Josh,
it seems that the problem has been identified:

https://bugzilla.redhat.com/show_bug.cgi?id=1965645
I got the same bug too, on a MSI Apache GE72 2QE, equipped with

CPU: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHzf
Discrete GPU: 3D controller: NVIDIA Corporation GM204M [GeForce GTX 965M] (rev a1)

This issue appeared before 5.12 release, the 5.11 branch is not affected. After some bisection, I was able to identify the commit responsible for this :

commit 2bbd6dba84d44219387df051a1c799b7bac46099
Author: Ville Syrjälä ville.syrjala@linux.intel.com
Date: Thu Jan 7 20:20:25 2021 +0200
drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure
Edit: Reverting this commit on top of kernel 5.13 solves the issue.

What I don't understand is if the fix is coming within the new 5.13.2 kernel?

https://lkml.org/lkml/2021/7/12/3506
This is the start of the stable review cycle for the 5.13.2 release. There are 800 patches in this series. Responses should be made by Wed, 14 Jul 2021.

JoshStrobl

crom5 Was already aware of that patch and backporting this wasn't possible given the drm-tip changes for just i915 alone between this commit and when 5.13.0's drm-tip merge was.

What I don't understand is if the fix is coming within the new 5.13.2 kernel?

I am not seeing any indication when looking at drm-tip that it has been tagged for 5.13.2, only 5.14-rc1. It's possible we will see it get merged, but not a guarantee.

crom5

Hello,
kernel developers are calling for testing of possible solution to this problem.
Is it possible to somehow test this patch in Solus?
Thanks in advance for any reply.

https://gitlab.freedesktop.org/drm/intel/-/issues/3714

Kai-Heng Feng @khfeng · 4 hours ago

Please test the following patch:

diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
index 75d4ebc669411..798e5022227d4 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -1330,7 +1330,7 @@ intel_dp_compute_link_config(struct intel_encoder *encoder,
limits.min_bpp = intel_dp_min_bpp(pipe_config->output_format);
limits.max_bpp = intel_dp_max_bpp(intel_dp, pipe_config);

if (intel_dp->use_max_params) {

if (intel_dp->use_max_params || intel_dp->dpcd[DP_DPCD_REV] <= DP_DPCD_REV_11) {
/*
* Use the maximum clock and number of lanes the eDP panel
* advertizes being capable of in case the initial fast

JoshStrobl

crom5 Cloning our linux-current repo from Phab, installing the necessary build tooling (check Help Center for documentation), add the patch (including to files/series) and compile + install. Or you can wait until I update the kernel, I can add that patch in 🙂

crom5

I would be very grateful for the second option 🙂
Hopefully this friday sync?
Thanks again 🙂

crom5

Hi Josh,
thank you very much for including the patch into Solus 5.13.8-191.current kernel.
Problem is finally solved 🙂

I will ask now developer Kai-Heng Feng when can we expect official inclusion of the patch into the kernel.