Red Hat Bugzilla – Bug 446882
Problems in intel driver (Xorg)
Last modified: 2010-10-22 21:03:54 EDT
Description of problem:
This is the comment in IT 124575, describing the problems LVM still has with the
We have now the results of the final tests available. Because there were so many
faults in the different tests I made some additional testings based on the
unique test results:
1. X starts with the correct resolution (1280x1024) but xrandr /
gnome-display-properties shows resolutions up to 1600x1024. I have captured
this in: xorg.0.log_lg1800p202kg_x61.log and lg1800p202kg_x61.txt as well as
2. X starts with a wrong resolution 1280x786 and the user can't set the correct
one. I have seen this on the Esprimo: xorg.0.log_lg1800p202kg_esprimo.log
3. X starts with a wrong resolution 1280x800. This is with different displays on
the T61 with lid open. Logfiles are: xorg.0.log_lg1800p206kg_t61_lid_open.log,
xorg.0.log_fscb17-1t7k03_t61_lid_open.log. Output of xrandr is in
Regarding the black screen phenomenon we have seen very often I can report that
with Option "modedebug" "on"
I never have seen this. Without this option we ran into this problem in most of
the display tests.
I did an crosscheck and disbled the option in xorg.conf but I was not able to
reproduce this problem. I had also removed the battery pack from my laptop.
After the next reboot I got the black screen.... At the moment
we can live with the "modedebug on" as workaround.
Steps to Reproduce:
see IT 124575 and attachments
original IT is 124575
Created attachment 305697 [details]
Created attachment 305761 [details]
fscb17-1t7k03_t61_open.txt from the attachment 305697 [details]
Created attachment 305762 [details]
lg1800p202kg_x61.txt from the attachment 305697 [details]
Created attachment 305763 [details]
lg1800p206kg.txt from the attachment 305697 [details]
Created attachment 305764 [details]
lg1800p206kg_t61_open.txt from the attachment 305697 [details]
Created attachment 305765 [details]
xorg.0.log_eizol985ex_t61_lid_open.log from the attachment 305697 [details]
Created attachment 305766 [details]
xorg.0.log_fscb17-1t7k03_t61_lid_open.log from the attachment 305697 [details]
Created attachment 305767 [details]
xorg.0.log_fscx180FG500_x61.log from the attachment 305697 [details]
Created attachment 305768 [details]
xorg.0.log_lg1800p202kg_esprimo.log from the attachment 305697 [details]
Created attachment 305769 [details]
xorg.0.log_lg1800p202kg_x61.log from the attachment 305697 [details]
Created attachment 305770 [details]
xorg.0.log_lg1800p206kg_t61_lid_open.log from the attachment 305697 [details]
Created attachment 305771 [details]
xorg.0.log_lg1800p206kg_x61.log from the attachment 305697 [details]
Comment on attachment 305697 [details]
we prefer all files unpacked and separate
1.6.5-9.15.el5 has been rebuilt against the new randr sources, which should at least make things fail differently.
Moving to MODIFIED.
I tested on snap4 x86_64 on a X61 with ViewSonic VX2025wm external monitor. I still see the same issue. The correct mode is used, but xrandr and gnome-display-properties still shows modes that do not work. I will attach x log and xrandr output.
Created attachment 325562 [details]
x log for X61 and viewsonic VX2025wm
Created attachment 325563 [details]
xrandr output for X61 with VX2025wm
Which ones don't work?
Neither of the 1920x modes worked. I spot checked mode smaller that 1680 and they worked. I can do a more thorough test of all the modes.
This is going to be awkward. We can avoid adding the default mode set to the list if the monitor doesn't claim to be continuous-frequency, but some do and some don't. And there's no really good way to know the size of the monitor in pixels, so we can't necessarily just toss bigger modes out.
Already built as xorg-x11-drv-i810-1.6.5-9.21.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.