<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Pure EFI: MacBookPro3,1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents" href="https://bugs.freedesktop.org/show_bug.cgi?id=91779#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Pure EFI: MacBookPro3,1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents" href="https://bugs.freedesktop.org/show_bug.cgi?id=91779">bug 91779</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to Jeremy Huddleston Sequoia from <a href="show_bug.cgi?id=91779#c13">comment #13</a>) > As you can see, the loading of /lib/firmware/vbios.rom fails with ENOENT, > but it's certainly there. I verified that /lib/firmware/vbios.rom is > exactly the same as /sys/kernel/debug/dri/0/vbios.rom in BIOS-emulation mode. > > Odd... gonna have to dig into it a bit more later, but if you have any > ideas, I'd appreciate them. The usual situation is that it's not there, and so ENOENT is returned. Note that it has to be there when nouveau loads, not at some later point in time, when, say, the real root partition is mounted. To maximize confusion, distro kernel builds like to load modules from initrd, and if nouveau is loaded there, you'll want to ensure that your vbios.rom is available from there as well. If you build your own kernel and don't plan on soldering in random hardware (esp not new disk controllers) into your laptop without first doing a rebuild, you can stick the vbios.rom directly into the kernel and avoid this frustration via CONFIG_EXTRA_FIRMWARE or something similar.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>