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 72180] [NVE6] Random GPU Lockups, works with blob PGRAPH fw
Date: Wed, 08 Jan 2014 20:34:21 +0000	[thread overview]
Message-ID: <bug-72180-8800-A9wN7HiiQc@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-72180-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #25 from Brandon Bertelsen <brandon-h6AymINWW/kV+D8aMU/kSg@public.gmane.org> ---
I suffered from the same bug. I was able to fix it with some help from users on
IRC as well as the files presented here. Figured I'd provide explicit
instructions for others. (I'm using Ubuntu 13.10). 

1. First make sure you have NV6 firmware

$dmesg | grep nouveau | grep Chipset

You should see something that looks like: 

[    2.318701] nouveau  [  DEVICE][0000:01:00.0] Chipset: GK106 (NVE6)

2. Download and move the files from Jordan Bass (thanks!) in comment 19

sudo mkdir /lib/firmware/nouveau
sudo /path/to/extractedfiles/* /lib/firmware/nouveau

3. Update initramfs

sudo update-initramfs -c -k <YOUR_KERNEL>

4. Update GRUB

sudo nano /etc/default/grub

Add nouveau.config=NvGrUseFW=1 to GRUB_CMDLINE_LINUX_DEFAULT so that it looks
like: 

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nouveau.config=NvGrUseFW=1"

5. Update grub

sudo update-grub

6. Restart and verify

sudo shutdown -r now

On restart: 

$dmesg | grep external

[    2.484773] nouveau  [  PGRAPH][0000:01:00.0] using external firmware

If you see PGRAPH using external firmware, you're done.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-01-08 20:34 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30 18:05 [Bug 72180] New: Nouveau Random GPU Lockups bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-72180-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-11-30 18:06   ` [Bug 72180] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-30 18:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-30 18:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-30 20:25   ` [Bug 72180] [NVE6] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-30 22:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-30 22:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 13:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 13:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 14:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 14:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 14:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 15:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 15:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 17:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 21:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-01 23:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-02 18:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-02 23:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-03  0:38   ` [Bug 72180] [NVE6] Random GPU Lockups, works with blob PGRAPH fw bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-03 17:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-17 22:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-17 22:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-17 22:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-02 22:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-08  5:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-08 20:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-01-09  3:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-03 10:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-03 17:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-05 13:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-12 18:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-21 17:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-22 23:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-01 17:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-01 17:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-01 17:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-01 17:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-01 17:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-01 20:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02  9:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 10:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-25 17:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-06-28 23:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 21:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 21:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 22:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-07 23:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-15 12:59   ` 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-72180-8800-A9wN7HiiQc@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.