You are not logged in.

#1 2010-04-06 18:02:28

davetrotteruk
Member
From: Cornwall, UK
Registered: 2010-04-06
Posts: 24

[SOLVED] Xorg resolution problems GTS 250 Nvidia

I have been using ubuntu for the last 3 days and i have no option to use anything but that because it is the only distro that accepts my t.v. resolution. i want to use arch as i have read alot about it but if i cannot get my resoution to work i cannot.
I have tried to use my xorg,conf file from ubuntu but with no luck. I don't know where to turn so i thought i would try my luck here. I have a Nvidia GTS 250 Graphics card and a Hitachi 42pd5200 plasma tv.

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 1.0  (buildd@crested)  Sun Feb  1 20:25:37 UTC 2009

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
  EndSection

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

Section "ServerFlags"
    Option         "Xinerama" "0"
EndSection

Section "Monitor"
    # HorizSync source: builtin, VertRefresh source: builtin
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "CRT-1"
    HorizSync       28.0 - 55.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTS 250"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "1360x768_60_0 +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.7.1.901 (1.7.2 RC 1)
Release Date: 2009-11-6
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.31-ARCH x86_64 
Current Operating System: Linux chakra 2.6.31-ARCH #1 SMP PREEMPT Sat Nov 14 17:35:20 CET 2009 x86_64
Kernel command line: initrd=chakra.img quiet lang=engb nonfree=yes xdriver=no BOOT_IMAGE=vmlinuz 
Build Date: 08 November 2009  04:08:18PM
 
Current version of pixman: 0.16.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: Tue Apr  6 17:52:57 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Device0"
(**) Option "Xinerama" "0"
(==) 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"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
    If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(II) Loader magic: 0x7c1a00
(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:4:0:0) 10de:0615:0000:0000 nVidia Corporation G92 [GeForce GTS 250] rev 162, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, 0xfa000000/33554432, I/O @ 0x0000ec00/128, BIOS @ 0x????????/131072
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded by default.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded by default.
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.7.1.901, 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: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.7.1.901, 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: "type1"
(WW) Warning, couldn't open module type1
(II) UnloadModule: "type1"
(EE) Failed to load module "type1" (module does not exist, 0)
(II) LoadModule: "freetype"
(WW) Warning, couldn't open module freetype
(II) UnloadModule: "freetype"
(EE) Failed to load module "freetype" (module does not exist, 0)
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    Module class: X.Org Server Extension
(II) NVIDIA GLX Module  190.42  Tue Oct 20 21:19:30 PDT 2009
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions/librecord.so
(II) Module record: vendor="X.Org Foundation"
    compiled for 1.7.1.901, module version = 1.13.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
    compiled for 1.7.1.901, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
    compiled for 1.7.1.901, module version = 1.1.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver  190.42  Tue Oct 20 20:42:04 PDT 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 04@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
    compiled for 1.7.1.901, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules/libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
    compiled for 1.7.1.901, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "TwinView" "0"
(**) NVIDIA(0): Option "MetaModes" "1360x768_60_0 +0+0"
(**) Apr 06 17:52:57 NVIDIA(0): Enabling RENDER acceleration
(II) Apr 06 17:52:57 NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) Apr 06 17:52:57 NVIDIA(0):     enabled.
(WW) Apr 06 17:52:58 NVIDIA(GPU-0): Unable to read EDID for display device CRT-1
(II) Apr 06 17:52:58 NVIDIA(0): NVIDIA GPU GeForce GTS 250 (G92) at PCI:4:0:0 (GPU-0)
(--) Apr 06 17:52:58 NVIDIA(0): Memory: 1048576 kBytes
(--) Apr 06 17:52:58 NVIDIA(0): VideoBIOS: 62.92.9a.00.00
(II) Apr 06 17:52:58 NVIDIA(0): Detected PCI Express Link width: 16X
(--) Apr 06 17:52:58 NVIDIA(0): Interlaced video modes are supported on this GPU
(--) Apr 06 17:52:58 NVIDIA(0): Connected display device(s) on GeForce GTS 250 at PCI:4:0:0:
(--) Apr 06 17:52:58 NVIDIA(0):     CRT-1
(--) Apr 06 17:52:58 NVIDIA(0): CRT-1: 400.0 MHz maximum pixel clock
(II) Apr 06 17:52:58 NVIDIA(0): Assigned Display Device: CRT-1
(WW) Apr 06 17:52:58 NVIDIA(0): No valid modes for "1360x768_60_0+0+0"; removing.
(WW) Apr 06 17:52:58 NVIDIA(0): 
(WW) Apr 06 17:52:58 NVIDIA(0): Unable to validate any modes; falling back to the default mode
(WW) Apr 06 17:52:58 NVIDIA(0):     "nvidia-auto-select".
(WW) Apr 06 17:52:58 NVIDIA(0): 
(II) Apr 06 17:52:58 NVIDIA(0): Validated modes:
(II) Apr 06 17:52:58 NVIDIA(0):     "nvidia-auto-select"
(II) Apr 06 17:52:58 NVIDIA(0): Virtual screen size determined to be 1024 x 768
(WW) Apr 06 17:52:58 NVIDIA(0): Unable to get display device CRT-1's EDID; cannot compute DPI
(WW) Apr 06 17:52:58 NVIDIA(0):     from CRT-1's EDID.
(==) Apr 06 17:52:58 NVIDIA(0): DPI set to (75, 75); computed from built-in default
(==) Apr 06 17:52:58 NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) Apr 06 17:52:58 NVIDIA(0): Initialized GPU GART.
(II) Apr 06 17:52:58 NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) Apr 06 17:52:58 NVIDIA(0):     may not be running or the "AcpidSocketPath" X
(II) Apr 06 17:52:58 NVIDIA(0):     configuration option may not be set correctly.  When the
(II) Apr 06 17:52:58 NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
(II) Apr 06 17:52:58 NVIDIA(0):     try to use it to receive ACPI event notifications.  For
(II) Apr 06 17:52:58 NVIDIA(0):     details, please see the "ConnectToAcpid" and
(II) Apr 06 17:52:58 NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
(II) Apr 06 17:52:58 NVIDIA(0):     Config Options in the README.
(II) Apr 06 17:52:58 NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Loading extension NV-GLX
(II) Apr 06 17:52:58 NVIDIA(0): Initialized OpenGL Acceleration
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) Apr 06 17:52:58 NVIDIA(0): Initialized X Rendering Acceleration
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing extension GLX
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
(II) config/hal: Adding input device Macintosh mouse button emulation
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
    compiled for 1.7.0.901, module version = 2.3.0
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 7.0
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found relative axes
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) acceleration profile 0
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/hal: Adding input device Logitech USB Receiver
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: Device: "/dev/input/event5"
(II) Logitech USB Receiver: Found 12 mouse buttons
(II) Logitech USB Receiver: Found scroll wheel(s)
(II) Logitech USB Receiver: Found relative axes
(II) Logitech USB Receiver: Found x and y relative axes
(II) Logitech USB Receiver: Found absolute axes
(II) Logitech USB Receiver: Found keys
(II) Logitech USB Receiver: Configuring as mouse
(II) Logitech USB Receiver: Configuring as keyboard
(**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
(**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
(**) Logitech USB Receiver: (accel) acceleration profile 0
(II) Logitech USB Receiver: initialized for relative axes.
(WW) Logitech USB Receiver: ignoring absolute axes.
(II) config/hal: Adding input device Logitech USB Receiver
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: Device: "/dev/input/event4"
(II) Logitech USB Receiver: Found keys
(II) Logitech USB Receiver: Configuring as keyboard
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (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/event2"
(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 Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event1"
(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"

Going into nvidia-settings only displays 4:3 resolutions as options.
I have widened the horiz and vert refresh rates and it gives me a broader spectum of resolutions but they are all still 4:3. i have now reverted back to the default xorg file (the one i have provided) the log is also for the same xorg.conf.
I have also tried to add lines to the xorg.conf to ignore EDID as mentioned in the xorg wiki page

Thank you to anyone that takes there time to try and help me

Last edited by davetrotteruk (2010-04-09 08:50:11)

Offline

#2 2010-04-07 08:22:14

flamelab
Member
From: Athens, Hellas (Greece)
Registered: 2007-12-26
Posts: 2,160

Re: [SOLVED] Xorg resolution problems GTS 250 Nvidia

Try having only these in your xorg.conf [that's my xorg.conf] [I also have xorg-input-drivers installed/HAL is running - since Xorg-server 1.8 you won't need HAL though]

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    Option "RandRRotation" "true"
    Option "NoLogo"        "true"
    Option "Coolbits"      "1"
    Option "TripleBuffer"  "True"
    Option "DamageEvents"  "True"
    Option  "UseEvents"    "True"
    Option "BackingStore" "True"
    Option "DPMS" "True"
    Option "RegistryDwords" "PerfLevelSrc=0x3333"
EndSection

restart Xorg and see if you can set the resolution through nvidia-settings.

Last edited by flamelab (2010-04-07 08:22:55)

Offline

#3 2010-04-07 16:19:47

Bregol
Member
Registered: 2008-08-15
Posts: 175

Re: [SOLVED] Xorg resolution problems GTS 250 Nvidia

I have a LCD with bad EDID and had to use the ignore EDID stuff from the wiki, too.  Then it wouldn't give me all the resolutions I wanted. After increasing the verbosity that nvidia logged in the xorg log, I saw that because it was not pulling resolutions from the EDID, it was falling back to some lists of modes that nvidia had and xorg had, but this was not sufficient for what I wanted. 

Sorta like how your log says "No valid modes for "1360x768_60_0+0+0"; removing" - you may tell it to try to use that resolution, but it doesn't have the modeline to do it.

So what I did was to give it the modelines I wanted and I think this will work for you too. Use an online modeline generator for you to get modelines to put into your xorg.conf.  So you need to give xorg a modeline named "1360x768_60_0" for it to use.

modeline generator:
http://xtiming.sourceforge.net/cgi-bin/xtiming.pl


Nai haryuvalyë melwa rë

Offline

#4 2010-04-08 08:32:19

davetrotteruk
Member
From: Cornwall, UK
Registered: 2010-04-06
Posts: 24

Re: [SOLVED] Xorg resolution problems GTS 250 Nvidia

Thanks i will reinstall arch this afternoon, I will try both methods that have been advised.
What I am really confused with is that i will work on ubuntu and debian (it aslo works on windows and osx) based distros but nothing else.
Anyway thanks for the advise and will be trying shortly.

Offline

#5 2010-04-09 08:08:00

davetrotteruk
Member
From: Cornwall, UK
Registered: 2010-04-06
Posts: 24

Re: [SOLVED] Xorg resolution problems GTS 250 Nvidia

Ok i have tried both methods and i think the second one could work and thanks i just have to find my dot clock for the resolution i need. This is proving harder than i thought. If anyone can help me i would appreciate it. Will post and add my method when i have got it to work.
Thanks guys

Offline

#6 2010-04-09 08:53:56

davetrotteruk
Member
From: Cornwall, UK
Registered: 2010-04-06
Posts: 24

Re: [SOLVED] Xorg resolution problems GTS 250 Nvidia

Because I could not find out my dot clock frequency i was struggling with the website that Bregol gave me. I found the timings for a resolution that I wanted but with a different tv thought I might aswell give them a shot. added @60 after the resolution in the modeline and restarted X and it worked. I cannot say for certain but it seems that with me at least, other timings from another tv worked. ArchLinux here i come. big_smile
Thanks to all that helped me out.

Offline

#7 2010-04-09 16:07:00

Bregol
Member
Registered: 2008-08-15
Posts: 175

Re: [SOLVED] Xorg resolution problems GTS 250 Nvidia

Yeah, that site has a quite a few blanks to try and fill in. I'm trying to remember what I ended up using to do my modelines. I think maybe there was a script I ran on my computer that asked me for frequency and resolution and so forth and didnt ask for dot clock stuff.  I don't remember for sure, but I know if you do a quick google search for "modeline generator", there are a few of them out there, some wanting more input than others to generate your modelines.

Glad you were able to get it working.


Nai haryuvalyë melwa rë

Offline

Board footer

Powered by FluxBB