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 97066] Blank screen when starting KMS on a GTX970 for kernel 4.6 series
Date: Sun, 24 Jul 2016 18:21:12 +0000	[thread overview]
Message-ID: <bug-97066-8800-JeDMndgHgR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97066-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #4 from smmilut <pil.smmilut-zJpx2rpV7r/QT0dZR+AlfA@public.gmane.org> ---
Indeed, and the exact commercial model name is "Msi GTX970 Gaming 4G".

When booting with :
nouveau.noaccel=1 nouveau.nofbaccel=1
i have a normal image on screen when entering KMS, and get my normal high
resolution tty.
However, i am unable to start Xorg.
(attached are the corresponding Xorg.log and dmesg)

When you say "moving the secboot firmware out of the way", does it mean i just
have to temporarily rename the directory "/lib/firmware/nvidia/gm204" ?

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

[-- Attachment #1.2: Type: text/html, Size: 1500 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:[~2016-07-24 18:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-24 17:16 [Bug 97066] New: Blank screen when starting KMS on a GTX970 for kernel 4.6 series bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-97066-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-07-24 17:18   ` [Bug 97066] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-24 17:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-24 17:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-24 18:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-07-24 18:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-24 18:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-24 18:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-24 21:22   ` 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-97066-8800-JeDMndgHgR@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.