LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 05-25-2010, 08:12 AM   #16
johnh10000
Member
 
Registered: Nov 2008
Distribution: Ubuntu Lucid Lynx
Posts: 541

Original Poster
Rep: Reputation: 33

Quote:
Originally Posted by johnsfine View Post
Try the native resolution (1440x900).

An LCD looks much better at its native resolution than at any other resolution. Even if 1280x1024 works, it is likely to be at least blurred and maybe distorted.
ok daft question, it is an lcd, where is this native res on the config thing?

also whats edid ???
 
Old 05-25-2010, 08:15 AM   #17
johnh10000
Member
 
Registered: Nov 2008
Distribution: Ubuntu Lucid Lynx
Posts: 541

Original Poster
Rep: Reputation: 33
Quote:
Originally Posted by johnh10000 View Post
ok daft question, it is an lcd, where is this native res on the config thing?

also whats edid ???
well i've put to auto now.

and your correct, it does seem "sharper"

Last edited by johnh10000; 10-31-2010 at 05:49 AM.
 
Old 05-25-2010, 08:20 AM   #18
johnh10000
Member
 
Registered: Nov 2008
Distribution: Ubuntu Lucid Lynx
Posts: 541

Original Poster
Rep: Reputation: 33
well it persists in defaulting to 1024x768
 
Old 05-25-2010, 08:26 AM   #19
LouRobytes
Member
 
Registered: Mar 2010
Location: Nova Scotia, Canada
Distribution: Ubuntu & Fedora
Posts: 189

Rep: Reputation: 44
If you have a widescreen display, then you shouldn't be using 1280x1024 because it is not the correct aspect ratio and objects will appear narrow and tall. johnsfine is right about using native to avoid blurring.

Cheers, Lou

EDIT: Damn my two-finger typing. I keep missing responses.

Last edited by LouRobytes; 05-25-2010 at 08:28 AM.
 
Old 05-25-2010, 08:30 AM   #20
johnh10000
Member
 
Registered: Nov 2008
Distribution: Ubuntu Lucid Lynx
Posts: 541

Original Poster
Rep: Reputation: 33
Quote:
Originally Posted by LouRobytes View Post
If you have a widescreen display, then you shouldn't be using 1280x1024 because it is not the correct aspect ratio and objects will appear narrow and tall. johnsfine is right about using native to avoid blurring.

Cheers, Lou
I have indeed got a a w/s monitor. I agree, the native one is best.

now to persuade it to change to it after a restart. more a niggle than anything else.

As this box, runs my sftp server, its on most of the time
 
Old 05-25-2010, 09:22 AM   #21
tredegar
LQ 5k Club
 
Registered: May 2003
Location: London, UK
Distribution: Debian "Jessie"
Posts: 6,017

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
Did you add those lines to xorg.conf as I suggested?

My resolution problem was not a problem with the nvidia driver, it was a problem with X reading the EDID from my monitor, so it chose the wrong resolution and messed up the display.

EDID is Extended Display Identification Data. Modern monitors can be asked what their capabilities (sync, screensize, resolution etc) are and they'll reply.

Once X was told to get the EDID data from the /proc filesystem rather than the screen hardware, it worked.
 
Old 05-25-2010, 09:42 AM   #22
johnh10000
Member
 
Registered: Nov 2008
Distribution: Ubuntu Lucid Lynx
Posts: 541

Original Poster
Rep: Reputation: 33
Quote:
Originally Posted by tredegar View Post
Did you add those lines to xorg.conf as I suggested?

My resolution problem was not a problem with the nvidia driver, it was a problem with X reading the EDID from my monitor, so it chose the wrong resolution and messed up the display.

EDID is Extended Display Identification Data. Modern monitors can be asked what their capabilities (sync, screensize, resolution etc) are and they'll reply.

Once X was told to get the EDID data from the /proc filesystem rather than the screen hardware, it worked.

You seem to know more about the /proc filesystem than I. Using your settings will prob fail. How would I find out MY monitor from the /proc fs?

the only reason why I have not
 
Old 05-25-2010, 10:00 AM   #23
LouRobytes
Member
 
Registered: Mar 2010
Location: Nova Scotia, Canada
Distribution: Ubuntu & Fedora
Posts: 189

Rep: Reputation: 44
If you add this option to the Device section of xorg.conf
Code:
	Option "ModeDebug" "True"
and then reboot, a wealth of info, including EDID reported data will be logged to Xorg.0.log.

This will tell you if it is reporting an incorrect resolution.

Attach the new log please.

Curious, Lou
 
Old 05-25-2010, 10:06 AM   #24
tredegar
LQ 5k Club
 
Registered: May 2003
Location: London, UK
Distribution: Debian "Jessie"
Posts: 6,017

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
The kernel has correctly read my LCD screen's EDID and made it available in the file /proc/acpi/video/NGFX/LCD/EDID

Your file will be in the same place, but the contents will be different because you have a different monitor.

Ubuntu 10.04's version of X was not reading, or perhaps interpreting, the EDID correctly when it queried my monitor (dont ask me why, I don't know). But when I told X to use the version stored in /proc ( which is what those lines in xorg.conf do), it worked.

You could copy your EDID from proc to a file
Code:
cat /proc/acpi/video/NGFX/LCD/EDID > edid.bin
It's a binary file, and quite complicated to understand. You can use your search engine for the details of the format, but there's a utility called parse-edid that'll make parts of it human-readable:

Code:
tred@vaio:~$ cat /proc/acpi/video/NGFX/LCD/EDID | parse-edid
        # EDID version 1 revision 4
Section "Monitor"
        # Block type: 2:0 3:fc
        Identifier "Nvidia Defaul"
        VendorName "MS_"
        ModelName "Nvidia Defaul"
        # Block type: 2:0 3:fc
        # Block type: 2:0 3:fc
        # DPMS capabilities: Active off:yes  Suspend:yes  Standby:yes

        Mode    "1920x1080"     # vfreq 59.940Hz, hfreq 68.571kHz
                DotClock        144.000000
                HTimings        1920 1980 2040 2100
                VTimings        1080 1085 1090 1144
                Flags   "-HSync" "-VSync"
        EndMode
        Mode    "1920x1080"     # vfreq 50.000Hz, hfreq 62.500kHz
                DotClock        144.000000
                HTimings        1920 2048 2176 2304
                VTimings        1080 1088 1096 1250
                Flags   "-HSync" "-VSync"
        EndMode
        # Block type: 2:0 3:fc
        # Block type: 2:0 3:fc
EndSection
 
Old 05-25-2010, 10:53 AM   #25
johnh10000
Member
 
Registered: Nov 2008
Distribution: Ubuntu Lucid Lynx
Posts: 541

Original Poster
Rep: Reputation: 33
Quote:
Originally Posted by LouRobytes View Post
If you add this option to the Device section of xorg.conf
Code:
	Option "ModeDebug" "True"
and then reboot, a wealth of info, including EDID reported data will be logged to Xorg.0.log.

This will tell you if it is reporting an incorrect resolution.

Attach the new log please.

Curious, Lou
ok I tried both, with your debug mode, I didn't even get to the logo/passwd screen other normal ops

Last edited by johnh10000; 10-31-2010 at 05:49 AM.
 
Old 05-25-2010, 11:11 AM   #26
LouRobytes
Member
 
Registered: Mar 2010
Location: Nova Scotia, Canada
Distribution: Ubuntu & Fedora
Posts: 189

Rep: Reputation: 44
The log file you attached was for the CustomEID option and not ModeDebug.
Quote:
(**) 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 "ConnectedMonitor" "DFP-0"
(**) NVIDIA(0): Option "TwinView" "0"
(**) NVIDIA(0): Option "MetaModes" "nvidia-auto-select +0+0"
(**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "CRT-0"
(**) NVIDIA(0): Option "CustomEDID" "DFP-0: /proc/acpi/video/NGFX/LCD/EDID"
With option ModeDebug, you would see
Quote:
(**) 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 "NoLogo" "True"
(**) NVIDIA(0): Option "ModeDebug" "True"
(**) May 25 11:49:59 NVIDIA(0): Enabling RENDER acceleration
along with all kinds of other info including something like
Quote:
(**) May 25 11:49:59 NVIDIA(0): Enabling RENDER acceleration
(II) May 25 11:49:59 NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) May 25 11:49:59 NVIDIA(0): enabled.
(II) May 25 11:49:59 NVIDIA(0): NVIDIA GPU GeForce 6150SE nForce 430 (C61) at PCI:0:13:0
(II) May 25 11:49:59 NVIDIA(0): (GPU-0)
(--) May 25 11:49:59 NVIDIA(0): Memory: 524288 kBytes
(--) May 25 11:49:59 NVIDIA(0): VideoBIOS: 05.61.32.26.00
(--) May 25 11:49:59 NVIDIA(0): Interlaced video modes are supported on this GPU
(--) May 25 11:49:59 NVIDIA(0): Connected display device(s) on GeForce 6150SE nForce 430 at
(--) May 25 11:49:59 NVIDIA(0): PCI:0:13:0:
(--) May 25 11:49:59 NVIDIA(0): CMO CMC 22 W (CRT-0)
(--) May 25 11:49:59 NVIDIA(0): CMO CMC 22 W (CRT-0): 350.0 MHz maximum pixel clock
(--) May 25 11:49:59 NVIDIA(0):
(--) May 25 11:49:59 NVIDIA(0): --- EDID for CMO CMC 22 W (CRT-0) ---
(--) May 25 11:49:59 NVIDIA(0): EDID Version : 1.3
(--) May 25 11:49:59 NVIDIA(0): Manufacturer : CMO
(--) May 25 11:49:59 NVIDIA(0): Monitor Name : CMO CMC 22 W
(--) May 25 11:49:59 NVIDIA(0): Product ID : 8744
(--) May 25 11:49:59 NVIDIA(0): 32-bit Serial Number : 16843009
(--) May 25 11:49:59 NVIDIA(0): Serial Number String : 0
(--) May 25 11:49:59 NVIDIA(0): Manufacture Date : 2007, week 19
(--) May 25 11:49:59 NVIDIA(0): DPMS Capabilities : Active Off
(--) May 25 11:49:59 NVIDIA(0): Prefer first detailed timing : Yes
(--) May 25 11:49:59 NVIDIA(0): Supports GTF : No
(--) May 25 11:49:59 NVIDIA(0): Maximum Image Size : 470mm x 300mm
(--) May 25 11:49:59 NVIDIA(0): Valid HSync Range : 30.0 kHz - 82.0 kHz
(--) May 25 11:49:59 NVIDIA(0): Valid VRefresh Range : 56 Hz - 76 Hz
(--) May 25 11:49:59 NVIDIA(0): EDID maximum pixel clock : 210.0 MHz
(--) May 25 11:49:59 NVIDIA(0):
(--) May 25 11:49:59 NVIDIA(0): Established Timings:
(--) May 25 11:49:59 NVIDIA(0): 640 x 480 @ 60 Hz
(--) May 25 11:49:59 NVIDIA(0): 640 x 480 @ 72 Hz
(--) May 25 11:49:59 NVIDIA(0): 640 x 480 @ 75 Hz
(--) May 25 11:49:59 NVIDIA(0): 800 x 600 @ 56 Hz
(--) May 25 11:49:59 NVIDIA(0): 800 x 600 @ 60 Hz
(--) May 25 11:49:59 NVIDIA(0): 800 x 600 @ 72 Hz
(--) May 25 11:49:59 NVIDIA(0): 800 x 600 @ 75 Hz
(--) May 25 11:49:59 NVIDIA(0): 1024 x 768 @ 60 Hz
(--) May 25 11:49:59 NVIDIA(0): 1024 x 768 @ 70 Hz
(--) May 25 11:49:59 NVIDIA(0): 1024 x 768 @ 75 Hz
(--) May 25 11:49:59 NVIDIA(0): 1280 x 1024 @ 75 Hz
(--) May 25 11:49:59 NVIDIA(0):
(--) May 25 11:49:59 NVIDIA(0): Standard Timings:
(--) May 25 11:49:59 NVIDIA(0): 1280 x 1024 @ 60 Hz
(--) May 25 11:49:59 NVIDIA(0): 1280 x 960 @ 60 Hz
(--) May 25 11:49:59 NVIDIA(0): 1152 x 864 @ 75 Hz
(--) May 25 11:49:59 NVIDIA(0): 1440 x 900 @ 60 Hz
(--) May 25 11:49:59 NVIDIA(0): 1440 x 900 @ 75 Hz
(--) May 25 11:49:59 NVIDIA(0): 1280 x 720 @ 60 Hz
(--) May 25 11:49:59 NVIDIA(0): 1360 x 765 @ 60 Hz
(--) May 25 11:49:59 NVIDIA(0):
(--) May 25 11:49:59 NVIDIA(0): Detailed Timings:
(--) May 25 11:49:59 NVIDIA(0): 1680 x 1050 @ 60 Hz
(--) May 25 11:49:59 NVIDIA(0): Pixel Clock : 146.25 MHz
(--) May 25 11:49:59 NVIDIA(0): HRes, HSyncStart : 1680, 1784
(--) May 25 11:49:59 NVIDIA(0): HSyncEnd, HTotal : 1960, 2240
(--) May 25 11:49:59 NVIDIA(0): VRes, VSyncStart : 1050, 1053
(--) May 25 11:49:59 NVIDIA(0): VSyncEnd, VTotal : 1059, 1089
(--) May 25 11:49:59 NVIDIA(0): H/V Polarity : -/+
(--) May 25 11:49:59 NVIDIA(0):
(--) May 25 11:49:59 NVIDIA(0):
Try it again with ModeDebug and no CustomEDID option.

Cheers, Lou.
 
Old 05-25-2010, 11:25 AM   #27
johnh10000
Member
 
Registered: Nov 2008
Distribution: Ubuntu Lucid Lynx
Posts: 541

Original Poster
Rep: Reputation: 33
Quote:
Originally Posted by LouRobytes View Post
The log file you attached was for the CustomEID option and not ModeDebug.

With option ModeDebug, you would see

along with all kinds of other info including something like

Try it again with ModeDebug and no CustomEDID option.

Cheers, Lou.
when I tried that I didn't even get to a login screen.

will try again though
 
Old 05-25-2010, 11:33 AM   #28
johnsfine
Guru
 
Registered: Dec 2007
Distribution: Centos
Posts: 5,109

Rep: Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114
That CustomEDID line is too specify to LouRobytes's situation and doesn't fit Johnh10000's system.

First the display connector is DFP-0 for LouRobytes vs. CRT-0 for Johnh10000

Also, I'm not too sure about /proc/acpi/video/NGFX/LCD/EDID
Before trying to use that, look at the directory tree starting at /proc/acpi/video and see what sub directories and files are present.

The log file last posted has no evidence of ModeDebug, maybe because it wasn't from a run using ModeDebug, maybe because ModeDebug didn't work.

I don't know how ModeDebug is supposed to work. A google search found this site discussing a problem that might be related and suggesting ModeDebug in the Monitor section (not the Device section)
http://www.cyberwizzard.nl/site/blog...solutions.html

Last edited by johnsfine; 05-25-2010 at 11:35 AM.
 
Old 05-25-2010, 11:33 AM   #29
johnh10000
Member
 
Registered: Nov 2008
Distribution: Ubuntu Lucid Lynx
Posts: 541

Original Poster
Rep: Reputation: 33
Quote:
Originally Posted by johnh10000 View Post
when I tried that I didn't even get to a login screen.

will try again though
take two

Last edited by johnh10000; 10-31-2010 at 05:49 AM.
 
Old 05-25-2010, 11:38 AM   #30
johnsfine
Guru
 
Registered: Dec 2007
Distribution: Centos
Posts: 5,109

Rep: Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114Reputation: 1114
See my post #28 if you missed it (we were posting at the same time).

Notice in the log attached to post #29 it says
Code:
(II) Loading extension NV-CONTROL
(WW) NVIDIA(0): Option "ModeDebug" is not used
So this nvidia driver cannot understand ModeDebug in the Device section. (I don't know whether it will understand ModeDebug in the Monitor section).

Last edited by johnsfine; 05-25-2010 at 11:41 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
nvidia xorg.conf OR X windows xorg.conf? machines Slackware 3 04-06-2008 02:10 PM
Gentoo / Nvidia / Xorg.conf GaMeS Linux - Newbie 8 10-29-2005 05:38 AM
xorg.conf and nvidia problem scarryharry Slackware 8 05-20-2005 04:00 PM
NVidia TV out thru xorg.conf jobless_joe Linux - Software 7 02-22-2005 11:59 PM
nvidia tv-out Xorg.conf copy needed... TomCollins Slackware 4 11-07-2004 02:50 PM


All times are GMT -5. The time now is 01:29 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration