https://bugs.freedesktop.org/show_bug.cgi?id=34348
--- Comment #4 from Dragos Delcea <[email protected]> 2011-02-21 06:38:47 PST --- (In reply to comment #3) .. > I'll start a new bisect with 85341f27b49833325f97580edcd687b4d90bb30b as the > good and v2.6.37 as the bad and report back..another 13 steps..doh. due some hardware related problems I had the internal display swapped with a new one (the internal display was occasionally flickering badly), and now the situation is completely upside down: 2.6.37 works, while 2.6.36 doesn't anymore. The flickering display problem was going on for some time, even back in the 2.6.35 and 2.6.36 times, and it was manifesting even during BIOS POST, hence the thinking that it was a hw problem. However, now I'm thoroughly confused about the current situation. Is the newer display different and triggers different (inverse) behavior? I can't see any meaningful difference in dmesg output of 2.6.37 between working and non working... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- 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
