Description of problem: In this package (xorg-x11-drv-i810) there are the drivers i810 and intel. On a Dell Latitude D610 with the i810 driver the screen is not as sharp as with the intel driver but you can suspend/hibernate and successfully resume... this is the main problem here: with the intel driver you're unable to use suspend/hibernate because the resume does not work with this driver... the problem did already exist in F8...and still in F9... Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. use "intel" as your Xorg driver on a Dell Latidue D610 (and probably others) 2. suspend 3. resume Actual results: screens keeps blank, backlight is on....you see the effort to restart the Xserver... no keyboard / mouse active...not able to switch to VT1 for example also CTRL+ALT+BACKSPACE does not respond... Expected results: Working again ;) Additional info:
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 308595 [details] xorg.conf - The xconfiguration used
Created attachment 308596 [details] Xorg.0.log with existing xorg.conf These are the log messages from Xorg.0.log while trying to resume / supsend with an existing xorg.conf (see attachment above)...
Created attachment 308597 [details] Xorg.0.log live messages with existing xorg.conf Here are some additional messages I could capture while logged on to the laptop over ssh....also this try is with an existing xorg.conf
Created attachment 308598 [details] Xorg.0.log restart try of X with existing xorg.conf Here you see the messages appearing, when I tried to restart the xserver (ssh login, kill Xserver pid, then simply start X...)
Created attachment 308599 [details] NoXorgConfig - Xorg.0.log These are the messages when trying to resume/suspend with NO xorg.conf (let Xserver detect all the hardware)...for the user the result remains the same...no difference recognizable for me...
Created attachment 308600 [details] NoXorgConfig - live messages Also with this setup I could get some additional messages...(while logged in through ssh)...here again without a xorg.conf
Created attachment 308601 [details] NoXorgConfig - restart try of X And here again the result for a restart try of X...
Ok, I hope I could give you the neccessary informations to further debug this issue...if not please let me know. cheers, Rolf
Are you sure it works with i810 driver on Fedora 9? [matej@viklef ~]$ ls -l /usr/lib/xorg/modules/drivers/i810_drv.so lrwxrwxrwx 1 root root 12 6. kvě 17.41 /usr/lib/xorg/modules/drivers/i810_drv.so -> intel_drv.so [matej@viklef ~]$ It's just a symlink to intel driver here.
Yes indeed, you're right. So in F9 it is not possible to use suspend/resume with a Dell Latitude D610...on F8 it was (when using i810 driver)... Any suggestions to be able to use suspending/resuming in F9??
Would some quirk (http://people.freedesktop.org/~hughsient/quirk/index.html and especially http://people.freedesktop.org/~hughsient/quirk/quirk-backlight-index.html) help?
sorry, the first URL should be http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-index.html
Ok, very strange: As I wanted to test the new debug steps of http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-advanced.html I just saw that when suspending with "pm-suspend" it is working....(with a small error, that the screens is not locked after resuming)... when suspending with system -> shut down -> suspend it is not...so what command is issued by suspend with gnome menu?? can I change the menu suspend command? suspending with on an open gnome-terminal with "pm-suspend" seems to work quite well (despite of the small error listed above)...
Not sure about proper component, so just throwing in the better direction.
Can you please provide the original wording of the error message? Please also report the output of: lshal | egrep "(system.hardware.(product|vendor|version)|system.firmware.version|power_management.quirk)"
There is no error message. As described above, when I'm suspend from a gnome-terminal with 'pm-suspend' resuming is working.... when I do suspend with the gnome menu system -> shut down -> suspend the xserver cannot resume... heres the output of the command: power_management.quirk.no_fb = true (bool) power_management.quirk.vbe_post = true (bool) power_management.quirk.vbestate_restore = true (bool) system.firmware.version = 'A03' (string) system.hardware.product = 'Latitude D610' (string) system.hardware.vendor = 'Dell Inc.' (string) system.hardware.version = '' (string)
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
since F10 this is running smoothly...