|
|
#13 | |
|
Registered User
Join Date: Jan 2003
Posts: 31
|
I have marked with green what I think is correct, with blue the part I gues is not validatedd but is output of xrandr (dont know why).
Code:
... (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 75 Hz (II) NVIDIA(0): Mode Source: EDID (II) NVIDIA(0): Pixel Clock : 78.75 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1040 (II) NVIDIA(0): HSyncEnd, HTotal : 1136, 1312 (II) NVIDIA(0): VRes, VSyncStart : 768, 769 (II) NVIDIA(0): VSyncEnd, VTotal : 772, 800 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. ... (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 60 Hz (II) NVIDIA(0): Mode Source: EDID (II) NVIDIA(0): Pixel Clock : 65.00 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1048 (II) NVIDIA(0): HSyncEnd, HTotal : 1184, 1344 (II) NVIDIA(0): VRes, VSyncStart : 768, 771 (II) NVIDIA(0): VSyncEnd, VTotal : 777, 806 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. ... II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 70 Hz (II) NVIDIA(0): Mode Source: EDID (II) NVIDIA(0): Pixel Clock : 75.00 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1048 (II) NVIDIA(0): HSyncEnd, HTotal : 1184, 1328 (II) NVIDIA(0): VRes, VSyncStart : 768, 771 (II) NVIDIA(0): VSyncEnd, VTotal : 777, 806 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. ... (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 43 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 44.90 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1032 (II) NVIDIA(0): HSyncEnd, HTotal : 1208, 1264 (II) NVIDIA(0): VRes, VSyncStart : 768, 768 (II) NVIDIA(0): VSyncEnd, VTotal : 776, 817 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : Interlaced (WW) NVIDIA(0): Mode is rejected: Interlaced modes not allowed. ... (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 65.00 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1048 (II) NVIDIA(0): HSyncEnd, HTotal : 1184, 1344 (II) NVIDIA(0): VRes, VSyncStart : 768, 771 (II) NVIDIA(0): VSyncEnd, VTotal : 777, 806 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. ... (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 70 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 75.00 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1048 (II) NVIDIA(0): HSyncEnd, HTotal : 1184, 1328 (II) NVIDIA(0): VRes, VSyncStart : 768, 771 (II) NVIDIA(0): VSyncEnd, VTotal : 777, 806 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. ... (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 78.80 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1040 (II) NVIDIA(0): HSyncEnd, HTotal : 1136, 1312 (II) NVIDIA(0): VRes, VSyncStart : 768, 769 (II) NVIDIA(0): VSyncEnd, VTotal : 772, 800 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. ... (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 94.50 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1072 (II) NVIDIA(0): HSyncEnd, HTotal : 1168, 1376 (II) NVIDIA(0): VRes, VSyncStart : 768, 769 (II) NVIDIA(0): VSyncEnd, VTotal : 772, 808 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (94.5 MHz) too high for EDID (WW) NVIDIA(0): (EDID Max: 80.0 MHz). ... II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 120 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 133.47 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1100 (II) NVIDIA(0): HSyncEnd, HTotal : 1212, 1400 (II) NVIDIA(0): VRes, VSyncStart : 768, 768 (II) NVIDIA(0): VSyncEnd, VTotal : 772, 1588 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: PixelClock (133.5 MHz) too high for EDID (WW) NVIDIA(0): (EDID Max: 80.0 MHz). ... (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 150 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 170.24 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1108 (II) NVIDIA(0): HSyncEnd, HTotal : 1220, 1416 (II) NVIDIA(0): VRes, VSyncStart : 768, 768 (II) NVIDIA(0): VSyncEnd, VTotal : 772, 1602 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: PixelClock (170.2 MHz) too high for EDID (WW) NVIDIA(0): (EDID Max: 80.0 MHz). ... (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 170 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 194.02 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1108 (II) NVIDIA(0): HSyncEnd, HTotal : 1220, 1416 (II) NVIDIA(0): VRes, VSyncStart : 768, 768 (II) NVIDIA(0): VSyncEnd, VTotal : 772, 1612 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: PixelClock (194.0 MHz) too high for EDID (WW) NVIDIA(0): (EDID Max: 80.0 MHz). ... (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 43 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 44.90 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1032 (II) NVIDIA(0): HSyncEnd, HTotal : 1208, 1264 (II) NVIDIA(0): VRes, VSyncStart : 768, 768 (II) NVIDIA(0): VSyncEnd, VTotal : 776, 817 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : Interlaced (WW) NVIDIA(0): Mode is rejected: Interlaced modes not allowed. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 60 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 65.00 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1048 (II) NVIDIA(0): HSyncEnd, HTotal : 1184, 1344 (II) NVIDIA(0): VRes, VSyncStart : 768, 771 (II) NVIDIA(0): VSyncEnd, VTotal : 777, 806 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 70 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 75.00 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1048 (II) NVIDIA(0): HSyncEnd, HTotal : 1184, 1328 (II) NVIDIA(0): VRes, VSyncStart : 768, 771 (II) NVIDIA(0): VSyncEnd, VTotal : 777, 806 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 75 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 78.80 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1040 (II) NVIDIA(0): HSyncEnd, HTotal : 1136, 1312 (II) NVIDIA(0): VRes, VSyncStart : 768, 769 (II) NVIDIA(0): VSyncEnd, VTotal : 772, 800 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 85 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 94.50 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1072 (II) NVIDIA(0): HSyncEnd, HTotal : 1168, 1376 (II) NVIDIA(0): VRes, VSyncStart : 768, 769 (II) NVIDIA(0): VSyncEnd, VTotal : 772, 808 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (94.5 MHz) too high for EDID (WW) NVIDIA(0): (EDID Max: 80.0 MHz). ... (II) NVIDIA(0): --- Modes in ModePool for Samsung (CRT-0) --- ... (II) NVIDIA(0): "1024x768" : 1024 x 768 @ 75.1 Hz (from: X Server, VESA) (II) NVIDIA(0): "1024x768_75_0" : 1024 x 768 @ 75.1 Hz (from: X Server, VESA) (II) NVIDIA(0): "1024x768_75" : 1024 x 768 @ 75.0 Hz (from: EDID) (II) NVIDIA(0): "1024x768_70" : 1024 x 768 @ 70.1 Hz (from: X Server, VESA, EDID) (II) NVIDIA(0): "1024x768_60" : 1024 x 768 @ 60.0 Hz (from: X Server, VESA, EDID) ... (II) NVIDIA(0): Assigned Display Device: CRT-0 (II) NVIDIA(0): Requested modes: (II) NVIDIA(0): "1024x768" (II) NVIDIA(0): "800x600" (II) NVIDIA(0): "640x480" (II) NVIDIA(0): Validated modes: (II) NVIDIA(0): MetaMode "1024x768": ... (II) NVIDIA(0): MetaMode "800x600": ... (II) NVIDIA(0): MetaMode "640x480": ... because it was rejected...But the mode accepted 1024x768@75 "Pixel Clock : 78.75 MHz" overpass the max rate??? of the manual... "VESA, 1024 x 768 Pixel clock 65.000 Mhz" Added the anterior paragraph. Last edited by hgb; 07-20-06 at 11:42 PM. |
|
|
|
|
|
|
#14 | |
|
Registered User
Join Date: Jan 2003
Posts: 31
|
Question...
There is a way I can force start "startx" with something like 1024x768@60???? and dosent let the driver select @ 75???? I see this like the only option that I have, but I dont know how. (I think that the EDID is not 80... in the manual say max pixel clock is 65 and not 80) |
|
|
|
|
|
|
#15 |
|
NVIDIA Corporation
Join Date: Dec 2004
Posts: 8,763
|
You can request the 1024x768_60 mode.
-Lonni |
|
|
|
|
|
#16 | |
|
Registered User
Join Date: Jan 2003
Posts: 31
|
I see that xrandr -s 1024x768_60 & xrandr -s 1024x768_75 make the monitor run black and the led blink, but hitting CTRL+ALT+"+" make the monitor go OK for 800x600, do a bigger window for 1024x768 (but display it no black window) and it never get to the resolution of 640x480 hitting this combination.
Anyway, I attach if serve of some a Xorg.0.log of "nv" (after restart of the graphical server from a session with nvidia driver) (first at 800x600... but the different modes work with nv). Do you have any hint why it work with nv but not with nvidia??? |
|
|
|
|
|
|
#17 | |
|
Registered User
Join Date: Aug 2003
Posts: 1,026
|
Quote:
Try to find something that can at least display 1280x1024 at a refreshrate of 75Hz or above. It will make your use of Linux much more enjoyable! Now that everyone wants a flatpanel, an old (but not THAT old) CRT monitor is easy to find second-hand. |
|
|
|
|
|
|
#18 | |
|
Registered User
Join Date: Jan 2003
Posts: 31
|
But I dont understand why under "nv" work perfectly (it fit perfectly... and it detect the rate perfectly 60hz), and like I see all the resolutions printed under xrandr work OK (even the lower ones).
|
|
|
|
|
|
|
#19 | |
|
Registered User
Join Date: Aug 2003
Posts: 1,026
|
Quote:
What I wanted to say is that working at 1024x768 is not much fun, and doing it at 60Hz is causing too many headaches. So after you have got it working under the nvidia driver you will still want another monitor, and you could just go out and get one first. Someone at my work recently bought a used 19" CRT (HP) for 30 euro, from the local 2nd hand shopping/trading site. Such monitors nicely run 1600x1200 at 75Hz. Smaller ones should be even cheaper. |
|
|
|
|
|
|
#20 |
|
Registered User
Join Date: Jan 2003
Posts: 31
|
The thing is that requesting the mode in xrandr dosent work
Code:
xrandr -s 1024x768_60 Code:
~$ xrandr SZ: Pixels Physical Refresh *0 1024 x 768 ( 283mm x 212mm ) *75 1 800 x 600 ( 283mm x 212mm ) 85 2 640 x 480 ( 283mm x 212mm ) 85 Current rotation - normal Current reflection - none Rotations possible - normal Reflections possible - none From this thread http://www.nvnews.net/vbulletin/showthread.php?t=73752 I follow and get this explanation http://download.nvidia.com/XFree86/L...ppendix-j.html Then after read a little... it say that the driver take all the valid modes and give a name and default the "best mode autodetected" to the name of the resolution in this case "1024x768"... and I see the names starting "startx -- -logverbose 6" or modifying /etc/gdm/gdm.conf (Im using gdm manager) and adding the "-logverbose 6" to the line of startx. Anyway, I see there the rate that I wanted @60... and I modifyied my xorg for request that name by available to xrandr (I guess) Code:
SubSection "Display"
Depth 24
Modes "1024x768_60" "1024x768" "800x600" "640x480"
EndSubSection
And tada.. It work perfect... the 1024x768_60 fit completely on my monitor not like the default 1024x768 that is 1024x768_75 .Now the mode is available to xrandr Code:
~$ xrandr SZ: Pixels Physical Refresh *0 1024 x 768 ( 283mm x 212mm ) *60 75 1 800 x 600 ( 283mm x 212mm ) 85 2 640 x 480 ( 283mm x 212mm ) 85 Current rotation - normal Current reflection - none Rotations possible - normal Reflections possible - none . |
|
|
|
|
|
#21 |
|
Registered User
Join Date: Aug 2003
Posts: 1,026
|
And you don't get a headache from the terrible flicker at 60Hz?
Then you should consider yourself lucky! (it may also be that the monitor has a slow phosphor. some older monitors do. I used to have an old 19" professional Sony fixed-frequency monitor that only runs at 60Hz, and its picture flickers much less than the typical PC monitor does) |
|
|
|
|
|
#22 |
|
Registered User
Join Date: Jan 2003
Posts: 31
|
I think no, I can play much time without problems... also is a little monitorI guess is OK the refresh for this size of monitor it is a 15" monitor... tought I dont know well how to install games on Linux.. I only have 2 or 3 and one FPS... in mean time I will buy another cmputer for get the new games
...By the way... do you know how to make my mouse wheel scroll the page???? and how to kill a game that has freeze and is full screen??? I need press the restart server combination. but dont know how to kill the game :S. |
|
|
|
![]() |
| Thread Tools | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Problems with configuring monitors and keeping them disabled with 302.17 | Erosmith | NVIDIA Linux | 2 | 06-20-12 12:10 AM |
| Max Payne 3 at Max resolution | News | Latest Tech And Game Headlines | 0 | 06-06-12 06:30 PM |
| Max Payne 3 for PC is Out Now and Comes with 3D Vision Support | News | Gaming Central | 0 | 06-02-12 08:30 PM |
| What resolution do you all run Unreal2003 retail version at with all details on max.? | imtim83 | Gaming Central | 9 | 10-04-02 10:17 AM |
| 30.82 and 40.41 resolution + monitor OSD. | Max3D | NVIDIA Windows Graphics Drivers | 2 | 09-05-02 02:15 AM |