Created attachment 709215 [details] dmesg -k Description of problem: I can not change the backlight on my DELL Inspiron using the Fn keys or the "Brightness and lock" menu, but echoing to /sys/class/backlight/intel_backlight/backlight works fine. When i resume from sleep, the brightness is at its lowest (unreadable) and I can't change it. When I use acpi_backlight=vendor on boot, i can change the brightness but when I resume it is still a black screen. Version-Release number of selected component (if applicable): kernel 3.8.2 How reproducible: Try to change the brightness Actual results: I can't. Expected results: I can. Additional info: Dell Inspiron 15r : http://www.dell.com/fr/p/inspiron-15r-se-7520/pd
Actually, with acpi_backlight=vendor and acpi_osi=Linux, it works fine on 3.8.3. But is was working without it before.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs. Fedora 18 has now been rebased to 3.11.4-101.fc18. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo. Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue. As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution If you experience different issues, please open a new bug report for those.