You are not logged in.

#1 2009-08-28 19:04:14

stkerr
Member
Registered: 2009-08-28
Posts: 12

X won't start properly

I'm working through my first install of Arch and I'm running into some trouble.

Whenever I use the command 'X -config /etc/X11/xorg.config', my monitors (I have dual monitors) just go black with no mouse cursor visible. When I press numlock or capslock, the keyboard lights come on and I can change tty with ctrl+alt+2 (or something similar). There is only 1 error message that appears:

(EE) Microsoft Natural? Ergonomic Keyboard 4000: failed to initialize for relative axes.

However, when i use the command 'startx', X starts properly and I am presented with several xterms and an X clock. The same error does appear though.

I have an Nvidia gtx 275 video card, one monitor is 1440x900 and the other is 1920x1080

Here is my xorg.conf file:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder62)  Tue Jul 28 19:48:57 PDT 2009

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
        Screen 1 "Screen1" RightOf "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"

    Option "xinerama" "on"
    Option "clone" "off"

EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/input/mouse1"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
    Option "XkbModel" "ps105"
    Option "XkbLayout" "us"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Dell"
    ModelName      "SE198"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Acer"
    ModelName      "H233H"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    Option "RandRRotation" "true"
    Option "RenderAccel" "true"
    Screen 0
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    Option "RandRRotation" "true"
    Option "RenderAccel" "true"
    Screen 1
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Modes   "1440x900"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    SubSection     "Display"
        Modes   "1920x1080"
        Depth       24
    EndSubSection
EndSection

Can you see what's wrong with this? (Or any other changes I should make?)

Also, is Twinview the proper setting that I want for 2 monitors? Or do I want seperate x screens?

Offline

#2 2009-08-28 20:25:38

djszapi
Member
From: Cambridge, United Kingdom
Registered: 2009-06-14
Posts: 1,439
Website

Re: X won't start properly

Hello stkerr!

Did you try with only 1 monitor in first step ?

Offline

#3 2009-08-30 12:59:50

stkerr
Member
Registered: 2009-08-28
Posts: 12

Re: X won't start properly

After working on my problem, I think X actually was starting properly. The "error" was due to the fact that the newer Xorg doesn't display the X when using just 'X' at the command line, as stated in wiki.

Offline

#4 2009-09-01 17:46:55

lestoil
Member
Registered: 2005-08-09
Posts: 81

Re: X won't start properly

For that keyboard  "axis" error message if you're having a problem check out /usr/share/X11/xkb/rules/xorg.lst for what your MS keyboard  is now called.  My MSNaturalKBPro gave same "axis" error  so in /etc/X11/xorg.conf I had to change the Option "XkbModel" to "microsoftpro" in Keyboard Input Device Section to stop that error. Good luck..

Offline

Board footer

Powered by FluxBB