All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207901] Nouveau: In a 4 monitor setup, 1-2 displays remains black after boot
Date: Mon, 27 Jul 2020 15:32:42 +0000	[thread overview]
Message-ID: <bug-207901-2300-y07cb0qMOo@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207901-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=207901

--- Comment #26 from Maurice Gale (mauricegale1@gmail.com) ---
Sorry for the delay and the mistake. It loaded the 5.3 kernel by default. I
recreated the log using 5.7-rc5 with the i2c timeout patch. I also added the
new grub options. The file size is much larger than the old one, so it should
be correct this time.

I noticed that I have more luck getting all monitors displayed when I do not
have the Display->MiniDisplay connected (Swap it out for Display->HDMI). It
seems as though mini display is causing some issues.

Again, thank you so much for your help, and please let me know if you need
anything else.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-07-27 15:32 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 19:17 [Bug 207901] New: Nouveau: In a 4 monitor setup, 1-2 displays remains black after boot bugzilla-daemon
2020-05-26 19:19 ` [Bug 207901] " bugzilla-daemon
2020-05-26 19:20 ` bugzilla-daemon
2020-05-26 19:20 ` bugzilla-daemon
2020-05-26 19:21 ` bugzilla-daemon
2020-05-26 19:26 ` bugzilla-daemon
2020-05-26 19:28 ` bugzilla-daemon
2020-05-27 15:37 ` bugzilla-daemon
2020-05-27 15:38 ` bugzilla-daemon
2020-05-27 15:38 ` bugzilla-daemon
2020-05-27 16:36 ` bugzilla-daemon
2020-05-27 19:35 ` bugzilla-daemon
2020-05-27 19:35 ` bugzilla-daemon
2020-05-27 19:37 ` bugzilla-daemon
2020-06-10 22:28 ` bugzilla-daemon
2020-06-10 23:49 ` bugzilla-daemon
2020-06-11 17:31 ` bugzilla-daemon
2020-06-18 15:14 ` bugzilla-daemon
2020-06-18 15:30 ` bugzilla-daemon
2020-06-23 16:49 ` bugzilla-daemon
2020-06-25 15:27 ` bugzilla-daemon
2020-06-25 15:28 ` bugzilla-daemon
2020-07-02 19:03 ` bugzilla-daemon
2020-07-13 14:51 ` bugzilla-daemon
2020-07-13 14:52 ` bugzilla-daemon
2020-07-20 21:44 ` bugzilla-daemon
2020-07-27 15:32 ` bugzilla-daemon [this message]
2020-07-27 15:37 ` bugzilla-daemon
2020-07-31 21:23 ` bugzilla-daemon
2020-08-10 15:32 ` bugzilla-daemon
2020-09-21 18:54 ` bugzilla-daemon
2020-11-02 15:48 ` 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-207901-2300-y07cb0qMOo@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.