Xorg.conf w/Matrox g550 agp

[WeakSauceIII]

New install of openbsd on a new machine with a matrox g550. To my surprise a simple startx went right into X at a 1600x1200 resolution. I then did a 'x -configure' and ran X with the new auto-generated xorg.conf.new and it displayed that blank default background for fvwm but no clock, terminal, or anything else. Clicking the mouse wouldn't do anything either. I can kill X with ctrl-alt-backspace though. It's odd to me that X works with no configuration file but the autogenerated one does not work. All my past problems with X involved bad refresh/resolution/monitor issues but I do not believe this is the case here because I get X loaded, it, just doesn't show anything on the desktop or allow mouse clicks. The log file shows no errors. Any suggestions to troubleshoot this behavior?

Here is the file xorg.conf.new

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/usr/X11R6/share/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/OTF"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
EndSection

Section "Module"
Load "GLcore"
Load "dbe"
Load "extmod"
Load "glx"
Load "record"
Load "xtrap"
Load "freetype"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "wsmouse"
Option "Device" "/dev/wsmouse"
Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
#DisplaySize 320 240 # mm
Identifier "Monitor0"
VendorName "VSC"
ModelName "E75f"
### Comment all HorizSync and VertRefresh values to use DDC:
HorizSync 30.0 - 86.0
VertRefresh 50.0 - 150.0
Option "DPMS"
EndSection

Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "SWcursor" # [<bool>]
#Option "HWcursor" # [<bool>]
#Option "PciRetry" # [<bool>]
#Option "SyncOnGreen" # [<bool>]
#Option "NoAccel" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "Overlay" # [<str>]
#Option "MGASDRAM" # [<bool>]
#Option "ShadowFB" # [<bool>]
#Option "UseFBDev" # [<bool>]
#Option "ColorKey" # <i>
#Option "SetMclk" # <freq>
#Option "OverclockMem" # [<bool>]
#Option "VideoKey" # <i>
#Option "Rotate" # [<str>]
#Option "TexturedVideo" # [<bool>]
#Option "Crtc2Half" # [<bool>]
#Option "Crtc2Ram" # <i>
#Option "Int10" # [<bool>]
#Option "AGPMode" # <i>
#Option "AGPSize" # <i>
#Option "DigitalScreen1" # [<bool>]
#Option "DigitalScreen2" # [<bool>]
#Option "TV" # [<bool>]
#Option "TVStandard" # [<str>]
#Option "CableType" # [<str>]
#Option "NoHal" # [<bool>]
#Option "SwappedHead" # [<bool>]
#Option "DRI" # [<bool>]
#Option "MergedFB" # [<bool>]
#Option "Monitor2HSync" # [<str>]
#Option "Monitor2VRefresh" # [<str>]
#Option "Monitor2Position" # [<str>]
#Option "MetaModes" # [<str>]
#Option "OldDmaInit" # [<bool>]
#Option "ForcePciDma" # [<bool>]
#Option "AccelMethod" # [<str>]
Identifier "Card0"
Driver "mga"
VendorName "Matrox Graphics, Inc."
BoardName "MGA G550 AGP"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768"
EndSubSection
EndSection

[BSDfan666]

X won't display anything on your "desktop" unless you explicitly start something... Create a .xinitrc file in your home directory and startx.. install fluxbox or something, gnome/kde if you're one of those people.

[ocicat]

Originally Posted by BSDfan666

X won't display anything on your "desktop" unless you explicitly start something...

Technically, this is correct; starting an X server by itself will not start any additional X applications, nor should it do so, & I suspect this was your point.

However, most users start X via the startx script. Unless ~/.xinitrc exists, startx will invoke /etc/X11/xinit/xinitrc which starts the fvwm(1) window manager, xclock, xterm, & xconsole.

[WeakSauceIII]

yes, what ocicat said is my problem. I assumed running "X -config xxx.config" would also run the xinitrc as startx does. The xclock, xterm, and xconsole don't start though and the mouse buttons don't seem to do anything although the default fvwm background is there. It's hard for me to work on because its not really an error, it just doesn't work as I expected. I suppose if its not running xinit then thats the problem other than the mouse buttons not working. That mouse behavior is not defined in a startup script is it? I can move the cursor around but clicking doesn't open a menu. Tomorrow I will copy that xorg.conf to the default directory and see if startx uses it and still starts the rest of the stuff. If so I have succeeded in wasting more of everyones time. You understand your replies will only encourage me to post more questions

I love this OS though. The purpose of this new machine is to try and run QEMU and a ReactOS virtual machine.

[ocicat]

Originally Posted by WeakSauceIII

I assumed running "X -config xxx.config" would also run the xinitrc as startx does. The xclock, xterm, and xconsole don't start though and the mouse buttons don't seem to do anything although the default fvwm background is there.

If you are running:

# X -config filename
...this is the expected behaviour. The mouse cursor will move with mouse movements, but there is no functionality attached to the mouse buttons at this point. Running an X server by itself isn't particularly interesting from a desktop user's perspective unless a failure is indicated.

I can move the cursor around but clicking doesn't open a menu.

Correct. Programmatic use of the mouse comes with a window manager which has not been loaded yet. This is part of the role of startx.

Part of your misperceptions on what X is doing may lie in what you may attribute to its functionality. X is not merely a desktop GUI; it has its own network protocol which will allow users to remotely run other machines. Because of all of this complexity, X is a resource pig. Simply running:

# X -config filename
...loads all kinds of code controlling the GUI, ties into the network stack, & loads both client & server software. The requirements of running X on a desktop are markedly higher than a desktop simply running ttys. You would benefit from studying:

• Section 11 of the FAQ: http://openbsd.org/faq/faq11.html
• The manpage to Xorg(1).

You understand your replies will only encourage me to post more questions

That's the nature of the game!