Bugzilla – Bug 666162
intel: Display backlight turns off forever
Last modified: 2012-08-02 15:58:27 UTC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_5; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10 When using 2.6.37 kernels from http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.3, Once backlight switched off by the kernel for powersaving reasons, it won't be turned on again until a suspend/resume cycle. Reproducible: Always Steps to Reproduce: 1. Install a kernel from the mentioned repository (I assume this is mostly the same as the factory release's kernel) 2. Restart the system 3. Wait for the kernel to switch off the backlight Actual Results: Backlight won't be back until switching to a character based vty and doing s2ram. Expected Results: Backlight shoud come back upon any human input.
Same problem here with Tumbleweed kernel 2.6.37-9-desktop.
*** Bug 669780 has been marked as a duplicate of this bug. ***
I'm having the same thing also in 64 bit VBox, RC1 kernel 2.6.37-20-desktop. When the screen saver (or rather dpms) blanks the screen it will never resume. My previous finding (later marked as duplicate of this one) is on EeePC, there the keyboard does not allow anything else than Sysrq, on this Vbox I can switch to F1 and run init 3. My workaround is xset s noblank xset -dpms -- Vahis
(In reply to comment #3) Why did you assign it to 64 bit architectures only? This symptom occurs on both 32 and 64 bit PC architectures. (I hope PC is the appropriate choice ;)
(In reply to comment #4) > (In reply to comment #3) > > Why did you assign it to 64 bit architectures only? This symptom occurs on both > 32 and 64 bit PC architectures. (I hope PC is the appropriate choice ;) I didn't. I reported it originally on a 32 bit real hardware system. It was then changed here to be a duplicate. Then I just added (to this duplicate) that have the same problem in 64 bit VirtualBox installation. -- Vahis
It applies to different Intel cards too, such as the Ironlake mentioned in https://bugzilla.novell.com/show_bug.cgi?id=673072
(In reply to comment #6) > It applies to different Intel cards too, such as the Ironlake mentioned in > https://bugzilla.novell.com/show_bug.cgi?id=673072 But that's a complete different issue.
(In reply to comment #7) > But that's a complete different issue. Yes, of course. That issue is completely different, but the graphic card affected by THAT issue is also affected by THIS issue. However, I'm afraid that the card affected by THIS issue might be affected by THAT issue :(((
*** Bug 675116 has been marked as a duplicate of this bug. ***
I don´t experience this anymore in openSUSE 11.4. Do you?
Is this possibly related to the following bug from Freedesktop.org: https://bugs.freedesktop.org/show_bug.cgi?id=29278 This bug involves some kernel-level issues with some of the later Intel chipsets. I experience very similar results trying to install SuSE onto my Dell Latitude E6510 - the install works, because it's using the VESA driver; however, as soon as the install is done and it boots with the real Intel driver, the backlight turns off and you can't get anything going on the display. Any chance the fixes mentioned in the drm-intel-next kernel tree could be back-ported into the openSuSE kernels, both for 11.4 and 11.3? I still experience this on 11.4. -Nick
With the coming release of openSUSE 12.2, openSUSE kernel developers are focusing their efforts there. Reports against openSUSE 11.4 and prior will not get the attention needed to resolve them before openSUSE 12.2 is release and openSUSE 11.4 becomes unmaintained. Please re-test with openSUSE 12.1 or openSUSE RC2+ and re-open with an updated Product if you still encounter your issue. We apologize for this issue not getting the attention it deserves but we are focusing our resources in the area where they will have the most impact for our users. We're working hard to make openSUSE 12.2 the best openSUSE release yet!