Bug 302484

Created attachment 159035 [details]
xorg.conf

Created attachment 159036 [details]
Xorg.tgz

DefaultDepth 24
SubSection "Display"
    Depth      24
    Modes      "1280x1024" 
EndSubSection

(II) intel(0): Output VGA using initial mode 1600x1024

This looks pretty bogus to me.

Unfortunately SaX2 on Beta2 was not finished yet. Could you try again with the latest SaX2 packages? These need to be mbuilded with the sources in  /work/src/done/STABLE/sax2/ first since SaX2 has not been checked in yet. Then attach /etc/X11/xorg.conf and /var/log/Xorg.0.log again. Thanks.

still same problem with sax2-8.1-212

Created attachment 160310 [details]
xorg.conf

Created attachment 160311 [details]
Xorg.0.log

This driver is still so broken. :-( Does it help to add

  Option "Monitor-VGA" "Monitor[0]"

to Section "Device" and and set new limits in the monitor section? Something like this:

  HorizSync    27-85
  VertRefresh  50-80

BTW, does this issue occur only right after reboot, i.e. picture is fine after Ctrl-Alt-BS to restart the Xserver?

Changes from Comment #7 did not change any behavior.

The problem occurs all the time - also after Ctrl-Alt-BS

Ok. Could you attach new logfile nevertheless? Thanks.

Created attachment 160358 [details]
Xorg.0.log

Here we go ;-)

Ok. Some high resolution modelines are now rejected due to the new limits, but this one is still active. :-(

> (II) intel(0): Output VGA using initial mode 1600x1024

I suggest to switch to i810 driver for now. :-(

I can reproduce this issue on a "Iiyama Vision Master Pro 450". It gets fixed by commenting out the HorizSync/VertRefresh completely.

--- /etc/X11/xorg.conf.orig     2007-08-29 03:50:45.000000000 +0200
+++ /etc/X11/xorg.conf  2007-08-29 03:51:18.000000000 +0200
@@ -83,12 +83,12 @@
 Section "Monitor"
   Option       "CalcAlgorithm" "XServerPool"
   DisplaySize  360 270
-  HorizSync    27-110
+  #HorizSync    27-110
   Identifier   "Monitor[0]"
   ModelName    "VISION MASTER PRO 450"
   Option       "DPMS"
   VendorName   "IIYAMA"
-  VertRefresh  50-150
+  #VertRefresh  50-150
   UseModes     "Modes[0]"
 EndSection
 
@@ -128,6 +128,7 @@
   Driver       "intel"
   Identifier   "Device[0]"
   VendorName   "Intel"
+  Option       "monitor-VGA" "Monitor[0]"
 EndSection

--- /var/log/Xorg.0.log.old     2007-08-29 03:49:11.000000000 +0200
+++ /var/log/Xorg.0.log 2007-08-29 03:51:25.000000000 +0200
-(II) intel(0): Output VGA using initial mode 1600x1024
+(II) intel(0): Output VGA using initial mode 1280x1024

This is still a broken driver behaviour, and a stupid workaround, but please give it a try nevertheless. Thanks.

X is starting without that HorizSync/VertRefresh data.

But can you explain why it does not start with 1600x1200? Switching to that resolution with krandrtray later works fine.

Created attachment 160576 [details]
Xorg.0.log

Created attachment 160578 [details]
xorg.conf

> But can you explain why it does not start with 1600x1200? Switching to that
> resolution with krandrtray later works fine.
I have no idea. :-( This is probably the reason.

[...]
(II) intel(0): Output VGA using initial mode 1280x1024
[...]

How to change this? I don't know. Something deep in RANDR 1.2. 

As workaround you can use the RANDR magic in /etc/sysconfig/displaymanager for now. Something like this:

DISPLAYMANAGER_RANDR_MODE_VGA="auto"
### should be one line !!!
DISPLAYMANAGER_RANDR_MODE_auto="1600x1200_70.00  190.50 1600 1720 1888 2176  1200 1203 1207 1252 -HSync +Vsync"

Modelines can be generated by running "cvt". The above one was generated with
"cvt 1600 1200 70".

Hope this helps.

Then xrandr will be started automatically during displaymanager start and will hopefully set your resolution to 1600x1200.

Does this help? I'm setting this one to LATER since such things needs to be fixed upstream.

reopen.

*** This bug has been marked as a duplicate of bug 257746 ***