Bug#927788: Debian 9.9 clean install and HDMI issue, EDID error log.
Dear maintainers,
Great thanks for 9.9. It works well on my main machines.
And I did clean install on the test machine, too.
I post additional report for this (not a new installation-reports), since,
1. The situation is not so different.
2. I got EDID error log on that.
FYI: H110 Skylake iGPU HDMI -> HDMI switch[*] -> LCD
[*] no EDID emulation, automatic switch, works fine on the other env.
EDID error log
---------------
kernel: PM: Finishing wakeup.
systemd[1]: Time has been changed
systemd[1]: apt-daily-upgrade.timer: Adding 38min 9.936334s random time.
systemd[1]: apt-daily.timer: Adding 4h 36min 57.197661s random time.
systemd[1837]: Time has been changed
kernel: Restarting tasks ... done.
kernel: video LNXVIDEO:00: Restoring backlight state
kernel: usb 1-6-port1: Cannot enable. Maybe the USB cable is bad?
kernel: [drm] RC6 on
kernel: [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is
invalid, remainder is 93
kernel: Raw EDID:
kernel: 00 ff ff ff ff ff ff 00 34 ac 3d 48 01 01 01 01
kernel: 02 15 01 03 80 33 1d 78 ea d9 45 a2 55 4d a0 27
kernel: 12 50 54 bf ef 80 71 4f 81 80 81 4f 8b c0 a9 c0
kernel: b3 00 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c
kernel: 45 00 fd 1e 11 ff ff ff ff ff ff ff ff ff ff ff
kernel: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
kernel: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
kernel: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
kernel: e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: Rx/Tx
CRON[662]: pam_unix(cron:session): session closed for user logcheck
systemd[1]: Started Getty on tty2.
NOTE: no HDMI LOS at this log. tty2 was GNOME session, and resumed.
Honestly, I have no idea about this. I'm not so familiar with linux
videos and EDID.
My guess is,
1. The LCD used by the test machine is old, resulting this.
2. Maybe LCD power management makes timing trouble,
since that old LCD has slow wake up response on HDMI signal.
My other LCD, relatively new, has very quick response.
Please do not mind the USB cable log.
I use cheap USB K(V)M. That's the cause, I guess.
Regards.
Reply to: