Hide Forgot
Description of problem: Grub2 sets screen brightness at lowest possible level. Version-Release number of selected component (if applicable): grub2-1.99-12.fc16.x86_64 How reproducible: Always Steps to Reproduce: 1. Install Fedora 16 with Grub 2. Reboot 3. Screen gets reset to lowest brightness setting. Actual results: Should be a minimal or max brightness so that user can actually see the screen. Expected results: Dark screen to low brightness. Additional info: Lenovo W520 Intel Graphics (Discrete Nvidia 1000M doesn't work at all on F16) Tried to configure options: acpi_osi=Linux acpi_backlight=vendor Neither Work....
Exactly what do you see, and why do you think it is grub2 that do something incorrectly? Do you see full brightness in the BIOS? And low brightness at the grub2 menu? I doubt that grub2 is aware of the brightness level at all. Kernel parameters will only be used by the kernel that is launched by grub2, so they would never be able to fix a problem in grub2.
It was an assumption that grub was the issue, I could be wrong. When grub comes online the screen is bright, but the moment it starts loading the ramdisk, the screen goes dark.
Yeah, that points at something grub. Can you try to choose the option for editing the boot menu and try to remove the load_video line and boot that? Do the brightness go away at the same place?
Yes, the brightness goes away right at the loading initial ramdisk.
Can you try to remove the ramdisk line and try to boot and see exactly when the brightness goes away? (The boot will then fail with a kernel oops that you might or might not see.) Do you see the same or different behaviour with a Fedora 16 live cd or other Fedora versions or other Linux distributions?
I haven't tried the Live CD but the screen issue did happen when installing F16.
Do you still see this issue? Can you try with a f17 beta live cd?
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.