Bugzilla – Bug 448055
SAX2 is not startable in init 3 Mode (Beta 5.2)
Last modified: 2008-11-26 14:49:02 UTC
I have a NVIDIA 8500GT and a LG L227WT 22" LCD Monitor connected digital, it is not possible to start SAX2 (-L, -r....) in init 3 mode. The monitor is always going out of range "HS". I can change the config in init 5 mode, but after the change I have to reboot ? A init 3 - 5 is not possible ?
Created attachment 254636 [details] SaX2 Log
Thanks. I'll try to reproduce with a similar card (8400 GS).
I don't see this issue on my 8400 GS with a CTX 1280x1024 monitor digitally connected. Tried with your xorg.conf. Screen comes up with 800x600 as expected. I suggest to remove the following lines from your xorg.conf: HorizSync 20-46 Option "PreferredMode" "800x600" VertRefresh 50-60 and replace SubSection "Display" Depth 24 Modes "800x600" EndSubSection with SubSection "Display" Depth 24 Modes "1680x1050" EndSubSection Does this help? Please attach new Xorg.0.log. Thanks.
? Ok I check this, but I have a other SaX2 created config ? The Test is starting in 1 - 2 Hours # /.../ # SaX generated X11 config file # Created on: 2008-11-22T10:42:48+0100. # # Version: 8.1 # Contact: Marcus Schaefer <sax@suse.de>, 2005 # Contact: SaX-User list <https://lists.berlios.de/mailman/listinfo/sax-users> # # Automatically generated by [ISaX] (8.1) # PLEASE DO NOT EDIT THIS FILE! # Section "Files" FontPath "/usr/share/fonts/misc:unscaled" FontPath "/usr/share/fonts/local" FontPath "/usr/share/fonts/75dpi:unscaled" FontPath "/usr/share/fonts/100dpi:unscaled" FontPath "/usr/share/fonts/Type1" FontPath "/usr/share/fonts/URW" FontPath "/usr/share/fonts/Speedo" FontPath "/usr/share/fonts/PEX" FontPath "/usr/share/fonts/cyrillic" FontPath "/usr/share/fonts/latin2/misc:unscaled" FontPath "/usr/share/fonts/latin2/75dpi:unscaled" FontPath "/usr/share/fonts/latin2/100dpi:unscaled" FontPath "/usr/share/fonts/latin2/Type1" FontPath "/usr/share/fonts/latin7/75dpi:unscaled" FontPath "/usr/share/fonts/baekmuk:unscaled" FontPath "/usr/share/fonts/japanese:unscaled" FontPath "/usr/share/fonts/kwintv" FontPath "/usr/share/fonts/truetype" FontPath "/usr/share/fonts/uni:unscaled" FontPath "/usr/share/fonts/CID" FontPath "/usr/share/fonts/ucs/misc:unscaled" FontPath "/usr/share/fonts/ucs/75dpi:unscaled" FontPath "/usr/share/fonts/ucs/100dpi:unscaled" FontPath "/usr/share/fonts/hellas/misc:unscaled" FontPath "/usr/share/fonts/hellas/75dpi:unscaled" FontPath "/usr/share/fonts/hellas/100dpi:unscaled" FontPath "/usr/share/fonts/hellas/Type1" FontPath "/usr/share/fonts/misc/sgi:unscaled" FontPath "/usr/share/fonts/xtest" FontPath "/opt/kde3/share/fonts" InputDevices "/dev/gpmdata" InputDevices "/dev/input/mice" EndSection Section "ServerFlags" Option "AllowMouseOpenFail" "on" Option "ZapWarning" "on" EndSection Section "Module" Load "freetype" Load "dbe" Load "dri" Load "glx" Load "extmod" EndSection Section "InputDevice" Driver "kbd" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbLayout" "de" Option "XkbModel" "microsoftmult" Option "XkbRules" "xfree86" Option "XkbVariant" "nodeadkeys" EndSection Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "Buttons" "17" Option "Device" "/dev/input/mice" Option "Name" "Microsoft Wireless Optical Desktop? 2.10" Option "Protocol" "explorerps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Option "CalcAlgorithm" "XServerPool" DisplaySize 451 338 HorizSync 30-83 Identifier "Monitor[0]" ModelName "LG L227W (DIGITAL)" Option "DPMS" Option "PreferredMode" "1280x1024" VendorName "LG" VertRefresh 56-75 UseModes "Modes[0]" EndSection Section "Modes" Identifier "Modes[0]" EndSection Section "Screen" DefaultDepth 24 SubSection "Display" Depth 15 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1280x768" "1280x720" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1280x768" "1280x720" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1280x768" "1280x720" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1280x768" "1280x720" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x480" EndSubSection Device "Device[0]" Identifier "Screen[0]" Monitor "Monitor[0]" EndSection Section "Device" BoardName "GeForce 8500 GT" Driver "nv" Identifier "Device[0]" Screen 0 VendorName "NVidia" EndSection Section "ServerLayout" Identifier "Layout[all]" InputDevice "Keyboard[0]" "CoreKeyboard" InputDevice "Mouse[1]" "CorePointer" Option "Clone" "off" Option "Xinerama" "off" Screen "Screen[0]" EndSection Section "DRI" Group "video" Mode 0660 EndSection Section "Extensions" Option "Composite" "off" EndSection
Ok. So SaX2 saves another config as it writes for startup. In this case remove HorizSync 30-83 Option "PreferredMode" "1280x1024" VertRefresh 56-75 and replace SubSection "Display" Depth 24 Modes "1280x1050" [...] EndSubSection with SubSection "Display" Depth 24 Modes "1680x1050" EndSubSection
OK, now I tested it. On my system Sax is not starting correct :(. The Monitor is going out of Sync
Instead of starting SaX please try starting Xorg directly and attach new Xorg.0.log.
You mean init 3, startx ? OK the log is attached.
Created attachment 254956 [details] The startx Log
Ok. Monitor again out of Sync when using startx?
No, it is only with SaX2 out of sync 81.3/65Hz ? the Monitor have HR 30-83 VR 56-75 I start hwinfo --monitor, is hwinfo broken ? techz:/ # hwinfo --monitor 34: None 00.0: 10000 Monitor [Created at fb.71] Unique ID: rdCR.EY_qmtb9YY0 Hardware Class: monitor Model: "Generic Monitor" Vendor: "Generic" Device: "Monitor" Resolution: 800x600@75Hz Driver Info #0: Max. Resolution: 800x600 Vert. Sync Range: 50-90 Hz Hor. Sync Range: 31-48 kHz Config Status: cfg=no, avail=yes, need=no, active=unknown
For some reasons the monitor cannot be detected by hwinfo. Then SaX2 make some weird assumptions, which result in HorizSync 20-46 VertRefresh 50-60 for xorg.conf used by sax2 to start the Xserver. But it seems these get ignored by nv anyway. So you still should have a working SaX2. I curently don't understand this behaviour.
Since I cannot reproduce this issue at all I'm afraid you need to live with that now. The easiest for you at the moment is to run 'sax2 -a -r', then adjust HorizSync, VertRefresh and resolution as mentioned before and then to do the finetuning on top of a running Xserver. Basically this is a duplicate. *** This bug has been marked as a duplicate of bug 440973 ***