Package: general
Severity: important
X-Debbugs-Cc: zazo...@gmail.com

Dear Maintainer,

I have a Zotac ZBOX CI547 nano with an intel core i5-7200U and an intel HD
Graphics 620 card on which I installed Debian 11 and the linux-firmware package
(fresh install, kernel 5.10.0-9). It is connected to a monitor supporting
1920*1080 via HDMI.

On boot, the grub resolution is fine, then while booting, on 90% of the case,
the screen resolution is set at 1280*800 and once on Gnome I cannot change to a
higher resolution, even with xrandr:

zbox@black-box:~$ xrandr --verbose
Screen 0: minimum 16 x 16, current 1280 x 800, maximum 32767 x 32767
XWAYLAND0 connected primary 1280x800+0+0 (0x22) normal (normal left inverted
right x axis y axis) 510mm x 280mm
        Identifier: 0x21
        Timestamp:  26284
        Subpixel:   unknown
        Gamma:      1.0:1.0:1.0
        Brightness: 0.0
        Clones:
        CRTC:       0
        CRTCs:      0
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter:
        non-desktop: 0
                supported: 0, 1
  1280x800 (0x22) 83.500MHz -HSync +VSync *current +preferred
        h: width  1280 start 1352 end 1480 total 1680 skew    0 clock  49.70KHz
        v: height  800 start  803 end  809 total  831           clock  59.81Hz



zbox@black-box:~$ cvt -v 1920 1080
# 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz
Modeline "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120
-hsync +vsync
zbox@black-box:~$ xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248
2576  1080 1083 1088 1120 -hsync +vsync
zbox@black-box:~$ xrandr --addmode XWAYLAND0 1920x1080_60.00
zbox@black-box:~$ xrandr --output XWAYLAND0 --mode 1920x1080_60.00
xrandr: Configure crtc 0 failed


Here is the full dmesg when the computer boot with the right resolution
(approximately 10% off the time):
http://pastebin.fr/97303

And here the dmesg when the resolution is wrong:
http://pastebin.fr/97302

Here are the relevant errors I could find when the resolution is wrong by
comparing the two files (line 860 of the file):

[    3.918717] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful


And here is the full dmesg with the drm.debug=0x1e log_buf_les=10M boot options
when the resolution is wrong:
http://pastebin.fr/97304

Here are the relevant lines regarding the error:

[    3.883899] i915 0000:00:02.0: [drm:intel_dp_start_link_train [i915]] Same
voltage tried 5 times
[    3.883953] i915 0000:00:02.0: [drm:intel_dp_start_link_train [i915]]
[CONNECTOR:95:DP-1] Link Training failed at link rate = 162000, lane count = 1
[    3.883955] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful



The second problem I have is that after suspend or hibernate, the display does
not come back but the system is fine (I can log on the machine by ssh). The
monitors says it does not receive any signal, and when I check with xrandr the
display is labeled as disconnected. This happens independently of the
resolution. I catch the following dmesg typing blindly on TTY mode.

Here is the full dmesg after suspend and wake, when the boot resolution is
right:
http://pastebin.fr/97306

And here is the full dmesg after suspend and wake, when the boot resolution is
wrong:
http://pastebin.fr/97305

And here is the dmesg with the drm.debug=0x1e log_buf_les=10M boot options when
the resolution is wrong:
http://pastebin.fr/97307

What I could see is this error appearing after suspend when the resolution is
right:
[code]
[  151.138095] i915 0000:00:02.0: [drm] *ERROR* failed to enable link training
[/code]

And this when the resolution is wrong:
[code]
[  854.422386] i915 0000:00:02.0: [drm] *ERROR* failed to enable link training
[  854.422390] i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
[/code]

I tried to install Debian 10 to check is the problem existed before and I have
exactly the same problems, intermittent wrong resolution and no display after
suspend. I guess the two problems are related and something goes wrong with the
intel firmware.

Reply via email to