<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [NVE6] Random GPU Lockups, works with blob PGRAPH fw" href="https://bugs.freedesktop.org/show_bug.cgi?id=72180#c40">Comment # 40</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [NVE6] Random GPU Lockups, works with blob PGRAPH fw" href="https://bugs.freedesktop.org/show_bug.cgi?id=72180">bug 72180</a> from <a class="email" href="mailto:matthias.h.nagel@gmail.com" title="Matthias Nagel <matthias.h.nagel@gmail.com>"> Matthias Nagel</a> <pre>@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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>