Nouveau - Jul 2016 - [Bug 97066] New: Blank screen when starting KMS on a GTX970 for kernel 4.6 series

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

            Bug ID: 97066
           Summary: Blank screen when starting KMS on a GTX970 for kernel
                    4.6 series
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: pil.smmilut at yandex.com
        QA Contact: xorg-team at lists.x.org

Created attachment 125292
  --> https://bugs.freedesktop.org/attachment.cgi?id=125292&action=edit
full dmesg when experiencing the bug, and with drm.debug=14 log_buf_len=16M

Hello,

Since i upgraded my kernel from 4.5.4 to 4.6.3, the screen goes
"blank" when
entering KMS, instead of giving the high resolution tty.
By "blank", i mean it has a uniform colour : during some boots
it's pure red,
other boots it's pure magenta, and sometimes pure white.
The system is functional and i am able to ssh remotely into the machine.

My setup :
- single 2560x1440 monitor
- NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1) (prog-if 00 [VGA
controller])
- both DVI and DisplayPort ports exhibit the issue
- Arch Linux

If i disable modesetting, i am able to see an image on the screen (low
resolution tty) and login to the system (no Xorg though, as expected).

I found bug 94990 which seems similar, although the symptoms are a bit
different (his monitor goes to sleep, mine remains ON and monochromatic). Also,
i have a similar motherboard (Z97-A).

So i tried one advice i saw there : booting with nouveau.config=NvForcePost=1
got me no signal instead of a uniform colour.

Sorry if i'm actually posting a duplicate, i'm not very experienced with
this
:) I'll try provide more info if i can.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160724/6b69275c/attachment.html>

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

--- Comment #1 from smmilut <pil.smmilut at yandex.com> ---
Created attachment 125293
  --> https://bugs.freedesktop.org/attachment.cgi?id=125293&action=edit
lspci -v

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160724/9ca93325/attachment.html>

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

--- Comment #2 from smmilut <pil.smmilut at yandex.com> ---
Created attachment 125294
  --> https://bugs.freedesktop.org/attachment.cgi?id=125294&action=edit
kernel config in 4.6.4

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160724/ee28c139/attachment.html>

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

--- Comment #3 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Observation for Alexandre: This GTX 970 also has 4GB of VRAM.

For the OP: you can probably restore your original functionality by booting
with

nouveau.noaccel=1 nouveau.nofbaccel=1

or alternatively by moving the secboot firmware out of the way
(/lib/firmware/nvidia/gm204) temporarily.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160724/ed0201c6/attachment.html>

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

--- Comment #4 from smmilut <pil.smmilut at yandex.com> ---
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160724/f9c75972/attachment.html>

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

--- Comment #5 from smmilut <pil.smmilut at yandex.com> ---
Created attachment 125295
  --> https://bugs.freedesktop.org/attachment.cgi?id=125295&action=edit
Xorg.0.log file when trying to start Xorg after selecting nouveau.noaccel=1
nouveau.nofbaccel=1

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160724/98266987/attachment-0001.html>

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

--- Comment #6 from smmilut <pil.smmilut at yandex.com> ---
Created attachment 125296
  --> https://bugs.freedesktop.org/attachment.cgi?id=125296&action=edit
dmesg when trying to start Xorg after selecting nouveau.noaccel=1
nouveau.nofbaccel=1

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160724/d47e771c/attachment.html>

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

--- Comment #7 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to smmilut from comment #5)
> Created attachment 125295 [details]
> Xorg.0.log file when trying to start Xorg after selecting nouveau.noaccel=1
> nouveau.nofbaccel=1
Fun. Looks like Xorg properly falls back to modesetting (yay), but then just
hangs there when trying to initialize glamor. No idea why.

I think there's some Xorg config option you can provide to avoid loading
glamor. Not sure what it is.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160724/ae103e6b/attachment.html>

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

Ilia Mirkin <imirkin at alum.mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #8 from Ilia Mirkin <imirkin at alum.mit.edu> ---


*** This bug has been marked as a duplicate of bug 94990 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20160824/5ec29c28/attachment.html>