http://bugzilla.novell.com/show_bug.cgi?id=500691
User sndirsch@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=500691#c11
Stefan Dirsch changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ms@novell.com,
| |sndirsch@novell.com
--- Comment #11 from Stefan Dirsch 2009-05-07 00:39:56 MDT ---
Looking at the SaX2 logfile it seems the Vsync value of the 1280X1024@60HZ
monitor entry in /usr/share/sax/api/data/cdb/Monitors
#==============================================
# 1280X1024@60HZ
#----------------------------------------------
--> VESA:1280X1024@60HZ {
Hsync=31-64
Modeline="1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync
+vsyn
c
Vsync=50-60
}
is changed.
--- /var/lib/sax/xorg.conf.first 2009-05-03 18:51:24.000000000 -0700
+++ /var/lib/sax/xorg.conf 2009-05-06 13:40:54.000000000 -0700
@@ -1,6 +1,6 @@
# /.../
# SaX generated X11 config file
-# Created on: 2009-05-03T18:51:16-0700.
+# Created on: 2009-05-06T13:40:54-0700.
#
# Version: 8.1
# Contact: Marcus Schaefer , 2005
@@ -81,14 +81,13 @@
Section "Monitor"
Option "CalcAlgorithm" "XServerPool"
- DisplaySize 377 301
+ DisplaySize 340 270
HorizSync 31-64
Identifier "Monitor[0]"
ModelName "1280X1024@60HZ"
- Option "DPMS"
Option "PreferredMode" "1280x1024"
VendorName "--> VESA"
- VertRefresh 50-60
+ VertRefresh 60-60
UseModes "Modes[0]"
EndSection
I don't know why. Maybe Marcus knows.
Russ, please forget about the failsafe mode. It's a complete different config
with a complete different driver (fbdev or vesa). The one from installation
without any 2D acceleration.
Russ, could you also provide the output of 'hwinfo --monitor'. Maybe SaX2 is
using the intersection for VSync of "1280X1024@60HZ" and real monitor. A very
wild guess though.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.