All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 89664] Nouveau fails to enter KMS with the Gigabyte G1 Gaming GTX970
Date: Mon, 10 Apr 2017 18:10:15 +0000	[thread overview]
Message-ID: <bug-89664-8800-fTpN4D1uud@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89664-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #19 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to Jonas Nordlund from comment #18)
> Is this perhaps bug 94990?

If it is, should be solved by using drm-next.

> It's too bad because it cripples the GTX 970 on most Linux distros, leaving
> one with the remaining option to add the nomodeset option to the Linux boot

You could also boot with

nouveau.config=gr=0,sec=0

which should disable the graph unit initialization, causing the trouble. (Might
be secboot and not sec.) Note, I haven't tested this, going from memory on how
this works.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2017-04-10 18:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 19:17 [Bug 89664] New: Nouveau fails to enter KMS with the Gigabyte G1 Gaming GTX970 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-89664-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-03-18 19:20   ` [Bug 89664] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-18 19:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-18 19:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22  7:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 11:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 16:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 21:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 21:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 21:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 21:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 21:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 22:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 22:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-06-15 14:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-09 20:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-09 20:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-09 20:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-10 17:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-10 18:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-04-28 19:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-30 20:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-20 16:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-20 16:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-22 18:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-22 22:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-25  9:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-25  9:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-26  2:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-26 15:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-26 15:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-27  1:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-27 14:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 14:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 17:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-89664-8800-fTpN4D1uud@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.