Arch Linux

Mirage

Member

Registered: 2009-03-19

Posts: 19

[Solved] Error: Unable to open displays (But startx works?)

Summing up my problems
- There's a stupid light sensor on my laptop and unless I'm sitting directly under a light, the screen dims to near illegibility
- Glxinfo|grep direct returns an error of unable to open display, help?

Would be great if anyone could give me a hand here.

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder62)  Thu Feb  5 00:08:50 PST 2009

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "SynapticsTouchpad" "SendCoreEvents"
EndSection

Section "Files"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "freetype"
    Load           "glx"
    Load        "synaptics"
EndSection

Section "InputDevice"
    Identifier     "SynapticsTouchpad"
    Driver         "synaptics"
    Option         "Device" "/dev/psaux"
    Option       "Protocol" "auto-dev"
    Option       "SHMConfig" "false"
    Option       "LeftEdge" "1700"
    Option       "RightEdge" "5300"
    Option       "TopEdge" "1700"
    Option        "BottomEdge" "4200"
    Option       "FingerLow" "25"
    Option       "FingerHigh" "30"
    Option       "MaxTapTime" "180"
    Option       "VertEdgeScroll" "true"
    Option         "HorizEdgeScroll" "true"
    Option       "CornerCoasting" "true"
    Option       "CoastingSpeed" "0.30"
    Option       "VertScrollDelta" "100"
    Option       "HorizScrollDelta" "100"
    Option       "MinSpeed" "0.10"
    Option       "MaxSpeed" "0.60"
    Option        "AccelFactor" "0.0020"
    Option       "VertTwoFingerScroll" "true"
    Option       "HorizTwoFingerScroll" "true"
EndSection

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

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    Option "ConnectedMonitor" "DFP"
    Option "RenderAccel" "True"
EndSection

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

Last edited by Mirage (2009-03-20 05:20:42)

sand_man

Member

From: Australia

Registered: 2008-06-10

Posts: 2,164

Re: [Solved] Error: Unable to open displays (But startx works?)

Is hal running? Make sure it is running before X starts

---

Mirage

Member

Registered: 2009-03-19

Posts: 19

Re: [Solved] Error: Unable to open displays (But startx works?)

Still needs to get this problem delt with :S

Last edited by Mirage (2009-03-19 04:03:49)

Knute

Member

From: Minot, ND

Registered: 2009-03-17

Posts: 604

Re: [Solved] Error: Unable to open displays (But startx works?)

So, to which laptop is this stupid sensor attached to?

Are there smart sensors that you can replace the stupid one with?? 
hehehe  (j/k on the second one btw)

---

Knute