You are not logged in.

Pages: 1

#1 2010-05-28 18:56:35

kissandra79
Member
Registered: 2008-08-17
Posts: 23

xorg configuration file

Is there anyone using an NVIDIA Geforce GTX 285M card? If so, could you please give me your xorg.conf file? I installed arch linux on my new laptop a week ago and for some reason haven't been able to get xorg to use the nvidia drivers. I am hoping that someone would have an xorg config file, for their GTX 285M card. I would be happy to try it out.. cos Im at my wits end trying to get it to work. All of last week, was just one big drag after another trying to find a solution. This is my last resort... I hate to think i might have to install crap vinduze..

Thank you.

PS: actually an xorg.conf file on a system with any of the newest nvidia cards might work I think.
thaks

Offline

#2 2010-05-28 19:01:03

brisbin33
Member
From: boston, ma
Registered: 2008-07-24
Posts: 1,796
Website

Re: xorg configuration file

have you tried nvidia-xconfig yet?

//github/

Offline

#3 2010-05-28 19:52:50

kissandra79
Member
Registered: 2008-08-17
Posts: 23

Re: xorg configuration file

brisbin33 wrote:

have you tried nvidia-xconfig yet?

I did..and it creates a config file that allows X to run in 24 bit mode.. and when i run it.. i get garbled output on the lcd screen. but when i try to run it in 32 bit mode.. it runs for a few seconds properly before unexpectingly quitting back to the console.. with no error messages..

Offline

#4 2010-05-29 02:00:31

theapodan
Member
From: Virginia, USA
Registered: 2008-10-21
Posts: 116

Re: xorg configuration file

kissandra79 wrote:
brisbin33 wrote:

have you tried nvidia-xconfig yet?

I did..and it creates a config file that allows X to run in 24 bit mode.. and when i run it.. i get garbled output on the lcd screen. but when i try to run it in 32 bit mode.. it runs for a few seconds properly before unexpectingly quitting back to the console.. with no error messages..

Most likely 32 bit depth isn't supported, see here:http://www.x.org/archive/X11R6.8.0/doc/xorg.conf.5.html

Depth depth
    This entry specifies what colour depth the Display subsection is to be used for. This entry is usually specified, but it may be omitted to create a match-all Display subsection or when wishing to match only against the FbBpp parameter. The range of depth values that are allowed depends on the driver. Most driver support 8, 15, 16 and 24. Some also support 1 and/or 4, and some may support other values (like 30). Note: depth means the number of bits in a pixel that are actually used to determine the pixel colour. 32 is not a valid depth value. Most hardware that uses 32 bits per pixel only uses 24 of them to hold the colour information, which means that the colour depth is 24, not 32.

Try posting Xorg.0.log using the xorg.conf generated by nvidia-xconfig.

Offline

#5 2010-05-29 10:59:18

kissandra79
Member
Registered: 2008-08-17
Posts: 23

Re: xorg configuration file

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder75)  Fri Mar 12 01:42:27 PST 2010

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

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

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
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 "NoLogo" "True"
EndSection

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

The only line I added was "Option "NoLogo" "True"".

As you can see, my xorg is very bare and plain. Could that be the reason why Im not getting display? Are there supposed to be certain options that I have missed?
And is DPMS necessary?

Thats the xorg.conf file.

What follows is the log file that you had asked for.

X.Org X Server 1.7.6
Release Date: 2010-03-17
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33-ARCH i686
Current Operating System: Linux TheRock 2.6.33-ARCH #1 SMP PREEMPT Thu May 13 12:06:25 CEST 2010 i686
Kernel command line: root=/dev/sdb1 ro
Build Date: 01 April 2010  05:35:33PM

Current version of pixman: 0.18.2
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat May 29 09:28:36 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/Type1" does not exist.
    Entry deleted from font path.
(==) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Keyboard0
(WW) Disabling Mouse0
(II) Loader magic: 0x81e4c60
(II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 6.0
    X.Org XInput driver : 7.0
    X.Org Server Extension : 2.0
(--) using VT number 7

(--) PCI:*(0:2:0:0) 10de:060f:1558:8687 nVidia Corporation rev 162, Mem @ 0xce000000/16777216, 0xd0000000/268435456, 0xcc000000/33554432, I/O @ 0x00002000/128
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.7.6, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.7.6, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(**) Logitech Optical USB Mouse: Device: "/dev/input/event11"
(II) Logitech Optical USB Mouse: Found 3 mouse buttons
(II) Logitech Optical USB Mouse: Found scroll wheel(s)
(II) Logitech Optical USB Mouse: Found relative axes
(II) Logitech Optical USB Mouse: Found x and y relative axes
(II) Logitech Optical USB Mouse: Configuring as mouse
(**) Logitech Optical USB Mouse: YAxisMapping: buttons 4 and 5
(**) Logitech Optical USB Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech Optical USB Mouse" (type: MOUSE)
(**) Logitech Optical USB Mouse: (accel) keeping acceleration scheme 1
(**) Logitech Optical USB Mouse: (accel) acceleration profile 0
(II) Logitech Optical USB Mouse: initialized for relative axes.
(II) config/hal: Adding input device BisonCam, NB Pro
(**) BisonCam, NB Pro: always reports core events
(**) BisonCam, NB Pro: Device: "/dev/input/event10"
(II) BisonCam, NB Pro: Found keys
(II) BisonCam, NB Pro: Configuring as keyboard
(II) XINPUT: Adding extended input device "BisonCam, NB Pro" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Sleep Button
(**) Sleep Button: always reports core events
(**) Sleep Button: Device: "/dev/input/event4"
(II) Sleep Button: Found keys
(II) Sleep Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event3"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Video Bus
(**) Video Bus: always reports core events
(**) Video Bus: Device: "/dev/input/event7"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event6"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"

There are a few warnings regarding ACPI and "AllowEmptyInput". Could that be the problem?

Thank you very much.

Offline

#6 2010-05-29 19:57:35

theapodan
Member
From: Virginia, USA
Registered: 2008-10-21
Posts: 116

Re: xorg configuration file

kissandra79 wrote:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder75)  Fri Mar 12 01:42:27 PST 2010
...

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 "NoLogo" "True"
EndSection

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

The only line I added was "Option "NoLogo" "True"".

As you can see, my xorg is very bare and plain. Could that be the reason why Im not getting display? Are there supposed to be certain options that I have missed?
And is DPMS necessary?

Try changing the HorizSync line in xorg.conf from 

HorizSync       28.0 - 33.0

to  

HorizSync       28.0 - 80.0

And DPMS isn't necessary, but I'd leave it on so your monitor can power down.

Offline

#7 2010-05-29 20:12:03

kissandra79
Member
Registered: 2008-08-17
Posts: 23

Re: xorg configuration file

@theapodan

But the value for the field "HorizSync" was given as default by nvidia-xconfig itself. So may i ask if it is wise to change that value. Besides, wouldn't it hurt the LCD panel in the longer run, using it with such a high HorizSync value?

Thank you.

Offline

#8 2010-05-29 20:44:48

theapodan
Member
From: Virginia, USA
Registered: 2008-10-21
Posts: 116

Re: xorg configuration file

kissandra79 wrote:

@theapodan

But the value for the field "HorizSync" was given as default by nvidia-xconfig itself. So may i ask if it is wise to change that value. Besides, wouldn't it hurt the LCD panel in the longer run, using it with such a high HorizSync value?

Thank you.

33.0 is too low to provide a usable resolution.  Since the monitor information is Unknown, I assume that nvidia-xconfig chose some very conservative defaults.

80.0 is just an arbitrary guess on my part.  This information should be available through your monitor documentation or the monitor's OSD.  The Hsync rate for my LCD monitor in the mode I'm using now - 1680x1050@60Hz - is 64 Hz

I've never heard of LCDs being damaged by being run at higher refresh rates.  Also, the actual rate chosen depends on the mode, so if you use a lower resolution, the Hsync rate will be lower, even if a max of 80.0 is in xorg.conf.

Offline

#9 2010-05-30 06:50:06

kissandra79
Member
Registered: 2008-08-17
Posts: 23

Re: xorg configuration file

@theapodan

Thanks for the suggestion. I tried it. But im still outta luck. Same stuff. garbled output for a few seconds and then back to the console. I am actually beginning to believe this could be a hardware problem of some sorts. But I would like to confirm after using a working version of the Xorg.conf file..

Offline

Pages: 1

Board footer

Powered by FluxBB