<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Nouveau fails to enter KMS with the Gigabyte G1 Gaming GTX970" href="https://bugs.freedesktop.org/show_bug.cgi?id=89664#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Nouveau fails to enter KMS with the Gigabyte G1 Gaming GTX970" href="https://bugs.freedesktop.org/show_bug.cgi?id=89664">bug 89664</a> from <a class="email" href="mailto:jonas.nordlund@gmail.com" title="Jonas Nordlund <jonas.nordlund@gmail.com>"> Jonas Nordlund</a> <pre>Is this perhaps <a class="bz_bug_link bz_status_NEW " title="NEW - [GM204] GTX 970 + 4GB VRAM fails at secboot (v4.6+)" href="show_bug.cgi?id=94990">bug 94990</a>? I also own an NVIDIA GTX 970 (Asus) and I can see the Gigabyte G1 Gaming GTX970 also has 4 GB VRAM. The problem here could be that NVIDIA made a controversial decision in making 3.5 GB VRAM full speed, but a special, subpar configuration for the remaining 0.5 GB making it approximately 7x slower than the "main" VRAM. And noveau doesn't support this. There are some tries with a hack in the bug above to have nouveau only use the initial 3.5 GB but I don't think it was successful yet as of April 2017. 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 options to get an initial low resolution unaccelerated boot, and while running that, blacklisting the nouveau driver and then finally installing the proprietary NVIDIA driver. A reboot after this, and it will (should) work with the caveat that caution is necessary with proprietary drivers and Kernel updates especially if using so called "rolling release" distros. I'm still having my hopes up for a fix! Would be the single most useful fix for the past two years for me.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>