[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 Martin Peres changed: What|Removed |Added Resolution|--- |MOVED Status|NEW

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #15 from Jeremy Huddleston Sequoia --- Yeah, it seems that it's getting loaded from the initial ramdisk now for some reason, where it wasn't in the past. Shoving it onto the initrd solved the issue. Oddly,

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #14 from Ilia Mirkin --- (In reply to Jeremy Huddleston Sequoia from comment #13) > As you can see, the loading of /lib/firmware/vbios.rom fails with ENOENT, > but it's certainly there. I verified that

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #13 from Jeremy Huddleston Sequoia --- After upgrading to Ubuntu 16.04.1, something seems off, and I'm having trouble locking it down. I'm still using the exact same kernel that I was before the upgrade

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #12 from Ilia Mirkin --- (In reply to Jeremy Huddleston Sequoia from comment #11) > So now that *I'm* up and running, what can we do to help out Joe User here? > I'll try out a newer kernel to see if

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #11 from Jeremy Huddleston --- Sweet. Thanks for the help. So with 'sudo modprobe nouveau config=NvBios=vbios.rom,NvForcePost=1', I'm seeing things working great so far. The kernel logging from the

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 Jeremy Huddleston jerem...@freedesktop.org changed: What|Removed |Added See Also|

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #7 from Jeremy Huddleston jerem...@freedesktop.org --- I'd file a new one OK. Forked off to bug #91804 then. I was just thinking that getting this configuration to work might just not be supported, but if you want to keep heading

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #10 from Ilia Mirkin imir...@alum.mit.edu --- (In reply to Jeremy Huddleston from comment #9) BTW, copying /sys/kernel/debug/dri/0/vbios.rom to /lib/firmware when in BIOS-emulation mode has allowed me to get nouveau loaded when in

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #9 from Jeremy Huddleston jerem...@freedesktop.org --- BTW, copying /sys/kernel/debug/dri/0/vbios.rom to /lib/firmware when in BIOS-emulation mode has allowed me to get nouveau loaded when in pure EFI mode via: $ sudo modprobe

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #8 from Ilia Mirkin imir...@alum.mit.edu --- (In reply to Jeremy Huddleston from comment #7) I'd file a new one OK. Forked off to bug #91804 then. I was just thinking that getting this configuration to work might just not be

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #5 from Jeremy Huddleston jerem...@freedesktop.org --- Thanks Ilia, I think the most pressing issue here is to get users a working fb when they boot in such a configuration (eg: Ubuntu's and Fedora's recent live cds). Can we use

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #6 from Ilia Mirkin imir...@alum.mit.edu --- (In reply to Jeremy Huddleston from comment #5) Thanks Ilia, I think the most pressing issue here is to get users a working fb when they boot in such a configuration (eg: Ubuntu's and

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #3 from Jeremy Huddleston jerem...@freedesktop.org --- Or perhaps instead of duping this to a make nouveau work in EFI ticket, could we instead use this to have nouveau fail more gracefully (eg: handing fb back to EFI VGA upon

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 Jeremy Huddleston jerem...@freedesktop.org changed: What|Removed |Added Summary|MacBookPro3,1 (NV84) fails |Pure EFI:

[Nouveau] [Bug 91779] Pure EFI: MacBookPro3, 1 (NV84) fails to load nouveau on linux 4.1 -- Invalid ROM contents

https://bugs.freedesktop.org/show_bug.cgi?id=91779 --- Comment #4 from Ilia Mirkin imir...@alum.mit.edu --- I believe the situation is that the mac bios normally sticks the gpu's vbios into either acpi or its pramin by executing the option rom. Once you've booted and you don't have it in ACPI or