From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 72180] [NVE6] Random GPU Lockups, works with blob PGRAPH fw Date: Tue, 02 Dec 2014 10:09:27 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1032990839==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "Nouveau" To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============1032990839== Content-Type: multipart/alternative; boundary="1417514967.b2A76B4.31908"; charset="UTF-8" --1417514967.b2A76B4.31908 Date: Tue, 2 Dec 2014 10:09:27 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=72180 --- Comment #40 from Matthias Nagel --- @Cedric: Well this means, that the kernel could not find the firmware. There are several ways how to do it and it depends on wether you have a initramfs or not, if the kernel has access to /lib/fimware when it tries to load the fw, if the the fw is directly included in the kernel or not, if you use an additional boot manager, etc. With UEFI: Does your UEFI directly load the Linux kernel or is there a boot manager in between. For example, I use "rEFInd" as boot manager, but I guess Debian uses grub2 by default. My setup is the following: (a) Boot manager "rEFInd" (b) No initramfs (c) FW directly included in kernel. This requires "CONFIG_FIRMWARE_IN_KERNEL=y" and "CONFIG_EXTRA_FIRMWARE=\"nouveau/...\"" to be set. In my experience, putting the fw directly into the kernel is the easiest way, because one does not need to bother with correct pathes and mount points during boot. Unfortunately, I cannot give you more detailed advices, because I turned my back to Debian long time ago. -- You are receiving this mail because: You are the assignee for the bug. --1417514967.b2A76B4.31908 Date: Tue, 2 Dec 2014 10:09:27 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 40 on bug 72180 from 
@Cedric: Well this means, that the kernel could not find the firmware. There
are several ways how to do it and it depends on wether you have a initramfs or
not, if the kernel has access to /lib/fimware when it tries to load the fw, if
the the fw is directly included in the kernel or not, if you use an additional
boot manager, etc. With UEFI: Does your UEFI directly load the Linux kernel or
is there a boot manager in between. For example, I use "rEFInd" as boot
manager, but I guess Debian uses grub2 by default.

My setup is the following:
(a) Boot manager "rEFInd"
(b) No initramfs
(c) FW directly included in kernel. This requires "CONFIG_FIRMWARE_IN_KERNEL=y"
and "CONFIG_EXTRA_FIRMWARE=\"nouveau/...\"" to be set.

In my experience, putting the fw directly into the kernel is the easiest way,
because one does not need to bother with correct pathes and mount points during
boot. Unfortunately, I cannot give you more detailed advices, because I turned
my back to Debian long time ago.

You are receiving this mail because:
  • You are the assignee for the bug.
--1417514967.b2A76B4.31908-- --===============1032990839== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cDovL2xpc3RzLmZy ZWVkZXNrdG9wLm9yZy9tYWlsbWFuL2xpc3RpbmZvL25vdXZlYXUK --===============1032990839==--