There should be a solution to this dilemma, considering that nvidia's binary blob does it correctly.
I got the nvapeek results for using the binary blob, and the results I got are: Before 0000e100: 001c1100 0000e28c: 00000100 0000e104: 72266640 0441474b 0000e280: 44444747 00000000 After 0000e100: 001c1100 0000e28c: 00000100 0000e104: 72266640 0441474b 0000e280: 44444747 00000000 Notice that unlike nouveau, register 0xe104's content is unaltered after resuming. What is this particular register for? The vbios before suspending is identical between nouveau and nvidia, and it is also identical to the one after resuming with nvidia. However, nvgetbios fails with nouveau after resuming: ./nvagetbios > vbios.txt No extraction method specified (using -s extraction_method). Defaulting to PRAMIN. Attempt to extract the vbios from card 0 (nv96) using PRAMIN Invalid signature(0x55aa). You may want to try another retrieval method. Is this a sign that the vbios is somehow wrong/corrupted after resume? Note that I am also using a Elitebook 8530W, with an nVidia Corporation G96M [Quadro FX 770M] card, using Linux 3.1.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921321 Title: nouveau: dark screen after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/921321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
