https://bugs.freedesktop.org/show_bug.cgi?id=91779
--- Comment #12 from Ilia Mirkin <[email protected]> --- (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 NvForcePost=1 is still required, and > if not, maybe we'll need a quirk. And what can we do to get the firmware > for Joe User? Did you have a chance to do that? Not sure what can be done for Joe User here -- we need the vbios. No vbios = no go. VBIOS has info about what connectors are on the board, how they're hooked up, any scripts that need to be run to init the card (necessary on resume), scripts to run when changing modes, etc. It's likely that the EFI bios brings the card up enough to fool nouveau into thinking that the card is initialized (which it is), but it sets *something* up differently and nouveau doesn't reset it properly. But the VBIOS init routines do. So I think Joe User will be stuck having to do the NvForcePost. [You can look at what all vbios init does with the help of nvbios in envytools.] Now in order to operate the screen, EFI needs the VBIOS as well. So it has it somewhere... the usual thing to do is to stick it at the top of PRAMIN for the OS to be able to read it down the line. Not sure if you have access to modify something like that. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Nouveau mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/nouveau
