Bug 423931
Summary: | M4300 backlight doesn't go off when lid is closed | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Larry Troan <ltroan> | ||||||
Component: | gnome-power-manager | Assignee: | Richard Hughes <rhughes> | ||||||
Status: | CLOSED ERRATA | QA Contact: | desktop-bugs <desktop-bugs> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | high | ||||||||
Version: | 5.1 | CC: | ichute, jfeeney, martinez, richard, tao, wwlinuxengineering, zcerza | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-01-20 20:50:54 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 391501 | ||||||||
Attachments: |
|
Description
Larry Troan
2007-12-13 19:47:16 UTC
Just an update on what I know: Yes, the most recent bios (A05) is loaded. I have used the nVidia binary driver (vers 169.09) as well as the Vesa xorg driver but neither have an effect on the backlight when the lid is closed as far as I can tell. I have noted that the button acpi driver is notified of the lid position and correctly updates the /proc/acpi/button/lid/LID/state contents (e.g. "open" when open and "closed" when closed). gnome-power-manager says "DPMS blanking screen because lid has been closed on ac power" when closed and "Turning LCD panel on..." when re-opened. I noticed that the backlight flashes when the lid is just about closed. Could this be the backlight is correctly turned off but then something incorrectly turns it back on, hence the flash? Looked for bios options but found nothing. Played with Preferences' Power Management options (suspend on lid close works) but "blank screen" still fails. Dell has found that with the addition of "xset dpms on/off" directive, the binary nVidia driver will turn off the backlight when the lid is closed. Thus, it would appear as though the issue is in the nv and vesa xorg drivers. As a result, I am re-assigning this bugzilla. This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". I don't see any root cause of this issue being described. Need more info on exactly what is broke and needs to be fixed before this is pushed out to next release. This issue blocked Dell's certification of RHEL5.1, so it needs more attention. Does the backlight come on by itself? If you disconnect all additional keyboards and mice from the laptop, and then close the lid - does the backlight stay off? Could you also do: lshal -m <shut lid> <wait 5 seconds> <open lid> <wait 5 seconds> and attach the information here. Many thanks. Hi Richard, The backlight never turns off. That's the problem. The screen blanks per the setting in gnome-power-preferences, but the backlight stays on. There are no additional keyboards, mice, or other peripherals attached to the laptop. # lshal -m Start monitoring devicelist: ------------------------------------------------- acpi_LID property button.state.value = true acpi_LID condition ButtonPressed = lid acpi_LID property button.state.value = false acpi_LID condition ButtonPressed = lid Chris, does the backlight turn off when you do "xset dpms force off" Richard. Hi Richard, Yes. The backlight does turn off with that command. Quick question here. Is it possible to put this command into the /etc/acpi/events/ directory? Maybe a lidclose event of some kind? --Chris Hi, Testing on RHEL5.2 Snapshot7 shows that this is still an issue. However, the 'xset dpms force off' command does now work with the open source nv driver. And if I ssh into the box while closing the lid, I can see the following message in syslogs when shutting the lid on the laptop: May 6 15:46:26 dhcp243-6 gnome-power-manager: (ctatman) DPMS blanking screen because the lid has been closed on ac power Can a script be provided that calls on 'xset dpms force off' when the lid is shut to fix this issue? I used to put my scripts in the /etc/acpi directory, but this does not appear to be working any more. Does pm-utils look elsewhere? Thanks! Who has the ball on this? It looks like Chris responded but it is still NEEDINFO for Larry but I don't see what is being asked of Larry. re-assigning to g-p-m This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. I really think g-p-m is doing the right thing here. You can see in /mnt/brew/packages/gnome-power-manager/2.16.0/9.el5/data/logs/i386/build.log that the rpm's are being built with DPMS support, and #c1 seems to verify that gnome-power-manager is talking to X asking to turn the panel off. It's very hard to debug this without any hardware to poke at. Actions I have for people with hardware: 1. does "xset dpms off" blank the same as "xset dpms force off"? 2. can you attach the complete X11/xorg.conf 3. are there any errors in .xsession-errors when you shut and re-open the lid? 4. are you using the nv, nvidia or vesa driver? 5. when the lid is shut (you emulate with a paperclip if it's a switch) does the panel flicker before going black? 6. Are any keys being pressed or mice being moved when the lid is shut? I've a funny feeling that Dell hardware does not kill the screen in hardware on lid close, XOrg is turning it off, and then something else is turning it on again. Maybe the lid close event wakes up the panel after g-p-m has asked it to sleep, and a few ms delay in g-p-m might do the trick. We don't want to add the events.d "fix" as this is just a hack around the real problem and might break existing setups. Hi Richard, 1. does "xset dpms off" blank the same as "xset dpms force off"? xset dpms off - returns an error xset: unknown option off xset dpms force off - blanks the screen 2. can you attach the complete X11/xorg.conf attached 3. are there any errors in .xsession-errors when you shut and re-open the lid? No errors. Attaching 'tail -f' capture file. 4. are you using the nv, nvidia or vesa driver? Using the nv driver. However, the vesa driver appears to be doing the same thing as well. 5. when the lid is shut (you emulate with a paperclip if it's a switch) does the panel flicker before going black? There is no switch that I can see for doing this. However, I can peer underneath the lid while it is closed (there's a gap), and there does not seem to be any flickering. 6. Are any keys being pressed or mice being moved when the lid is shut? No Created attachment 311716 [details]
requested xorg.conf file - from stock install of RHEL5.2
Created attachment 311717 [details]
tail -f on user .xsession-errors while closing and opening the lid
Right, I've now got my own Dell M4300 to play with. I can reproduce the bug, but it's very confusing. sudo killall hald killall gnome-screensaver killall gnome-power-manager acpi_listen & xset dpms force off -panel goes black- {shut lid} # button/lid LID 00000080 00000011 about 4mm from actually stutting the lid, the panel backlight is turned on {open lid} # button/lid LID 00000080 00000012 So we can rule out bugs in hal, gnome-power-manager or gnome-screensaver. So, I wanted to see if we could re-turn the panel off: sleep 5 && xset dpms force off & xset dpms force off -panel goes black- {shut lid} -panel comes back on- {wait 5 seconds} -panel goes black- So something is turning the panel back on when we shut the lid. Sanity check: /sbin/init 1 acpi_listen {shut lid} # button/lid LID 00000080 0000001b {open lid} # button/lid LID 00000080 0000001c So we have different ACPI event codes if we are in X or text mode. I'll turn my attention to X and the kernel to try and work out what's awaking the display. XOrg (hw/xfree86/os-support/linux/lnx_acpi.c) seem to only parse the "VIDEO" events, not the LID events. We're thinking this is a generated keypress that is waking up X. Is this NVIDIA graphics specific? Can anyone reproduce with ATI or Intel graphics? If I do: service acpid stop xset dpms force off then shut the lid, it stays blank. Unloading the button kernel module does the trick too. I'm sure none of the script in /etc/acpi/events are getting run, so this must be X (userspace) rather than anything in BIOS / kernel. Okay, I've worked around this the same way as in upstream. Can you please try the rpms here: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=1432175 If they work (or improve the situation), then these are good to go. Hi All, I just tested the rpm out, and it seems to have fixed the issue. I now see the backlight turning off when I close the lid. note: Had to reboot the laptop after installing the rpm before it worked. Maybe I just needed to restart X? Anyway, thanks Richard! --Chris This event sent from IssueTracker by ctatman issue 163882 Rez -- Here are the rpms so you can test them as well: http://people.redhat.com/martinez/.gnome/ Let us know how it goes! Patch committed and building, http://brewweb.devel.redhat.com/brew/taskinfo?taskID=1435308 *** Bug 423991 has been marked as a duplicate of this bug. *** VERIFIED in gnome-power-manager-2.16.0-10.el5 An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0082.html |