Hi,
My monitor seems to be working fine, but my keyboard is screwed up. My delete key is completely dead. I changed keyboards and see the same behavior so it appears to be my X setup and not my hardware.

Executing sax2, I get an X message:
Cannot Deactivate All Displays
At least one display must be active.

Click OK. Looking at the Keyboard, I see that it was incorrectly detected as ms natural keyboard pro. It is actually a Logitech Cordless Desktop Pro. There is a type option "Logitech Cordless Desktop (alternate option)". I don't know what the "alternate" means, but it may be better than ms.

OK, Save ->
Saving Configuration Failed...
X config: Data incomplete in file /var/lib/sax/xorg.conf. Undefined Screen "P0/+-" referenced by ServerLayout "(null)"

from: /var/lib/sax/xorg.conf
Section "ServerLayout"
Identifier "Layout[all]"
InputDevice "Keyboard[0]" "CoreKeyboard"
InputDevice "Mouse[1]" "CorePointer"
InputDevice "Mouse[3]" "SendCoreEvents"
Option "Clone" "off"
Option "Xinerama" "off"
Screen "aticonfig-Screen[0]-0"
EndSection

There is no "aticonfig-Screen[0]-0" in the sax file, however there is one in /etc/X11/xorg.conf:
brianp@godzilla2:~/download$ grep aticonfig-Screen /etc/X11/xorg.conf
Screen 0 "aticonfig-Screen[0]-0" 0 0
Identifier "aticonfig-Screen[0]-0"

brianp@godzilla2:~/download$ grep Screen /var/lib/sax/xorg.conf
Section "Screen"
Screen 0
Screen "aticonfig-Screen[0]-0"

I see that my sax 'Section "Screen" ' has no identifier like the X11 version does. When I hack in ' Identifier "aticonfig-Screen[0]-0" ' into the screen section, it changes the error.

I kill sax, hack the file to add the correct looking screen identifier, save the file and execute sax2 again and get a HorizSync error. When I look at the sax xorg.conf file, my correction has been erased and I get a different error:
Parse error line 99... HorizSync must be followed by a list of numbers or ranges.

Check the HorizSync, I see that it is set to " HorizSync 0-". The HorizSync is only used for CRT monitors, not LCDs.

Kill sax2, hack the sax xorg.conf. Delete the HorizSync line entirely (X11/xorg.conf does not have one at all), insert the 'Identifier "aticonfig-Screen[0]-0"', save and execute sax2 again....

Now, I am back to the undefined screen error.

How can I know which one of the xorg.conf files is actually being used? They are quite different. The sax version is obviously corrupted but it refuses to accept my hacks. Is this info stored in some database somewhere?

So, I try to fix the screen. The monitor is set to ATI whereas it is a Samsung 305T, 30 inch, 2560/1600 WQXGA monitor. Change monitor shows a IQ Automation model Q17. Change to Samsung. There is no setting model 305T available. This monitor was PC Magazine's Editor's choice a year ago. How did they miss it?

Try Vendor = "--> LCD". The highest resolution they list is 1920x1200@75Hz. Samsung, Apple, HP, Dell and NEC all sell 30 inch, 2560x1600 monitors. How can I hack my resolution into this menu? And, there was never a utility disk sold with the monitor (I checked the original box).

I looked at /usr/bin/startx. It is a shell script but it does not contain the string "xorg.conf". How in this spaghetti logic does it figure out which xorg.conf file to use?

Any ideas on how to get out of this quagmire?

Thank you,
BrianP

?

It is the case that the generic LCD setting in sax2 doesn't give you the screen size you need even if you open the tabs and set the specifications manually? Do any of the screen choices by brand name give you a screen that is large enough? You might try to choose it and adjust the size and frequencies to correspond to your Samsung and see if sax2 will accept that.

I assume that sax2 does not compare names and specifications, merely the card and screen it finds and the specifications you claim the screen can achieve.

I have an Eizo CRT that is found by name, but with the wrong size. As long as the screen dimensions, H and V and a nominal size large enough to have those dimensions, plus the frequency limits, are entered, sax2 configures the screen, though a bit small. My screen controls then enlarge the image to fit

When I recently ran sax2 in console mode, that is after stopping X with init 3, I ran it as "sax2- r -m 0=nvidia" to find my desired driver. Have you tried to start sax2 such that it points to the driver or module you wish? This assumes that the limiting factor is the driver, and that the sax2 adjustment screen that should come up as the last part of the process is different, with the chance of setting up your Samsung.

If this doesn't help it puts the problem at the top of the list for more eyes to see and they may know more.

Idea #2

If you have your favorite driver or module set up so that the system boots, but the settings on your Samsung are still to small, you might try to edit your xorg.config file to the content that corresponds to your screen. Then, from the console, run sax2 -m 0="your driver". If i understand thing, this should load that driver with the settings from the modified xorg.config without overwriting them.

If it helps, sax2 generates a log at /var/log/SaX.log

xorg.config is in /etc/X11

I also found this which may help if you have not read it.

http://en.opensuse.org/SDB:X_Server_...(8.1_or_Higher)

Idea#3

http://www.linux-noob.com/forums/ind...showtopic=3335

Hi,
For the third time, Suse 11.1 has had X problems and destroyed itself.

I killed X. On the command line (run level 3), I executed sas2. It started X again. Then it went to flashing red, green, blue, black, white, ... screens. Control-Alt-Backslash killed it and took me back to the character mode.

`starts` brought up a mangled X with repeated patterns of mangled icons and a hard lockup requiring a power off to reboot.

Then, suse locked up immediately after the bios post.

I nuked it (with extreme prejudice), reformatted and installed Ubu 9.04. It actually works fine. No monkeying with X at all, no manual install of the fglrx driver, no fiddling around with sax. All keys work as expected. They even fixed the suspend problem and those dreaded flying, rubber windows!

I use 11.0 on a server here and it works great. 11.1 is too darn fragile and buggy to be used on a workstation.

Thank goodness for Ubuntu!!!

Thanks for your help,

BrianP