Red Hat Bugzilla – Bug 358671
intel video suspend/resume - requires VT switch to restore X
Last modified: 2013-03-05 22:53:33 EST
Description of problem:
Dell D620 using 'intel' video driver. When resuming from suspend, X will not
come back up until you switch to a text console and back, eg. <ALT>-F1, then
<ALT>-F7. (even though text mode console doesnt actually work: see BZ# 358631)
The driver displays a funkadelic screen with interesting vertical green lines
Works ok with 'i810' driver.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Dell D620 with core2 duo processor running SMP
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS, 943/940GML
Express Integrated Graphics Controller (rev 03)
Linux duo 220.127.116.11-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 x86_64
The moon is 2160 miles in diameter.
Created attachment 243981 [details]
this is the xorg.conf
The issue cannot be reproduced without an xorg.conf because the system defaults
to 'i810' driver.
Created attachment 243991 [details]
Xorg.0.log from before suspend
Created attachment 244001 [details]
Xorg.0.log from after resume
Comment on attachment 243991 [details]
Xorg.0.log from before suspend
obsolete because description shows up wrong in comment list...
Looks like this needs to be added to the quirks list for this machine? (Latitude
D620 with intel 945 video)
cloned the upstream git repo per
The upstream repository appears to already have these quirks. When is the next
update going to be released with this patch?
Changing component to people who are responsible for maintaining the quirks.
*** Bug 312901 has been marked as a duplicate of this bug. ***
Same problem, but that quirk does not work for me, intel 945 video as well. I
can get the console back with --quirk-vbemode-restore. When I use the post,
nothing changes and i get a lot of "enters" in the terminal.
(In reply to comment #10)
> Same problem, but that quirk does not work for me, intel 945 video as well. I
> can get the console back with --quirk-vbemode-restore. When I use the post,
> nothing changes and i get a lot of "enters" in the terminal.
*** Bug 389541 has been marked as a duplicate of this bug. ***
There is tone of information in bug 389541 which was closed as duplicate of this
I'm not sure this is really a duplicate of 389541 as for me on a Dell M1330 with
intel hardware after resuming, X is fine, it's just the brightness is low.
Changing to VT1 and back restores the brightness.
Reporter, is this really different from your experience?
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "CLOSED INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.
Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9.
I have manualy pached my quirks-file, so it works-for-me (now) - but has the
patch from upstream trickled down to fedora?
Care to share the patch? I know it's not fixed in F8 as my wife's 1330 still has
with kernel-18.104.22.168-64.fc8 and last intel drive (from gits) , works for me
(In reply to comment #18)
> Care to share the patch? I know it's not fixed in F8 as my wife's 1330 still has
> the problem.
In /usr/share/hal/fdi/information/10freedesktop, edit the file
I added this <match> tag:
<match key="system.hardware.product" contains="D520">
<merge key="power_management.quirk.vbe_post" type="bool">true</merge>
You should match the model and/or make of the computer correctly, but this is
how you do it. Also check that you are using the right (combination) of quirks
first. The possible quirks may be found at:
Restarted hal (maybe rebooted?), and it worked.