<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [snb] backlight issue on TOSHIBA PORTEGE R830 after suspend/resume" href="https://bugs.freedesktop.org/show_bug.cgi?id=82634#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [snb] backlight issue on TOSHIBA PORTEGE R830 after suspend/resume" href="https://bugs.freedesktop.org/show_bug.cgi?id=82634">bug 82634</a> from <a class="email" href="mailto:sylvain.pasche@gmail.com" title="Sylvain Pasche <sylvain.pasche@gmail.com>"> Sylvain Pasche</a> <pre>(In reply to Hans de Goede from <a href="show_bug.cgi?id=82634#c22">comment #22</a>) > Sylvain, do you still have an xorg.conf file hanging around telling the > intel ddx to use the intel_backlight interface? Can you try running the > latest Fedora-22 kernel without such a file and without any special kernel > commandline arguments? If that does not help then I'm afraid I'm all out of > ideas and one of the intel devs will need to look at reg-dumps and figure > out what exactly is going on at a much lower level. Hi Hans. I didn't have a xorg.conf file lying around. In fact, I also tested with the Fedora Workstation 22 installation DVD to make sure that I have nothing interfering. In this situation, I have the behavior described above: * two backlight interfaces are exposed: acpi_video0 and intel_backlight * they both work after boot * after suspend / resume, only the intel_backlight interface works * backlight is turned on after boot or resume Maybe we could implement the workaround in user space: set a udev device property telling Gnome that it should ignore the acpi_video0 interface and fall back to the intel_backlight one.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>