https://bugzilla.kernel.org/show_bug.cgi?id=25052 Elmar Stellnberger <estellnb@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|PATCH_ALREADY_AVAILABLE | --- Comment #6 from Elmar Stellnberger <estellnb@xxxxxxxxx> 2011-01-10 17:56:05 --- Oops; it had only worked because the drm.edid_strict option made the still unchanged radeon module refuse to load. The external screen however is only blackened as soon as radeon is modprobed. If you apply the patch correctly and get the changed module shipped (which didn`t work in first place for whatever reason) the following happens if you specify drm.edid_strict on the kernel command line: integrated screen: whitened (fully white) external screen: black, no response At first it was still possible to switch back to vt01-03 and text modes were displayed correctly. Then suddenly everything was black and only a Ctrl-Alt-Delete could help me out. Somehow looks as if it was not beneficial to use the EDID data of that screen or do you see another possibility? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl -- _______________________________________________ Dri-devel mailing list Dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/dri-devel _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
