Radeon Device aa68 Graphics card (Cedar). Used in hybrid graphics with Intel i915 vgaswitcheroo, hence both are compiled in (Bug #36783 [1]) and KMS enabled (without KMS the problem usually not occurs). On boot, the screen tunrs of the backlight by itsself and has to be turned on manually[2]. A message in dmesg that is likely to be related says Firmware Bug: ACPI: No _BCQ method THe log has several errors related to the radeon. Kernel is 39-rc5. [1] https://bugs.freedesktop.org/show_bug.cgi?id=36783 [2] http://forums.gentoo.org/viewtopic-t-874961.html
Created attachment 46307 [details] dmesg
Created attachment 46384 [details] [review] possible fix Does this kernel patch help?
(In reply to comment #2) > Created an attachment (id=46384) [details] > possible fix > > Does this kernel patch help? No (tried on next-20110506).
This looks like a duplicate of bug 41306.
(In reply to comment #4) > This looks like a duplicate of bug 41306. Negative. It is related in thus far as that this problem (as I've mentioned in Bug #41306) constitutes the part where the backlight initially goes off. However, it's is not assumed, nor it is likely, that it is directly related to the problem that the backlight cannot be brought back on (which is, what the other bug concerns). Prior to the 3 series there have been times when the backlight would go off (with the error mentioned above) but could be brought back on nonetheless. As also mentioned in the other bug, these scenarios could, however, not be reproduced for unknown reasons. After all this bug should stay open and a priori assumed to be uncorrelated.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/issues/19.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.