Bug 448317
Summary: | D820: wrong quirks leads to failed resume | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mads Villadsen <maxx> | ||||||
Component: | hal-info | Assignee: | David Zeuthen <davidz> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 9 | CC: | ajax, kevin, linux-bugs, mclasen, richard | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-07-14 15:11:00 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: | |||||||||
Attachments: |
|
Description
Mads Villadsen
2008-05-25 20:37:28 UTC
Oddly my D820 with intel graphics works just fine out of the box with Fedora 9. What bios version do you have? # dmidecode | grep "BIOS Revision" here shows version 08. # lspci | grep -i disp 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) [root@ice ~]# dmidecode | grep "BIOS Revision" BIOS Revision: 0.7 [root@ice ~]# lspci | grep -i disp 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) So my BIOS is older than yours. I guess I will have a go at updating it then. I upgraded my BIOS to version 0.8 and the suspend/resume problem is still there with the standard quirks file - and the solution I mentioned also still works. Very strange. Yeah, quite strange. Can't think of much else that could be causing the difference. :( Does this fix still need applying using F9? if so, please email the hal development mailing list and we'll review your quirk there. Thanks. Well, the odd thing is that it seems Mads and I have the same laptop, but it works for me, but not for him. What version of hal-info do you have? hal-info-20080508-1.fc9.noarch here. I also have hal-info-20080508-1.fc9.noarch. So it would seems that everything about our machines are identical. My machine is running with a screen resolution of 1920x1200 - not that it should matter but there has to be a difference somewhere between our two machines to make them not behave identical. My wireless card is an ipw3945 if that makes a difference. Can you try using the line <merge key="power_management.quirk.dpms_on" type="bool">true</merge> instead of <merge key="power_management.quirk.vbestate_restore" type="bool">true</merge> in the D820 section of /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-dell.fdi to see if it works for you? sorry for the delay. I tried using the line in comment #7. It results in a resume where the screen is bright white and unusable. You can get the screen back by switching to a vty and back, but thats hardly something most people would know to try. :( I'm at a loss to explain why our two laptops would be so different here. I have the same screen and wireless. I'm going to attach my /var/log/Xorg.0.log, perhaps you can check it against yours? Created attachment 308666 [details]
Xorg.0.log
My Xorg.0.log file.
I will attach my xorg log file as well. The differences I can see are related to your machine being 64-bit and mine 32-bit. Also there is a difference with the EDID vendor (not sure what that means): < (II) intel(0): EDID vendor "SEC", prod id 12885 --- > (II) intel(0): EDID vendor "SHP", prod id 5053 And there is a difference with the amount of memory: < (II) intel(0): Kernel reported 488960 total, 1 used < (II) intel(0): I830CheckAvailableMemory: 1955836 kB available --- > (II) intel(0): Kernel reported 810752 total, 1 used > (II) intel(0): I830CheckAvailableMemory: 3243004 kB available Created attachment 308694 [details]
xorg log file
Wacky. I just talked to someone on IRC that has a D820, with the same EDID vendor as you, and it works fine for them. ;( Can you try it with no quirks at all set? Running with no quirks at all (using either pm-suspend or pm-suspend --quirk-none) works fine for me. Sadly, running with --quirk-none here gets me the bright white screen on resume. ;( Can anyone suggest any further way to tell the two types apart? I am going to add Ajax (X maintainer) and the dell linux folks here... 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 Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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. |