Description of problem: When booting from liveCD not working display backlight. Tested on emachines 525. Intel GMA 4500M graphics card. Version-Release number of selected component (if applicable): How reproducible: Booting Fedora 16 with a livecd Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Can you provide the output of acpidump for these machines, as well as the output of "ls /sys/class/backlight/*"
Acer Aspire 5734-Z4836 which runs fine on F14. I tried to boot F15 & F16 on this machine: * The screen goes blank. * Backlight is off. * ALT-F keys don't work * The CD just spins forever ... Get same results if I turn off graphic/boot login and quiet (F16). If you can get me to a prompt where I can startx (or another method of your choice) I will be glad to assist. I live down the road from your Raleigh campus. B
BTW -- xdriver=vesa parm did not help
I get the same behavior on a eMachines E725 w/Fedora 16 while booting from: - LiveCD - Installation DVD - HDD It starts normally but backlight gets turned off a few seconds after the boot image starts loading (as far as I can tell). Sometimes, playing with the backlight settings through the keyboard (changing its brightness or turning it on/off repeatedly) makes it stay turned on. Default settings were used on all boot attempts.
The xdriver=vesa nomodeset works
Created attachment 548022 [details] acpi dump
[brent@brent-laptop ~]$ ls /sys/class/backlight/* /sys/class/backlight/acpi_video0: actual_brightness brightness max_brightness subsystem uevent bl_power device power type /sys/class/backlight/intel_backlight: actual_brightness brightness max_brightness subsystem uevent bl_power device power type [brent@brent-laptop ~]$ acpidump.txt attached Acer Aspire 5734Z-4836
Acer Aspire using intel drivers: # works # echo "400" > /sys/class/backlight/intel_backlight/brightness # /sys/class/backlight/intel_backlight/brightness == 0 on boot # does not work # reinstalling bash # does not work - adding this kernel parm # acpi_backlight=vendor Using a second monitor to get the thing up and running. If you need something tested, let me know.
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
Same results. Kernel param lines acpi_backlight=vendor xdriver=intel Tried with and without acpi_backlight param. Splash "F" screen is has no backlight, after that I have a script in the init sequence to turn on backlight.
I have this problem on Fedora 17. Backlight works only with "acpi_osi=Linux acpi_backlight=vendor" and manually adding to the file /etc/rc.d/rc.local "echo 1589670 > /sys/class/backlight/intel_backlight/brightness" uname -a: Linux Emachines-E525 3.4.3-1.fc17.x86_64 #1 SMP Mon Jun 18 19:53:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Is this still being seen with the 3.5 kernels in F17?
I updated to latest code in repository. Removed the kernel parms: "xdriver=intel acpi_backlight=vendor". Removed the rc2.d script with: echo "400" > /sys/class/backlight/intel_backlight/brightness She boots and backlight works from grub to desktop .. no issues. Once I am logged in, the "ctrl <" and "ctrl >" display the info box and show the "intensity" bar ... but no change to intensity. lsmod shows i915 driver.
*** Bug 771351 has been marked as a duplicate of this bug. ***
(In reply to comment #15) > She boots and backlight works from grub to desktop .. no issues. Are you sure? I used a different workround which periodically turns the backlight full on. With a fully updated F17 the backlight still goes out during booting and stays off until my script turns it on.
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.
Duplicate of #753012?
Please re-open this bug. It is still present in F17. I will provide whatever info is needed.