Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 07-15-06, 03:20 AM   #1
v9400-user
Registered User
 
Join Date: Jul 2006
Posts: 6
Default Asus V9400-X 64M in 1600x1200

I have a V9400-X (MX4000) Asus card that I would like to run in 1600x1200 resolution. It works just fine in 1280x1024 mode but the nvidia driver refuse to start in higher resolution (from Xorg.0.log):

"(II) NVIDIA(0): Mode "1600x1200" is larger than BIOS programmed panel size of 1280 x 1024. Removing."

The card is speced to be able to run in a much higher resolution so this can not be a hardware problem.

Is there a way arround this, or do I need to get another graphics card that is supported under Linux ?

Thanks in advance

PS: I am running SuSE9.2 and will probably upgrade to 10.1 soon.
v9400-user is offline   Reply With Quote
Old 07-15-06, 06:14 AM   #2
Chalnoth
Registered User
 
Join Date: Jul 2002
Posts: 1,293
Default Re: Asus V9400-X 64M in 1600x1200

Well, that sounds like your graphics card thinks you're running a flat panel display with a native resolution of 1280x1024. What kind of display are you running?
__________________
"Physics is like sex. Sure, it may give some practical results, but that's not why we do it." - Richard P. Feynman
Chalnoth is offline   Reply With Quote
Old 07-15-06, 08:36 AM   #3
v9400-user
Registered User
 
Join Date: Jul 2006
Posts: 6
Default Re: Asus V9400-X 64M in 1600x1200

Thanks for the response !

Yes, the monitor is a 1600x1200 TFT. As I read it, the card BIOS has a fixed limit of 1280x1024.

The driver is:

(II) NVIDIA: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,...
(the MX 4000 is *not* on the very long list).

which is supported by:

(--) Chipset Unknown NVIDIA chip found

DDC return:

(II) NVIDIA(0): Supported VESA Video Modes:
(II) NVIDIA(0): 720x400@70Hz
(II) NVIDIA(0): 640x480@60Hz
(II) NVIDIA(0): 640x480@75Hz
(II) NVIDIA(0): 800x600@60Hz
(II) NVIDIA(0): 832x624@75Hz
(II) NVIDIA(0): 1024x768@60Hz
(II) NVIDIA(0): 1024x768@75Hz
(II) NVIDIA(0): 1280x1024@75Hz
(II) NVIDIA(0): 1152x870@75Hz
(II) NVIDIA(0): Manufacturer's mask: 0
(II) NVIDIA(0): Supported Future Video Modes:
(II) NVIDIA(0): #0: hsize: 640 vsize 480 refresh: 85 vid: 22833
(II) NVIDIA(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
(II) NVIDIA(0): #2: hsize: 1024 vsize 768 refresh: 85 vid: 22881
(II) NVIDIA(0): #3: hsize: 1280 vsize 960 refresh: 60 vid: 16513
(II) NVIDIA(0): #4: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) NVIDIA(0): #5: hsize: 1280 vsize 1024 refresh: 85 vid: 39297
(II) NVIDIA(0): #6: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
(II) NVIDIA(0): Supported additional Video Mode:
(II) NVIDIA(0): clock: 162.0 MHz Image Size: 408 x 306 mm
(II) NVIDIA(0): h_active: 1600 h_sync: 1664 h_sync_end 1856 h_blank_end 2160 $
(II) NVIDIA(0): v_active: 1200 v_sync: 1201 v_sync_end 1204 v_blanking: 1250 $
(II) NVIDIA(0): Ranges: V min: 48 V max: 85 Hz, H min: 30 H max: 92 kHz, PixC$
.
.
.
(--) NVIDIA(0): CRTC 0 is currently programmed for DFP
(II) NVIDIA(0): Using DFP on CRTC 0
(--) NVIDIA(0): Panel size is 1280 x 1024
(--) NVIDIA(0): VideoRAM: 65536 kBytes


Why does the BIOS limit the resolution to 1280x1024 ? Is there a way to break this limit ?

Thanks in advance
v9400-user is offline   Reply With Quote
Old 07-15-06, 11:45 AM   #4
Chalnoth
Registered User
 
Join Date: Jul 2002
Posts: 1,293
Default Re: Asus V9400-X 64M in 1600x1200

I don't think that's what it is, though. There certainly shouldn't be a hard resolution limitation of 1280x1024 in the video card's BIOS. I think it's improperly-detecting the flat panel.

Try running "nvidia-xconfig -A |less" to get a list of all options available when running the X server under nVidia's drivers. There may possibly be an option that may help.
__________________
"Physics is like sex. Sure, it may give some practical results, but that's not why we do it." - Richard P. Feynman
Chalnoth is offline   Reply With Quote
Old 07-15-06, 12:15 PM   #5
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Asus V9400-X 64M in 1600x1200

Please start X with the following command:
startx -- -logverbose 6

and then generate and post an nvidia-bug-report.log.

Thanks,
Lonni
netllama is offline   Reply With Quote
Old 07-15-06, 06:34 PM   #6
v9400-user
Registered User
 
Join Date: Jul 2006
Posts: 6
Default Re: Asus V9400-X 64M in 1600x1200

Thanks for your support... no need for a bugreport - case solved: I used YaST to install the nvidia driver. Something must have gone wrong in that installation. After a manual reinstallation 1600x1200 now works just fine !
v9400-user is offline   Reply With Quote
Old 08-03-06, 07:54 AM   #7
v9400-user
Registered User
 
Join Date: Jul 2006
Posts: 6
Default Re: Asus V9400-X 64M in 1600x1200

Hi again,

It seems like I am not quite done with the setup of my V9400-X... my display show that it is running in 1600x1200@ 59Hz and the display is not as rock-stable as I have come to expect using DVI for many years now. I have found the following link: http://suif.stanford.edu/~csapuntz/rv280-linux-dvi.html - actually about an ATI GPU, but this could be a similar issue. I would like to try to use reduced blanking timings, but the nvidia driver ignores my setup in xorg.conf. This is an extract from Xorg.0.log generated by "startx -- -logverbose 6":

(II) NVIDIA(0): Mode timing constraints for : GeForce4 MX 4000
(II) NVIDIA(0): Maximum mode timing values :
(II) NVIDIA(0): Horizontal Visible Width : 8192
(II) NVIDIA(0): Horizontal Blank Start : 8192
(II) NVIDIA(0): Horizontal Blank Width : 4096
(II) NVIDIA(0): Horizontal Sync Start : 8184
(II) NVIDIA(0): Horizontal Sync Width : 504
(II) NVIDIA(0): Horizontal Total Width : 8224
(II) NVIDIA(0): Vertical Visible Height : 8192
(II) NVIDIA(0): Vertical Blank Start : 8192
(II) NVIDIA(0): Vertical Blank Width : 256
(II) NVIDIA(0): Veritcal Sync Start : 8191
(II) NVIDIA(0): Vertical Sync Width : 15
(II) NVIDIA(0): Vertical Total Height : 8193
(II) NVIDIA(0):
(II) NVIDIA(0): Minimum mode timing values :
(II) NVIDIA(0): Horizontal Total Width : 40
(II) NVIDIA(0): Vertical Total Height : 2
(II) NVIDIA(0):
(II) NVIDIA(0): Mode timing alignment :
(II) NVIDIA(0): Horizontal Visible Width : multiples of 8
(II) NVIDIA(0): Horizontal Blank Start : multiples of 8
(II) NVIDIA(0): Horizontal Blank Width : multiples of 8
(II) NVIDIA(0): Horizontal Sync Start : multiples of 8
(II) NVIDIA(0): Horizontal Sync Width : multiples of 8
(II) NVIDIA(0): Horizontal Total Width : multiples of 8
(II) NVIDIA(0):
(--) NVIDIA(0): Connected display device(s) on GeForce4 MX 4000 at PCI:1:0:0:
(--) NVIDIA(0): HP LP2065 (DFP-0)
(--) NVIDIA(0): HP LP2065 (DFP-0): 135.0 MHz maximum pixel clock
(--) NVIDIA(0): HP LP2065 (DFP-0): Internal Single Link TMDS
(--) NVIDIA(0): HP LP2065 (DFP-0): Native FlatPanel Scaling is supported
(--) NVIDIA(0): HP LP2065 (DFP-0): DFP modes are limited to 60 Hz refresh
(--) NVIDIA(0): rate
(--) NVIDIA(0):
(--) NVIDIA(0): --- EDID for HP LP2065 (DFP-0) ---
(--) NVIDIA(0): EDID Version : 1.3
(--) NVIDIA(0): Manufacturer : HWP
(--) NVIDIA(0): Monitor Name : HP LP2065
(--) NVIDIA(0): Product ID : 2674
(--) NVIDIA(0): 32-bit Serial Number : <snip>
(--) NVIDIA(0): Serial Number String : CNG61008BY
(--) NVIDIA(0): Manufacture Date : 2006, week 10
(--) NVIDIA(0): DPMS Capabilities : Standby Suspend Active Off
(--) NVIDIA(0): Prefer first detailed timing : Yes
(--) NVIDIA(0): Supports GTF : No
(--) NVIDIA(0): Maximum Image Size : 410mm x 310mm
(--) NVIDIA(0): Valid HSync Range : 30 kHz - 92 kHz
(--) NVIDIA(0): Valid VRefresh Range : 48 Hz - 85 Hz
(--) NVIDIA(0): EDID maximum pixel clock : 170.0 MHz
(--) NVIDIA(0):
(--) NVIDIA(0): Established Timings:
(--) NVIDIA(0): 640 x 480 @ 60 Hz
(--) NVIDIA(0): 640 x 480 @ 75 Hz
(--) NVIDIA(0): 800 x 600 @ 60 Hz
(--) NVIDIA(0): 1024 x 768 @ 60 Hz
(--) NVIDIA(0): 1024 x 768 @ 75 Hz
(--) NVIDIA(0): 1280 x 1024 @ 75 Hz
(--) NVIDIA(0):
(--) NVIDIA(0): Standard Timings:
(--) NVIDIA(0): 640 x 480 @ 85 Hz
(--) NVIDIA(0): 800 x 600 @ 85 Hz
(--) NVIDIA(0): 1024 x 768 @ 85 Hz
(--) NVIDIA(0): 1280 x 960 @ 60 Hz
(--) NVIDIA(0): 1280 x 1024 @ 60 Hz
(--) NVIDIA(0): 1280 x 1024 @ 85 Hz
(--) NVIDIA(0):
(--) NVIDIA(0): Detailed Timings:
(--) NVIDIA(0): 1600 x 1200 @ 60 Hz
(--) NVIDIA(0): Pixel Clock : 162.00 MHz
(--) NVIDIA(0): HRes, HSyncStart : 1600, 1664
(--) NVIDIA(0): HSyncEnd, HTotal : 1856, 2160
(--) NVIDIA(0): VRes, VSyncStart : 1200, 1201
(--) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250
(--) NVIDIA(0): H/V Polarity : +/+
(--) NVIDIA(0):
(--) NVIDIA(0):
(--) NVIDIA(0): Raw EDID bytes:
(--) NVIDIA(0):
(--) NVIDIA(0): 00 ff ff ff ff ff ff 00 22 f0 72 0a 01 01 01 01
(--) NVIDIA(0): 0a 10 01 03 80 29 1f 78 ee a6 a5 a3 57 4a 9d 25
(--) NVIDIA(0): 12 50 54 a5 2b 80 31 59 45 59 61 59 81 40 81 80
(--) NVIDIA(0): 81 99 a9 40 01 01 48 3f 40 30 62 b0 32 40 40 c0
(--) NVIDIA(0): 13 00 98 32 11 00 00 1e 00 00 00 fd 00 30 55 1e
(--) NVIDIA(0): 5c 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 48
(--) NVIDIA(0): 50 20 4c 50 32 30 36 35 0a 20 20 20 00 00 00 ff
(--) NVIDIA(0): 00 43 4e 47 36 31 30 30 38 42 59 0a 20 20 00 88
(--) NVIDIA(0):
(--) NVIDIA(0): --- End of EDID for HP LP2065 (DFP-0) ---
(--) NVIDIA(0):
(II) NVIDIA(0): Frequency information for HP LP2065 (DFP-0):
(II) NVIDIA(0): HorizSync : 30.000-92.000 kHz
(II) NVIDIA(0): VertRefresh : 48.000-85.000 Hz
(II) NVIDIA(0): (HorizSync from EDID)
(II) NVIDIA(0): (VertRefresh from EDID)
(II) NVIDIA(0):
(II) NVIDIA(0): --- Building ModePool for HP LP2065 (DFP-0) ---
(II) NVIDIA(0): Validating Mode "1600x1200":
(II) NVIDIA(0): 1600 x 1200 @ 60 Hz
(II) NVIDIA(0): Mode Source: EDID
(II) NVIDIA(0): Pixel Clock : 162.00 MHz
(II) NVIDIA(0): HRes, HSyncStart : 1600, 1664
(II) NVIDIA(0): HSyncEnd, HTotal : 1856, 2160
(II) NVIDIA(0): VRes, VSyncStart : 1200, 1201
(II) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250
(II) NVIDIA(0): H/V Polarity : +/+
(II) NVIDIA(0): Mode is valid.
(II) NVIDIA(0): Reduced Blanking enabled to bring Pixel Clock in range.


So the nvidia driver clearly know about "reduced blanking" - but I would like to try to reduce it further. How do I do that ?

And what is the difference between the two reported max pixel clocks:

(--) NVIDIA(0): HP LP2065 (DFP-0): 135.0 MHz maximum pixel clock

and

(--) NVIDIA(0): EDID maximum pixel clock : 170.0 MHz

The 135MHz limit is the limit normally reported in Xorg.0.log (without -logverbose).

Thanks in advance


PS: I have tried to use the driver on SuSE 10.1 (installing via YaST2 using the nVidia instructions on top of a fully updated 10.1). While my SuSE 9.2 has been solid as a rock for the past year, the SuSE 10.1 has crashed several times within a few hours. Common to these crashes is that the mouse cursor disappear from the screen. Are there any known stability issues for the nvidia driver on SuSE 10.1 ?
v9400-user is offline   Reply With Quote
Old 08-03-06, 12:30 PM   #8
v9400-user
Registered User
 
Join Date: Jul 2006
Posts: 6
Default Re: Asus V9400-X 64M in 1600x1200

OK, I figured out how to set my new favorite mode - just neede to give it a unique name and reference it:

.
.
.
Modeline "1600x1200-reduced-blank" 130.42 1600 1648 1680 1760 1200 1203 1207 1235
.
.
.
and

.
.
.
Section "Screen"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1600x1200-reduced-blank"
.
.
.

I think the change had the desired effect. Is it possible to reduce the blanking further (does EDID provide the nvidia driver with information about required blanking intervals from the monitor ?).

The two other questions (difference between the two max pixel clocks reported and SuSE 10.1 stability) remain.

Thanks in advance
v9400-user is offline   Reply With Quote

Old 08-03-06, 01:03 PM   #9
Chalnoth
Registered User
 
Join Date: Jul 2002
Posts: 1,293
Default Re: Asus V9400-X 64M in 1600x1200

Well, I'm running openSuSE 10.1 on a GeForce 7800 GT SLI rig, and it's quite stable. So there definitely isn't any global stability issue with the nVidia drivers on 10.1.

Since you mentioned something about the cursor, you might try turning off the hardware-accelerated cursor. Check the drivers' readme for how.
__________________
"Physics is like sex. Sure, it may give some practical results, but that's not why we do it." - Richard P. Feynman
Chalnoth is offline   Reply With Quote
Old 08-03-06, 05:13 PM   #10
v9400-user
Registered User
 
Join Date: Jul 2006
Posts: 6
Default Re: Asus V9400-X 64M in 1600x1200

Thanks for the response.

I was missing one or two things in my xorg.conf so the display was not totally stable (glitches in the sync). With a new mode line: 'Modeline "1600x1200-reduced-blank" 130.25 1600 1648 1680 1760 1200 1203 1207 1235 +hsync -vsync' and possibly the option 'Option "ExactModeTimingsDVI" "yes"' for the nvidia driver, it now seems that the display is glitch-free. I found there is another thread about reduced blanking on DVI in this forum: http://www.nvnews.net/vbulletin/showthread.php?t=52052
The VESA xls was helpful.

Haven't tried it on 10.1 yet. I suspect that the problem I saw on 10.1 was caused by a combination of an USB mouse and what appears to be somewhat flaky USB on my MOBO. I have now converted to PS/2 mouse.
v9400-user is offline   Reply With Quote
Reply


Thread Tools

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 On
HTML code is Off
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
ARCTIC Accelero Xtreme III review (w/ Asus GTX680 DirectCU II TOP) News Archived News Items 1 07-01-12 03:39 PM
Review of the 23-inch Asus VG23AH Passive 3D IPS Display News Archived News Items 0 06-21-12 07:40 PM
Asus ditches Android for Windows 8 in new Transformer laptop/tablet News Archived News Items 0 06-04-12 02:10 PM
ASUS GeForce GTX 670 DirectCU II Top Unveiled Features 1137MHz Boost Clock (WCCFTECH) News GeForce GTX 670 Reviews 0 05-10-12 06:30 AM

All times are GMT -5. The time now is 03:54 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.