dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107823] [amdgpu/displayport] Blackscreen on native resolution
Date: Wed, 17 Oct 2018 19:23:22 +0000	[thread overview]
Message-ID: <bug-107823-502-cbU6Uwq9Rc@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107823-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 918 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107823

--- Comment #12 from raxondmc@gmail.com ---
I've tried with a monitor I have with my 580x :

Here is the modeline your monitor has: 

[ 49.626518] [drm:drm_mode_debug_printmodeline [drm]] Modeline 64:"1680x1050"
60 146250 1680 1784 1960 2240 1050 1053 1059 1089 0x48 0x6


Here is mine: 

<div> [drm:drm_mode_debug_printmodeline [drm]] Modeline 68:"1680x1050" 60
146250 1680 1784 1960 2240 1050 1053 1059 1089 0x40 0x6

Now, the diff seems to be second last print on the lines. That said, my monitor
is not 1680x1050 native, but it supports this mode. 

Clocks seems to be the same, now i am wondering if it's the panel (NEC) in your
case that is picky or just Carrizo PLL's are not encoding at that modulated
clock.

I'll try to find a CZ and try it.

Cheers.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1714 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-10-17 19:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 14:40 [Bug 107823] [amdgpu/displayport] Blackscreen on native resolution bugzilla-daemon
2018-09-04 14:40 ` bugzilla-daemon
2018-09-04 14:41 ` bugzilla-daemon
2018-09-04 14:51 ` bugzilla-daemon
2018-09-04 14:52 ` bugzilla-daemon
2018-09-04 14:52 ` bugzilla-daemon
2018-10-15 18:31 ` bugzilla-daemon
2018-10-16  8:37 ` bugzilla-daemon
2018-10-16 17:27 ` bugzilla-daemon
2018-10-16 20:08 ` bugzilla-daemon
2018-10-17  9:56 ` bugzilla-daemon
2018-10-17 16:03 ` bugzilla-daemon
2018-10-17 19:23 ` bugzilla-daemon [this message]
2018-10-17 19:56 ` bugzilla-daemon
2018-10-18  7:29 ` bugzilla-daemon
2018-11-15 15:06 ` bugzilla-daemon
2018-11-15 15:08 ` bugzilla-daemon
2018-11-15 15:09 ` bugzilla-daemon
2018-11-20 20:52 ` bugzilla-daemon
2018-11-22  8:19 ` bugzilla-daemon
2018-11-28 13:36 ` bugzilla-daemon
2018-11-28 13:37 ` bugzilla-daemon
2018-11-28 13:37 ` bugzilla-daemon
2018-12-03 23:34 ` bugzilla-daemon
2018-12-05 17:13 ` bugzilla-daemon
2019-11-19  8:54 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107823-502-cbU6Uwq9Rc@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox