From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 72051] [JUNIPER] with kernel 3.12 some HDMI screens are not recognized Date: Tue, 17 Dec 2013 13:43:44 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1345716032==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 0B146FC8F4 for ; Tue, 17 Dec 2013 05:43:44 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces@lists.freedesktop.org Errors-To: dri-devel-bounces@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1345716032== Content-Type: multipart/alternative; boundary="1387287824.81B855120.29987"; charset="us-ascii" --1387287824.81B855120.29987 Date: Tue, 17 Dec 2013 13:43:44 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=72051 --- Comment #11 from Alex Deucher --- (In reply to comment #10) > Indeed, this option is set. Commit that was pointed out by you fixes the > problem. > > However, now when booting when the problematic screen is attached, I see a > message that EDID is invalid: > > [ 8.922653] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, > remainder is 255 > [ 8.922666] Raw EDID: > [ 8.922670] ff ff ff ff ff ff ff 00 22 64 e5 20 fb 01 00 00 > [ 8.922676] 17 14 01 03 80 3b 25 78 ea af f6 a6 54 4c 9e 23 > [ 8.922680] 10 4f 54 bf ef 80 d1 00 b3 00 a9 40 95 00 90 40 > [ 8.922684] 81 80 81 40 71 4f 28 3c 80 a0 70 b0 23 40 30 20 > [ 8.922688] 36 00 51 73 21 00 00 1a 00 00 00 ff 00 30 32 33 > [ 8.922692] 4c 4b 33 51 41 30 30 35 30 37 00 00 00 fd 00 38 > [ 8.922696] 4b 18 50 0f 00 0a 20 20 20 20 20 20 00 00 00 fc > [ 8.922700] 00 48 48 32 38 31 0a 20 20 20 20 20 20 20 01 e2 > > repeated 4 times. This is probably is separate problem? Does it work correctly without the hw_i2c option? If not, it's probably a buggy monitor or a hdmi receiver that doesn't patch the checksum correctly. -- You are receiving this mail because: You are the assignee for the bug. --1387287824.81B855120.29987 Date: Tue, 17 Dec 2013 13:43:44 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 11 on bug 72051 from 
(In reply to comment #10)
> Indeed, this option is set. Commit that was pointed out by you fixes the
> problem. 
> 
> However, now when booting when the problematic screen is attached, I see a
> message that EDID is invalid:
> 
> [    8.922653] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid,
> remainder is 255
> [    8.922666] Raw EDID:
> [    8.922670]          ff ff ff ff ff ff ff 00 22 64 e5 20 fb 01 00 00
> [    8.922676]          17 14 01 03 80 3b 25 78 ea af f6 a6 54 4c 9e 23
> [    8.922680]          10 4f 54 bf ef 80 d1 00 b3 00 a9 40 95 00 90 40
> [    8.922684]          81 80 81 40 71 4f 28 3c 80 a0 70 b0 23 40 30 20
> [    8.922688]          36 00 51 73 21 00 00 1a 00 00 00 ff 00 30 32 33
> [    8.922692]          4c 4b 33 51 41 30 30 35 30 37 00 00 00 fd 00 38
> [    8.922696]          4b 18 50 0f 00 0a 20 20 20 20 20 20 00 00 00 fc
> [    8.922700]          00 48 48 32 38 31 0a 20 20 20 20 20 20 20 01 e2
> 
> repeated 4 times. This is probably is separate problem?

Does it work correctly without the hw_i2c option?  If not, it's probably a
buggy monitor or a hdmi receiver that doesn't patch the checksum correctly.

You are receiving this mail because:
  • You are the assignee for the bug.
--1387287824.81B855120.29987-- --===============1345716032== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1345716032==--